See information about the latest product version
Configuring aggregation flows
Use aggregation message flows to generate and fan-out a number of related requests, fan-in the corresponding replies, and compile those replies into a single aggregated reply message, by using the AggregateControl, AggregateRequest, and AggregateReply nodes.
By default, the messages are put onto a set of default storage queues (beginning SYSTEM.BROKER.AGGR) for processing, but you can use an Aggregation configurable service to specify alternative queues. You can also use the Aggregation configurable service to set a timeout for the aggregation.
For an overview of using aggregation in message flows, see Message flow aggregation.
To configure aggregation flows see the following topics:
- Creating the aggregation fan-out flow
- Creating the aggregation fan-in flow
- Associating fan-out and fan-in aggregation flows
- Setting timeout values for aggregation
- Processing timed out aggregation messages
- Using multiple AggregateControl nodes
- Correlating input request and output response aggregation messages
- Using control messages in aggregation flows
- Handling exceptions in aggregation flows
- Configuring the storage of events for aggregation nodes
You can view information about samples only when you use the information center that is integrated with the WebSphere® Message Broker Toolkit or the online information center. You can run samples only when you use the information center that is integrated with the WebSphere Message Broker Toolkit.