This topic describes the steps necessary to upgrade the
Jazz Team Server and Change and Configuration Management from 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
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.
If you plan to upgrade multiple products, see Upgrade order to
help you decide what to upgrade first.
Important: To use the upgrade script in a distributed
environment where you install Change and Configuration Management
application separately from the Jazz Team Server, the upgrade script
must be able to access the drive or file system where the Jazz Team
Server is installed. On Windows, for example, the mapping must be
of the form <mapped drive letter>:\server\conf.
An absolute path (\\<machine name>\<installdir>server\conf)
will not work. The mounted drive must be configured with read-write-execute
privileges for the admin account.
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:
Note: You can run the script by specifying
all of the arguments on the command line. As an alternative, if you
are going to rerun the upgrade script multiple times, you can also
edit the script's parameters file and run an abbreviated command line.
See the next optional step for instructions about the parameters file.
Important: Although the script file is located under the upgrade
directory, it must be run from the server directory. Also if your
path contains spaces, ensure you enclose it in double quotation marks.
Windows
upgrade\jts_upgrade.bat -oldJTSHome <3.0JTS_install_dir>\server\conf
UNIX
upgrade/jts_upgrade.sh -oldJTSHome <3.0JTS_install_dir>/server/conf
If
you need more details about the command line options, see jts_upgrade.
The script completes these
tasks with the indicated user interactions:
- Optional: As an alternative to the previous step, you can open
the script's parameters file, modify the default values, and run an
abbreviated form of the command line.
The English and translated
versions of the jts_params files are located
in the <3.0.1JTS_install_dir>/server/upgrade/params directory.
- To get the exact name of the parameters file for your language,
from the <3.0.1JTS_install_dir>\server\upgrade directory,
run the locale.bat -jts -showParamFileName command
on Windows or the locale.sh -jts -showParamFileName command
on the UNIX systems.
- Open jts_params or a translated version of
it for editing and specify values for each parameter. One of the parameters
that must be set is the path to the OLD_JTS_HOME directory.
- 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 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:
Note: You can run the script by specifying
all of the arguments on the command line. As an alternative, if you
are going to rerun the upgrade script multiple times, you can also
edit the script's parameters file and run an abbreviated command line.
See the next optional step for instructions about the parameters file.
Important: Although the script file is located under the upgrade
directory, it must be run from the server directory. Also if your
path contains spaces, ensure you enclose it in double quotation marks.
In addition, ensure to provide the applicationContextRoot parameter
and set it ccm. By the default the applicationContextRoot is
jazz.
Windows
upgrade\ccm_upgrade.bat -oldApplicationHome <3.0CCM_install_dir>\server\conf -applicationContextRoot ccm
UNIX
upgrade/ccm_upgrade.sh -oldApplicationHome <3.0CCM_install_dir>/server/conf -applicationContextRoot ccm
If
you need more details about the command line options, see ccm_upgrade.
The script completes these
tasks with the indicated user interactions:
- Runs the -migration_ccm_updateConfigurationFiles command
and updates the configuration and Tomcat files. Enter [E] to execute
the command, [S] to skip the step, or press [Enter] to cancel the
script execution.
- After the configuration files are merged successfully, enter [C]
to continue. A Notepad window (or a vi editor on the UNIX systems)
opens in which you can verify the CCM teamserver.properties file.
Verify that the Public URI root denoted by the com.ibm.team.repository.server.webapp.url
property is correct. Also verify that the database properties are
correct. The database location must be different from the JTS database
location. When done, save your changes if any and close the editor
to continue the script execution. For information about verifying
configuration files, see Verifying the configuration files during upgrade.
- Continue running the script until you see a message that the CCM
upgrade succeeded.
- Optional: As an alternative to the previous step, you can open
the script's parameters file, modify the default values, and run an
abbreviated form of the command line.
The English and translated
versions of the ccm_params files are located
in the <3.0.1CCM_install_dir>/server/upgrade/params directory.
- To get the exact name of the parameters file for your language,
from the <3.0.1CCM_install_dir>\server\upgrade directory,
run the locale.bat -ccm -showParamFileName command
on Windows or the locale.sh -ccm -showParamFileName command
on the UNIX systems.
- Open the ccm_params file or a translated
version of it for editing and specify values for each parameter. One
of the parameters that must be set is the path to the OLD_AAPLICATION_HOME
directory. Ensure that the path does not contain any spaces.
- 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 ccm.war provided
with 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.