Before using DCM, be sure that source and destination projects
have the same update properties. If they do not, transferred objects
might not be correctly configured into projects in the destination
databases.
The update properties do not have to be the same
for all databases in a DCM cluster. However, each pair of source and
destination databases must have the same values for the project purpose
list, platform, release delimiter, release definitions, and task attribute
value range settings.
- Project
purpose list
- The destination database must be able to recognize
the project purpose of a transferred prep project.
The possible values for this property are stored in the project_purpose_list attribute
of a base model object. To modify the project purpose list, use the project
purpose command. This property is used when a prep project
is created, checked out, or updated.
- Platform
- The destination database uses the platform setting
of transferred objects to update projects. The possible values for
this property are stored in the etc\om_hosts.cfg file
in the Rational® Synergy
installation area.
- The platform setting is used by task-based CM.
- Release
delimiter
- The release delimiter is used to construct release
values from the component name and component release part of a release
definition. The release delimiter must be identical in all databases
in a DCM cluster for a release definition to generate the same release
value or for a release value to reference its corresponding release
definition.
- Release
definitions
- The
destination database uses the release setting of transferred objects
to update the membership of projects. Therefore, the release definitions
that correspond to the values that are being used with the transferred
objects must be equivalently defined. This situation is most easily
achieved by allowing the release definitions to be replicated, and
by including release definitions in the transfer sets used to replicate.
Each transfer set normally includes eligible release definitions by
default.
- Task attribute
value range settings
- The task attribute value range settings define the
possible values for task attributes. The destination database must
be able to recognize at least some attribute values of the tasks in
order to update the projects of the destination database.
By default, only the release attribute
of a task is used in a task-based update operation. The platform and task_subsys attributes
can also be used. In the destination database, folder queries can
be set up based on the values of these attributes. The attribute value
range settings for the destination database must include the values
of the release, platform, and task_subsys attributes,
as applicable.