Using aggregation

If you want to use aggregation 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 aggregation 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 following topics describe the benefits of message flow aggregation, and explain how to configure your message flows to support message aggregation:

• Message flow aggregation
• Configuring aggregation flows