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 policy to specify alternative queues. You can also use the Aggregation policy 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: