This topic describes the AggregateControl node.
This topic contains the following sections:
Use the AggregateControl node to mark the beginning of a fan-out of requests that are part of an aggregation.
Aggregation is an extension of the request/reply application model. It combines the generation and fan-out of a number of related requests with the fan-in of the corresponding replies, and compiles those replies into a single aggregated reply message.
The aggregation function is provided by the following three nodes:
The AggregateControl node is contained in the Routing drawer of the palette, and is represented in the workbench by the following icon:
When you have put an instance of the AggregateControl node into a message flow, you can configure it; see Configuring a message flow node. The properties of the node are displayed in the Properties view.
All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.
This node creates the LocalEnvironment.ComIbmAggregateControlNode folder. This folder and the fields within it are for internal use by WebSphere Message Broker and you should not rely on their existence or values when developing your message flows.
The following steps describe how to configure the AggregateControl node:
The AggregateControl node terminals are described in the following table.
Terminal | Description |
---|---|
In | The input terminal that accepts a message for processing by the node. |
Out | The output terminal to which the original message is routed when processing completes successfully. |
Control | The output terminal to which a control message is routed.
The control message is sent to a corresponding AggregateReply node. The Control terminal is deprecated in Version 6.0; to use connections from the Control terminal, see Using control messages in aggregation flows. |
The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the bar file to deploy it).
The AggregateControl node Description properties are described in the following table:
Property | M | C | Default | Description |
---|---|---|---|---|
Node name | No | No | The node type | The name of the node. |
Short Description | No | No | A brief description of the node. | |
Long Description | No | No | Text that describes the purpose of the node in the message flow. |
The AggregateControl node Basic properties are described in the following table:
Property | M | C | Default | Description |
---|---|---|---|---|
Aggregate Name | Yes | Yes | A name that used to associate the fan-out message flow with the fan-in message flow. | |
Timeout (sec) | Yes | No | 0 | The amount of time, in seconds, that it waits for replies
to arrive at the fan-in.
|