WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with a third-party messaging provider

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

We 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 we have existing investments.

Before beginning

For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, we can use the default messaging provider. To integrate WAS messaging into a predominately WebSphere MQ network, we can use the WebSphere MQ messaging provider. We 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 Choose a messaging provider. A third-party JCA 1.5-compliant or 1.6-compliant messaging provider takes the form of a resource adapter that you install in WAS. Use dmgr console to administer the activation specifications (for message-driven beans) and other J2C administered objects for the provider.

• Install the third-party JCA 1.5-compliant or 1.6-compliant messaging provider.

  Install the resource adapter for the third-party provider, as described in Install a resource adapter archive.

• Configure an activation specification for a third-party JCA resource adapter.
• Configure an administered object for a third-party JCA resource adapter.

Subtopics

• Configure an activation specification for a third-party JCA resource adapter
  We can configure an activation specification used to deploy message-driven beans with a Java™ Connector Architecture (JCA), also called J2EE Connector (J2C), resource adapter not included as part of the WAS.
• Configure an administered object for a third-party JCA resource adapter
  We can configure an administered object for a Java™ Connector Architecture (JCA), also called J2EE Connector (J2C), resource adapter not included as part of the WAS.

Related

Manage messaging with a third-party non-JCA messaging provider

+

Search Tips   |   Advanced Search