This topic describes how messages are converted as they flow through
the WebSphere MQ link.
Most conversions are automatically carried out and require no action on
your part. However there are some fields and properties that you can choose
to convert or preserve.
The WebSphere MQ link can send to and receive messages from WebSphere MQ
queue managers.
Conversions are performed as follows:
- Application messages received by the WebSphere MQ link from
a WebSphere MQ network are automatically converted into service integration
bus format JMS messages. For details see Mapping of messages flowing through the WebSphere MQ link.
- Messages sent by an application through the WebSphere MQ link to
a WebSphere MQ system are converted either to WebSphere MQ JMS messages that
include an MQRFH2 header, or to non-JMS messages, depending on how the destination
has been configured. For details see Mapping between a WebSphere service integration bus and WebSphere MQ.
- In addition to the conversion of JMS fields and properties, there is a
set of JMS provider-specific properties that reflect a message's underlying
WebSphere MQ representation for WebSphere Application Server applications
that are designed to be WebSphere MQ-aware. For details see Mapping of WebSphere MQ message fields and properties to JMS.
- MQRFH2 header fields which are automatically converted to service integration
bus format JMS fields or properties. For details see Mapping of MQRFH2 header fields to JMS.
- Although in most cases fields from the WebSphere MQ MQMD or MQRFH2 map
one-to-one to individual JMS header fields or properties, the MQMD Report
field options map to fewer JMS provider-specific properties. For details see Mapping of MQMD Report fields to JMS provider-specific properties.
- An additional set of message fields specific to WebSphere Application Server service
integration can convey extra information not used in WebSphere MQ.
These properties can be inserted in the sib folder of the MQRFH2 header of application messages,
and used to influence the routing of messages within the messaging bus.
These properties can be inserted in the sib and jms folders
of the MQRFH2 header of application messages, and used to influence the routing
of messages within the messaging bus.
For details see Mapping of additional MQRFH2 header fields in service integration.
Publications (publish and subscribe messages) are converted in the same
way as point-to-point messages.