WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resourcesManage messaging with the WebSphere MQ messaging provider
WebSphere MQ can be used as an external provider of JMS messaging resources. To enable, configure the WebSphere MQ messaging provider to define JMS resources for connecting to queue managers on the MQ network. We can use WAS to configure MQ resources for applications (for example queue connection factories) and to manage messages and subscriptions associated with JMS destinations. You administer security through MQ. We can use WAS to coordinate global transactions including MQ without configuring the extended transactional client. The preferred solution for publish and subscribe messaging with MQ as an external JMS messaging provider is to use a message broker such as WebSphere MQ Event Broker.
WebSphere MQ messaging provider supports...
- JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces)
- Java EE Connector Architecture (JCA) 1.5 activation specification mechanism for message-driven beans
Subtopics
- 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
- Disable WebSphere MQ functionality in WAS
- Learn about
- Choose messaging providers for a mixed environment.
Related :
Introduction: Messaging resources
Interoperation with WebSphere MQ
Interoperation using the WebSphere MQ messaging provider
Choose a messaging provider
Programming to use asynchronous messaging
JMS provider settings
WMQAdminCommands command group for AdminTask
Map of dmgr console panel names to command names and WebSphere MQ names