Messaging with WebSphere MQ
Overview
Having JMS applications leverage WebSphere MQ as the external messaging provider allows...
- Using the same interfaces for both point-to-point and publish/subscribe messaging
- Using point-to-point and publish/subscribe messaging within the same transaction
Use WAS to...
- Configure connections to MQ resources such as queue connection factories
- Manage messages and subscriptions associated with JMS destinations
Security is administered through WebSphere MQ.
In a mixed-version WAS cell, we can administer MQ resources on nodes of all versions. However, some properties are not available on all versions. In this situation, the admin console displays only the properties of that particular node.
The WebSphere MQ messaging provider also supports the JCA 1.5 activation spec mechanism for message-driven beans. For publish and subscribe messaging with MQ as an external JMS messaging provider use WebSphere MQ Event Broker.
Use MQ as a messaging provider for WAS
- Review MQ network concepts
- Set JMS resources for MQ using the console or MQ admin commands
- List JMS resources for MQ
Related
Messaging resources
JMS provider settings
WMQAdminCommands
Map of admin console panel names to command names and WebSphere MQ names
Manage messaging with a third-party or V5 default messaging provider
Administer activation specifications and listener ports for message-driven beans
Secure messaging
Tune messaging
Troubleshoot messaging
Program to use asynchronous messaging
Manage messaging with the default messaging provider
Choose a messaging provider