Replication of release definitions and associated process rules

Replication of release definitions allows a user to centrally administer release definitions and their associated process rules. Then, users can automatically update other databases in the DCM cluster.

If a DCM cluster uses release values to configure shared data into projects, the release values of transferred objects must be defined as release definitions in the destination database.

The replication of release definitions and information is controlled by these parameters and settings:

Table 1. Actions for update release definitions
Update release definitions Action
none All release information in the DCM transfer package is ignored.
active Release definitions in the package are used to create or update release definitions in the receiving database. However, a release definition is created only if it is an active release. New release definitions for inactive releases are not created. Existing release definitions that are inactive and have been received before continue to be updated.

This setting is the default setting.

inactive Release definitions in the package are used to create or update release definitions in the receiving database. Release definitions for both active and inactive releases are created or updated.

During a DCM generate operation, DCM includes release definitions, process rules, or folder templates only. The objects must have been modified or become members of the transfer set more recently than the last generate time for that transfer set and database. If you perform a DCM Generate since Never, and the transfer set release scope is set to Releases and Templates, and the release query is blank, all the release definitions and their associated process rules and user-defined folder templates are included in the DCM transfer package.

To check or manually change release definitions, use the ccm release command.


Feedback