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.
The general approach to deploying the resource adapter is to write a deployment XML file to configure the required and optional properties for the JMS connection factory and JMS resources that will be accessed, and then deploy the resource adapter by using the deployment XML file. The installation process varies, depending on the particular application server that you are using. Before starting this task, see the documentation specific to your application server for information about how to install and use a JMS resource adapter RAR file.
An enterprise application that looks up a Resource Adapter for JMS with WebSphere Application Server connection factory in the local Java Naming and Directory Interface (JNDI) repository can access service integration resources through the resource adapter, provided that the required messaging engine is available in WebSphere Application Server. All outbound connections must access all queues and topics by using Queue or Topic resources. These resources are configured using your particular application server configuration mechanism when the resource adapter is deployed.
The Resource Adapter for JMS with WebSphere Application Server supports full two-phase XA transactional connections (except under the JBoss Application Server) but can also be run using local transactions or no transaction connections.
Multiple deployments of the resource adapter are possible.
You can turn trace and First Failure Data Capture (FFDC) on for the resource adapter in the same way as for the Thin Client for JMS with WebSphere Application Server . For further information, see Adding tracing and logging for stand-alone clients.
You can configure secure connections by configuring connection factories that require a secure bootstrap and/or connection transport chain in the same way as for the Thin Client for JMS with WebSphere Application Server . For further information, see Securing JMS client and JMS resource adapter connections.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |