Packages -  General

The "unit" of life cycle management is the package. Within the DSMC, you store packages in the software library.

A package contains the data required to install software or to perform other administrative tasks on one installation target or on several installation targets. Depending on the type of package this includes for example, files, scripts and settings for customizing the installation.
Package is an umbrella term for specific package types such as eScript Package, MSI Package, Driver Package or Patch Package.
All packages are subject to revisioning. This means that the different "statuses" of a package are saved as a revision and each of them is also available on its own in the software library.

After a package has been released, it can be assigned to an installation target. The DSM infrastructure then automatically takes care of distribution of the package data and installation on the target computer.

Constituent Parts

A package consists of several constituent parts which are physically stored in different places:

• Installation files - the data which has to be copied and installed by the DSM Client (also referred to as "bulk data"). The installation files are held in the package directory (subdirectory of the repository in the depot). The registry extension files (<package name>.NIR also belong to the package files).
• eScript - the eScript contains commands which are executed when the package is executed by the DSM Client, for example commands for copying files, registry extension commands and commands to create links. The eScript is stored in the include file script.inc by default. It is also contained in the package directory.
• Revisions - released "statuses" of installation files and eScripts are in each case stored as revisions in a separate subdirectory of the package directory. Each revision is completely restorable and can be assigned to an installation target.
• Distribution - the specified distribution targets and the permitted timespan for the associated installation files (source files).
  The corresponding distribution files are stored in the package directory.
  The distribution files include:
  • Job Definition File (Project.jdf)
  • Distribution Status files (Project.status, CompProject.sta­tus)
  • Files which contain the source files and the include file in compressed (_NI5.ZIP)
  • FPI file which is used for consistency checking (package.fpi)
  • Checksum of the FPI file (package.fpi.checksum)
• Control data - This includes package properties, such as ID, name, reporting settings and execution settings.
  These properties are stored in the DSMDB. Properties which can be edited can be edited either in the detailed window tab Properties or in the Packaging Workbench. The Properties detail window tab contains a brief description of the properties.

Package Types

The following package types exist:

Icon	Package Type	Content
	eScript Package	Standard package, based on an eScript. Depending on the commands used, this package allows for the automation of various actions, e.g. the installation of software, client management commands etc.
	MSI Package	Package which contains MSI-based software
	Configuration Package	Package which makes it easier to prepackage configuration settings for computers by using configuration items.
	Driver Package	Package which contains a driver installation. It can be installed during Unattended Installation and when Windows is running.
	Software Set	A software set combines different packages in a set (unit). A software set cannot contain other software sets. Specific software sets for DSM OS Deployment are called OS Installation Set.

The DSM uses Infrastructure Packages to distribute the DSM program files. The terms application package and software package are collective terms for package types in use.
On top of this there are other package types where additional DSM modules are used, such as DSM OS Deployment or DSM Patch Management (see separate documentation).

Besides the packages, the software library also contains package templates for certain types of packages. These templates define properties, parameters, platforms and file contents, in particular for the Script.inc file.