Deploying 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.

Before you begin

The Resource Adapter for JMS with WebSphere Application Server requires JRE 1.5 or later. The resource adapter is called sibc.jmsra.rar and is available from the following runtime directories:
  • WebSphere Application Server install
  • Application Client for WebSphere Application Server install
Before starting the deployment of the resource adapter, you must first obtain the following information from the WebSphere Application Server administrator:
  • Bus name
  • Endpoint provider address
  • Target transport chain
  • Messaging engine name
  • Any other required connection and destination properties
  • One or more destination names

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.

About this task

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.

Procedure

  1. To deploy an outbound JMS resource on the Resource Adapter for JMS with WebSphere Application Server, use your particular application server configuration mechanism to configure the following service integration bus properties:
    • Bus name
    • Provider endpoints
  2. If you want to use XA resources over a Resource Adapter for JMS with WebSphere Application Server connection, use your particular application server configuration mechanism to configure the following additional service integration bus properties:
    • Target type must be set to "ME"
    • Target significance must be set to "Required"
    • Target must be set to the name of the required messaging engine
    These properties permit the recovery of indoubt transactions, should this be necessary. For further information about indoubt transactions, see Resolving indoubt transactions.

    See Configuration properties for the Resource Adapter for JMS with WebSphere Application Server for a description of these property names and other properties that might also be configured.

Results

Subsequent usage of the resource adapter is in accordance with the Java EE programming specifications. That is, any enterprise bean or message-driven bean might obtain a Resource Adapter for JMS with WebSphere Application Server connection factory or use an activation specification to connect to a service integration messaging engine. Message-driven beans behave in just the same way as they would in any other Java EE environment.

What to do next

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.

Task topic    

Terms and conditions for information centers | Feedback

Last updated: April 17, 2014 10:32 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=tjj_sibra_deploy
File name: tjj_sibra_deploy.html