You might find it useful to design a fan-out flow with multiple AggregateControl nodes, all with the same value set for the property Aggregate Name, but with different values for the Timeout property. This is the only situation in which you can reuse an Aggregate Name.
Before you start:
To complete this task, you must have completed the following task:
For example, if you have created an aggregation flow that books a business trip, you might have some requests that need a reply within two days, but other, more urgent requests, that need a reply within two hours.
To configure an aggregation flow that uses multiple AggregateControl nodes:
You must connect the two AggregateControl nodes in parallel, not in sequence. This means that you must connect both to the Filter node (one to the true terminal, one to the false), and both to the downstream nodes that handle the requests for the fan-out. Each input message must pass through only one of the AggregateControl nodes. If you connect the nodes such that a single message is processed by more than one AggregateControl node, duplicate records are created in the database by the AggregateRequest node and subsequent processing results are unpredictable.
The following diagram shows an example fan-out message flow that uses this technique.
Related concepts
Message flows
Message flow aggregation
Related tasks
Configuring aggregation flows
Creating the aggregation fan-out flow
Creating the aggregation fan-in flow
Associating fan-out and fan-in aggregation flows
Setting timeouts for aggregation
Handling exceptions and database deadlocks in aggregation flows
Designing a message flow
Creating a message flow
Defining message flow content
Related reference
AggregateControl node
AggregateReply node
AggregateRequest node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac12330_ |