WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Using more than one input node
You can include more than one input node in a single message flow.
Before you start:
Read the following
concept topic:
You might find this useful in the following situations:
- The message flow provides common processing for messages that
are received from multiple transports. For example, a single message
flow might handle:
- Data in messages received from WebSphere® MQ, and therefore through a WebSphere MQ queue and an MQInput node
- Messages that are received from native IP connections (a Real-timeInput node)
- You need to set standard properties on the MQInput node if input messages:
- are predefined, and
- are all received from WebSphere MQ, and
- do not include an MQRFH2 header.
This requirement is not necessary for self-defining messages.
- Each input node in a message flow causes the broker to start a
separate thread of execution. Including more than one input node might
improve the message flow performance. However, if you include multiple
input nodes that access the same input source (for example, a WebSphere MQ queue), the order in which the
messages are processed cannot be guaranteed. If you want the message
flow to process messages in the order in which they are received,
this option is not appropriate.
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.
Look at the following sample :
This sample uses two input nodes: an MQInput node and a Real-timeInput node. You can
use these two input nodes to enable the sample's message flow to accept
input from both WebSphere MQ
transport and native IP connections. You can view information about samples only when
you use the information center that is integrated with the WebSphere Message Broker Toolkit or the online information
center. You can run samples only when you use the information center
that is integrated with the WebSphere Message Broker Toolkit.