!--a11y-->
TerminologyThis section contains the most important terms used in this documentation:
· Software Deployment Archive (SDA)
ZIP-compatible archive format for delivering SAP software components as archives. An SDA contains at least the following files:
¡ MANIFEST
¡ SAP MANIFEST
¡ SDA Deployment Descriptor
· Software Component Archive (SCA)
Physical representation of a version of a software component. It contains a specific number of SDAs, whose quantity describes a precisely-defined version level.
A SCA update always results in a new version level of the software component.
· Software component
The smallest delivery component in terms of installation. You never install only parts of a software component.
· Manifest
File with meta information on the content of a Java archive (jar).
· SAP Manifest:
File with meta information. As well as the standard manifest information, this file also contains information on software logistical processing. Among other things, this includes the following information:
¡ Descriptions of dependencies
¡ Internal SAP descriptions of versions
· Deployment:
Transfer of the selected archives to the runtime environment of the target system
· Deployment Action:
Specific action performed during deployment. It can be one of the following actions:
¡ Initial deployment
¡ Update existing SDAs
¡ Delete deployment
· SDM Repository:
Repository of all archives and applications in an SAP System that are managed with the SDM.
· Deployment Manager:
Standard Java software that implements certain interfaces, enabling it to be linked to the SDM. The Deployment Manager deploys software of a certain type (such as J2EE).
· Deployment Descriptor:
XML file that must be included in every SDA. It must contain all information required for the deployment. The development team responsible for the SDA is responsible for providing this file.
· Undeployment
Remove selected archives from runtime environment of system
