Repository

The installation data (mass data) of the packages is stored in the repository. Physically, the repository is located in the Work and Install child directories of the depot share.
This means that the contents of the repositories are separate from the control data of the contained packages which is stored in the DSMDB.

Depending on the network size, usually a different number of depots are created in the infrastructure.

Repositories are distributed via DSM's integrated distribution facility to all existing depots.

Directories

The paths for the repository corresponding to the depot share are strictly preset; they cannot be changed. The description of the path in the Repository in the configuration table is for your information.

Installation Copy

Directory on the depots in which the write-only copy of the repository is located. This copy of the repository is used for installing on managed computers (exe­cuting packages).

Value: .\Install\<Database name>

Work Copy

Directory on the depots containing the copy of the repository that is read from and written to during cascaded distribution. For example, changes resulting from newly created packages are written in the copy that creates the starting point of the distribution, the master depot of the repository context.

Value: .\Work\<Database name>

Support for Several Repositories

DSM makes it possible to work with several repositories. Several repositories makes decentralized administration of DSM possible. For exam­ple, you can assign every site a separate repository, which is managed from there. However, the packages that are stored in these repositories are only available for managed computers assigned to the respective site.

If you are working with several repositories, the names of the repositories must be unique in the entire organization. Packages located in different folders can, however have the same name. The same is true for packages and folders in different repositories. This is made possible by the use of IDs.

We recommend the following when you are using several repositories:
Create one repository for each site where packaging takes place and/or where specific packages are required (e.g. language-dependent).