Upgrading from version 2 to 3.0.1 using the upgrade script

You can use the upgrade script to minimize the number of commands that you must manually run while upgrading your application data.

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 version 2 repository database.

Ensure that the clocks on all servers 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.

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 Rational Team Concert database (<RTC2_install_dir>\server\repositoryDB) from 2 to 3.0.1. For more information, see Backing up and restoring the Derby database.

If you plan to upgrade multiple products, see Upgrade order to help you decide what to upgrade first.

Procedure

  1. Review the topics in the section on Planning the deployment and upgrade as needed.
  2. Verify your existing version 2 teamserver.properties file for the public URL property com.ibm.team.repository.server.webapp.url.

    You must use the same public URL in version 3.0.1. If a public URL was not set, use the version 2 administrative web interface (Advanced Properties) to set the qualified hostname URL (https://hostname.example.com:port) before upgrading.

    The public URL line in the teamserver.properties should look similar to this:
    com.ibm.team.repository.server.webapp.url=https\://<hostname.example.com>\:9443/jazz
  3. Shut down the version 2 server.
  4. If you have not already installed, install Jazz Team Server and the Change and Configuration Management (CCM) application to a new location. If you have already installed Jazz Team Server and upgraded to version 3.0.1, just install the Change and Configuration Management application.
  5. During installation, select Use Rational Team Concert 2.x context root.
  6. At the end of installation, select None for Which program do you want to start.
  7. Create a separate database for Jazz Team Server with the same parameters but different database name as your v2.x database. For more information about creating databases, see Setting up the database.
    Note: A separate Jazz Team Server database from the CCM database is required. Create a new JTS database if you have not already done so.
  8. Navigate to <CCM3.0.1_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.

    If you need more details about the command line options, see ccm_upgrade.

    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.

    If you installed the version 3.0.1 Jazz Team Server together with the CCM application, and this is the first or only application you are upgrading, the command syntax is as follows:

    Windows
    upgrade\ccm_upgrade.bat -oldApplicationHome <RTC2.x_install_dir>\server\conf -createJTSTables
    UNIX
    upgrade/ccm_upgrade.sh -oldApplicationHome <RTC2.x_install_dir>/server/conf -createJTSTables
    Note: The -createJTSTables parameter applies to installations where you are installing the Jazz Team Server 3.0.1 for the first time.

    If you installed the version 3.0.1 Jazz Team Server separately from the CCM application, such as in a distributed deployment, you need to specify the location of the 3.0.1 Jazz Team Server and run the script from the CCM 3.0.1 installation directory. In this case, include the -newJTSHome argument.

    Windows
    upgrade\ccm_upgrade.bat -oldApplicationHome <RTC2.x_install_dir>\server\conf -newJTSHome <JTS3.0.1InstallDir>\server\conf
    UNIX
    upgrade/ccm_upgrade.sh -oldApplicationHome <RTC2.x_install_dir>/server/conf -newJTSHome <JTS3.0.1InstallDir>/server/conf
    Note: If you have a distributed deployment and have not configured the Jazz Team Server, then you can add the -createJTSTables parameter to the command line example above.
    The script completes the following 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 running the script.
      Important: Do not modify the properties to connect to the data warehouse database, even if they are currently set to Derby. Only use the server setup wizard to modify these properties.
      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.
  9. 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.

    1. To get the exact name of the parameters file for your language, from the <3.0.1CCM_install_dir>\server\upgrade directory, run locale.bat -ccm -showParamFileName on Windows or locale.sh -ccm -showParamFileName on the UNIX systems.
    2. Open ccm_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_AAPLICATION_HOME directory. Ensure that the path does not contain any spaces.
  10. If you are using Apache Tomcat, see Setting up Apache Tomcat.
  11. If you are using WebSphere Application Server, uninstall your previously installed web applications and redeploy jts.war, ccm.war, and clmhelp.war provided with 3.0.1 installation. For further details, see Setting up WebSphere Application Server for the version 3 upgrade.
  12. Configure the server and any CLM applications that you installed.

    Run the server setup wizard if you are upgrading the Jazz Team Server together with Change and Configuration Management or any of the CLM applications. (see Running the setup wizard) 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.


Feedback