InfoCenter Home >
4: Developing applications >
4.6: Java Technologies >
4.6.3: Java Message Service (JMS) overview >
4.6.3.2: Using the JMS publish/subscribe messaging approach

4.6.3.2: Using the JMS publish/subscribe messaging approach

This article describes the "publish/subscribe" messaging approach using WebSphere Application Server's default JMS provider, MQSeries. You can implement the "publish/subscribe" messaging approach in MQSeries with the Pub-Sub SupportPac or with Integrator.

To alleviate the complexity of a multiple queue manager topology, MQSeries introduced the concept of Message Brokers with the MQSeries Integrator product. The following graphic illustrates five queue managers configured to use a Message Broker:

publish and subscribe messaging topology

In addition to the Message Broker, the Integrator product also supports a Message Repository Manager, and the publish and subscribe messaging approach. With this approach, the Message Broker matches a topic on a published message with a list of clients who have subscribed to that topic. Neither publisher nor subscriber is aware of each other. Publishers only know of the topics they describe for their messages, and subscribers only know of the topics they requested.

In this topology, WebSphere Application Server can be a publisher or subscriber, or both, but requires the configuration and resource support of the MQSeries Integrator product.

Visit the MQSeries Integrator site for more information.

Note for SuSE Linux users: The message broker never completes starting for the WebSphere Application Server MQSeries implementation on SuSE Linux 7.2.

When you issue the strmqbrk -m command, it never completes. Also, the command cannot be interrupted with CRL-C. If you check the status of the message broker with the dspmqbrk command, the result is similar to:

MQSeries message broker for queue manager <Queue Manager> starting.

SuSE Linux 7.2 by default does not have the group ID nobody, which is required by MQSeries. If you experience the problem as described, halt all MQSeries processes and create the group ID nobody. Then you can start the message broker.

Go to previous article: Using the JMS point-to-point messaging approach Go to next article: Support of Java Message Service resources

 

 
Go to previous article: Using the JMS point-to-point messaging approach Go to next article: Support of Java Message Service resources