sendCustomerChanges service
The sendCustomerChanges service communicates changes made to customers in Sterling Order Management System Software to the external system.
The following figure illustrates a process flow of the sendCustomerChanges service:
The following table describes the sendCustomerChanges service:
| Step | Description |
|---|---|
| 1. Is the customer valid for synching? | If the customer is valid for synchronization, the service continues; if it is not, the service ends. Customers are deemed valid for synchronization if they are a consumer, have a user ID that is not blank, and have an IsSyncRequired flag set to 'Y'. |
| 2. 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.
|
| 3. sendCustomerChangesTOExternalSystem | This service contains modules that provide an
XSL translation to create a common XML file for the customer, and
send the XML to the external system. Note: The Java™ class name for the external
client must be specified in the sendCustomerChangesTOExternalSystem
service's API component.
|
| 4. Is the operation a delete? | If the change being made to the customer is deletion, the service ends. If it is not, the service continues. |
| 5. Make manageCustomer 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. manageCustomer API | The customer XML is passed to the manageCustomer API, which commits the changes to Sterling Order Management System Software. |