Read the concept topic about message flow nodes.
You can include more than one input node in a single message flow. You might find this useful in the following situations:
If you are not concerned about message order, consider using additional instances of the same message flow rather than multiple input nodes. If you set the Additional Instances property of the message flow when you deploy it to the broker, multiple copies of the message flow are started in the execution group. This is the most efficient way of handling multiple instances.
The Scribble sample uses two input nodes: an MQInput node and a Real-timeInput node. This enables the sample's message flow to accept input across both WebSphere MQ transport and native IP connections.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac00360_ |