Configuring timeout flows

Use the TimeoutControl and TimeoutNotification nodes in message flows to process timeout requests or to generate timeout notifications at specified intervals.

Information about the state of in-flight messages is held on storage queues that are controlled by IBM® MQ. If you are using timeout flows 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 the TimeoutControl and TimeoutNotification nodes. If you are using these 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.

The system queues that hold the state information are owned by the queue manager that is specified on the integration server. You associate a queue manager with the integration server by specifying the queue manager name on the defaultQueueManager property in the server.conf.yaml configuration file; for more information, see Configuring an integration server by modifying the server.conf.yaml file.

You must create the system queues by running a script command, as described in Creating the default system queues on an IBM MQ queue manager.

For more information about using IBM MQ with IBM App Connect Enterprise, see Interaction between IBM App Connect Enterprise and IBM MQ and Installing IBM MQ.