Configuring Resource Adapter Deployment

If you select Configure Resource Adapter Deployment on the Deployment Information page of the J2C wizard, you can use the Resource Adapter Deployment page to configure RAR.

Before you begin

The resource adapter can be deployed as a standalone resource adapter or as part of an EAR file. Typical environments use the standalone method, so that all modules on the application server are visible to the adapter.

About this task

Important: Do not install multiple resource adapters as standalone on the same runtime server, especially if they are for the same EIS type (for example, CICS® ECI 5.1 and CICS ECI 6.2). All standalone resource adapters share the same class loader.

Procedure

  1. On the Resource Adapter Deployment page, select either Deploy as a Stand Alone or Deploy within EAR
    • Deploy as a Stand Alone: If you deploy the resource adapter as a standalone adapter, then it is visible to all EAR applications deployed on that server. Specify the server you want to deploy to or click New to create a server.
      Note: If you are deploying on WebSphere® Application Server V.7,, the following situation occurs:

      Before WebSphere Application Server, V.7, if the resource adapters were installed on the server in standalone mode, the single classloader was used to load the classes of these resource adapters. That created classloader problems when different adapter versions were installed on the server. WebSphere Application Server, V.7 introduced isolated classloader option for RARs installed on the server in standalone mode. If this option is enabled, separated classloaders is used for separated RARs installed on the server. This allows to resolve the potential classloader issues. However, the RAR files are visible only to the application that uses the RAR file if the managed connection option is used AND a corresponding resource reference exists. Since managed connection plus existence of resource reference is considered to be recommended approach for J2C application, our code installs RAR on WebSphere Application Server, V.7 with the isolate classloader option enabled by default.

      Therefore, if you have a non-managed J2C application or a managed plus no-resource-ref J2C application deployed on the server, you have to disable the isolate classloader option through WebSphere Application Server administration console to test your applications.

    • Deploy within EAR: If you select to deploy the resource adapter within the selected EAR file, the resource adapter is only visible to that specific EAR file.
  2. Click Finish.

Feedback