You need to consider how the JMS message structure is mapped onto a WebSphere MQ message if you want to transmit messages between JMS applications and traditional WebSphere MQ applications. This includes scenarios where you want to use WebSphere MQ to manipulate messages transmitted between two JMS applications; for example, using WebSphere MQ as a message broker.

By default, JMS messages held on WebSphere MQ queues use an MQRFH2 header to hold some of the JMS message header information. Many traditional WebSphere MQ applications cannot process messages with these headers, and require their own characteristic headers, for example the MQCIH for CICS Bridge, or MQWIH for WebSphere MQ Workflow applications. For more information about how the JMS message structure is mapped onto an WebSphere MQ message, see the section "Mapping JMS to a native WebSphere MQ application" in the chapter "JMS Messages" of the WebSphere MQ Using Java book.

Related tasks
Programming to use JMS and messaging directly
Programming to use message-driven beans

Related reference
JMS interfaces

Related information
Programming