If you installed IBM® Rational® Change in Central
Server mode, you can immediately start submitting new CRs. To see
any pre-existing CRs (CRs that were created in a development database
before Central Server mode was being used), you must migrate them
into your central CR database.
About this task
The migration process can be lengthy. The CR migrate process
can take hours, or even days for large databases. Any DCM packages
received while CR migrate is in progress can extend the migration
time.
Users can continue to use the product during a CR migrate.
Both the central CR database and the development database can remain
enabled. As CRs are migrated into the central CR database, they are
available immediately for users to view and edit. The newest CRs are
transferred first.
Procedure
To migrate change requests to a central server:
- Start an Admin session on the Rational Change server that has the database
that you want to migrate.
- On the Action Panel, click System Administration.
- On the Server tab, click Properties.
- At the bottom of the Properties tab,
click CR Migrate.
- Select the database containing the CRs you want to migrate.
- Specify whether you want to be notified when CR migrate
is complete.
Your central server must be configured
to send mail through an SMTP server to use this feature. If you do,
verify that your email address is correct.
- Click Migrate.
The CR
Migrate window shows the progress of the migration. Closing
the window does not stop the migration. You can open and close the
window to check on the progress.
If you decide to stop the
migration, click Stop. You can continue the
migration later by migrating the same database again. The migration
resumes from where it was stopped. If a migration failed because of
network problems or other errors, restart and continue it from where
the problem occurred.
After the CR migrate has finished, optimize
your central CR database by running the ccmdb update_statistics command.
You can also run this command in the middle of the CR migration process
when you suspect the migration is getting slower. You might improve
performance when you run this command.