JMS support in IBM WAS Network Deployment V5.1

 

J2EE 1.3 supports JMS which includes two types of messaging:

  1. point-to-point
  2. publish/subscribe

Message-driven beans (MDBs) use these services. The WebSphere Embedded JMS server of WebSphere V5 supports all messaging functions as described in J2EE 1.3.

In addition to the WebSphere Embedded JMS server, which is included in WebSphere V5.1, you can also use the full WebSphere MQ product. WebSphere MQ supports more functions than Embedded JMS, such as queue manager clustering. WebSphere MQ needs to be purchased separately.

Depending on your needs, you will configure the appropriate JMS provider.

  • Embedded WebSphere JMS provider
  • External WebSphere MQ JMS provider
  • Other generic JMS providers

    The following is a high-level description of the configuration steps needed:

    1. First, set the scope to cell to make sure that clustered WASs on several hosts can access the same source of messaging.

      The cell scope must be chosen for appservers to share Embedded JMS messages in WebSphere Network Deployment V5

    2. Next, you need to configure the Connection Factories and destinations for your queues or topic. Define the location of your JMS servers (host and port).

    3. In order for MDBs to use the defined JMS provider, you need to specify the Message Listener Service in the Additional Properties of your appservers.

    4. The last step is to define MDB listener ports in the Additional Properties of the Message Listener Service. When you assemble/install your MDBs, you need to use these listener ports. Set the initial state to Started to make sure the listener ports are also started when your appserver is started.

    The Embedded JMS server can be administered (on the Deployment Manager server) through scripting or the Administrative Console. The figure below shows the basic WebSphere Network Deployment configuration using the WebSphere Embedded JMS server.

    When the JMS server (queue manager) fails, no appserver can access messages available for processing, and application clients cannot put messages into the queue. Therefore, the JMS server becomes an SPOF for IBM WAS Network Deployment V5.1.

    There are four approaches to handling WebSphere JMS SPOF:

    1. Use hardware-software clustering for WebSphere Embedded JMS server.

    2. Use hardware-software clustering for WebSphere MQSeries® server.

    3. Use WebSphere MQ built-in queue manager clustering.

    4. Use a combination of hardware/software clustering and WebSphere MQ built-in queue manager clustering for best availability and scalability.

    Approach 1 provides highly available IBM WAS Network Deployment V5.1 messaging. Approach 2 provides highly available WebSphere messaging, plus it is interoperable with non-JMS applications. Approach 3 provides scalable WebSphere messaging but messages in failed local queues may experience indefinite delays until the failed queue managers are restarted, so the timely processing of messages cannot be ensured. Approach 4 eliminates this problem and ensures that WebSphere messaging is highly available and scalable for time-critical applications.

      Prev | Home | Next

     

    WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

     

    IBM is a trademark of the IBM Corporation in the United States, other countries, or both.