Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources
Manage messaging with 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.
To enable this approach, you configure the WebSphere MQ messaging provider in WAS to define JMS resources for connecting to any queue manager on the WebSphere MQ network.
If your business uses WebSphere MQ, and to integrate WAS 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 you are not sure which provider combination is best suited to your requirements, see Choosing messaging providers for a mixed environment.
The preferred solution for publish and subscribe messaging with WebSphere MQ as an external JMS messaging provider is to use a message broker such as WebSphere MQ Event Broker.
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 WAS.
We can use WAS 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 WAS to coordinate global transactions including WebSphere MQ without configuring the extended transactional client.
In a mixed-version WAS cell, you 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:
- With WebSphere MQ v6 on distributed platforms, you can use either a message broker such as WebSphere MQ Message Broker or the built-in publish and subscribe capability of WebSphere MQ.
- With WebSphere MQ Version 7 on any platform you can use the built-in publish and subscribe capability of WebSphere MQ. Note that you cannot use WebSphere MQ Message Broker v7 for this because it no longer provides a publish and subscribe capability.
Procedure
- 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.
Related
JMS provider settingsNew feature: Resource adapter properties
Install WebSphere MQ to interoperate with WAS
List JMS resources for the WebSphere MQ messaging provider
Configure JMS resources for the WebSphere MQ messaging provider
Configure properties for the WebSphere MQ resource adapter
WMQAdminCommands command group
Map of administrative console panel names to command names and WebSphere MQ names
Interoperation with WebSphere MQ
Interoperation using the WebSphere MQ messaging provider
Introduction: Messaging resources
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Manage message-driven beans
Secure messaging
Tune messaging
Troubleshoot messaging
Program to use asynchronous messaging
Manage messaging with the default messaging provider
Choosing a messaging provider