Managing messaging with the IBM MQ messaging provider

Through the IBM MQ messaging provider in WebSphere® Application Server, Java™ Message Service (JMS) messaging applications can use your IBM MQ system as an external provider of JMS messaging resources. To enable this approach, you configure the IBM MQ messaging provider in WebSphere Application Server to define JMS resources for connecting to any queue manager on the IBM MQ network.

Before you begin

If your business uses IBM MQ, and you want to integrate WebSphere Application Server messaging applications into a predominantly IBM MQ network, the IBM 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 requirements, see Choosing messaging providers for a mixed environment.

About this task

The IBM 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 IBM MQ resources for applications (for example queue connection factories) and to manage messages and subscriptions associated with JMS destinations. You administer security through IBM MQ.

You can use WebSphere Application Server to coordinate global transactions including IBM MQ without configuring the extended transactional client.

In a mixed-version WebSphere Application Server cell, you can administer IBM MQ resources on nodes of all versions. However, some properties are not available on all versions. In this situation, only the properties of that particular node are displayed in the administrative console.

For publish and subscribe messaging with IBM MQ as an external JMS messaging provider you have several options:
  • [z/OS]With IBM MQ Version 6 on z/OS®, you can use a separate message broker product.
  • With IBM MQ Version 6 on distributed platforms, you can use either a separate message broker product, or the built-in publish and subscribe capability of IBM MQ.
  • With IBM MQ Version 7 or later on any platform you can use the built-in publish and subscribe capability of IBM MQ. Note that you cannot use WebSphere Message Broker Version 7 or later for this because it no longer provides a publish and subscribe capability.

Procedure


指出主題類型的圖示 作業主題



時間戳記圖示 前次更新: July 9, 2016 11:16
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=tmm_ep
檔名:tmm_ep.html