Packaging and Deployment of
Adapters
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 mechanisms for the ConnectionFactory JNDI lookup, based on a serializable class or on a referenceable class. Although the Adapter Framework only uses one of the two classes, you must adhere to the JCA specification and implement both.
There is an example for each of the mechanisms described below:
● RAR (Resource Adapter Archive) deployment
More information: com.sap.aii.adapter.sample.ra.rar in SAPXIAF<SP>_<HF>.sca
<SP> stands for Support Package number; <HF> stands for hotfix number.
● EAR (Enterprise Archive) deployment
Not supported at present.
● SCA (Software Component Archive) deployment
More information: sample_ra.sda in SAPXIAF<SP>_<HF>.sca
The following deployment options are available:
● Stand-Alone Deployment as RAR
● SAP-Specific Deployment Using SDM as SDA
● Create SCA files for standard deployment and shipment to customers.
The Java SP manager (JSPM) can only process SCA files and not RAR files.
The SAP NetWeaver migration controller only accepts SCA files.
This is relevant if you have already shipped an adapter with a previous release.
● It is easier for development to use RAR files, especially when they are using the Development Studio deploy view.
You can deploy the RAR file immediately, without having to use any other tools.
SAP may provide tools in the future that enable you to convert RAR files to SCA files without the SAP-specific deployment descriptors being created automatically.

Read SAP Note 1004000to find out whether such tools are available.