Through this messaging provider, Java Message Service (JMS) messaging applications can use your WebSphere MQ system as an external provider of JMS messaging resources.
The WebSphere MQ messaging provider supports JMS 1.1 domain-independent interfaces (sometimes referred to as "unified" or "common" interfaces). This enables applications to use the same interfaces for both point-to-point and publish/subscribe messaging, and also enables both point-to-point and publish/subscribe messaging within the same transaction. With JMS 1.1, this approach is recommended for new applications. The domain-specific interfaces are supported for backwards compatibility for applications developed to use domain-specific queue interfaces, as described in section 1.5 of the JMS 1.1 specification.
The WebSphere MQ messaging provider also supports the J2EE Connector Architecture (JCA) version 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.
In a mixed-version WebSphere Application Server cell, you can administer WebSphere MQ resources on nodes of all versions. However, some properties are not available on all versions. In this situation, the administrative console displays only the properties of that particular node.
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.
To use WebSphere MQ as a messaging provider for WebSphere Application Server, complete one or more of the following steps:
In this information ...Subtopics
| IBM Redbooks, demos, education, and more |