IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Associating fan-out and fan-in aggregation flows

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 when you created your fan-in and fan-out flows, you must complete this task.

Before you start:

You must have completed the following tasks:

The Aggregate Name must be contextually unique within a broker. You can have only one AggregateControl node and one AggregateReply node with a particular Aggregate Name, although you can have more than one AggregateControl node with the same Aggregate Name, see Using multiple AggregateControl nodes. Do not deploy a fan-in flow to multiple integration servers on the same broker; results are unpredictable.

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 when you set the Aggregate Name property.

How you configure your aggregation flow depends on a number of factors:

The design of your message flow.
The hardware on which the broker is running.
The timeout values that you choose, see Setting timeout values for aggregation.
How you expect to maintain the message flows.

You can include the fan-out and fan-in flow within the same message flow. However, you might prefer to create two separate flows. The advantages of creating separate fan-out and fan-in flows are:

You can modify the two flows independently.
You can start and stop the two flows independently.
You can deploy the two flows to separate integration servers to take advantage of multiprocessor systems, or to provide data segregation for security or integrity purposes.
You can allocate different numbers of additional threads to the two flows, as appropriate, to maintain a suitable processing ratio.

The following sample shows the use of two flows for aggregation:

Airline Reservations

You can view information about samples only when you use the product documentation that is integrated with the IBM® Integration Toolkit or the online product documentation. You can run samples only when you use the product documentation that is integrated with the IBM Integration Toolkit.

To associate the fan-out flow with the fan-in flow:

Switch to the Integration Development perspective.
Open the message flow that contains your fan-out flow.
Select the AggregateControl node to open the Properties view. The node properties are displayed.
Set the Aggregate Name property of the AggregateControl node to identify this aggregation. The Aggregate Name that you specify must be contextually unique within a broker.
If you have separate fan-out and fan-in flows:
1. Press Ctrl-S or click File > Save name on the taskbar menu (where name is the name of this message flow) to save the message flow and validate its configuration.
2. Open the message flow that contains your fan-in flow.
Select the AggregateControl node to open the Properties view. The node properties are displayed.
Set the Aggregate Name property of the AggregateReply node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl node in the fan-out flow.
Press Ctrl-S or click File > Save name to save the message flow and validate its configuration.

In IBM Integration Bus, fan-out and fan-in flows were also associated by sending control messages from the AggregateControl node to the AggregateReply node. This facility is no longer available. For optimum performance, do not connect the AggregateControl and AggregateReply node. However, if you do want to use control messages in your aggregations, and you want to connect these two nodes, see Using control messages in aggregation flows.

ac12311_.htm |

Last updated Friday, 21 July 2017