receiveItemChanges service

The receiveItemChanges service accepts changes made to items in the external system and commits them to Sterling™ Order Management System Software, if running in near-real-time mode. If batch mode is used, the service is called after the item synchronization cron job is run.

The following figure shows the process flow of the receiveItemChanges service:

Receive Item Chnages Service

The following table describes the ReceiveItemChanges service:

Table 1. ReceiveItemChanges service
Step Description
1. Generic JMS queue The Generic JMS queue stores messages until they can continue through the service.
Note: When configuring the ReceiveItemChanges service, the Provider URL for the JMS Receiver must be manually configured. The queue name must also be set to ItemSyncReceiveItemChangesQueue.
2. Make receiveItemChanges input from common XML The XSL translation takes the common XML from the external system and removes all synchronization related data as well as transforms the XML into a format that can be read by Sterling Order Management System Software.
Note: By default, items are deleted from Sterling Order Management System Software when a message for deletion is received from the external system. This can be avoided by modifying the XSL translator in this step by changing Action="Delete" to Action="Modify" and placing the item into a custom status.
3. receiveItemChanges API The receiveItemChanges API accepts the item XML from the external system and invokes the functionality of the manageItem API.