Central change request database selection

In a central server, all change requests (CRs) reside in a single, central CR database. You can view, modify, and report on CRs without switching databases. This database is dedicated to CRs. Your tasks and objects are kept in separate development databases. You can associate CRs in your central CR database to tasks in any of the development databases.
Attention: You select a central CR database during the installation process and you cannot change it later.

Before installing IBM® Rational® Change, select a central CR database. You have two options:

  1. Create a new database.

    Unpack a new, empty database to be your central CR database. That way, there are no development objects, such as tasks or source files, in the database. Then, you can migrate all existing CRs into that database with the CR migrate feature.

  2. Use an existing database.

    If you have an existing system environment where the set up is like a central database, you can designate that existing, non-empty database as your central CR database. Do so only when you have a database dedicated to CRs. For example, you can initially submit all CRs into one database. Then, use IBM Rational Synergy Distributed, also called Distributed Configuration Management (DCM), to transfer them to other databases before associating tasks.

    If you have any tasks or objects, anything other than CRs and their attachments, in that initial database, they might become inaccessible or damaged in a central server. The advantage of using an existing database is that it might speed up migration if most of your CRs are already modifiable in that database.


Feedback