Nodes to perform a variety of tasks.
- Nodes for collating requests
- Group nodes and aggregation nodes provide alternative ways to collate related requests and responses. Use these nodes to generate several requests in response to one input message, to control and coordinate the responses that are received in response to those requests, and to combine the information that is provided by the responses to continue processing.
- Group nodes: GroupScatter, GroupGather, and GroupComplete.
- Aggregate nodes: AggregateControl, AggregateReply, and AggregateRequest
For more information about these nodes, see Group nodes and aggregation nodes.
- Node for creating message collections
Use the Collector node to generate collections of messages and make multiple synchronous or asynchronous requests in parallel. The Collector node does not need an initial fan-out stage, and can group unrelated input messages by correlating their content. You can configure dynamic input terminals on a Collector node to receive messages from different sources. You can also configure properties on the Collector node, known as event handlers, to determine how messages are added to a message collection, and when a message collection has completed.
- Nodes for controlling the sequence of messages
- Use the Sequence node to apply a sequence number to a message received from an input source, and the Resequence node to change the sequence of messages that contain a sequence number. You can divide messages into sequence groups and use the Sequence and Resequence nodes to control the sequences in groups of messages that arrive at the nodes.
- Nodes for handling and reporting errors
Use the following nodes to affect error handling and reporting:
- Trace node
- Include a Trace node to generate one or more trace entries to record what is happening in the message flow at this point.
- TryCatch node
- Include a TryCatch node to control the error processing when exceptions are thrown.
- Throw node
- Include a Throw node to force an exception to be thrown, and specify the identity of the exception, to make it easier to diagnose the problem.
- Node for invoking the message flow security manager
- Use the SecurityPEP node to invoke the message flow security manager at any point in the message flow between an input node and an output (or request) node. The SecurityPEP node enables you to invoke the security manager even if your input nodes do not support message flow security. You can also use the SecurityPEP node to invoke different aspects of security (for example, authentication and authorization) at different points in the message flow.