SAP-Specific Deployment as SDA Using SDM (SAP Library

SAP-Specific Deployment as SDA Using SDM

Deploying your adapter as a software delivery archive (SDA) offers you all the advantages of the Software Deployment Manager (SDM):

· Deployment information is saved in the database and can be tracked.

· Deployment management at exactly one location.

· Distribution to cluster nodes, and so on.

Recommendation

Deployment as an SDA is optional, but recommended.

A valid SDA for a resource adapter consists of the following files:

Files in the SDA

File Name	Use
RAR file	See also: Stand-Alone Deployment as RAR
Log-configuration.xml with path META-INF	See also: Stand-Alone Deployment as RAR, with path META-INF
Manifest.mf with path META-INF	Contains the version numbers and the provider names. See also: sample_ra.sda, Manifest.mf
SAP_manifest.mf with path META-INF	Contains version numbers, content, and component names, similar to a catalog. The SDM uses this information to manage the deployment information in its database. See also: sample_ra.sda, SAP_manifest.mf
application.xml with path META-INF	Contains display names and references to icons if the adapter is displayed with SAP J2EE tools. See also: sample_ra.sda, application.xml
com.sap.aii.af.sample.adapter.ra-dd.xml with path META-INF	Not currently used, but should be present. See also: sample_ra.sda, com.sap.aii.af.sample.adapter.ra-dd.xml
application-j2ee-engine.xml	Contains references required during SDM deployment.