Use this procedure to install and set up the central server.
Before you begin
Before upgrading to a central server, ensure that these setting are in place:
- The databases are DCM initialized and DCM compatible with each other.
Your central CR database and the development databases you use with it must all be DCM initialized with unique database IDs. Additionally, you can only migrate databases that are DCM compatible with your central CR database. For example, your development databases must have the same case setting, LOWER, or PRESERVE. For more details, go to "Administering > Administering Rational® Synergy Distributed" in the IBM® Rational Synergy information center.
- The system clocks are synchronized.
If you are migrating from a remote server on a different host than the central server, synchronize the system clocks of the two hosts.
Procedure
To install and set up the central server:
- Install IBM Rational Change.
- During installation, when prompted, select Central Server.
- For your database, type the path to the central CR database you selected in Central change request database selection.
Attention: You cannot change this database later.
- Optionally, install Rational Change remote servers.
- If you access any of your development databases using remote servers, proceed to the next step to connect those servers now.
- If not, skip to 4.
- Connect your central server and remote servers.
- On each remote server, log on to the Admin interface.
- Click the System Administration link in the Action Panel.
- Select , and then click Register.
- Type the HTTP or HTTPS address of the central server. You can also perform this action from the central server.
- Add development databases.
- Log on to your central server.
- Click the System Administration link in the Action Panel, and then go to the Server tab.
- Add your development databases that are local to the central server. Repeat this procedure for each remote server and the development databases that are local to them.
Results
Now, a functional central server is connected to its development databases, and, optionally, the development databases of your remote servers. You can submit new CRs and associate them to tasks in any of the development servers. You cannot see any pre-existing CRs from those development databases. To access those CRs, migrate them into your central CR database.