The aggregation fan-in flow receives the responses to the request messages sent out by the fan-out flow and constructs a combined response message containing all the responses received.
Before you start:
To complete this task, you must have completed the following task:
You are also advised to read the overview about Message flow aggregation, before completing this task.Depending on whether the fan-out flow is transactional
and, if not,
the timeout values that you have specified, the combined
response message might be generated before all the replies have been received
by the fan-in flow.
See, Creating the aggregation fan-out flow for
more information on this topic.
To review an example of a fan-in flow, see the Airline sample that is supplied with WebSphere Business Integration Message Broker.
To create the fan-in flow:
The AggregateReply node creates a folder in the combined message tree below Root, called ComIbmAggregateReplyBody. Below this, it creates a number of folders using the folder names that you set in the AggregateRequest nodes. The associated reply messages are put beneath them.
For example, the request messages might have folder names:
The resulting aggregated reply message created by the AggregateReply node might have a structure similar to that shown below:
You can use a Compute node to access the reply from the taxi company using the following correlation name:
InputRoot.ComIbmAggregateReplyBody.TAXI.xyz
The folder name does not have to be unique. If you have multiple requests with the folder name TAXI, you can access the separate replies using the array subscript notation, for example:
InputRoot.ComIbmAggregateReplyBody.TAXI[1].xyz InputRoot.ComIbmAggregateReplyBody.TAXI[2].xyz
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac12300_ |