Software Library

All packages are administered in the DSMC software library. The software library is a logical, hierarchical folder structure with whose aid all the packages in an DSM environment can be stored and edited. The software library is stored in the DSMDB.

You can structure the software library through the use of software folders. Furthermore, you can assign packages to different categories on an individual basis. The packages are identified by the icon .

Moreover, for every package you also determine the storage location for the installation data: the repository.
When a package is created, a separate subdirectory <Package ID> is created in the repository. The package ID is automatically assigned. The folders in the software library have no correspondence in the file system of the repository (ClosedIllustration).

Packages contained in the software library can be easily assigned to user-specified installation targets (e.g. via drag & drop). The result is to automatically create a policy which is stored in the DSMDB.

Folders and Categories

The software library supports two kinds of grouping of packages:

  • Software folder
  • Software categories

This diagram illustrates the software library in the DSMC:

Software Folders

The software folder assigns a unique place within the software library to the package: each package can only be assigned to one software folder.
In addition, role-based authorizations can be linked to software folders so that the packages contained in them can only be read, edited or deleted by authorized staff.

As criteria for organizing into software folders, the following are recommended, for example:

  • Separate folders for software for which particular staff are responsible
  • Separate folders for software earmarked for particular target groups
  • Separate folders for software which is stored in separate repositories

Software Categories

Unlike software folders, the same package can be assigned to different software categories.
Software categories are used to group packages which have shared properties into groups. These can be types of software, responsibilities or any other properties.

Software categories can be dynamic or static. This enables them to be adapted to different requirements on an individual basis:

  • Dynamic software categories group packages together dynamically (at runtime) on the basis of defined filter criteria. Software categories can be nested.
  • You can manually assign any number of computers to static software categories - e.g. for special cases or exceptions.
  • Software categories can only contain packages which belong to or are subordinate to the same software folder in the software library.

On the subject of filters, see also: LDAP Filters

Examples for organizing in categories:

  • Which packages are linked to each other?
  • Which packages of a particular type are there (e.g. Driver Packages, Patch Packages)?
  • Which packages are available only in site XY?
  • Which staff are responsible for the packages?

Repositories

Repositories contain the package installation files. The software folders and categories do not have any correspondence in the file structure.
To ensure that packages are unique within the repository, the package directories are designated not with a name but with an ID. This ID is automatically assigned to the package when it is created. It cannot be changed.
Packages in different repositories or folders can have the same names: they are kept distinct by means of the package ID.

The package ID should not be confused with the UID (Unique Identifier = globally unique designation. The UID accompanies a package as a property. The UID is used to file install and uninstall information and the installation status of a package in the registry on managed computers.

When packages are exchanged between different DSM environments, the UID remains unchanged, while the package ID is redefined.

The installation data for packages in the software library can be stored in different repositories. This means that the desired repository can be selected for each package.

DSM Database (DSMDB)

The control data for packages from the software library is held in the DSMDB.
This control data consists primarily of properties, settings and parameters.