Managing messaging with a third-party messaging provider
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.
Before you begin
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
To administer a third-party messaging provider, you use either the resource adaptor (for a Java EE Connector Architecture (JCA) 1.5-compliant or 1.6-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 or 1.6-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: