Configuring the storage of events for Resequence nodes
You can use a Resequence configurable service to control the storage of events for Resequence nodes.
About this task
Information about the state of in-flight messages is held on storage queues that are controlled by WebSphere® MQ, so you must install it on the same computer as your integration node if you want to use the capabilities provided by the Resequence node. The storage queues that hold the state information are owned by the queue manager that is associated with the integration node, and you specify this queue manager by using the -q property of the mqsicreatebroker command; see mqsicreatebroker command.
If the integration node has the necessary permissions to create the default system queues, they are created automatically when a flow containing Resequence nodes is deployed. If the default queues are not created automatically, you can create them manually; see Creating the default IBM Integration Bus queues on a WebSphere MQ queue manager.
- SYSTEM.BROKER.EDA.EVENTS
- SYSTEM.BROKER.EDA.COLLECTIONS
These queues are also used by the Collector node.
However, you can control the queues that are used by different Resequence nodes by creating alternative queues that contain a QueuePrefix variable, and by using a Resequence configurable service to specify the names of those queues for storing events.
Follow these steps to specify the queues that are used to store event states, and to set the timeout and the start and end of the sequence: