WAS v8.5 > WebSphere applications > Messaging resourcesInteroperation with WebSphere MQ
We can enable JMS interaction with a WebSphere MQ network using the WebSphere MQ messaging provider. Service integration can also provide interoperation through a WebSphere MQ link or a WebSphere MQ server. Each type of connectivity is designed for different situations, and provides different advantages.
- For a comparison of the different ways of interoperating, see Interoperation with WebSphere MQ: Comparison of architectures and Interoperation with WebSphere MQ: Comparison of key features.
- If you are not familiar with WebSphere MQ concepts, see Interoperation with WebSphere MQ: Key WebSphere MQ concepts.
- To understand about using WebSphere MQ as an external JMS messaging provider, see Interoperation using the WebSphere MQ messaging provider.
- To understand how best to develop the applications for interoperating with a WebSphere MQ network, see How messages are passed between service integration and a WebSphere MQ network.
- To understand the WebSphere MQ link solution, see Interoperation using a WebSphere MQ link.
- To understand the WebSphere MQ server solution, see Interoperation using a WebSphere MQ server.
For more information about WebSphere MQ, see the WebSphere MQ library.
When a WAS process or an application client process starts, and while this process is running, an amount of processing is performed to allow it to support WebSphere MQ-related functionality such as the WebSphere MQ messaging provider. By default this processing is performed regardless of whether any WebSphere MQ-related functionality is ever used. If we do not need to take advantage of any WebSphere MQ functionality, it is possible to disable all WebSphere MQ functionality in an application server or client process to give increased performance. For more information, see Disable WebSphere MQ functionality in WAS.
Subtopics
- Comparison of WAS and WebSphere MQ messaging
If you are not already an established user of either WAS or WebSphere MQ, and you are considering whether the service integration platform or WebSphere MQ better meets your messaging needs, use this table to compare the main features of the two platforms.- Interoperation with WebSphere MQ: Comparison of architectures
The three different ways that we can send messages between WAS and a WebSphere MQ network are compared at a high level, showing the relative advantages and disadvantages of each approach.- Interoperation with WebSphere MQ: Comparison of key features
There are three different ways that we can send messages between WAS and a WebSphere MQ network. This topic compares the key features of each of the three ways.- Interoperation with WebSphere MQ: Key WebSphere MQ concepts
If you are not familiar with basic WebSphere MQ concepts, read about the objects in WebSphere MQ that are important for interoperation with WAS.- Interoperation using the WebSphere MQ messaging provider
Through the WebSphere MQ messaging provider in WAS, JMS messaging applications can use your WebSphere MQ system as an external provider of JMS messaging resources.- How messages are passed between service integration and a WebSphere MQ network
When you program a WAS application that interoperates with WebSphere MQ through the default messaging provider and a service integration bus, service integration automatically handles most aspects of the conversion and mapping for messages. Understanding how this process works and the differences between the two environments helps you to program and troubleshoot the applications more effectively.- Interoperation using a WebSphere MQ link
A WebSphere MQ link provides a server to server channel connection between a service integration bus and a WebSphere MQ queue manager or queue-sharing group, which acts as the gateway to the WebSphere MQ network.- Interoperation using a WebSphere MQ server
A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS) queue-sharing group. Service integration can communicate directly with a WebSphere MQ queue manager or queue sharing group where a WebSphere MQ queue is located. We can configure a service integration queue-type destination to add messages directly onto the WebSphere MQ queue, and retrieve messages directly from the queue.
Related
Disable WebSphere MQ functionality in WAS
Related information: