For messaging between application servers, most requirements
are best met by either the default messaging provider or the WebSphere® MQ messaging provider. However,
you can instead use a third-party messaging provider (that is, use
another company's product as the provider). You might want to do this, for example, if you have existing investments. For backwards
compatibility with earlier releases, there is also support for the
V5 default 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
- Choose a third-party messaging provider.
To administer a third-party messaging provider, you use either the resource adaptor (for a Java EE Connector Architecture (JCA) 1.5-compliant messaging provider) or the client (for a non-JCA messaging provider) that is supplied by the third party. You use the WebSphere Application Server administrative console to administer the activation specifications, 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, third-party messaging providers must either provide an inbound JCA 1.5-compliant resource adapter, or (for non-JCA messaging providers) include Application Server Facility (ASF), an optional feature that is part of the JMS Version 1.1 specification.
To work
with a third-party provider, choose one of the following options:
- Manage messaging
with a third-party JCA 1.5-compliant messaging provider.
- Manage
messaging with a third-party non-JCA messaging provider.
- Choose the (deprecated) V5 default messaging provider.
This deprecated 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 or later 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 or later resources in a mixed cell. To configure and manage
messaging to interoperate with WebSphere Application
Server Version 5, see Maintaining (deprecated) Version 5 default messaging resources.