This topic describes the manual process of using repository
tools for upgrading Rational Team Concert version 3.0 to 3.0.1.
Before you begin
Before you upgrade the server, ensure that you have a completely
up to date and valid backup of your Rational Team Concert and Jazz
Team Server v3.0 repository database.
Also ensure that the clocks on all machines are synchronized using
the Network Time Protocol (NTP). Time is the critical element that
allows 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.
If you plan to upgrade multiple products, see Upgrade order to
help you decide what to upgrade first.
If you are using the Derby database, copy the JTS and CCM databases
from 3.0 to 3.0.1. For more information, see
Backing up and restoring the Derby database.
Note: If
you are using the same database, data migration is not required. But
if you are switching the database while upgrading, you must export
your data from previous database and import it into the new database.
Upgrading Jazz Team Server (JTS)
- Review the topics in the section on Planning the deployment and upgrade as needed.
- Shut down the JTS 3.0 server.
- If you have not already installed Jazz Team Server as part of
a CLM installation, install Jazz Team Server to a new location on
disk. If you have already installed Jazz Team Server and upgraded
to version 3.0.1 and want to install and upgrade the Change and Configuration
Management application, proceed to Upgrading Change and Configuration Management (CCM).
- During installation, select Use default 3.x application
context roots.
- At the end of installation, select None for Which
program do you want to start.
- Navigate to <3.0.1JTS_install_dir>/server and
run the following command:
If you are using WebSphere Application
Server, specify the updateTomcatFiles=no parameter
in the command. For information about all possible parameters that
can be used with this command, see -migration_jts_updateConfigurationFiles.
repotools-jts -migration_jts_updateConfigurationFiles oldJTSHome=<3.0JTS_install_dir>/server/conf
The
command completes the following tasks:
- Updates the V3.0.1 teamserver.properties file based on the information
from V3.0 file.
- Copies the content of the Tomcat users xml file.
Remember: For
Tomcat user database only. The tomcat-users.xml file is copied (not
merged with the existing file). If you are upgrading multiple CLM
applications with a common JTS, you must manually merge the users
and group information in the tomcat-users.xml file. The user and group
information will be different if users are part of different groups
in different applications. For example, userA has JazzAdmins role
in CCM and JazzUsers role in QM. In addition, if some users are present
in one application and not in the other or vice versa, they must manually
be added to the tomcat-users.xml file.
- Merges the content of the V3.0 server.xml and web.xml files with
version 3.0.1.
- Navigate to <3.0.1JTS_install_dir>/server and
run the following command to create JTS database tables:
repotools-jts -addTables
- If you are using Apache Tomcat, see Setting up Apache Tomcat.
- If you are using WebSphere Application Server, uninstall your
previously installed web application and redeploy jts.war, admin.war,
and clmhelp.war provided with 3.0.1 installation.
For further details, see Setting up WebSphere Application Server for the version 3 upgrade.
- Start the JTS server.
- Continue with Running the setup wizard to
configure the server.
Upgrading Change and Configuration
Management (CCM)
- Review the topics in the section on Planning the deployment and upgrade as needed.
- Shut down the CCM 3.0 server.
- Install the CCM application to a new location on disk.
- During installation, select Use default 3.x application
context roots.
Important: If your Rational
Team Concert version 3.0 was upgraded from version 2, select Use
Rational Team Concert 2.x context root to preserve the /jazz context
root.
- At the end of installation, select None for Which
program do you want to start.
- Navigate to <3.0.1CCM_install_dir>/server and
run the following command:
If you are using WebSphere Application
Server, specify the updateTomcatFiles=no parameter
in the command. For information about all possible parameters that
can be used with this command, see -migration_ccm_updateConfigurationFiles.
Note: The
default applicationContextRoot is jazz. If you
are upgrading from version 3, ensure to specify the applicationContextRoot parameter
and set it to ccm.
repotools-ccm -migration_ccm_updateConfigurationFiles oldApplicationHome=<3.0CCM_install_dir>/server/conf applicationContextRoot=ccm
The
command completes the following tasks:
- Updates the v3.0.1 application teamserver.properties file based
on the information from v3.0 file.
- Copies the content of the tomcat-users.xml file.
Remember: For Tomcat user database only. The tomcat-users.xml file
is copied (not merged with the existing file). If you are upgrading
multiple CLM applications with a common JTS, you must manually merge
the users and group information in the tomcat-users.xml file.
The user and group information will be different if users are part
of different groups in different applications. For example, userA
has JazzAdmins role in CCM and JazzUsers role in QM. In addition,
if some users are present in one application and not in the other
or vice versa, they must manually be added to the tomcat-users.xml file.
- Merges the content of the v3.0 server.xml and web.xml files
with version 3.0.1.
- Navigate to <3.0.1CCM_install_dir>/server and
run the following command to create CCM database tables:
repotools-ccm -addTables
- If you are using Apache Tomcat, see Setting up Apache Tomcat.
- If you are using IBM WebSphere Application Server, uninstall your
previously installed web application and redeploy the ccm.war that
is provided with the version 3.0.1 installation. For further details,
see Setting up WebSphere Application Server for the version 3 upgrade.
- Start the CCM server.
- Use the administrative web interface if you are adding Change
and Configuration Management to an established Jazz Team Server. See Registering applications with the Jazz Team Server.