Interoperation with IBM MQ

You can enable JMS interaction with an IBM MQ network by using the IBM MQ messaging provider. Service integration can also provide interoperation through an IBM MQ link or an IBM MQ server.

Note: The interoperation through IBM MQ server (queue manager or queue-sharing group) is deprecated in WebSphere® Application Server version 9. As an alternative method, you can use IBM MQ resource adapter or IBM MQ link to connect to the IBM MQ network for interoperation.

Each type of connectivity for interoperation is designed for different situations, and provides different advantages.

For a comparison of the different ways of interoperating, see Interoperation with IBM MQ: Comparison of architectures and Interoperation with IBM MQ: Comparison of key features.
If you are not familiar with IBM MQ concepts, see Interoperation with IBM MQ: Key IBM MQ concepts.
To understand about using IBM MQ as an external JMS messaging provider, see Interoperation using the IBM MQ messaging provider.
To understand how best to develop your applications for interoperating with a IBM MQ network, see How messages are passed between service integration and an IBM MQ network.
To understand the IBM MQ link solution, see Interoperation using an IBM MQ link.
To understand the IBM MQ server solution, see Interoperation using an IBM MQ server.

For more information about IBM MQ, see the IBM MQ documentation.

When a WebSphere Application Server process or an application client process starts, and while this process is running, an amount of processing is performed to allow it to support IBM MQ-related functionality such as the IBM MQ messaging provider. By default this processing is performed regardless of whether any IBM MQ-related functionality is ever used. If you do not need to take advantage of any IBM MQ functionality, it is possible to disable all IBM MQ functionality in an application server or client process to give increased performance.