Persistence

You can define queues as being persistent or nonpersistent. Messages in persistent queues are preserved after a restart. Using the same example from above, the same 100 messages are in the queue after a restart

However, messages in nonpersistent queues are lost after the queue is restarted. For example, if you have 100 messages in the queue, all those messages are lost when the WebLogic JMS server or the IBM® MQ queue manager is restarted. .

In general, the following recommendations apply:

• All queues used by the Sterling™ Order Management System Software agent should be defined as nonpersistent. As we described above, the agents can easily recreate the messages if lost.
• All integration queues used for external communications, either for messages coming from external systems to Sterling Order Management System Software or for messages going from Sterling Order Management System Software to external systems, must be defined as persistent. In most cases, recreating integration messages can be difficult especially when the information in two or more systems have to be re-synchronized.