Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with a third-party or (deprecated) V5 default messaging provider
Manage messaging with a third-party JCA 1.5-compliant messaging provider
We can configure WAS to use a third-party JCA 1.5-compliant messaging provider. You might want to do this, for example, if we have existing investments. For messaging between application servers, perhaps with some interaction with a WebSphere MQ system, you can use the default messaging provider.
To integrate WAS messaging into a predominately WebSphere MQ network, you 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 Choosing a messaging provider.
A third-party JCA 1.5-compliant messaging provider takes the form of a resource adapter that you install in WAS. You use the admin console to administer the activation specifications (for message-driven beans) and other J2C administered objects for the provider.
In a mixed-version WAS dmgr cell, you can administer third-party messaging resources on v7, v6 and v5 nodes. For v5 nodes, the admin console presents the subset of resources and properties that are applicable to WAS v5.
Procedure
- Install the third-party JCA 1.5-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.
Related
Configure an activation specification for a third-party JCA resource adapter
Configure an administered object for a third-party JCA resource adapter
Manage messaging with a third-party non-JCA messaging provider
Manage messaging with a third-party or (deprecated) V5 default messaging provider