Managing messaging with a third-party non-JCA messaging provider
You can configure WebSphere® Application Server to use a third-party non-JCA messaging provider. You might want to do this, for example, if you have existing investments. You can configure any third-party non-JCA messaging provider that supports the JMS Version 1.1 unified connection factory.
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 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 Version 1.1 specification.
About this task
To administer a third-party non-JCA messaging provider, you use the client that is supplied by the third party. You use the administrative console to administer the connection factories and destinations that are within WebSphere Application Server, but you cannot use the administrative console to administer the JMS provider itself, or any of its resources that are outside of WebSphere Application Server.
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.