IBM Integration Bus provides
the following nodes for working with message received from or sent
to
WebSphere MQ applications:
- MQInput node
- Use an MQInput node
if the messages arrive at the broker on a WebSphere MQ queue, and the node is to be
at the start of a message flow.
- MQGet node
- Use an MQGet node to
retrieve a message from a WebSphere MQ queue,
if you want to get the message later in the message flow.
- MQReply node
- Use an MQReply node
if the target application expects to receive messages on the WebSphere MQ reply-to queue that is specified
in the input message MD.
- MQOutput node
- Use an MQOutput node
if the target application expects to receive messages on a WebSphere MQ queue, or on the WebSphere MQ reply-to queue that is specified
in the input message MD.
- MQHeader node
- Use the MQHeader nodes
to manipulate WebSphere MQ transport
headers and their properties without writing compute nodes. Use the MQHeader node to add, modify,
or delete Message Descriptor (MD) and Dead Letter Header (DLH) headers.
- JMSMQTransform node
- Use the JMSMQTransform node
to transform a message with a JMS message tree into a message that
has a tree structure that is compatible with the format of messages
that are produced by the WebSphere MQ JMS
provider.
The JMSMQTransform node
can be used to send messages to existing message flows and to interoperate
with WebSphere MQ JMS and WebSphere MQ Publish/Subscribe.
- MQJMSTransform node
- Use the MQJMSTransform node
to receive messages that have a WebSphere MQ JMS
provider message tree format, and transform them into a format that
is compatible with messages that are to be sent to JMS destinations.
You
can use the MQJMSTransform node
to send messages to existing message flows and to interoperate with WebSphere MQ JMS and WebSphere MQ Publish/Subscribe.
Use the following links to find more information
about configuring your message flows and related resources for handling
messages received from or sent to WebSphere MQ applications:
Last updated Friday, 21 July 2017