Getting started with WebSphere MQ JMS and publish/subscribe

Choosing a broker

WebSphere MQ offers a choice of three brokers:

• The MQSeries Publish/Subscribe broker is a publish/subscribe broker using WebSphere MQ and a SupportPac.

  The SupportPac MA0C is available for download from

  http://www.ibm.com/software/ts/mqseries/txppacs
  

• WebSphere MQ Integrator provides a broker that can be run in one of two modes. Compatibility mode, which provides a broker of equivalent functionality to the WebSphere MQ broker; and native mode, which provides additional functionality. Currently, WebSphere MQ JMS can connect to WebSphere MQ Integrator in compatibilty mode only.
• WebSphere MQ Event Broker provides a broker that can be connected to in two different ways:

  Using message queues and WebSphere MQ

  With this connection, you can run the broker in either compatibility mode or native mode.

  Directly using a TCP/IP socket

  With this connection, you can only run the broker in native mode. Also there is no support for:

  • Persistent messages
  • Transacted messages
  • Durable subscriptions

Setting up the broker to run the WebSphere MQ JMS

Broker setup is dependent on the broker you intend to use and how you intend to use it. Each broker provides its own documentation describing installation and setup. However, for convenience and because of WebSphere MQ JMS requirements, some setup instructions are given here.

Connecting to your broker via WebSphere MQ

This section applies to the MQSeries Publish/Subscribe broker and the broker in WebSphere MQ Integrator. It also applies to the WebSphere MQ Event Broker broker when you choose to connect to it via WebSphere MQ.

Each broker requires its own queue manager. Please refer to the broker's documentation regarding installation and set up.

For the WebSphere MQ JMS publish/subscribe implementation to work correctly, a number of system queues must be created on the queue manager on which the broker is runnning. These message queues must be created on each queue manager for each broker you wish to run WebSphere MQ JMS. WebSphere MQ JMS provides a script that creates these queues (see Create the WebSphere MQ JMS system queues).

Run the script to create the system queues. If you are using the MQSeries Publish/Subscribe broker, your broker is now fully configured. To check that the broker is correctly configured, run the publish/subscribe verification as described in Publish/subscribe verification without JNDI.

If you are using the broker provided by WebSphere MQ Integrator or WebSphere MQ Event Broker, you must configure a publish/subscribe message flow in the broker for messages to be correctly routed. The method for creating the required message flow is similar in both cases. Refer to Appendix D, Connecting with other products for details.

Connecting to your broker directly

This is only possible when you use the broker provided in WebSphere MQ Event Broker. Because the connection to this broker is made directly, no system queues are required. However, you must set up a publish/subscribe message flow in the broker for messages to be correctly routed. Refer to Appendix D, Connecting with other products for details.