Deploy template files
Use this information to identify, rename, and deploy sample template files.
About this task
To support integration, Sterling Order Management contains the following sample template files, which need to be renamed as non-sample :
- Events:
- DRAFT_ORDER_CONFIRM.ON_SUCCESS.xml.sample
- ORDER_CHANGE.ON_CANCEL.xml.sample
- ORDER_CHANGE.ON_SUCCESS.xml.sample
- ORDER_CREATE.ON_SUCCESS.xml.sample
- REALTIME_ATP_MONITOR.REALTIME_AVAILABILITY_CHANGE.xml.sample
- REALTIME_ATP_MONITOR.REALTIME_AVAILABILITY_CHANGE_LIST.xml.sample
- CHANGE_ORDER.ON_DELETE.xml.sample
- ORDER_CHANGE.DELETE_ORDER.xml.sample
- User exits:
- getOrderPrice.xml.sample
- getItemPrice.xml.sample
- getPricingRuleDetails.xml.sample
- validateCoupon.xml.sample
- APIs
- findInventory.xml.sample
- getOrderLineDetails.xml.sample
- monitorItemAvailability.xml.sample
- getCompleteOrderDetails.xml.sample
- getOrderList.xml.sample
- reserveAvailableInventory.xml.sample
Procedure
- Copy event templates from <INSTALL_DIR>/repository/scwc_integration/template/event into <INSTALL_DIR>/extensions/global/template/event and rename as non-sample xml files. If this target directory does not exist, create it.
- Copy user exit templates from <INSTALL_DIR>/repository/scwc_integration/template/userexit into <INSTALL_DIR>/extensions/global/template/userexit and rename as non-sample xml files.
- Copy API templates from <INSTALL_DIR>/repository/scwc_integration/template/api into <INSTALL_DIR>/extensions/global/template/api and rename as non-sample xml files.
- Rebuild the resources.jar and rebuild the ear.
- Redeploy the ear and restart the Sterling Order Management server.
- OPTIONAL: If the Extn element is added to an event template, declare the element by adding the following to the Sterling Order Management schema files that are located on the Sterling side:
<xsd:element name="Extn" type="myType" maxOccurs="1" minOccurs="0" />
where
myType is an attribute. No child element can be added.