Installing Server Access for J2EE

As part of the IBM WebSphere InterChange Server installation, InterChange Server Installer installs the files in the directories shown in Table 6. These directory paths are relative to the InterChange Server product directory.

Table 6. Installed file structure for Server Access for J2EE

Directory Description
DevelopmentKits\J2EE\ ResourceAdapter Contains the CCI implementation

Server Access for J2EE is packaged into a single Resource Adapter Archive (RAR) file, called CWResourceAdapter.rar. This RAR file contains the following files:

  • CWResourceAdapter.jar file
  • Deployment descriptor: META-INF/ra.xml
  • IBM WebSphere Server Access Interface libraries
DevelopmentKits\J2EE\ ResourceAdapter\samples Contains source code for the sample EJB client

Using IBM WebSphere InterChange Server Installer

To install Server Access for J2EE, run ICS Installer and select options as follows:

When InterChange Server Installer installs Server Access for J2EE, it copies to the machine the contents of the directories listed in Table 6. For information on InterChange Server Installer, see the System Installation Guide for Windows or for UNIX.

Deploying the WebSphere Access Resource Adapter

The following sections describe how Server Access for J2EE is deployed in each of the environments that the J2EE Connector Architecture specification 1.0. defines.

Note:
For information about deploying Server Access for J2EE in a particular WebSphere business integration system-certified application server, see "Deploying the resource adapter".

In a managed environment

In a managed environment, Server Access for J2EE can be used in either of the following ways:

The Server Access for J2EE RAR file (CWResourceAdapter.rar) contains the deployment descriptor, ra.xml. The deployment descriptor contains a <connector> element, which is the root element of the deployment descriptor. This <connector> element contains information about the Access Resource Adapter. All general information is represented in string format.

Table 7 shows the elements in the deployment descriptor of the WebSphere Access Resource Adapter.

Table 7. Contents of the WebSphere Access Resource Adapter deployment descriptor

Deployment descriptor element Description
<display-name> Name of the resource adapter
<vendor-name> Name of the vendor who provides the resource adapter
<spec-version> Version of the J2EE Connector Architecture specification that is supported by the resource adapter
<version> Version of the resource adapter
<resourceadapter> Marks the beginning of the subsection within the <connector> element that provides information specific to the implementation of the resource-adapter library
<managedconnectionfactory-class> The fully qualified name of the Java class that implements the ManagedConnectionFactory interface:javax.resource.spi.Managed-ConnectionFactory
<connectionfactory-interface> The fully qualified name of the Java class that implements the ConnectionFactory interface:javax.resource.cci.ConnectionFactory
<connectionfactory-impl-class> The actual implementation of the ConnectionFactory interface
<connection-interface> The fully qualified name of the Java class that implements the Connection interface
<connection-impl-class> The actual implementation of the Connection interface
<transaction-support> Because IBM WebSphere InterChange Server Access for J2EE does not support transaction management in this release, this value is set to:NoTransaction
<config-property> These configuration properties provide connection information for each connection request to ICS. For more information, see Configuring Server Access for J2EE.

Note:
The ra.xml deployment descriptor is consistent with the XML DTD for the resource adapter, as specified in the J2EE Connector Architecture specification 1.0..

Figure 7 shows a sample deployment descriptor of the Access Resource Adapter, which is contained in the ra.xml file. You do not usually need to edit this file. Most application servers provide tools that provide access to the deployment descriptor.

Figure 7. WebSphere Access Resource Adapter deployment descriptor

<connector>
  <display-name>Resource Adapter for CrossWorlds</display-name> 
  <vendor-name>CrossWorlds Software, Inc.</vendor-name> 
  <spec-version>1.0</spec-version> 
  <eis-type /> 
  <version>1.0</version> 
 
  <resourceadapter> 
    <managedconnectionfactory-class>
      com.crossworlds.j2eeconnector.CwManagedConnectionFactory
      </managedconnectionfactory-class> 
    <connectionfactory-interface>
      javax.resource.cci.ConnectionFactory
      </connectionfactory-interface> 
    <connectionfactory-impl-class>
      com.crossworlds.j2eeconnector.CwConnectionFactory
      </connectionfactory-impl-class> 
    <connection-interface>javax.resource.cci.Connection</connection-interface> 
    <connection-impl-class>
      com.crossworlds.j2eeconnector.CwConnection
      </connection-impl-class> 
    <transaction-support>NoTransaction</transaction-support> 
    <config-property> 
      <config-property-name>IorFilename</config-property-name> 
      <config-property-type>java.lang.String</config-property-type> 
      <config-property-value>crossworlds.ior</config-property-value> 
      </config-property> 
    <config-property> 
      <config-property-name>MaxConnections</config-property-name> 
      <config-property-type>java.lang.Integer</config-property-type> 
      <config-property-value>100</config-property-value> 
      </config-property> 
    <config-property> 
      <config-property-name>UserName</config-property-name> 
      <config-property-type>java.lang.String</config-property-type> 
      <config-property-value>admin</config-property-value> 
      </config-property> 
    <config-property> 
      <config-property-name>UserPassword</config-property-name> 
      <config-property-type>java.lang.String</config-property-type> 
      <config-property-value>null</config-property-value> 
      </config-property> 
    <authentication-mechanism> 
      <authentication-mechanism-type>
        BasicPassword
        </authentication-mechanism-type> 
      <credential-interface>
        javax.resource.security.PasswordCredential
        </credential-interface> 
      </authentication-mechanism> 
    <reauthentication-support>false</reauthentication-support> 
  </resourceadapter> 
</connector>

Important:
The WebSphere Access Resource Adapter deployment descriptor in Figure 7 has been formatted differently from the actual ra.xml file. In this version, carriage returns have been inserted into the text to improve readability. These carriage returns do not appear in the actual deployment descriptor. Consult the actual ra.xml file on your system for the most accurate and most current version of this file.

In a non-managed environment

In a non-managed environment, the application developer must define the deployment mechanism. This developer must define a deployment environment and tool to handle deployment of all resource adapters. This deployment tool can use the deployment descriptor that InterChange Server provides in the CWResourceAdapter.rar file.

Copyright IBM Corp. 1997, 2004