Choosing a messaging provider

For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, you can use the default messaging provider. To integrate WebSphere Application Server messaging into a predominantly WebSphere MQ network, you can use the WebSphere MQ messaging provider. You can also use other providers (a 3rd party messaging provider or, for backwards compatibility with earlier releases, the V5 default messaging provider). To choose the provider that is best suited to your needs, consider what the application needs to do, and the business need for the provider to integrate well with your enterprise infrastructure.

About this task

Enterprise applications in WebSphere Application Server can use asynchronous messaging through services based on Java Message Service (JMS) messaging providers and their related messaging systems. These messaging providers conform to the JMS Version 1.1 specification.

You can configure any of the following messaging providers:

The types of messaging provider that can be configured in WebSphere Application Server are not mutually exclusive:

No one of these providers is necessarily better than another. The choice of provider depends on what your JMS application needs to do, and on other factors relating to your business environment and planned changes to that environment.

Procedure

  1. Determine the environment and application requirements.

    If you have to use a third-party messaging provider, or interoperate with WebSphere Application Server Version 5 resources, use the associated provider. For more information, see Managing messaging with a third-party or V5 default messaging provider.

    If your existing or planned messaging environment involves both WebSphere MQ and WebSphere Application Server systems, and it is not clear to you whether you should use the default messaging provider, the WebSphere MQ messaging provider or a mixture of the two, complete the task Choosing messaging providers for a mixed environment.

  2. Choose the messaging provider:
    • Choose the default messaging provider.

      If you mainly want to use messaging between applications in WebSphere Application Server, perhaps with some interaction with a WebSphere MQ system, the default messaging provider is the natural choice because this provider is fully integrated with the WebSphere Application Server runtime. For more information, see Default messaging provider. To configure and manage messaging with the default messaging provider, see Managing messaging with the default messaging provider.

    • Choose the WebSphere MQ messaging provider.

      If your business also uses WebSphere MQ, and you want to integrate WebSphere Application Server messaging applications into a predominately WebSphere MQ network, the WebSphere MQ messaging provider allows you to define resources for connecting directly to the queues in a WebSphere MQ system. For more information, see WebSphere MQ messaging provider. To configure and manage messaging with the WebSphere MQ messaging provider, see Managing messaging with the WebSphere MQ messaging provider.

    • Choose a third-party messaging provider.
      You can use any third-party messaging provider that supports the JMS Version 1.1 unified connection factory. You might want to do this, for example, because of existing investments.
      Notes:
      • To administer a third-party messaging provider, use the resource adaptor or client supplied by the third party. You can still use the WebSphere Application Server administrative console to administer the JMS connection factories and destinations that are within WebSphere Application Server, but you cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WebSphere Application Server.
      • To use message-driven beans (MDBs), third-party messaging providers must include Application Server Facility (ASF), an optional feature that is part of the JMS Version 1.1 specification, or use an inbound resource adapter that conforms to the Java™ EE Connector Architecture (JCA) Version 1.5 specification.
      To work with a third-party provider, see Managing messaging with a third-party JCA 1.5-compliant messaging provider or Managing messaging with a third-party non-JCA messaging provider.
    • Choose the V5 default messaging provider.

      This provider is identical to the WebSphere Application Server Version 5 default provider. Only the name has changed. It provides backwards compatibility that enables WebSphere Application Server Version 6 applications to connect to WebSphere Application Server Version 5 resources in a mixed cell. It also allows WebSphere Application Server Version 5 applications to connect to WebSphere Application Server Version 6 resources in a mixed cell. To configure and manage messaging to interoperate with WebSphere Application Server Version 5, see Maintaining Version 5 default messaging resources.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 11:08:29 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-mp&topic=tm_ep
File name: tm_ep.html