When you design and configure message flows that support aggregation, there are some restrictions on the protocols that can be used by participating client applications:
WebSphere Business Integration Message Broker provides the following protocols and input and output nodes to support the request/reply model:
The following transport protocols do not support a request/reply model:
If you choose to create user-defined nodes, and use an alternative transport protocol, the protocol you use must meet the following criteria for input and output nodes to support aggregation requests and responses:
The protocol-specific output node must:
The field Protocol must be an unambiguous name describing the transport. In the supplied MQOutput node, Protocol is MQ. In the supplied MQeOutput node, Protocol is MQe.
For each destination that the message is sent to, there must be a folder called DestinationData. The only field underneath this required by aggregation is called ReplyIdentifier. You can include additional information if you choose. For WebSphere MQ, this field contains the MsgId from the MQMD.
If you are writing your own plug-in node, you can put whatever information is useful and relevant underneath the DestinationData folder. For example, the MQOutput node includes the queue name and queue manager name.
The information that is contained beneath WrittenDestination is valid only for the last output node that delivered the message. For example, if you connect two MQOutput nodes in series, the WrittenDestination relates only to the second node.
The protocol-specific input node must:
When you write user-defined nodes, you can override these properties by navigating to the Properties folder and using cniCreateElementAsFirstChild() or equivalent. Ensure that the value used for the Protocol is consistent and is unique for the protocol.
Related concepts
Message flows
LocalEnvironment tree
Message flow aggregation
Related tasks
Designing a message flow
Creating a message flow
Defining message flow content
Configuring aggregation flows
Configuring ESQL within nodes
Related reference
AggregateControl node
AggregateReply node
AggregateRequest node
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac12350_ |