Software Delivery Unit 

Definition

A software component archive (SCA), Java archive (JAR) or SAP archive (SAR) that can be deployed by the JSPM.

Use

The following software delivery units (SDUs) can be deployed by the JSPM:

·        Support package stacks

Support package stacks are defined by SAP collections of support packages for all software components in one product. Support package stacks have been designed to reduce the amount of different combinations of software versions at customer systems and to provide customers with a set of versions that can work best together.

A support package stack contains a combination of the following:

¡        A set of different SCAs

¡        The SDM JAR – SDMkit.jar

¡        The kernel SARs:

§         Database Independent: SAPEXE.SAR, IGSEXE.SAR, and other operating system dependent SARs

§         Database Dependent: SAPEXEDB.SAR and other database dependent SARs

§         The SAP archiving tool – SAPCAR

¡        A configuration XML file, which includes a description of the components that are part of the stack and their respective support package and patch levels.

·        Single support packages

SAP provides support packages on a component level. Java support packages contain the complete version of the development components of an application. You, therefore, need to import the latest support package only. If there are dependencies with other Java support packages, they are specified in an SAP Note.

SAP provides support packages also as a single component patch. For example, patch 2 of support package 3 may include some fixes.

Support packages are provided in the form of SCAs, JARs, and SARs.

·        New software components

Third-party software components and SAP software components that are not part of a SAP NetWeaver usage type.

Software components are provided in the form of SCAs.

Structure

Each SCA has the following attributes:

·        Vendor

The company that produced the software, for example, SAP AG.

·        Name

·        Counter

Contains the release, support package level, patch level, and timestamp. For example, 1000.7.00.2.0.20050524093600, where 7.00 is the release, 2 is the support package level, 0 is the patch level, and 20050524093600 is the timestamp.

·        Build location

The system where the software has been built.

An SCA may have several versions. An SCA version is defined by a combination of all of the attributes above. Before the deployment of a software component, the JSPM performs the following types of version checks:

·        Checks on own software components

The JSPM checks if the new software component can overwrite the old software component that is deployed in the system. Only new software components that have a higher support package and patch level than the support package and patch level of the old software components can be deployed.

·        Checks on foreign software components

The JSPM checks if, after the deployment of a software component, the dependencies on other software components are fulfilled.

Integration

Before the deployment of a software component, the SDM server performs additional version checks. Only new software components that have a higher counter than the counter of the old software components can be deployed.