You can upgrade a second Rational Team Concert™ server
so that it shares the same version 3.0.1 Jazz™ Team
Server.
Before you begin
Important: Ensure that the clocks on all machines
are synchronized using the Network Time Protocol (NTP). Time is the
critical element that enables an event on one network node to be mapped
to a corresponding event on another. To avoid problems, these challenges
can be overcome by the enterprise deployment of the NTP service. For
more information about NTP, visit
http://www.ntp.org/. In addition,
all servers must use the same authentication method for their users.
About this task
The steps for upgrading a second server are the same steps
that you followed to
upgrade
the first server, except that you must also complete the following
tasks.
Procedure
- Run the pre-upgrade steps. See the "Before you begin" section
of Upgrading manually from version 2 to 3.0.1.
- Back up your Rational
Team Concert version 2 database.
- Update the database properties in the second 3.0.1 CCM teamserver.properties to
point to the version 2 database. See Verifying the configuration files during upgrade.
- Run the following command to add tables to the database:
<3.0.1CCM_install_dir>/repotools-jazz -clean -addTables
- Export the Jazz Team
Server user data from the second Rational Team Concert version
2 server to a file that is named differently from the file on first
server.
Note: It is likely that the second CCM instance
is on another server. You must copy the exported tar file to the server
that contains the Jazz Team
Server.
<3.0.1CCM_install_dir>/repotools-jazz -migration_exportJTSData toFile=jtsData2.tar
- Import user data from the second server into the team server.
Important: When importing data into an existing
team server, you must not use the createTable parameter.
If you specify the createTable parameter, the
existing data in the team server repository is removed.
<3.0.1JTS_install_dir>/repotools-jts -migration_importJTSData fromFile=jtsData2.tar createMappingFile=rtc-mapping2.txt
Note: The rtc-mapping2.txt file
contains a mapping of the team server contributor information itemids to the Rational Team Concert itemids. Although you must run the -migration_importJTSData command
on the shared team server, you must also run the -migration_importUserMapping on
the second server to complete the user synchronization.
- Import the mapping data into the second server.
<3.0.1CCM_install_dir>/repotools-jazz -migration_importUserMapping fromMappingFile=rtc-mapping2.txt
- Start the JTS and CCM servers.
- Open a browser and go to the Administration page on the
team server machine (https://hostname.example.com:port/jts/admin).
- Click the Applications tab and type
the discovery URL for the second Rational Team Concert server,
for example, https://hostname2.example.com:port/jazz/scr.
You must register the second server with a different name from the
first server.