Managing messaging with a third-party JCA 1.5 or 1.6-compliant messaging provider

You can configure WebSphere® Application Server to use a third-party JCA 1.5-compliant or 1.6-compliant messaging provider. You might want to do this, for example, if you have existing investments.

Before you begin

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 predominately WebSphere MQ network, you can use the WebSphere MQ messaging provider. You can also use a third-party messaging provider as described in this topic.

About this task

A third-party JCA 1.5-compliant or 1.6-compliant messaging provider takes the form of a resource adapter that you install in WebSphere Application Server. You use the administrative console to administer the activation specifications (for message-driven beans) and other J2C administered objects for the provider.

In a mixed-version WebSphere Application Server deployment manager cell, you can administer third-party messaging resources on Version 8, Version 7 and Version 6 nodes.

Procedure