Choosing a broker

 

WebSphere MQ offers the following choice of brokers:

• WebSphere MQ Publish/Subscribe

• WebSphere MQ Integrator, V2 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 Publish/Subscribe broker; and native mode, which provides additional functionality. WebSphere MQ JMS can connect to WebSphere MQ Integrator in native mode with JMS V5.2.1 and later. With earlier JMS versions, it can connect to WebSphere MQ Integrator in compatibility mode only.

  Note, however, that broker based subscription stores are not supported by WebSphere MQ Integrator. For more information about subscription stores, see Subscription stores.

• WebSphere MQ Event Broker, V2.1, WebSphere Business Integration Event Broker, V5.0, and WebSphere Business Integration Message Broker, V5.0 each provide a broker that can be connected to in two different ways:

  Using message queues and WebSphere MQ

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

  Directly using a TCP/IP socket

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

  • Persistent messages

  • Transacted messages

  • Durable subscriptions

  This has implications for the implementation of the JMS specification for direct connections to a broker:

  • Because there are no persistent messages, JMSDeliveryMode is always NON_PERSISTENT, and JMSExpiration has no meaning for messages received on direct connections.

  • Because there are no transacted messages, JMSRedelivered has no meaning for messages received on direct connections.

For specific information on each publish and subscribe interface, see Package com.ibm.mq.jms.

uj24620_