Managing messaging with the WebSphere MQ messaging provider

Through this messaging provider, Java Message Service (JMS) messaging applications can use your WebSphere MQ system as an external provider of JMS messaging resources.

Before you begin

If your business uses WebSphere MQ, and you want to integrate WebSphere Application Server messaging applications into a predominately WebSphere MQ network, the WebSphere MQ messaging provider is the natural 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.

About this task

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.

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 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.

For publish and subscribe messaging with WebSphere MQ as an external JMS messaging provider you have several options:
  • [z/OS] With WebSphere MQ Version 6 on z/OS, you can use a message broker such as WebSphere MQ Event Broker.
  • With WebSphere MQ Version 6 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 Version 7 for this because it no longer provides a publish and subscribe capability.

To use WebSphere MQ as a messaging provider for WebSphere Application Server, complete one or more of the following steps.

Procedure




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=tmm_ep
File name: tmm_ep.html