To ensure that the integration points between Sterling Selling and Fulfillment Foundation Sterling Application Platform and other systems that are using JMS messaging queues are working properly, the number of messages in the queues should be monitored.
If the messages in the queue are not being processed quickly enough or not at all, then something is wrong at the integration point. If the problem at this integration point is not resolved quickly, then more problems are sure to happen somewhere further along in the process.
The number of messages for the JMS queues being monitored are recorded during every persist interval. Note that this statistic is only recorded for JMS queues that are actually being monitored. For information about how to monitor a JMS queue, see Monitor group details screen.
The JMS queue monitor retrieves data every 10 minutes. For information about monitoring more real-time data for your JMS queues, see the documentation provided by your JMS server software vendor.
It is possible to configure a service to be run if the number of messages in a JMS queue goes above a threshold limit. This service can do anything at all including sending an e-mail message or creating an alert for a system administrator. For more information about the data available for the service, see Data published for health monitor alerts.
There is no default value for the number of messages threshold limit. This threshold must be specified when adding a JMS queue to monitor. For more information, see Monitor group details screen.