Use 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 WebSphere Application Server is designed to be deployed into third party application servers, that is, into non-WebSphere Application Server application servers, that support Java EE Connector Architecture (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:
- WebSphere Application Server Community Edition Version 2.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 WebSphere Application Server.
- 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 WebSphere Application Server to a third party application server
To provide connections to service integration resources running inside WebSphere Application Server, the Resource Adapter for JMS with WebSphere Application Server must be installed into the third party application server.
- Deploy inbound connections for the Resource Adapter for JMS with WebSphere Application Server
When deploying inbound connections, configure message-driven beans to use the Resource Adapter for JMS with WebSphere Application Server. A JMS activation configuration associated with one or more message-driven beans provides the configuration necessary for them to receive messages.
- Configure high availability for the Resource Adapter for JMS with WebSphere Application Server in a third party application server
For XA connections, the Resource Adapter for JMS with WebSphere Application Server must always connect to the same messaging engine in a bus. High availability is therefore an important consideration.
Subtopics
- Deploy the Resource Adapter for JMS with WebSphere Application Server to a third party application server
To provide connections to service integration resources running inside WebSphere Application Server, the Resource Adapter for JMS with WebSphere Application Server must be installed into the third party application server.
- Deploy inbound connections for the Resource Adapter for JMS with WebSphere Application Server
When deploying inbound connections, configure message-driven beans to use the Resource Adapter for JMS with WebSphere Application Server. A JMS activation configuration associated with one or more message-driven beans provides the configuration necessary for them to receive messages.
- Configure high availability for the Resource Adapter for JMS with WebSphere Application Server in a third party application server
For XA connections, the Resource Adapter for JMS with WebSphere Application Server must always connect to the same messaging engine in a bus. High availability is therefore an important consideration.
Related tasks
Secure JMS client and JMS resource adapter connections Add tracing and logging for stand-alone clients