Manage messaging with the WebSphere MQ messaging provider
Through the WebSphere MQ messaging provider in WebSphere Application Server, Java Message Service (JMS) messaging applications can use the WebSphere MQ system as an external provider of JMS messaging resources. To enable this approach, you configure the WebSphere MQ messaging provider in WebSphere Application Server to define JMS resources for connecting to any queue manager on the WebSphere MQ network.
If the business uses WebSphere MQ, and to integrate WebSphere Application Server messaging applications into a predominantly WebSphere MQ network, the WebSphere 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 the requirements, see Choose messaging providers for a mixed environment.
The WebSphere 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 WebSphere Application Server.
We can use WebSphere Application Server to configure WebSphere MQ resources for applications (for example queue connection factories) and to manage messages and subscriptions associated with JMS destinations. You administer security through WebSphere MQ.
We can use WebSphere Application Server to coordinate global transactions including WebSphere MQ without configuring the extended transactional client.
In a mixed-version WAS cell, we can administer WebSphere 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 WebSphere MQ as an external JMS messaging provider we have several options:
- (zos) With WebSphere MQ Version 6 on z/OS , we can use a separate message broker product.
- With WebSphere MQ Version 6 on distributed platforms, we can use either a separate message broker product, or the built-in publish and subscribe capability of WebSphere MQ.
- With WebSphere MQ Version 7 or later on any platform we can use the built-in publish and subscribe capability of WebSphere MQ. Note that we cannot use WebSphere Message Broker Version 7 or later for this because it no longer provides a publish and subscribe capability.
- Learn about the WebSphere MQ messaging provider.
- Configure JMS resources for the WebSphere MQ messaging provider.
We can do this through the WAS administrative console, or through the WAS set of WebSphere MQ administrative commands.
- List JMS resources for the WebSphere MQ messaging provider.
Subtopics
- Install WebSphere MQ to interoperate with WebSphere Application Server
When you install a new WebSphere MQ network, we can tune the installation for working with WebSphere Application Server. If we have an established WebSphere MQ network, we can choose whether to modify some of the settings for better interoperation.
- Listing JMS resources for the WebSphere MQ messaging provider
Use the WAS administrative console to list JMS resources for the WebSphere MQ provider, for administrative purposes.
- Configure JMS resources for the WebSphere MQ messaging provider
Use the WAS administrative console to configure activation specifications, connection factories and destinations for the WebSphere MQ JMS provider.
- Configure properties for the WebSphere MQ resource adapter
We can configure the WebSphere MQ resource adapter properties that affect the connection pool, which is used by WebSphere MQ messaging provider activation specifications.
- Disable WebSphere MQ functionality in WebSphere Application Server
If we do not need to use WebSphere MQ functionality in an application server we can disable it by using either the administrative console or an administrative command. We can also disable WebSphere MQ functionality in a client process by specifying a custom property.
Related concepts
Introduction: Messaging resources Interoperation with WebSphere MQ Interoperation using the WebSphere MQ messaging provider
Related tasks
Choose a messaging provider Programming to use asynchronous messaging Choose a messaging provider
JMS provider settings WMQAdminCommands (AdminTask) Mapping of administrative console panel names to command names and WebSphere MQ names