Packaging and Deployment of Adapters 

Use

Adapter deployment follows the JCA specification.

The references refer to chapter 10 of the document J2EE Connector Architecture Specification, Final Version 1.0.

You can download this document at java.sun.com/j2ee/connector.

Third-party adapters are deployed as follows:

·        In the stand-alone variant, if all functions are implemented in the adapter and the default Adapter Framework is used.

·        In the bundled variant, if you provide your own Enterprise JavaBeans that are used in your own Adapter Framework module chain definition.

A bundled deployment scenario of the Adapter Framework with a third-party adapter is not supported.

The JCA specification allows two different mechanisms for the ConnectionFactory JNDI lookup, based on a serializable class or referenceable class. Although the Adapter Framework only uses one of the two classes, you must adhere to the JCA specification and implement both.

Integration

There is an example for each of the mechanisms described below:

·        RAR deployment (Resource Adapter Archive)

See also: sample_ra.rar in sample_ra.sda in SAPXIAF<SP>_<HF>.sca

<SP> stands for Support Package number and <HF> stands for hotfix number.

·        EAR deployment (Enterprise Archive)

Currently not supported.

·        SDA deployment (Software Delivery Archive)

See also: sample_ra.sda in SAPXIAF<SP>_<HF>.sca

Features

The following deployment options are available:

·        Stand-alone deployment as RAR

·        Bundled deployment as EAR

·        SAP-specific deployment as SDA using SDM