
PACreateMetaphorBatchCmd scheduler command
This scheduler command creates a Product Exploration metaphor, Product Comparison metaphor, or a Guided Sell metaphor for a category based on the input XML file provided.
Parameter values
- xmlFileName
- Required: The name of the input XML
file with the fully qualified path. The XML file must exist
on the machine where you have installed WebSphere Commerce. For example,
WCDE_installdir\samples\pa\xml\PE_PC_GS_60001.xml
Behavior
- Deletes a metaphor for the category if any one of the following
XML tags are present in the input XML file:
- delete_productComparer
- delete_productExplorer
- delete_salesAssistant
- Creates metaphors that are defined in the input XML file.
- Deletes an existing Product Exploration metaphor, Product Comparison metaphor, or a Guided Sell, and then recreates the metaphor based on the input XML file provided.
- Populates the following database tables when a Product Exploration
metaphor or Product Comparison metaphor is created:
- ICMETAFEAT
- ICMETAPHOR
- ICFEATPROP
- Populates the following database tables when a Guided Sell is
created:
- ICMETAPHOR
- ICMETAPROP
- ICCNCPTLNK
- ICCONSTRNT
- ICCONSTVAL
- ICKNOWDESC
- ICKNOWLEDG
- ICMERDESC
- ICMERTREE
- ICMREGDESC
- Creates a inputXMLName_timestamp.log log
file in the following directory:
WC_installdir \instances\ instance_name \logs.
WC_userdir \instances\ instance_name \logs.
Exception conditions
- If the search space for a category does not exist, then the command throws the ECApplicationException exception.
- If the input parameter is wrong, then the command throws the ECApplicationException exception.
- If the file name provided for the xmlFileName parameter is not valid, then the command throws the ECApplicationException exception.
- If the elements defined in the XML input file do not correspond to the DTD, then the command throws the ECApplicationException exception.
If a non root user runs the WebSphere Commerce instance but does not have the relevant read permissions for the input XML file, then the command fails.
If the instance user profile does not have the permissions to access the file, the command will fail.