Migrating a broker for use with aggregation nodes

This topic describes how to migrate a broker for use with aggregation nodes that use WebSphere MQ to store state. The aggregation nodes need new queues to be created to store aggregation information. If you create a new broker, the queues are created automatically. If you are using an existing broker, perform the following steps:

Windows, Linux, and UNIX:

  1. Stop the broker by issuing the mqsistop command.
  2. Migrate the queues by issuing the mqsimigratequeues command.
  3. Start the broker by issuing the mqsistart.
z/OS:
  1. Stop the broker.
  2. Re-run the mqsicustomize command.
  3. Re-run the queue creation JCL (BIP$MQ01).
  4. Start the broker.
Related concepts
Message flows overview
Message flow aggregation
Related tasks
Using WebSphere MQ to store state in aggregation nodes
Configuring a broker environment to use WebSphere MQ for aggregation nodes
Configuring a broker environment to send control messages
Configuring aggregation flows
Developing message flows
Designing a message flow
Creating a message flow
Defining message flow content
Related reference
mqsistop command
mqsistart command
AggregateControl node
AggregateReply node
AggregateRequest node