Through the WebSphere® MQ messaging provider in WebSphere Application Server, Java™ Message Service (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 WebSphere Application Server to define JMS resources for connecting to any queue manager on the WebSphere MQ network.
If your business uses WebSphere MQ, and you want 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 you are not sure which provider combination is best suited to your needs, 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 WebSphere Application Server.
You 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.
You can use WebSphere Application Server to coordinate global transactions including WebSphere MQ without configuring the extended transactional client.
In this information ...Subtopics
Related concepts
Related tasks
Related information
| IBM Redbooks, demos, education, and more(Index) |