sendItemChanges service
The sendItemChanges service is used to relay changes made to items in Sterling Order Management System Software to the external system. This service is triggered as soon as an update or change to an item is made.
The following figure shows the process flow of the sendItemChanges service.
The following steps are described in the figure:
| Step | Description |
|---|---|
| 1. Is the item valid for synching? | If the item is valid for synchronization, the service continues; if it is not, the service ends. Items are deemed valid for synchronization if the ItemGroupCode is equal to PROD and the item is not a dynamic physical kit or a logical kit. |
| 2. Generic JMS queue | The Generic JMS queue stores messages until
they can continue through the service. Note: When
configuring the SendItemChanges service, the Provider URL for both
the JMS Sender and JMS Receiver must be manually configured. The queue
name for both must also be set to ItemSyncQueue.
|
| 3. sendItemChangesTOExternalSystem | This service contains modules that provide an
XSL translation to create a common XML file for the item, and send
the XML to the external system. Note: The Java™ class name for the external
client must be specified in the sendItemChangesTOExternalSystem service's
API component.
|
| 4. Is the action a delete? | If the change being made to the item is deletion, the service ends. If it is not, the service continues. |
| 5. Make manageItem input to SyncTS | An XSL translation takes place which adds a
timestamp for when the synchronization took place. Note: SyncTS is the only column change that can occur in this
XSL.
|
| 6. manageItem API | The item XML is passed to the manageItem API which commits the changes to Sterling Order Management System Software. |