Using message collections

If you want to use message collections on an integration server that is managed by an integration node, you must install IBM MQ on the same computer as your integration node. 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 the iib_createqueues command, as described in Creating the default system queues on an IBM MQ queue manager.

If you want to use message collections with 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 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 topics in this section describe how message collection works, and explain how you can configure your message flow to process message collections.

• Message collections
• Creating a message collection by using ESQL
• Creating a message collection by using Java
• Creating a flow that uses message collections
• Configuring the Collector node
• Using control messages with the Collector node
• Configuring the storage of events for Collector nodes