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
To install Server Access for J2EE, run ICS Installer and select options as follows:
Expand the Development Kits for J2EE option of Installer, and select the Resource Adapter for InterChange Server option in addition to other options for installing WebSphere business integration system software.
Expand the Development Kits for J2EE option, and select only the Resource Adapter for InterChange Server option.
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.
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.
In a managed environment, Server Access for J2EE can be used in either of the following ways:
The J2EE Connector Architecture specification 1.0. provides requirements for the assembly and packaging of J2EE applications. The developer of the J2EE application must package and deploy it with the application.
InterChange Server provides a deployment descriptor for Server Access for J2EE. This descriptor deploys the Access Resource Adapter as a stand-alone unit in the application server.
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. |
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>
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.