web server - Borland Technical Publications

Deploying the Resource Adapter
Packaging and deployment
The file format for a packaged Resource Adapter module defines the contract between
a Resource Adapter provider and a Resource Adapter deployer. A packaged Resource
Adapter includes the following elements:
■
■
■
■
Java classes and interfaces that are required for the implementation of both the
Connectors system-level contracts and the functionality of the Resource Adapter
Utility Java classes for the Resource Adapter
Platform-dependent native libraries required by the Resource Adapter
Help files and documentation
■
Descriptive meta information that ties the above elements together
For more information on packaging requirements, refer to Section 10.3 and 10.5 of the
Connectors 1.0 specification, which discuss deployment requirements and supporting
JNDI configuration and lookup, respectively.
Deploying the Resource Adapter
Deployment of Resource Adapters is similar to deployment of EJBs, Enterprise
Applications and Web Applications. As with these modules, a Resource Adapter can
be deployed as an archive file or as an expanded directory. A Resource Adapter can
be deployed either dynamically using the Borland Enterprise Server Console or the
iastool utilities, or as a part of an EAR. See the Borland Enterprise Server User's
Guide for deployment details.
When a Resource Adapter is deployed, a name must be specified for the module. This
name provides a logical reference to the Resource Adapter deployment that, among
other things, can be used to update or remove the Resource Adapter. Borland
Enterprise Server implicitly assigns a deployment name that matches the filename of
the RAR file or deployment directory containing the Resource Adapter. This logical
name can be used to manage the Resource Adapter after the server has started. The
Resource Adapter deployment name remains active in the Borland Enterprise Server
until the module is undeployed.
Application development overview
Developing application components
Common Client Interface (CCI)
The client APIs used by application components for EIS access can be categorized as
follows:
■
■
■
The standard common client interface (CCI) defined in Section 9 of the Connectors
1.0 specification.
A general client interface specific to the type of Resource Adapter and its underlying
EIS. For example, JDBC is one such interface for RDBMSs.
A proprietary client interface specific to the particular Resource Adapter and its
underlying EIS. For example, the CICS Java Gateway is one such interface for the
IBM CICS transaction processor, and the JFC for the SAP R/3 enterprise resource
planner is another.
270 BES Developer’s Guide