Use IBM MQ and WebSphere Application Server together

Through the IBM MQ messaging provider in WebSphere Application Server, Java Message Service (JMS) messaging applications can use your IBM MQ system as an external provider of JMS messaging resources.

About this task

Applications that are written in Java that are running under WebSphere Application Server can use the Java Messaging Service (JMS) specification to perform messaging. Messaging in this environment can be provided by an IBM MQ queue manager.

A benefit of using an IBM MQ queue manager is that connecting JMS applications can participate fully in the functionality of an IBM MQ network, which allows the applications to exchange messages with queue managers that are running on a multitude of platforms.

Applications can use either the client transport or bindings transport for the queue connection factory object. For bindings transport, the queue manager must exist locally to the application that requires a connection.

By default, JMS messages that are held on IBM MQ queues use an MQRFH2 header to hold some of the JMS message header information. Many legacy IBM MQ applications cannot process messages with these headers, and require their own characteristic headers, for example the MQCIH for CICS® Bridge, or MQWIH for IBM MQ Workflow applications. For more information about these special considerations, see Mapping JMS messages onto IBM MQ messages.