ReceiveCustomerChanges service

The receiveCustomerChanges service accepts changes made to customers in the external system and commits them to Sterling™ Order Management System Software. This service is triggered as soon as an update or change to an customer is made.

The following figure illustrates a process flow for the receiveCustomerChanges service:

Receive Customer Change Servicer

The following table explains more about the receiveCustomerChanges service:

Table 1. ReceiveCustomerChanges service
Step Description
1. Generic JMS queue The Generic JMS queue stores messages until they can continue through the service.
Note: When configuring the sendCustomerChanges service, the URL for both the JMS Sender and JMS Receiver must be manually configured. The queue name for both must also be set to CustomerSyncQueue.
2. Make receiveCustomerChanges 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.
3. receiveCustomerChanges API The receiveCustomerChanges API accepts the item XML from the external system and invokes the functionality of the manageItem API.