DCM transfer sets in central server mode

While in central server mode, do not use DCM to transfer CRs between databases. Remove CRs from all of your DCM transfer sets in IBM® Rational® Synergy.

Set the CR Scope of your transfer sets to None and delete their CR Query strings. Remove the modifiable_in attribute (Work In DB) from the show and transition forms of your existing, stand-alone IBM Rational Change servers. Doing so prevents users from trying to transfer CRs before a CR migrate. Or you can remove the databases to be migrated from those servers.

Receiving all outstanding DCM transfer packages before you migrate your CRs ensures that no CRs are in transit between databases when you perform a CR migrate. If you later realize that you missed some CRs that were in transit, you can always migrate the database again to pick up the remaining CRs.

When you turn off CR transfers between your new central CR database and remote databases, consider what other data continues to be transferred between the database. Update your DCM transfer sets and scripts accordingly. For example, if you centrally administer releases and process rules, you need transfer sets and DCM scripts to continue maintaining that process. You need to do so, even after you turn off the transfer of CRs. For information about the replication of releases, processes, and templates, go to the IBM Rational Synergy information center, and see the "Administering > Administering Rational Synergy Distributed" section.


Feedback