WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging providerUse JMS from a third party application server to interoperate with service integration resources
The Resource Adapter for JMS with WebSphere Application Server provides first class connectivity to service integration resources from the third party application server on which it is deployed.
The Resource Adapter for JMS with WAS is designed to be deployed into third party application servers, that is, into non-WAS application servers, that support JCA 1. 5 and are J2EE 1.4 compliant. The stand-alone resource adapter provides these third party application servers with full connectivity to service integration resources running inside WAS v6.0.2 and later.
Supported third party application servers are:
- WAS Community Edition v2.0 and later
- Apache Geronimo v2.0 and later
- JBoss Application Server v4.0.5 and later
Restriction:
- The resource adapter does not support the unmanaged JCA environment. In an unmanaged environment use the Thin Client for JMS with WAS.
- To use XA connections to a WAS v6.0.2 application server, contact IBM Support to obtain a required service update.
Subtopics
- Deploy the Resource Adapter for JMS with WAS to a third party application server
To provide connections to service integration resources running inside WAS, the Resource Adapter for JMS with WAS must be installed into the third party application server.- Deploy inbound connections for the Resource Adapter for JMS with WAS
When deploying inbound connections, configure message-driven beans to use the Resource Adapter for JMS with WAS. A JMS activation configuration associated with one or more message-driven beans provides the configuration necessary for them to receive messages.
Subtopics
- Deploy the Resource Adapter for JMS with WAS to a third party application server
To provide connections to service integration resources running inside WAS, the Resource Adapter for JMS with WAS must be installed into the third party application server.- Deploy inbound connections for the Resource Adapter for JMS with WAS
When deploying inbound connections, configure message-driven beans to use the Resource Adapter for JMS with WAS. A JMS activation configuration associated with one or more message-driven beans provides the configuration necessary for them to receive messages.
Related
Secure JMS client and JMS resource adapter connections
Add tracing and logging for stand-alone clients