Configuring the storage of events for timeout nodes
You can use a Timer policy to control the storage of events for TimeoutNotification and TimeoutControl nodes.
About this task
Information about the state of in-flight messages is held on storage queues that are controlled by IBM® MQ. The storage queues that hold the state information are owned by the queue manager that is associated with the integration server.
If you are using TimeoutControl and TimeoutNotification nodes on an integration server that is managed by an integration node, you must install IBM MQ on the same computer as your integration node in order to use the capabilities that are provided by these nodes. If you are using TimeoutControl and TimeoutNotification nodes on an independent integration server, you can use a remote default queue manager to control the system queues, without the need to install IBM MQ on the same machine as the integration server. Interactions between an independent integration server and IBM MQ can use a client connection to a remote queue manager, by using a default policy setting. For more information about using a remote default queue manager, see Using a remote default queue manager and Configuring an integration server to use a remote default queue manager.
If the integration server has the necessary permissions to create the default system queues, they are created automatically when a flow containing TimeoutControl or TimeoutNotification nodes is deployed. If the default queues are not created automatically, you can create them manually by running the iib_createqueues command, as described in Creating the default system queues on an IBM MQ queue manager.
By default, the storage queue used by all timeout nodes is the SYSTEM.BROKER.TIMEOUT.QUEUE. However, you can control the queues that are used by different timeout nodes by creating alternative queues that contain a QueuePrefix variable, and by using a Timer policy to specify the names of those queues for storing events.
Follow these steps to specify the queue that is used to store event states: