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

You can configure WebSphere® Application Server to use a third-party JCA 1.5-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. To choose the provider that is best suited to your needs, see Choosing a messaging provider.

About this task

A third-party JCA 1.5-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 7, Version 6 and Version 5 nodes. For Version 5 nodes, the administrative console presents the subset of resources and properties that are applicable to WebSphere Application Server Version 5.

Procedure




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 Task topic    

Terms of Use | Feedback

Last updatedLast updated: Sep 19, 2011 3:08:41 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=tmp_ep_ra
File name: tmp_ep_ra.html