Message queues in Sterling Order Management System Software

Sterling™ Order Management System Software uses message queues extensively.

Message queue usage in Sterling Order Management System Software can be characterized as:

Integration queues for external communications
Temporary work-in-progress queues for Sterling Order Management System Software and custom time-triggered transactions

These queues can be implemented in:

IBM® MQ
IBM WebSphere® default messaging providers
Oracle WebLogic JMS
TIBCO EMS

The agent and integration servers use messaging primarily for two reasons:

Integration queues
Agent work queues

The failover and load balancing capabilities of JMS clustering provide high availability for message queues. IBM supports different JMS cluster implementations, depending on the application server and whether the JMS cluster is used for integration services or agents. For more information about JMS clustering, refer to High availability using JMS clustering.

Note: The agent and integration servers use messaging primarily for two reasons. Uses JNDI to look up the QCF in order to get a connection to a queue. For this reason, two single points of failure can occur: JMS and JNDI. To achieve a truly fault-tolerant environment, JNDI entries for the QCF and queues should be deployed to a cluster of servers. Ideally, the servers should be running on different hosts.