The aggregation use case is used to measure the performance of an integration solution that splits an incoming XML message into 4 messages, and then performs a four message aggregation using the Aggregation nodes that are supplied with IBM Integration Bus. For example, this scenario represents the type of processing that is required when travel is booked, and arrangements for a flight, hotel, car and money must be made. Requests to four different applications are made and the replies are consolidated into a single reply.

The Aggregation use case demonstrates a simple four-way aggregation operation, using the AggregateControl, AggregateRequest, and AggregateReply nodes. It contains three message flows to implement a four-way aggregation:

Results per platform

Results for the aggregation use case can be found for each platform here:


FanOut message flow

This flow takes the incoming request message, generates four different request messages, sends them out on request/reply, and starts the tracking of the aggregation operation.

Back to top


RequestReplyApp message flow

This flow is used to simulate the back-end service applications that typically processes the request messages from the aggregation operation.

Back to top


FanIn message flow

This flow receives all the replies from the RequestReplyApp flow, and aggregates them into a single output message. The output message from the AggregateReply node cannot be output directly by an MQOutput node without some processing so a Compute node is added to process the data into a format where it can be written to a queue.

Back to top

Join The Discussion

Your email address will not be published. Required fields are marked *