Associate the fan-out message flow processing with its corresponding fan-in message flow processing by setting the Aggregate Name property of the AggregateControl and AggregateReply nodes in your aggregation flow to the same value. If you did not configure this property whilst creating your fan-in and fan-out flows you must complete this task.
Before you start:
To complete this task, you must have completed the following tasks:
The Aggregate Name must be contextually unique within a broker. In general, this means that there should only be one AggregateControl node and one AggregateReply node with a particular Aggregate Name, although it is possible to have more than one AggregateControl node with the same Aggregate Name, as described in Using multiple AggregateControl nodes. It is not advisable to deploy a fan-in flow to multiple execution groups on the same broker.
You can either create the fan-out and fan-in flows in the same message flow, or in two different message flows. In either case, the two parts of the aggregation are associated by setting the Aggregate Name property.
The way in which you configure your aggregation flow depends on a number of factors:
A single flow is easier to implement for a simple case, but there are some limitations to this approach, and, in most cases, you will find that the flexibility offered by two message flows is preferable. The sampleAirline Reservations sample shows the use of two flows for aggregation.
The advantages of creating separate fan-out and fan-in flows are:
To associate the fan-out flow with the fan-in flow:
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac12311_ |