WebSphere Application Server Network Deployment, Version 6.1
             Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

             Personalize the table of contents and search results

Managing messaging with a third-party or V5 default messaging provider

For messaging between application servers, most requirements are best met by either the default messaging provider or MQ messaging provider. However, you can instead use a 3rd party messaging provider (that is, use another company's product as the provider). For backwards compatibility with earlier releases, there is also support for the Version 5 default messaging provider.

Before you begin

If you are not sure which provider combination is best suited to your needs, see Types of messaging provider.

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.

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. Choose the 3rd party messaging provider.
    The generic messaging provider supports the JMS Version 1.1 unified connection factory and allows you to use 3rd party JMS providers, for example because of existing investments.
    Note:
    • To administer 3rd party JMS providers, use the resource adaptor or client supplied by the 3rd 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), 3rd party JMS providers must include Application Server Facility (ASF), an optional feature which is part of the JMS Version 1.1 specification, or use an inbound resource adapter that conforms to the J2EE Connector Architecture (JCA) Version 1.5 specification.
    To work with a 3rd party provider, see Managing messaging with a 3rd party messaging provider.
  2. 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


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

This feature requires Internet access.

IBM Suggests
Task topic    

Terms of Use | Feedback

Last updated: Feb 25, 2009 9:32:38 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/tm_other.html