IBM MQ messaging provider
Through the IBM MQ messaging provider in WebSphere Application Server, Java Message Service (JMS) messaging applications can use the IBM MQ system as an external provider of JMS messaging resources. To enable this approach, we configure the IBM MQ messaging provider in WAS to define JMS resources for connecting to any queue manager on the IBM MQ network.
If our business uses IBM MQ, and we want to integrate WAS messaging applications into a predominantly IBM MQ network, the IBM MQ messaging provider is a logical choice. However, there can be benefits in using another provider. If we are not sure which provider combination is best suited to your requirements, see Choosing messaging providers for a mixed environment.
The IBM MQ messaging provider supports JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces), and also supports the Java EE Connector Architecture (JCA) 1.5 activation specification mechanism for message-driven beans (MDBs) across all platforms supported by WAS.
Use WAS to configure IBM MQ resources for applications (for example queue connection factories) and to manage messages and subscriptions associated with JMS destinations. You administer security through IBM MQ.
Use WAS to coordinate global transactions including IBM MQ without configuring the extended transactional client.
In a mixed-version WAS cell, we can administer IBM MQ resources on nodes of all versions. However, some properties are not available on all versions. In this situation, only the properties of that particular node are displayed in the administrative console.
For publish and subscribe messaging with IBM MQ as an external JMS messaging provider we have several options:
- With IBM MQ Version 6 on z/OS, we can use a separate message broker product.
- With IBM MQ Version 6 on distributed platforms, we can use either a separate message broker product, or the built-in publish and subscribe capability of IBM MQ.
- With IBM MQ v7 or later on any platform we can use the built-in publish and subscribe capability of IBM MQ. Note that we cannot use WebSphere Message Broker v7 or later for this because it no longer provides a publish and subscribe capability.
Tasks
- Learn about the IBM MQ messaging provider.
- Configure JMS resources for the IBM MQ messaging provider with the console.
- Configure JMS resources for the IBM MQ messaging provider using administrative commands
- List JMS resources for the IBM MQ messaging provider.
Subtopics
- Install IBM MQ to interoperate with WAS
- Configure properties for the IBM MQ resource adapter
- Disable IBM MQ functionality in WAS
Related:
Introduction: Messaging resources Interoperation with IBM MQ Interoperation using the IBM MQ messaging provider Choose a messaging provider Programming to use asynchronous messaging JMS provider settings WMQAdminCommands Mapping of administrative console panel names to command names and IBM MQ names