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 non-JCA messaging provider

We can configure WebSphere Application Server to use a third-party non-JCA messaging provider. You might want to do this, for example, if we have existing investments. We can configure any third-party non-JCA messaging provider that supports the JMS v1.1 unified connection factory.


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.

To work with message-driven beans, the third-party non-JCA messaging provider must include Application Server Facility (ASF), an optional feature that is part of the JMS v1.1 specification. To administer a third-party non-JCA messaging provider, we use the client supplied by the third party. Use dmgr console to administer the connection factories and destinations that are within WAS, but we cannot use the dmgr console to administer the JMS provider itself, or any of its resources that are outside of WAS.


Subtopics


Related


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


+

Search Tips   |   Advanced Search