Upgrading to version 5.0.1

Upgrading from version 3 to version 5.x: Upgrading from version 3 to any release of version 5 is a two-step process. You must first upgrade your server to the latest fix pack of version 4 release, and then upgrade to version 5.x. For instructions on upgrading from version 3 to version 4, see the latest version 4 documentation.

z/OS upgrade: For information about upgrading the CLM applications on z/OS, see Planning to upgrade on z/OS.

Use this guide to upgrade all releases of version 4 and version 5 of the Rational® solution for Collaborative Lifecycle Management (CLM) applications to version 5.0.1:

Select the options that best describe your installation environment

Select an application to upgrade:

Note: In a Rational solution for CLM environment, you must upgrade Jazz Team Server first. In a distributed topology, select one application to upgrade at a time.

Select your current product version:
Select your deployment topology:
Select the operating system for your application server:
Select your application server:
Select your database server:
Did you configure a data warehouse in your previous installation?
Do you need to integrate with other products?

The complete instructions to upgrade your product to version 5.0.1 are generated based on the selections that you made on the previous page.

Important: Before you upgrade, read these important notes.

Complete the planning checklist

Use this planning checklist to ensure that you are ready to upgrade.

  Planning task More information
Use the software product compatibility reports: On this page, you can search and generate reports for a specific product. The information includes prerequisites, product translation into a specific language, end of service, server virtualization environments, and more. Software product compatibility reports
Use the upgrade data sheet: On the upgrade data sheet, you can gather and record specific data that is required during the upgrade process, such as URLs and user IDs. Datasheet for performing an upgrade to the CLM environment
Verify that your hardware and software meet the minimum system requirements: New requirements exist for version 5.0.1, and a few older versions are deprecated. To learn about the new requirements and to see whether your system meets the minimum requirements, click the System requirements link. System requirements
Get the product installation media: For a local repository download, you need approximately 5 GB of hard drive space to download and extract your product installation media. You can download the server installation files from jazz.net
Review an upgrade topology example.
Synchronize the clocks on all servers: In a distributed environment, ensure that the clocks on all servers are synchronized by using the Network Time Protocol (NTP). For more information about NTP, visit ntp.org
Understand the upgrade process: Learn about the upgrade process and how the upgrade might affect your deployment. Understanding the deployment and upgrade process
Plan for your applications to be unavailable: Your applications will be unavailable for a brief period while you back up everything and update your applications to version 5.0.1. All of the applications that are connected to Jazz Team Server will be offline while Jazz Team Server is offline. Be sure to provide time to completely back up your existing applications.  
Meet your database prerequisites:
  • You can access the previous release database and copy the derby/repositoryDB directory.
  • You have the correct user name and password.
    • On UNIX systems, use the password for the DB2 instance owner, which is typically the db2inst1 user.
  • You backed up your database before you started the upgrade process.
  • You have the correct user name and password.
  • You backed up your database before you started the upgrade process. For more information about backing up databases, see your database vendor documentation.
  • You are using JRE version 6.0 or 7.0, and you are using ojdbc6.jar. The Rational solution for CLM 5.0.1 no longer supports JRE version 5.0. Only JRE version 6.0 and 7.0 are supported. The ojdbc5.jar class library requires JRE version 5.0 and the ojdbc6.jar class library requires JRE version 6.0 or later.
  • You created an environment variable named ORACLE_JDBC_DRIVER_FILE and pointed to the ojdbc6.jar JDBC driver.
  • You have the correct user name and password.
  • You backed up your database before you started the upgrade process. For information about backing up databases, see your database vendor documentation.
  • You ensured that the Java Database Connectivity (JDBC) driver is installed, and you are using sqljdbc4.jar. The Rational solution for CLM 5.0.1 no longer supports JRE version 5.0. Only JRE version 6.0 and 7.0 are supported. The sqljdbc4.jar class library requires JRE 6.0 or later.
  • The SQL service is started.

Important: Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

Learn about licensing: You must obtain new licenses for version 5.0.1 applications. Version 5.0.1 applications will not work with version 4.0.x licenses. However, version 4.0.x applications work with version 5.0.1 licenses. Managing licensing
Check browser compatibility:
  • Enable JavaScript in your web browsers so that wizards can be displayed.
  • For web browsers that are used for migrations, make sure that pop-up blockers are disabled.
 
Check your Java Virtual Machine options: Make sure that the Java Virtual Machine has the appropriate heap size setting.
If you run Jazz Team Server in Apache Tomcat as a Windows service, see Running in Apache Tomcat as a Windows service (64-bit).

Abbreviations for applications and directories

These abbreviations refer to applications and installation directories:

Optional: Stage a test environment for the upgrade process

Before you upgrade your production environment, set up a test environment to avoid issues. For more information, see Staging a test environment for the upgrade process.

Record server name, profile name, node name, heap size values, and previously installed application names

During the upgrade you need to know some information about your current environment. Make sure you record the following information.

  1. Log on to WebSphere Application Server Integrated Solutions Console.
  2. Expand Servers > Server types, and then click WebSphere Application Servers.
  3. Record the server name and node name.
  4. Click server1, expand Java and Process Management and then click Process definition > Java Virtual Machine.
  5. Record the values under Initial heap size, Maximum heap size, and Generic JVM arguments.
  6. Expand Applications > Application types, and then click WebSphere Enterprise Application.
  7. Record the names of the following installed applications:
    • Jazz Team Server (jts_war)
    • CLMHelp (clmhelp_war)
    • Admin (admin_war)
    • Change and Configuration Management (ccm_war)
    • Quality Management (qm_war)
    • Requirements Management (rm_war)

Known issue: Base Licenses are not installed with Trial Keys package

Important: If you are upgrading from CLM 4.0.0.x in a distributed environment and you are planning to upgrade and start ONLY Jazz Team Server at this time and other CLM applications at a later time, you must follow these steps to install the appropriate base licenses required by the upgrade. If you are upgrading and starting JTS together with other CLM applications, you do not need to perform these steps.

  1. Make sure Jazz Team Server is installed and started by following the steps outlined in this guide.
  2. Go to Jazz.net and download the ContributedCALs40xCompatible.zip file that contains the required base licenses.
  3. Extract the .zip file into a temp directory.
  4. Log into https://hostname.example.com:9443/jts/admin and click Server > License Key Management.
  5. To upload the missing license files, click Add and then browse for the license files that you extracted in previous step.

    If you will be upgrading the CCM application at a later time, add these licenses:

    • CCM_Data_Collector_Unlocked.jar
    • RTC_BuildSystem_Unlocked.jar
    • RTC_CC-Synchronizer_Unlocked.jar
    • RTC_CQ-Synchronizer_Unlocked.jar

    If you will be upgrading the QM application at a later time, add these licenses:

    • QM_Data_Collector_Unlocked.jar
    • RQM_Connector_Unlocked.jar

    Click Finish.

  6. When you are ready to upgrade the Change and Configuration Management application, log into the Admin web UI and click Server > License Key Management. Delete the following CALs:
    • CCM Data Collector
    • Build System
    • ClearCase Synchronizer
    • ClearQuest Synchronizer
  7. Proceed with upgrading the CCM application.
  8. When you are ready to upgrade the Quality Management application, log into the Admin web UI and click Server > License Key Management. Delete the following CALs:
    • QM Data Collector
    • RQM Connector
  9. Proceed with upgrading the QM application.

Install the Rational solution for CLM version 5.0.1

Install the CLM version 5.0.1 applications, including the trial license keys, but do not run the setup wizard after the installation. For distributed configurations, install the version 5.0.1 applications that correspond to the previously installed applications. For information about installing the server, see Installing by using IBM Installation Manager or Installing by using command-line commands.

Note: In a distributed environment, the trial license keys must only be installed on the JTS server.

Install the CLM version 5.0.1 applications, but do not run the setup wizard. For distributed configurations, install the version 5.0.1 applications that correspond to the previously installed applications. For information about installing the server, see Installing on IBM i using licensed programs.

Optional: Online migration of quality management data

The Quality Management application online migration is an optional upgrade step that is done while the old server is still running. It migrates data in the live repository to reduce the amount of downtime incurred during normal migration. The data is migrated in such a way as to not affect users on the existing server.

Procedure

  1. Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

    The following tables must contain up-to-date database statistics:

    • REPOSITORY.ITEM_STATES
    • REPOSITORY.ITEM_CURRENTS
    • REPOSITORY.ITEM_TYPES
    • LINKS.AUDITABLE_LINK
    • REPOSITORY_ITEM_STATES
    • REPOSITORY_ITEM_CURRENTS
    • REPOSITORY_ITEM_TYPES
    • LINKS_AUDITABLE_LINK

    For information about the DB2 database RUNSTATS command, see the DB2 website.

    For information about the Oracle database DBMS_STATS command, see the Oracle website.

    For information about the SQL Server database Update Statistics command, see the SQL Server website.

  2. On the server on which you installed the new version of the Quality Management application, open a command window and enter the following command to estimate the data to migrate and to evaluate whether the online migration is appropriate for the repository.

    The teamserver.properties parameter must point to an absolute path on the old server.

    cd C:\Program Files\IBM\JazzTeamServer5.0.1\server\
    repotools-qm.bat -onlineMigrateEstimate teamserver.properties=C:\Program Files\IBM\JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0\server\conf\qm\teamserver.properties logFile=repotools_onlineMigrateEstimate.log

    cd /opt/IBM/JazzTeamServer5.0.1/server/
    ./repotools-qm.sh -onlineMigrateEstimate teamserver.properties=/opt/IBM/JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0/server/conf/qm/teamserver.properties logFile=repotools_onlineMigrateEstimate.log

    For more information about the -onlineMigrateEstimate command and its parameters, see Repository tools command for evaluating the online migration process.

  3. To start the online migration enter the following command:

    The teamserver.properties parameter must point to an absolute path on the old server.

    cd C:\Program Files\IBM\JazzTeamServer5.0.1\server\
    repotools-qm.bat -onlineMigrate teamserver.properties=C:\Program Files\IBM\JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0\server\conf\qm\teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

    cd /opt/IBM/JazzTeamServer5.0.1/server/
    ./repotools-qm.sh -onlineMigrate teamserver.properties=/opt/IBM/JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0/server/conf/qm/teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

    For more information about the -onlineMigrate command and its parameters, see Repository tools command for online migration.

You can stop the online migration or revert to a previous state by using other repository tools commands.

To safely stop the online migration at any time, use the -onlineMigrateStop command. For more information, see Repository tools command for stopping online migration.

To revert the database to a previous state, use the -onlineMigrateRevert command. For more information, see Repository tools command for reverting online migration.

Optional: Online migration of change and configuration management data

The Change and Configuration Management application online migration is an optional upgrade step that is done while the old server is still running. It migrates data in the live repository to reduce the amount of downtime incurred during normal migration. The data is migrated in such a way as to not affect users on the existing server.

Procedure

  1. Before you start the Change and Configuration Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

    The following tables must contain up-to-date database statistics:

    • REPOSITORY.ITEM_STATES
    • REPOSITORY.ITEM_CURRENTS
    • REPOSITORY.ITEM_TYPES
    • LINKS.AUDITABLE_LINK
    • REPOSITORY_ITEM_STATES
    • REPOSITORY_ITEM_CURRENTS
    • REPOSITORY_ITEM_TYPES
    • LINKS_AUDITABLE_LINK

    For information about the DB2 database RUNSTATS command, see the DB2 website.

    For information about the Oracle database DBMS_STATS command, see the Oracle website.

    For information about the SQL Server database Update Statistics command, see the SQL Server website.

  2. On the server on which you installed the new version of the Change and Configuration Management application, open a command window and enter the following command to estimate the data to migrate and to evaluate whether the online migration is appropriate for the repository.

    The teamserver.properties parameter must point to an absolute path on the old server.

    cd C:\Program Files\IBM\JazzTeamServer5.0.1\server\
    repotools-ccm.bat -onlineMigrateEstimate teamserver.properties=C:\Program Files\IBM\JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0\server\conf\ccm\teamserver.properties logFile=repotools_onlineMigrateEstimate.log

    cd /opt/IBM/JazzTeamServer5.0.1/server/
    ./repotools-ccm.sh -onlineMigrateEstimate teamserver.properties=/opt/IBM/JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0/server/conf/ccm/teamserver.properties logFile=repotools_onlineMigrateEstimate.log

    For more information about the -onlineMigrateEstimate command and its parameters, see Repository tools command for evaluating the online migration process.

  3. To start the online migration enter the following command:

    The teamserver.properties parameter must point to an absolute path on the old server.

    cd C:\Program Files\IBM\JazzTeamServer5.0.1\server\
    repotools-ccm.bat -onlineMigrate teamserver.properties=C:\Program Files\IBM\JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0\server\conf\ccm\teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

    cd /opt/IBM/JazzTeamServer5.0.1/server/
    ./repotools-ccm.sh -onlineMigrate teamserver.properties=/opt/IBM/JazzTeamServer4.0.0.xJazzTeamServer4.0.1JazzTeamServer4.0.2JazzTeamServer4.0.3JazzTeamServer4.0.4JazzTeamServer4.0.5JazzTeamServer4.0.6JazzTeamServer4.0.7JazzTeamServer5.0/server/conf/ccm/teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

    For more information about the -onlineMigrate command and its parameters, see Repository tools command for online migration.

You can stop the online migration or revert to a previous state by using other repository tools commands.

To safely stop the online migration at any time, use the -onlineMigrateStop command. For more information, see Repository tools command for stopping online migration.

To revert the database to a previous state, use the -onlineMigrateRevert command. For more information, see Repository tools command for reverting online migration.

Back up the WebSphere Application Server profile

Optionally, create a backup of your WebSphere Application Server profile. If the upgrade fails, you can use the backup to restore the profile.

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

  1. Open a command prompt and change to the bin folder of the WebSphere Application Server installation directory. For example, C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\bin.
  2. Enter the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password. Make sure that the directory path to the compressed file exists.
  3. backupConfig.bat Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password

    For example:

    backupConfig.bat C:\WAS_backup\CLM_4.0.0.x_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.1_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.2_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.3_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.4_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.5_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.6_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_4.0.7_profile.zip -username WAS admin -password WAS admin password

    backupConfig.bat C:\WAS_backup\CLM_5.0_profile.zip -username WAS admin -password WAS admin password

    Note: The command shuts down the server before starting the backup process.

    Tip: You can restore the backed-up profile by running the restoreConfig.bat command. For example, restoreConfig.bat C:\WAS_backup\CLM_4.0.0.x_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.1_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.2_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.3_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.4_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.5_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.6_profile.zip restoreConfig.bat C:\WAS_backup\CLM_4.0.7_profile.zip restoreConfig.bat C:\WAS_backup\CLM_5.0_profile.zip

  1. Open a command shell and change to the bin folder of the WebSphere Application Server installation directory. For example, /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
  2. Enter the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password. Make sure that the directory path to the compressed file exists.
  3. Note: The command shuts down the server before starting the backup process.

    ./backupConfig.sh Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password

    For example:

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.0.x_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.1_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.2_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.3_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.4_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.5_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.6_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.7_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_5.0_profile.zip -username admin -password password

    Note: The directory path to the compressed file must exist before running the backup command.

    Tip: You can restore the backed-up profile by running the ./restoreConfig.sh command. For example, ./restoreConfig.sh /root/WAS_backup/CLM_4.0.0.x_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.1_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.2_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.3_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.4_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.5_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.6_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.7_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_5.0_profile.zip

  1. Open a command prompt and change to the bin folder of the WebSphere Application Server installation directory. For example, /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/bin.
  2. Enter the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password. Make sure that the directory path to the compressed file exists.
  3. Note: The command shuts down the server before starting the backup process.

    ./backupConfig.sh Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password

    For example:

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.0.x_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.1_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.2_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.3_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.4_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.5_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.6_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_4.0.7_profile.zip -username admin -password password

    ./backupConfig.sh /root/WAS_backup/CLM_5.0_profile.zip -username admin -password password

    Note: The directory path to the compressed file must exist before running the backup command.

    Tip: You can restore the backed-up profile by running the ./restoreConfig.sh command. For example, ./restoreConfig.sh /root/WAS_backup/CLM_4.0.0.x_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.1_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.2_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.3_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.4_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.5_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.6_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_4.0.7_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_5.0_profile.zip

Uninstall the previously installed applications from WebSphere Application Server

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

  1. If you backed up your WebSphere Application Server profile, the command shut down the server. Restart the server.
  2. Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
  3. Click Applications > Application Types > WebSphere enterprise applications.
  4. Click jts_war and then under Detail Properties click Security role to user/group mapping. Write down the security roles mapping for jts_war application. You will use this information to remap the application for its version 5.0.1 counterpart.
  5. Click ccm_war and then under Detail Properties click Security role to user/group mapping. Write down the security roles mapping for ccm_war application. You will use this information to remap the application for its version 5.0.1 counterpart.
  6. Click qm_war and then under Detail Properties click Security role to user/group mapping. Write down the security roles mapping for qm_war application. You will use this information to remap the application for its version 5.0.1 counterpart.
  7. Click the Enterprise Applications link and then stop and uninstall the following installed applications:
    • jts_war
    • clmhelp_war
    • admin_war
    • ccm_war
    • qm_war
    • rm_war
    • converter_war
  8. When you are prompted to save the changes to the master configuration, save them.

Update the JAZZ_HOME and log4j.configuration custom properties

In a distributed topology, you must update JAZZ_HOME and log4j.configuration custom properties on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

  1. Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
  2. Click Servers > Server Types > WebSphere application servers.
  3. Click the server name to open it. The default server name is server1.
  4. Under Server Infrastructure section, click Java and Process Management > Process definition.
  5. Under Additional Properties, click Java Virtual Machine.
  6. Under Additional Properties, click Custom properties.
  7. Click JAZZ_HOME and update its value to file:///5.0.1_install_dir/server/conf. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_5.0.1/server/conf.
  8. Click JAZZ_HOME and update its value to file:///5.0.1_install_dir/server/conf. For example, file:///opt/IBM/JazzTeamServer_5.0.1/server/conf.
  9. Click JAZZ_HOME and update its value to file:///5.0.1_install_dir/server/conf. For example, file:///usr/IBM/JazzTeamServer_5.0.1/server/conf.
  10. Click log4j.configuration and update its value to file:///5.0.1_install_dir/server/conf/startup_log4j.properties. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_5.0.1/server/conf/startup_log4j.properties.
  11. Click log4j.configuration and update its value to file:///5.0.1_install_dir/server/conf/startup_log4j.properties. For example, file:///opt/IBM/JazzTeamServer_5.0.1/server/conf/startup_log4j.properties.
  12. Click log4j.configuration and update its value to file:///5.0.1_install_dir/server/conf/startup_log4j.properties. For example, file:///usr/IBM/JazzTeamServer_5.0.1/server/conf/startup_log4j.properties.
  13. If you are connecting to an Oracle database, ensure that ORACLE_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file.
  14. If you are connecting to SQL Server database, ensure that SQLSERVER_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file.
  15. Save the changes to the master configuration when prompted.

For detailed information, see Setting up a WebSphere Application Server.

Stop WebSphere Application Server

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application
  • Any application that is registered with Jazz Team Server

  1. Open a command prompt and change to the WAS_profile_dir\bin directory.
  2. Enter the following command:
  3. stopServer.bat server1 -user admin_userid -password admin_password

  1. Open a command prompt and change to the WAS_profile_dir/bin directory.
  2. Enter the following command:
  3. ./stopServer.sh server1 -user admin_userid -password admin_password

  1. In QShell, navigate to the old configuration directory, for example, /QIBM/UserData/JazzTeamServer40/server
  2. Enter the following command:
  3. ./serverShutdown.sh profileName wasVersion wasOption adminId adminPwd

In addition to QShell, you can use the CL command. Enter QJTS50/STPJAZZSVR on the 5250 command prompt, then press PF4 to prompt for parameters. The following table shows the default values:

Command name Default value Possible values
WAS PROFILE NAME JTS Name
WAS VERSION V85 V8, V85
WAS OPTION BASE Name
WAS ADMIN USER ID JTSADMIN Name
WAS ADMIN PASSWORD None Name

Clean up the WebSphere Application Server temp directories

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

Remove the application-related contents from the following wscache and temp directories in the profile. Depending on which applications were installed, these directories might be in the profile and can be removed:

  • jts_war
  • ccm_war
  • qm_war
  • rm_war
  • converter_war
  • admin_war
  • clmhelp_war

WAS_profile_dir\wscache location example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\wscache

WAS_profile_dir\temp example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\temp

WAS_profile_dir/wscache location example:

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/wscache

WAS_profile_dir/temp example:

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp

WAS_profile_dir/wscache location example:

usr/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/wscache

WAS_profile_dir/temp example:

usr/IBM/WebSphere/AppServer/profiles/AppSrv01/temp

Note: If the temp directories have files that are deeper than your MAX_PATH characters, usually 100 characters long, when you try to delete the directories, you might get an Access Denied error. For instructions to delete the directories, see the documentation for your operating system.

Clean up the logs directory

In a distributed topology, you must complete the next step on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

Remove the application-related log files form the logs directory in the profile.

WAS_profile_dir\logs location example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs

WAS_profile_dir/logs location example:

/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs

WAS_profile_dir/logs location example:

usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs

Stop the servers

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application
  • Any application that is registered with Jazz Team Server

  1. Open a command prompt and change to the CLM_4.0.0.x_install_dir\server directory.
  2. Open a command prompt and change to the CLM_4.0.1_install_dir\server directory.
  3. Open a command prompt and change to the CLM_4.0.2_install_dir\server directory.
  4. Open a command prompt and change to the CLM_4.0.3_install_dir\server directory.
  5. Open a command prompt and change to the CLM_4.0.4_install_dir\server directory.
  6. Open a command prompt and change to the CLM_4.0.5_install_dir\server directory.
  7. Open a command prompt and change to the CLM_4.0.6_install_dir\server directory.
  8. Open a command prompt and change to the CLM_4.0.7_install_dir\server directory.
  9. Open a command prompt and change to the CLM_5.0_install_dir\server directory.
  10. Enter the following command:
  11. server.shutdown.bat

  1. Open a command shell and change to the CLM_4.0.0.x_install_dir/server directory.
  2. Open a command shell and change to the CLM_4.0.1_install_dir/server directory.
  3. Open a command shell and change to the CLM_4.0.2_install_dir/server directory.
  4. Open a command shell and change to the CLM_4.0.3_install_dir/server directory.
  5. Open a command shell and change to the CLM_4.0.4_install_dir/server directory.
  6. Open a command shell and change to the CLM_4.0.5_install_dir/server directory.
  7. Open a command shell and change to the CLM_4.0.6_install_dir/server directory.
  8. Open a command shell and change to the CLM_4.0.7_install_dir/server directory.
  9. Open a command shell and change to the CLM_5.0_install_dir/server directory.
  10. Enter the following command:
  11. ./server.shutdown

Copy the Derby databases from the CLM version 4.0.0.x CLM version 4.0.1 CLM version 4.0.2 CLM version 4.0.3 CLM version 4.0.4 CLM version 4.0.5 CLM version 4.0.6 CLM version 4.0.7 CLM version 5.0 installation directory

  1. Before copying the Derby database, go to the directory where you just installed the version 5.0.1 applications and delete the Derby repositoryDB directory. Alternatively, you can open a command prompt and enter the following commands to clear the default version 5.0.1 Derby repositoryDB directory:
  2. del /s /f 5.0.1_install_dir\server\conf\jts\derby\repositoryDB
    del /s /f 5.0.1_install_dir\server\conf\ccm\derby\repositoryDB
    del /s /f 5.0.1_install_dir\server\conf\qm\derby\repositoryDB
    del /s /f 5.0.1_install_dir\server\conf\rm\derby\repositoryDB
    rm -rf 5.0.1_install_dir/server/conf/jts/derby/repositoryDB
    rm -rf 5.0.1_install_dir/server/conf/ccm/derby/repositoryDB
    rm -rf 5.0.1_install_dir/server/conf/qm/derby/repositoryDB
    rm -rf 5.0.1_install_dir/server/conf/rm/derby/repositoryDB
  3. Go to the directory where you previously installed the CLM applications, copy the Derby database, and paste it in the equivalent directory for version 5.0.1. You can also open a command prompt and enter the following commands to copy the Derby database.

    Starting from version 5.0, the Requirements Management application uses its own database for data storage. In previous versions, the requirements management data was shared with Jazz Team Server database. To use your requirements management data, you must copy your previous Jazz Team Server database.

  4. Note: The following commands work if you are using the Derby database that is provided with the packaged product. If you changed your Derby database location, update the path accordingly.

    xcopy /s CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir\server\conf\jts\derby\repositoryDB 5.0.1_install_dir\server\conf\jts\derby\repositoryDB
    xcopy /s CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir\server\conf\jtsrm\derby\repositoryDB 5.0.1_install_dir\server\conf\rm\derby\repositoryDB
    xcopy /s CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir\server\conf\jts\derby\warehouseDB 5.0.1_install_dir\server\conf\jts\derby\warehouseDB
    xcopy /s CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir\server\conf\ccm\derby\repositoryDB 5.0.1_install_dir\server\conf\ccm\derby\repositoryDB
    xcopy /s CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir\server\conf\qm\derby\repositoryDB 5.0.1_install_dir\server\conf\qm\derby\repositoryDB

    In a WebSphere Application Sever deployment, the default database location is under WebSphere installation.

    xcopy /s WAS_install_dir\OldAppServerHostIntall\jts\derby\conf\repositoryDB WAS_install_dir\AppServerHost5Intall\jts\derby\conf\repositoryDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\jtsrm\derby\conf\repositoryDB WAS_install_dir\AppServerHost5Intall\rm\derby\conf\repositoryDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\jts\derby\conf\warehouseDB WAS_install_dir\AppServerHost5Intall\jts\derby\conf\warehouseDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\ccm\derby\conf\repositoryDB WAS_install_dir\AppServerHost5Intall\ccm\derby\conf\repositoryDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\qm\derby\conf\repositoryDB WAS_install_dir\AppServerHost5Intall\qm\derby\conf\repositoryDB
    cp -R CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/jts/derby/repositoryDB 5.0.1_install_dir/server/conf/jts/derby/repositoryDB
    cp -R CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/jtsrm/derby/repositoryDB 5.0.1_install_dir/server/conf/rm/derby/repositoryDB
    cp -R CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/jts/derby/warehouseDB 5.0.1_install_dir/server/conf/jts/derby/warehouseDB
    cp -R CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/ccm/derby/repositoryDB 5.0.1_install_dir/server/conf/ccm/derby/repositoryDB
    cp -R CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/qm/derby/repositoryDB 5.0.1_install_dir/server/conf/qm/derby/repositoryDB

    In a WebSphere Application Sever deployment, the default database location is under WebSphere installation.

    cp -R WAS_install_dir/OldAppServerHostIntall/jts/derby/conf/repositoryDB WAS_install_dir/AppServerHost5Intall/jts/derby/conf/repositoryDB
    cp -R WAS_install_dir/OldAppServerHostIntall/jtsrm/derby/conf/repositoryDB WAS_install_dir/AppServerHost5Intall/rm/derby/conf/repositoryDB
    cp -R WAS_install_dir/OldAppServerHostIntall/jts/derby/conf/warehouseDB WAS_install_dir/AppServerHost5Intall/jts/derby/conf/warehouseDB
    cp -R WAS_install_dir/OldAppServerHostIntall/ccm/derby/conf/repositoryDB WAS_install_dir/AppServerHost5Intall/ccm/derby/conf/repositoryDB
    cp -R WAS_install_dir/OldAppServerHostIntall/qm/derby/conf/repositoryDB WAS_install_dir/AppServerHost5Intall/qm/derby/conf/repositoryDB

Copy the Jazz Team Server database

Starting in version 5.0, the Requirements Management (RM) application uses its own database for data storage. In earlier versions, the RM data is shared with the Jazz Team Server database. To use your RM data, you must copy your existing Jazz Team Server database.

Be sure to make a note of your new RM database connection URL. When you run the RM script, you are prompted to enter the database location when you enter the JDBC location.

To create a copy of the Jazz Team Server database to use as the RM application database, you back up your Jazz Team Server database and restore it into the RM database

Before you begin

  • You must know the name of the Jazz Team Server database that was created in the previous installation. If you do not know the name of the Jazz Team Server database, before you continue, contact an administrator.
  • The backup directory that you use in the command must exist.

Procedure

  1. Copy the Jazz Team Server database by opening a DB2 command window and entering this command. Replace JTS with your database name:

    db2 backup database JTS to /home/db2inst1/sqllib/backup

    db2 backup database JTS to C:\DB2_backup

  2. Restore the backup into a new database named RM by entering this command:

    db2 restore database JTS from /home/db2inst1/sqllib/backup into RM

    db2 restore database JTS from C:\DB2_backup into RM

To copy the Jazz Team Server data and use it for the Requirements Management application, you create empty tablespaces, export the user's schema and then import it with some remapping options:

Before you begin:

  • You must have SYSTEM or SYSDBA privileges on the computer that you are upgrading the Requirements Management application.
  • You must know the name of the Oracle user that was created for JTS tablespace in the previous installation. If you do not know this value, before you continue, contact an administrator.

Procedure

  1. Open an SQL *Plus windows and log in as SYSTEM or SYSDBA.
  2. To create a tablespace for the Requirements Management application, enter the following command. Replace RM with the tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with your CLM database name, and RM.DBF with the datafile name that you want to create.

    CREATE TABLESPACE RM
    DATAFILE 'ORACLE_BASE/oradata/CLMDB/RM.DBF'
    SIZE 1G AUTOEXTEND ON EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

  3. To create a temporary tablespace, enter the following command. Replace RM_TEMP with the temporary tablespace name, ORACLE_BASE with the absolute path where Oracle is installed, CLMDB with your CLM database name, and RM_TEMP.DBF with the datafile name that you want to create.

    CREATE TEMPORARY TABLESPACE RM_TEMP
    TEMPFILE 'ORACLE_BASE/oradata/CLMDB/RM_TEMP.DBF'
    SIZE 20M AUTOEXTEND ON EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

  4. After the tablespaces are created, a special Oracle user must be created for the Requirements Management application to use the Oracle database. The Oracle database user must be able to create database objects in its tablespace (either unlimited or with a space quota) with privileges to create session, table, procedure, and views. Enter the following commands to create the RM_DB_USER and to grant the required permissions:

    CREATE USER RM_DB_USER IDENTIFIED BY Passw0rd DEFAULT TABLESPACE RM QUOTA UNLIMITED ON RM TEMPORARY TABLESPACE RM_TEMP;

    GRANT CREATE PROCEDURE, CREATE SESSION, CREATE TABLE, CREATE VIEW TO RM_DB_USER;

  5. Create a temporary dump directory with enough disk space to export the JTS data:

    CREATE DIRECTORY dump_dir AS 'C:\ORACLE\temp\dump_dir/opt/ORACLE/tmp/dump_dir';

  6. Open a command window and change the directory to ORACLE_BASE/BIN. When prompted, enter the user name and password.
  7. Enter the following command to export the JTS tablespace.

    expdp DIRECTORY=dump_dir schemas=JTS_DB_USER dumpfile=exp_schema_jts_db_user.dmp logfile=exp_schema_jts_user.log

  8. Enter the following command to import the data with remap_schema and remap_tablespace options. Enter the user name and password when prompted.

    impdp DIRECTORY=dump_dir dumpfile=exp_schema_jts_db_user.dmp logfile=imp_schema_jts_db_user_2remaps.log remap_schema=JTS_DB_USER:RM_DB_USER remap_tablespace=JTS:RM

    Note: If your Oracle version is 11.2.0.3 or earlier, you might get the following warnings which can be safely ignored:
    ORA-31684: Object type USER:"RM_DB_USER" already exists
    ORA-39082: Object type VIEW:"RM_DB_USER"."COMMON_SNAPSHOT_SMPL_ITER" created with compilation warnings
    ORA-39082: Object type VIEW:"RM_DB_USER"."REPOSITORY_SNAPSHOT_LATEST" created with compilation warnings
    ORA-39082: Object type VIEW:"RM_DB_USER"."REPOSITORY_CONTRIBUTOR" created with compilation warnings


    The only view that is required by the Requirements Management application is REPOSITORY_CONTRIBUTOR. This view will be automatically recreated correctly during the repotools-rm -addTables command.

You can use the Copy Database Wizard to copy your Jazz Team Server database. You can also use the Wizard to upgrade your SQL Server 2008 to SQL Server 2012. Because CLM version 5.0.1 does not support SQL Server 2008, you must first upgrade to SQL Server 2012 before upgrading CLM applications.

Before you begin

  • You must be a member of the sysadmin fixed server role.
  • You must have the SQL Server Authentication user name and password.
  • Ensure that SQL Server Agent is started.

Procedure

  1. In SQL Server Management Studio, in Object Explorer, expand Databases, right-click the JTS database, point to Tasks, and then click Copy Database.
  2. From the Select a Source Server page, enter the server and login information for the server with the JTS database to copy. Click Next.
  3. From the Select a Destination Server page, specify the location where the database will be copied. Click Next.
  4. From the Select a Transfer Method page, select the desired transfer method.
  5. From the Select Database page, select the JTS database to copy. Click Next.
  6. From the Configure Destination Database page, change the database name to RM.
  7. From the Select Database Objects page, select the objects to include in the copy operation. This page is only available when the source and destination are different servers.
  8. From the Location of Source Database Files page, specify a file system share that contains the database files on the source server. This is required if the source and destination server instances are on different computers.
  9. The Copy Database Wizard creates a SSIS package to transfer the database from the Configure the Package page, customize the package if appropriate.
  10. From the Schedule the Package page, select Run immediately to start the copy operation after you click Next.
  11. From the Complete the Wizard page, review the summary of the selected options. Click Back to change an option. Click Finish to create the database. During the transfer, the Performing operation page monitors status information about the execution of the Copy Database Wizard.

To create a copy of the Jazz Team Server database to use as the Requirements Management application database, you use the repotools command to export your JTS database and then import it into a new RM database.

Procedure

  1. In a QShell environment enter the following command to export the Jazz Team Server database:

    cd /QIBM/UserData/JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server
    ./repotools-jts.sh -export toFile=jtsdb.tar

  2. Enter this command to copy the Jazz Team Server teamserver.properties file into a new file called rm.teamserver.properties:

    cp conf/jts/teamserver.properties conf/jts/rm.teamserver.properties

  3. Open conf/jts/rm.teamserver.properties and change the com.ibm.team.repository.db.db2i.schema.name value with the new RM database schema name, for example, JAZZRMDB.
  4. Enter this command to import the Jazz Team Server database from the .tar file:

    ./repotools-jts.sh -import fromFile=jtsdb.tar teamserver.properties=conf/jts/rm.teamserver.properties

Note: You must use rm.teamserver.properties during the RM upgrade.

Verify the index locations

Note: The indexing feature was enhanced in version 4.0.3 and later. You are not required to perform the following steps if you are upgrading from version 4.0.3 or later, the path to the index location in the .properties file is relative, and indexes are not located in the WebSphere Application Server profile directory.

To automatically copy the index files during the upgrade, before you start the upgrade verify that the index locations in the application's .properties files are pointing to absolute paths on the file system, rather than relative paths.

  1. For Jazz Team Server, go to CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/jts and open teamserver.properties file for editing.
  2. For Change and Configuration Management application, go to CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/ccm and open teamserver.properties file for editing.
  3. For Quality Management application, go to CLM_4.0.0.x_install_dirCLM_4.0.1_install_dirCLM_4.0.2_install_dirCLM_4.0.3_install_dirCLM_4.0.4_install_dirCLM_4.0.5_install_dirCLM_4.0.6_install_dirCLM_4.0.7_install_dirCLM_5.0_install_dir/server/conf/qm and open teamserver.properties file for editing.
  4. Search for the com.ibm.team.fulltext.indexlocation line.
  5. If the location is a relative path, for example, com.ibm.team.fulltext.indexLocation=conf/jts/indices/workitemindex, the indices might be located relative to the WebSphere Application Server profile hosting the applications. Check your WebSphere Application Server profile directory and if the indices are located there, change the location to an absolute path to ensure that the script can find the index files for copying during the upgrade. If the path is absolute, you do not need to change it. During the upgrade, after the properties are merged, the teamserver.properties file will be opened for preview and at that time, you will have the opportunity to modify the path to a stable location on your drive:
    • For Jazz Team Server, enter com.ibm.team.fulltext.indexLocation=WAS_Install_Dir/AppServer/profiles/AppSrv01/conf/jts/indices/workitemindex where WAS_Install_Dir is the WebSphere Application Server installation directory and AppSrv01 is the application server profile name.
    • For Change and Configuration Management application, enter com.ibm.team.fulltext.indexLocation=WAS_Install_Dir/AppServer/profiles/AppSrv01/conf/ccm/indices/workitemindex where WAS_Install_Dir is the WebSphere Application Server installation directory and AppSrv01 is the application server profile name.
    • For Quality Management application, enter com.ibm.team.fulltext.indexLocation=WAS_Install_Dir/AppServer/profiles/AppSrv01/conf/qm/indices/workitemindex where WAS_Install_Dir is the WebSphere Application Server installation directory and AppSrv01 is the application server profile name.
  6. During the upgrade, after the properties are merged, the script opens the version 5.0.1 teamserver.properties file so that you can preview the properties. In the version 5.0.1 teamserver.properties file, change the location of the index files to an absolute path of a stable location on your drive. A stable location is a directory that will not be deleted when an application is uninstalled. The absolute stable location should look like this example:
    • com.ibm.team.fulltext.indexLocation=JTS_5.0.1_install_dir/server/conf/jts/indices/workitemindex where JTS_5.0.1_install_dir is the location where Jazz Team Server 5.0.1 application is installed.
    • com.ibm.team.fulltext.indexLocation=CCM_5.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_5.0.1_install_dir is the location where Change and Configuration Management 5.0.1 application is installed.
    • com.ibm.team.fulltext.indexLocation=QM_5.0.1_install_dir/server/conf/qm/indices/workitemindex where QM_5.0.1_install_dir is the location where Quality Management 5.0.1 application is installed.
    The script then copies the indexes from the previous installation location to the new version 5.0.1 stable directory.

Copy the index files

Attention: Do these steps only if the index files in the teamserver.properties files are located on relative paths or on absolute paths to unstable directories. An example of an unstable directory is old_install_dir. If the index files are in that directory and the directory is uninstalled, you will lose your index files.

Copy your JFS/text indices from previous installation directory to 5.0.1. For distributed systems go to the appropriate server and copy the files.

  1. Open a command prompt and enter this command to clear the default version 5.0.1 indices directory:
  2. Del /s /f JTS_5.0.1_install_dir\server\conf\jts\indices
    Del /s /f CCM_5.0.1_install_dir\server\conf\ccm\indices
    Del /s /f QM_5.0.1_install_dir\server\conf\qm\indices
    Del /s /f RM_5.0.1_install_dir\server\conf\rm\indices
    rm -rf JTS_5.0.1_install_dir/server/conf/jts/indices
    rm -rf CCM_5.0.1_install_dir/server/conf/ccm/indices
    rm -rf QM_5.0.1_install_dir/server/conf/qm/indices
    rm -rf RM_5.0.1_install_dir/server/conf/rm/indices
  3. Open a command prompt and enter this command to copy the indices from the previous installation to version 5.0.1:
  4. copy JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf\jts\indices JTS_5.0.1_install_dir\server\conf\jts\indices
    copy CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf\ccm\indices CCM_5.0.1_install_dir\server\conf\ccm\indices
    copy QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf\qm\indices QM_5.0.1_install_dir\server\conf\qm\indices
    copy RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir\server\conf\jtsrm\indices RM_5.0.1_install_dir\server\conf\rm\indices
    cp -R JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf/jts/indices JTS_5.0.1_install_dir/server/conf/jts/indices
    cp -R CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf/ccm/indices CCM_5.0.1_install_dir/server/conf/ccm/indices
    cp -R QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf/qm/indices QM_5.0.1_install_dir/server/conf/qm/indices
    cp -R RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf/jtsrm/indices RM_5.0.1_install_dir/server/conf/rm/indices

To copy your JFS/text indices from a previous installation to version 5.0.1, follow these steps. For distributed systems, go to the appropriate server and copy the files.

  1. Open a command prompt and enter this command to clear the default version 5.0.1 indices directory:
  2. Del /s /f JTS_5.0.1_install_dir\server\conf\jts\indices
    Del /s /f CCM_5.0.1_install_dir\server\conf\ccm\indices
    Del /s /f QM_5.0.1_install_dir\server\conf\qm\indices
    Del /s /f RM_5.0.1_install_dir\server\conf\rm\indices
    rm -rf JTS_5.0.1_install_dir/server/conf/jts/indices
    rm -rf CCM_5.0.1_install_dir/server/conf/ccm/indices
    rm -rf QM_5.0.1_install_dir/server/conf/qm/indices
    rm -rf RM_5.0.1_install_dir/server/conf/rm/indices
  3. Open the teamserver.properties file for each application and search for com.ibm.team.fulltext.indexlocation.
  4. If the property com.ibm.team.fulltext.indexlocation is pointing to a relative path, for example, com.ibm.team.fulltext.indexLocation=conf/ccm/indices/workitemindex, depending on how the previous version of the application was installed or customized, the full text indices might be located relative to the WebSphere Application Server profile hosting the applications. For example: WAS_install_dir/AppServer/profiles/Appsrv01, or relative to the application's installation directory.

    Change this relative path to an absolute path to a stable location in the CLM 5.0.1 application's teamserver.properties file. An example of absolute stable location looks like this: com.ibm.team.fulltext.indexLocation=5.0.1_install_dir/server/conf/ccm/indices/workitemindex where 5.0.1_install_dir is the location where CLM 5.0.1 application is installed.

    If the com.ibm.team.fulltext.indexlocation property is pointing to a unstable absolute path, such as path to the old_install_dir directory that might be uninstalled and deleted, change the path to an absolute path that points to a stable location.

    An example of an absolute stable location looks like this example: com.ibm.team.fulltext.indexLocation=5.0.1_install_dir/server/conf/ccm/indices/workitemindex, where 5.0.1_install_dir is the location where the CLM version 5.0.1 application is installed.

    Open a command prompt and enter the following command to copy the full text indices from previous version to 5.0.1. Change the source directory according to the location of the index files:

  5. copy JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf\jts\indices JTS_5.0.1_install_dir\server\conf\jts\indices
    copy CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf\ccm\indices CCM_5.0.1_install_dir\server\conf\ccm\indices
    copy QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf\qm\indices QM_5.0.1_install_dir\server\conf\qm\indices
    copy RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir\server\conf\jtsrm\indices RM_5.0.1_install_dir\server\conf\rm\indices
    cp -R JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf/jts/indices JTS_5.0.1_install_dir/server/conf/jts/indices
    cp -R CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf/ccm/indices CCM_5.0.1_install_dir/server/conf/ccm/indices
    cp -R QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf/qm/indices QM_5.0.1_install_dir/server/conf/qm/indices
    cp -R RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf/jtsrm/indices RM_5.0.1_install_dir/server/conf/rm/indices

Run the upgrade Repository Tools commands

Upgrading Jazz Team Server

To upgrade Jazz Team Server configuration files, go to the JTS_5.0.1_install_dir/server and run the following commands:

If the path contains spaces, make sure that the path is enclosed in double-quotation marks.

repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf

repotools-jts.bat -addTables

repotools-jts.bat -upgradeWarehouse

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. For more information, see Migrating the data warehouse.

repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf updateTomcatFiles=no

repotools-jts.bat -addTables

repotools-jts.bat -upgradeWarehouse

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. For more information, see Migrating the data warehouse.

./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf

./repotools-jts.sh -addTables

./repotools-jts.sh -upgradeWarehouse

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. For more information, see Migrating the data warehouse.

./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf updateTomcatFiles=no

./repotools-jts.sh -addTables

./repotools-jts.sh -upgradeWarehouse

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. For more information, see Migrating the data warehouse.

Upgrading the Change and Configuration Management application

To upgrade the CCM application configuration files, go to the CCM_5.0.1_install_dir/server and run these commands:

The default application context root is jazz. If your upgrade path originated from a release of version 3 or 4, use the applicationContextRoot=ccm switch in the command.

If the path contains spaces, make sure that the path is enclosed in double-quotation marks.

repotools-ccm.bat -migration_ccm_updateConfigurationFiles oldApplicationHome=CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=ccm

repotools-ccm.bat -addTables

repotools-ccm.bat -migration_ccm_updateConfigurationFiles oldApplicationHome=CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=ccm updateTomcatFiles=no

repotools-ccm.bat -addTables

./repotools-ccm.sh -migration_ccm_updateConfigurationFiles oldApplicationHome=CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=ccm

./repotools-ccm.sh -addTables

./repotools-ccm.sh -migration_ccm_updateConfigurationFiles oldApplicationHome=CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=ccm updateTomcatFiles=no

./repotools-ccm.sh -addTables

Upgrading the Quality Management application

Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

The following tables must contain up-to-date database statistics:

  • REPOSITORY.ITEM_STATES
  • REPOSITORY.ITEM_CURRENTS
  • REPOSITORY.ITEM_TYPES
  • LINKS.AUDITABLE_LINK
  • REPOSITORY_ITEM_STATES
  • REPOSITORY_ITEM_CURRENTS
  • REPOSITORY_ITEM_TYPES
  • LINKS_AUDITABLE_LINK

For information about the DB2 database RUNSTATS command, see the DB2 website.

For information about the Oracle database DBMS_STATS command, see the Oracle website.

For information about the SQL Server database Update Statistics command, see the SQL Server website.

To upgrade the QM application configuration files, go to the QM_5.0.1_install_dir/server and run these commands:

The default application context root is jazz. If your upgrade path originated from a release of version 3 or 4, use the applicationContextRoot=qm switch in the command.

If the path contains spaces, make sure that the path is enclosed in double-quotation marks.

repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome=QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=qm

repotools-qm.bat -addTables

repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome=QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=qm updateTomcatFiles=no

repotools-qm.bat -addTables

./repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=qm

./repotools-qm.sh -addTables

./repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=qm updateTomcatFiles=no

./repotools-qm.sh -addTables

The commands that you ran in the previous steps do these tasks:

  • Update the version 5.0.1 teamserver.properties file based on the information from the older version
  • Add tables to the databases
  • Upgrade the data warehouse schema
  • Copy the content of the tomcat-users.xml file.

    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 Jazz Team Server, 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 might have the JazzAdmins role in the CCM application and the JazzUsers role in the QM application. In addition, if users are present in one application but not in the other or vice versa, those users must manually be added to the tomcat-users.xml file.

  • Merge the content of the older version's server.xml and web.xml files with version 5.0.1

For more information about these Repository Tools commands, see these help topics:

Upgrading the Requirements Management application

Procedure

To upgrade the RM application, do these steps:

  1. Open a command window and change the directory to RM_5.0.1_install_dir\serverRM_5.0.1_install_dir/server

    If the path contains spaces, make sure that the path is enclosed in double-quotation marks.

  2. Run this command to update the RM configuration files:
  3. repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=RM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=rm

    repotools-rm.bat -addTables

    repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=RM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=rm updateTomcatFiles=no

    ./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=RM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=rm

    ./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=RM_5.0_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=rm updateTomcatFiles=no

  4. Run this command to add the database tables:
  5. repotools-rm.bat -addTables

    ./repotools-rm.sh -addTables

  • Shut down Jazz Team Server.

To upgrade the Requirements Management (RM) application configuration files, follow these steps:

  1. Run the -migration_rm_updateConfigurationFiles repotools command to merge the existing configuration files to a single teamserver.properties:

    The default application context root is rm. If your upgrade path originated from a release of version 2, use the applicationContextRoot=rdm switch in the command.

    cd RM_5.0.1_Install_Dir\server
    repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir\server\conf ignoreJTSVersionCheck

    cd RM_5.0.1_Install_Dir/server
    ./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf ignoreJTSVersionCheck

    If you are using the Derby database and do not specify the location of the database that you copied in previous step with the db.jdbc.location parameter, the default location will be used. RM50_Install_Dir/server/conf/rm/derby/repositoryDB

    For the complete list of parameters in the -migration_rm_updateConfigurationFiles command, see Repository tools command to update the Requirements Management application configuration files.

  2. Run the -addTables command to update the Jazz Team Server's base schema. This command updates any necessary database schemas and process areas, for example, permissions and runs the actual migration which includes updating the type system, and updating resources like folders.

    repotools-rm.bat -addTables

    ./repotools-rm.sh -addTables

  3. Run the -finalizeApplicationMigration command to complete all necessary offline migration.

    This command removes any Jazz Team Server-specific data from the cloned database and modifies the RM process areas so that the RM server can access them. You must run this command after the -addTable command for the RM application.

    Also when you enter this command with repotools-rm, do not specify the checkOauthDomain, applicationId, or repositoryURL arguments. These arguments must only be specified with repotools-jts in the next step.

    repotools-rm.bat -finalizeApplicationMigration

    ./repotools-rm.sh -finalizeApplicationMigration

    The RM application ID and public URL will be output in the command window. Make a note of them because you will be entering them in a later step. The application ID will also be logged in the repotools-rm_finalizeApplicationMigration.log file.

  4. Run the following command to clean up the RM data from Jazz Team Server.

    Important: Ensure to specify checkOauthDomain and set its value to true. Not specifying this argument or setting its value to false, might prevent you from creating new projects in the /admin page.

    cd JTS50_Install_Dir\server
    repotools-jts.bat -finalizeApplicationMigration checkOauthDomain=true applicationId=RM-application-id repositoryURL=NEW_RM_PUBLIC_URL

    cd JTS50_Install_Dir/server
    ./repotools-jts.sh -finalizeApplicationMigration checkOauthDomain=true applicationId=RM-application-id repositoryURL=NEW_RM_PUBLIC_URL

  5. Run the -reindex command. This step is optional, but recommended. At this point, there are no indexes for RM data. The data will be fully re-indexed when the server is started. To avoid a slow server startup, you can run a manual reindex.

    repotools-rm.bat -reindex all

    ./repotools-rm.sh -reindex all

Run the upgrade script

This script uses Repository Tools commands to update the configuration files and update the databases and data warehouse schemas to version 5.0.1. Follow the on-screen prompts to upgrade your application. For more information, see Upgrade script files.

In a distributed environment where applications are installed on separate servers and you want to upgrade all applications from one server, you must be able to access the drive or file system where other applications are installed. The mounted drive must be configured with read-write-execute privileges for the administrator account. chmod -R 777 /opt/IBM/JazzTeamServer. If you cannot access the shared drives from one server, you must physically go to each server and perform the upgrade. On Windows systems for example, the mount must be in this format: mounted drive letter:\server\conf. An absolute path, such as \\computer name\JTS_5.0.1_install_dir\server\conf, will not work.On UNIX systems for example, the mount must be in this format: mount -t nfs IP Address of the server:/opt/IBM/JazzTeamServer.

Important: Although the script file is in the upgrade/application context root directory, the file must be run from the server directory.

Upgrading Jazz Team Server

To upgrade Jazz Team Server, open a command prompt with administrative privileges, go to the JTS_5.0.1_install_dir\server directory, and enter this command:

upgrade\jts\jts_upgrade.bat -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf

upgrade\jts\jts_upgrade.bat -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf

During the upgrade, after the configuration files are merged, a window opens in which you can check the Jazz Team Server teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled.

An absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=JTS_5.0.1_install_dir/server/conf/jts/indices/workitemindex, where JTS_5.0.1_install_dir is the location where Jazz Team Server 5.0.1 is installed.

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.

Upgrading the Change and Configuration Management application

To upgrade Change and Configuration Management application, open a command prompt with administrative privileges, go to the CCM_5.0.1_install_dir\server directory, and enter this command:

upgrade\ccm\ccm_upgrade.bat -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf

upgrade\ccm\ccm_upgrade.bat -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf

During the upgrade, after the configuration files are merged, a window opens in which you can check the Change and Configuration teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled.

An absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=CCM_5.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_5.0.1_install_dir is the location where Change and Configuration Management application 5.0.1 is installed.

Upgrading the Quality Management application

Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

The following tables must contain up-to-date database statistics:

  • REPOSITORY.ITEM_STATES
  • REPOSITORY.ITEM_CURRENTS
  • REPOSITORY.ITEM_TYPES
  • LINKS.AUDITABLE_LINK
  • REPOSITORY_ITEM_STATES
  • REPOSITORY_ITEM_CURRENTS
  • REPOSITORY_ITEM_TYPES
  • LINKS_AUDITABLE_LINK

For information about the DB2 database RUNSTATS command, see the DB2 website.

For information about the Oracle database DBMS_STATS command, see the Oracle website.

For information about the SQL Server database Update Statistics command, see the SQL Server website.

To upgrade Quality Management application, open a command prompt with administrative privileges, go to the QM_5.0.1_install_dir\server directory, and enter this command:

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf

During the upgrade, after the configuration files are merged, a window opens in which you can check the Quality Management teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=QM_5.0.1_install_dir/server/conf/qm/indices/workitemindex where QM_5.0.1_install_dir is the location where Quality Management application 5.0.1 is installed.

Upgrading the Requirements Management application

To upgrade the Requirements Management application, open a command prompt with administrative privileges, go to the RM_5.0.1_install_dir\server directory, and enter this command:

upgrade\rm\rm_upgrade.bat -oldApplicationHome RM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf

During the upgrade, after the configuration files are merged, a window opens in which you can check the RM teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled.

An absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=RM_5.0.1_install_dir/server/conf/rm/indices/workitemindex, where RM_5.0.1_install_dir is the location where the Requirements Management application version 5.0.1 is installed.

Before you begin

  • Shut down Jazz Team Server.

Procedure

To upgrade Requirements Management application, open a command prompt with administrative privileges, go to the RM_5.0.1_install_dir\server directory, and enter this command:

Note: During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

upgrade\rm\rm_upgrade.bat -oldApplicationHome RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf

At the -migration_rm_updateConfigurationFiles, you will be prompted to enter a database connection with the db.jdbc.location parameter. This is the database that you copied in the earlier step.

During the upgrade, make a note of the RM application ID and public URL. At a later step when cleaning up the existing data from JTS, you will be prompted to enter the RM application ID and public URL. The application ID will also be logged in the repotools-rm_finalizeApplicationMigration.log file.

For a complete list of steps in the rm_upgrade script file, see this Deployment wiki page.

Upgrading Jazz Team Server

To upgrade Jazz Team Server, open a command shell, go to the JTS_5.0.1_install_dir/server directory, and enter this command:

upgrade/jts/jts_upgrade.sh -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf

upgrade/jts/jts_upgrade.sh -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf

During the upgrade, after the configuration files are merged, an editor opens in which you can check the Jazz Team Server teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=JTS_5.0.1_install_dir/server/conf/jts/indices/workitemindex where JTS_5.0.1_install_dir is the location where Jazz Team Server 5.0.1 is installed.

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.

Upgrading the Change and Configuration Management application

To upgrade Change and Configuration Management application, open a command shell, go to the CCM_5.0.1_install_dir/server directory, and enter this command:

upgrade/ccm/ccm_upgrade.sh -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf

upgrade/ccm/ccm_upgrade.sh -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

During the upgrade, after the configuration files are merged, an editor opens in which you can check the Change and Configuration Management teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=CCM_5.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_5.0.1_install_dir is the location where Change and Configuration Management application 5.0.1 is installed.

Upgrading the Quality Management application

Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

The following tables must contain up-to-date database statistics:

  • REPOSITORY.ITEM_STATES
  • REPOSITORY.ITEM_CURRENTS
  • REPOSITORY.ITEM_TYPES
  • LINKS.AUDITABLE_LINK
  • REPOSITORY_ITEM_STATES
  • REPOSITORY_ITEM_CURRENTS
  • REPOSITORY_ITEM_TYPES
  • LINKS_AUDITABLE_LINK

For information about the DB2 database RUNSTATS command, see the DB2 website.

For information about the Oracle database DBMS_STATS command, see the Oracle website.

For information about the SQL Server database Update Statistics command, see the SQL Server website.

To upgrade Quality Management application, open a command shell, go to the QM_5.0.1_install_dir/server directory, and enter this command:

upgrade/qm/qm_upgrade.sh -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf

upgrade/qm/qm_upgrade.sh -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

During the upgrade, after the configuration files are merged, an editor opens in which you can check the Quality Management teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=QM_5.0.1_install_dir/server/conf/qm/indices/workitemindex where QM_5.0.1_install_dir is the location where Quality Management application 5.0.1 is installed.

Upgrading the Requirements Management application

To upgrade the Requirements Management application, open a command shell, go to the RM_5.0.1_install_dir/server directory, and enter this command:

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_5.0_install_dir/server/conf

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

During the upgrade, after the configuration files are merged, an editor opens in which you can check the Requirements Management teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is relative path, you do not need to change the path. If the location is absolute path, make sure the directory is stable and will not be deleted if an application is uninstalled. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=RM_5.0.1_install_dir/server/conf/rm/indices/workitemindex where RM_5.0.1_install_dir is the location where Requirements Management application 5.0.1 is installed.

Before you begin

  • Shut down Jazz Team Server.

Procedure

To upgrade Requirements Management application, open a command shell, go to the RM_5.0.1_install_dir/server directory, and enter this command:

Note: During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

For a complete list of steps in the rm_upgrade script file, see this Deployment wiki page.

Note: The indexing feature was enhanced in version 4.0.3 and later. If you are upgrading from version 4.0.3 or later, you are not required to change the .properties file during the script execution if the path to the index location is relative and indexes are not located in the WebSphere Application Server profile directory.

Upgrading Jazz Team Server

To upgrade Jazz Team Server, open a command prompt with administrative privileges, go to the JTS_5.0.1_install_dir\server directory, and enter this command:

upgrade\jts\jts_upgrade.bat -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf -updateTomcatFiles no

upgrade\jts\jts_upgrade.bat -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir\server\conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, a window opens in which you can check the Jazz Team Server teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=JTS_5.0.1_install_dir/server/conf/jts/indices/workitemindex where JTS_5.0.1_install_dir is the location where Jazz Team Server 5.0.1 is installed.

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.

Upgrading the Change and Configuration Management application

To upgrade Change and Configuration Management application, open a command prompt with administrative privileges, go to the CCM_5.0.1_install_dir\server directory, and enter this command:

upgrade\ccm\ccm_upgrade.bat -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf -updateTomcatFiles no

upgrade\ccm\ccm_upgrade.bat -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, a window opens in which you can verify the Change and Configuration Management application teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=CCM_5.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_5.0.1_install_dir is the location where Change and Configuration Management application 5.0.1 is installed.

Upgrading the Quality Management application

Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

The following tables must contain up-to-date database statistics:

  • REPOSITORY.ITEM_STATES
  • REPOSITORY.ITEM_CURRENTS
  • REPOSITORY.ITEM_TYPES
  • LINKS.AUDITABLE_LINK
  • REPOSITORY_ITEM_STATES
  • REPOSITORY_ITEM_CURRENTS
  • REPOSITORY_ITEM_TYPES
  • LINKS_AUDITABLE_LINK

For information about the DB2 database RUNSTATS command, see the DB2 website.

For information about the Oracle database DBMS_STATS command, see the Oracle website.

For information about the SQL Server database Update Statistics command, see the SQL Server website.

To upgrade Quality Management application, open a command prompt with administrative privileges, go to the QM_5.0.1_install_dir\server directory, and enter this command:

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf -updateTomcatFiles no

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, a window opens in which you can verify the Quality Management application teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=QM_5.0.1_install_dir/server/conf/qm/indices/workitemindex where QM_5.0.1_install_dir is the location where Quality Management application 5.0.1 is installed.

Upgrading the Requirements Management application

To upgrade the Requirements Management application, open a command prompt with administrative privileges, go to the RM_5.0.1_install_dir\server directory, and enter this command:

upgrade\rm\rm_upgrade.bat -oldApplicationHome RM_5.0_install_dir\server\conf -updateTomcatFiles no

upgrade\rm\rm_upgrade.bat -oldApplicationHome RM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, a window opens in which you can verify the Requirements Management application teamserver.properties file. If the location of the com.ibm.team.jfs.index.root.directory property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.jfs.index.root.directory=RM_5.0.1_install_dir/server/conf/rm/indices where RM_5.0.1_install_dir is the location where Requirements Management application 5.0.1 is installed.

Before you begin

  • Shut down Jazz Team Server.

Procedure

To upgrade Requirements Management application, open a command prompt with administrative privileges, go to the RM_5.0.1_install_dir\server directory, and run this command:

Note: During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

upgrade\rm\rm_upgrade.bat -oldApplicationHome RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir\server\conf -newJTSHome JTS_5.0.1_install_dir\server\conf

For a complete list of steps in the rm_upgrade script file, see this Deployment wiki page.

Upgrading Jazz Team Server

To upgrade Jazz Team Server, open a command shell, go to the JTS_5.0.1_install_dir/server directory, and enter this command:

upgrade/jts/jts_upgrade.sh -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf -updateTomcatFiles no

upgrade/jts/jts_upgrade.sh -oldJTSHome JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, an editor opens in which you can check the Jazz Team Server teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=JTS_5.0.1_install_dir/server/conf/jts/indices/workitemindex where JTS_5.0.1_install_dir is the location where Jazz Team Server 5.0.1 is installed.

Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.

Upgrading the Change and Configuration Management application

To upgrade Change and Configuration Management application, open a command shell, go to the CCM_5.0.1_install_dir/server directory, and enter this command:

upgrade/ccm/ccm_upgrade.sh -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf -updateTomcatFiles no

upgrade/ccm/ccm_upgrade.sh -oldApplicationHome CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, an editor opens in which you can verify the Change and Configuration Management application teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=CCM_5.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_5.0.1_install_dir is the location where Change and Configuration Management application 5.0.1 is installed.

Upgrading the Quality Management application

Before you start the Quality Management application upgrade, run statistics to update the database tables. Otherwise, the migration might take several hours.

The following tables must contain up-to-date database statistics:

  • REPOSITORY.ITEM_STATES
  • REPOSITORY.ITEM_CURRENTS
  • REPOSITORY.ITEM_TYPES
  • LINKS.AUDITABLE_LINK
  • REPOSITORY_ITEM_STATES
  • REPOSITORY_ITEM_CURRENTS
  • REPOSITORY_ITEM_TYPES
  • LINKS_AUDITABLE_LINK

For information about the DB2 database RUNSTATS command, see the DB2 website.

For information about the Oracle database DBMS_STATS command, see the Oracle website.

For information about the SQL Server database Update Statistics command, see the SQL Server website.

To upgrade Quality Management application, open a command shell, go to the QM_5.0.1_install_dir/server directory, and enter this command:

upgrade/qm/qm_upgrade.sh -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf -updateTomcatFiles no

upgrade/qm/qm_upgrade.sh -oldApplicationHome QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, an editor opens in which you can verify the Quality Management application teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=QM_5.0.1_install_dir/server/conf/qm/indices/workitemindex where QM_5.0.1_install_dir is the location where Quality Management application 5.0.1 is installed.

Upgrading the Requirements Management application

To upgrade the Requirements Management application, open a command shell, go to the RM_5.0.1_install_dir/server directory, and enter this command:

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_5.0_install_dir/server/conf -updateTomcatFiles no

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf -updateTomcatFiles no

During the upgrade, after the configuration files are merged, an editor opens in which you can verify the Requirements Management application teamserver.properties file. If the location of the com.ibm.team.fulltext.indexlocation property is a relative path in this file, you must change it to an absolute path and make sure the particular directory is stable and will not be deleted if an application is uninstalled. Example of an unstable directory is the old_install_dir that may be uninstalled and you will lose your index files. The absolute stable location should look like this example: com.ibm.team.fulltext.indexLocation=RM_5.0.1_install_dir/server/conf/rm/indices/workitemindex where RM_5.0.1_install_dir is the location where the Requirements Management application 5.0.1 is installed.

Before you begin

  • Shut down Jazz Team Server.

Procedure

To upgrade Requirements Management application, open a command shell, go to the RM_5.0.1_install_dir/server directory, and enter this command:

Note: During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

For a complete list of steps in the rm_upgrade script file, see this Deployment wiki page.

Note: During the upgrade after the "(RM) finalizeApplicationMigration" step is complete, you will see the following message in the command window:

The following application was migrated: APPID000-0000-0000-0000-000000000000. To finalize the migration, on the Jazz Team Server that the application is registered with, run the finalizeApplicationMigration command with the "applicationId=APPID000-0000-0000-0000-000000000000" parameter.

You do not need to stop the script execution at this point to run the command that was described in the message. The next step in the upgrade script "(JTS) finalizeApplicationMigration" runs the command automatically.

upgrade/rm/rm_upgrade.sh -oldApplicationHome RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf -newJTSHome JTS_5.0.1_install_dir/server/conf

For a complete list of steps in the rm_upgrade script file, see this Deployment wiki page.

Note: In version 5.0 and later, Requirements Management indexes are separate from Jazz Team Server and are saved in their own directory.

Note: The log4j.properties files are not merged. If you customized these files in previous versions, you must manually migrate your customized settings over to the new log4j.properties files. If you did not customize these files, no migration is required.

For Chinese and Japanese languages only: Rebuild text indices

In version 4.0.3 and later, full text search has been significantly improved for Chinese and Japanese languages. To take advantage of this improvement, do these steps:

  1. Make sure that your server is running on a Japanese or Chinese locale.
  2. After upgrading and before starting the server, reindex the existing work items:
    1. Open a command prompt and go to CCM_5.0.1_install_dir\serverCCM_5.0.1_install_dir/server.
    2. Enter this command:

      repotools-ccm.bat -rebuildTextIndices

      ./repotools-ccm.sh -rebuildTextIndices

For more information about the rebuildTextIndices command and its usage, see Repository tools command to rebuild text indexes.

Run the upgrade script on IBM i

  1. Log on to IBM i operating system using a user ID that has QSECOFR authority.
  2. In QShell, navigate to the Jazz Team Server 5.0.1 configuration directory /QIBM/UserData/JazzTeamServer50/server.
  3. Enter this command to upgrade Jazz Team Server:

    upgrade/jts/jts_upgrade.sh -oldJTSHome /QIBM/UserData/JTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dirJTS_4.0.3_install_dirJTS_4.0.4_install_dirJTS_4.0.5_install_dirJTS_4.0.6_install_dirJTS_4.0.7_install_dirJTS_5.0_install_dir/server/conf

  4. Enter this command to upgrade Change and Configuration Management application:

    upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /QIBM/UserData/CCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dirCCM_4.0.3_install_dirCCM_4.0.4_install_dirCCM_4.0.5_install_dirCCM_4.0.6_install_dirCCM_4.0.7_install_dirCCM_5.0_install_dir/server/conf

  5. Enter this command to upgrade Quality Management application:

    upgrade/qm/qm_upgrade.sh -oldApplicationHome /QIBM/UserData/QM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dirQM_4.0.3_install_dirQM_4.0.4_install_dirQM_4.0.5_install_dirQM_4.0.6_install_dirQM_4.0.7_install_dirQM_5.0_install_dir/server/conf

  6. Enter this command to upgrade Requirements Management application:

    upgrade/rm/rm_upgrade.sh -oldApplicationHome /QIBM/UserData/RM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dirRM_4.0.3_install_dirRM_4.0.4_install_dirRM_4.0.5_install_dirRM_4.0.6_install_dirRM_4.0.7_install_dirRM_5.0_install_dir/server/conf

  7. Run the next command to update the previous version WebSphere Application Server and deploy the .war files for the version 5.0.1 CLM applications. The command also does a backup, updates the JVM settings, updates the environment variable settings, deletes the temp directories, and restarts the server.

    upgrade/was_upgrade.sh profileName serverName nodeName wasVersion wasOption maxHeapSize adminId adminPwd jvmVersion jazzAppName jtsAppName clmHelpAppName qmAppName rmAppName adminAppName

    Where:

    • profileName is the previous version profile name.
    • serverName is the previous version server name.
    • nodeName is the previous version server node name.
    • wasVersion is the WebSphere Application Server version.
    • wasOption is the WebSphere Application Server option (Base, ND, or Express) you chose for the Jazz Team Server 3.0.1 server on IBM i.
    • maxHeapSize is the maximum heap size you need for the application server.
    • adminId and adminPwd are the ID and password you used to secure the WebSphere Application Server on IBM i.
    • jvmVersion is the Java Virtual Machine (JVM) version (std64 for V6R1 /V7R1).
    • jazzAppName is the name of Change and Configuration Management application.
    • jtsAppName is the name of Jazz Team Server.
    • qmAppName is the name of Quality Management application.
    • rmAppName is the name of Requirements Management application.
    • clmHelpAppName is the name of the CLM help application.
    • adminAppName is the name of the Lifecycle Project Administration application.

Start the WebSphere Application Server

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application
  • Any application that is registered with Jazz Team Server

Note: On Linux systems, an error might occur when you start the Requirements Management (RM) server from a command line (headless mode). For troubleshooting, see Fixing a converter issue while using the server in headless mode on a Linux system.

Before you begin: Make sure that you switched your JDBC environment variable to point to the JRE6 JDBC driver. For more information, see Setting up an Oracle database.

Before you begin: Make sure that you switched your JDBC environment variable to point to the JRE6 JDBC driver. For more information, see Setting up an SQL Server database.

  1. Open a command prompt and change to the WAS_profile_dir\bin directory.
  2. Enter this command:
  3. startServer.bat server1

  1. Open a command prompt and change to the WAS_profile_dir/bin directory.
  2. Enter this command:
  3. ./startServer.sh server1

Deploy the version 5.0.1 WAR files in WebSphere Application Server

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

WAR file locations: If you used Installation Manager to install the CLM applications, and during the installation you cleared the check box for the Tomcat 7 application server, the WAR files were copied into the 5.0.1_install_dir/server/webapps directory by default. If you selected the Tomcat 7 application server, the WAR files were copied into the 5.0.1_install_dir/server/tomcat/webapps directory.

  1. Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp.
  2. Click Applications > Applications Types > WebSphere enterprise applications.
  3. Install the following web applications:
    • jts_war
    • ccm_war
    • qm_war
    • rm_war
    • converter_war
    • clmhelp_war
    • admin_war
  4. Map the security roles appropriately for:
    • jts_war
    • ccm_war
    • qm_war

For detailed information, see Deploying CLM applications on WebSphere Application Server.

Important: If you work in an environment such as AIX or Solaris that does not support converter, you must install the 5.0.1 version of the converter.war on the dedicated converter server. For detailed information, see the Delegated Configuration section of the Requirements Management Converter Application Configuration and Troubleshooting Guide.

Note: If you want to install the 5.0.1 version of the converter.war file on the dedicated converter server, see the Delegated Configuration section of the Requirements Management Converter Application Configuration and Troubleshooting Guide.

Start the applications

On the Enterprise Applications page, start these applications:

In a distributed topology, you must complete the next step on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application

Log on to the Integrated Solutions Console and start these applications:

  • jts_war
  • ccm_war
  • qm_war
  • rm_war
  • converter_war
  • admin_war
  • clmhelp_war

Update the instance of Tomcat Windows service

If you used a Windows service to start the Apache Tomcat server, you must update or delete the old service and create a new one to use the upgraded Tomcat location. For information about running the server as a Windows service, see Configuring Apache Tomcat server to run as a Windows service.

Start the servers

In a distributed topology, you must complete the next steps on the application server that hosts:

  • Jazz Team Server
  • Change and Configuration Management application
  • Quality Management application
  • Requirements Management application
  • Any application that is registered with Jazz Team Server

Before you begin: Make sure that you switched your JDBC environment variable to point to the JRE6 JDBC driver. For more information, see Setting up an Oracle database.

Before you begin: Make sure that you switched your JDBC environment variable to point to the JRE6 JDBC driver. For more information, see Setting up an SQL Server database.

Start all of the version 5.0.1 application servers:

  1. Open a command prompt and change to the 5.0.1_install_dir\server directory.
  2. Enter this command:
  3. server.startup.bat

  1. Open a command prompt and change to the 5.0.1_install_dir/server directory.
  2. Enter this command:
  3. ./server.startup

Update project associations

After your Requirements Management application is upgraded and all servers are started, including Jazz Team Server and all associated CLM applications, run the following repotools command to update the project associations.

  1. Open a command window and enter this command:
  2. cd 5.0.1_install_dir\server
    repotools-rm.bat -rmUpdateProjectBacklinksOnline adminUserId=admin_user_id adminPassword=admin_password repositoryURL=RM_repository_URL

  1. Open a command shell and enter this command:
  2. cd 5.0.1_install_dir/server
    ./repotools-rm.sh -rmUpdateProjectBacklinksOnline adminUserId=admin_user_id adminPassword=admin_password repositoryURL=RM_repository_URL

For more information about the -rmUpdateProjectBacklinksOnline command, see Repository tools command for updating project associations against a live server.

Obtain licenses

You must obtain new licenses for version 5.0.1 applications. Version 5.0.1 applications do not work with version 4.0.x licenses. However, version 4.0.x applications work with version 5.0.1 licenses.

If you previously used floating, token, or authorized user single install licenses, install their version 5.0.1 counterparts. Your existing user license assignments will be kept during installation of version 5.0.1 licenses.

To update your token licenses:

  1. Log into https://hostname.example.com:9443/jts/admin and click Server > License Key Management.
  2. In the Floating License Server section, click Add and upload your version 5.0.1 license file.
  3. After upload is complete, there will be 2 entries in the Floating License Server section. Hover over the version 4.x license entry and click the red X icon to delete the entry. If a warning message is shown, click OK.
  4. Go to Users > Client Access License Management, select a token license, and confirm that the list of users that had the version 4.x licenses is present.

For more information about licenses, see Managing licenses.

Upgrade Rational Reporting for Development Intelligence (RRDI)

Note: Before you upgrade Rational Reporting for Development Intelligence, you must upgrade the Rational solution for CLM. You do not need to upgrade the data warehouse with Rational Reporting for Development Intelligence because it is upgraded during the CLM upgrade.

For upgrading RRDI version 1.0.xversion 2.0.x to version 5.0.1, make sure to follow the steps in the Pre-upgrade tasks, then see Upgrading Rational Reporting for Development Intelligence from version 1.0.x to version 5.0.1Upgrading Rational Reporting for Development Intelligence from version 2.0.x to version 5.0.1.

For information about version compatibility between RRDI and CLM, see Upgrading Rational Reporting for Development Intelligence.

After you upgrade to version 5.0.1 of Rational Reporting for Development Intelligence, download the latest report samples and resources and load them to the report server. For complete instructions, see Upgrading reporting artifacts.

Rational Insight users: If you use Rational Insight, you must upgrade the data warehouse by running the Rational Insight migrateDW command first, followed by the repotools-jts -upgradeWarehouse command. The migrateDW command will upgrade all the schemas in the data warehouse except for the RICALM schema. It is also capable of handling schemas that have been customized. After running the migrateDW command, run the repotools-jts -upgradeWarehouse command to upgrade the RICALM schema.

Redeploying predefined templates

A project template called Base in previous versions was renamed to Requirements Templates for Testers in version 5.0.1. To continue using this template after upgrade, you must update the lifecycle project templates. For detailed information, see Creating lifecycle projects from a template.

Configure data warehouse

If you did not configure the data warehouse in your previous installation and want to configure a data warehouse for version 5.0.1, follow these steps:

  1. Create a database to use as your data warehouse. For more information, see Setting up the database.
  2. Run the setup wizard, skip to the configuring the data warehouse step, and configure the data warehouse. For more information, see Configuring or changing the data warehouse after you have configured the Jazz Team Server.

    Note: You do not have to run the setup wizard to set up the version 5.0.1 server. The setup wizard is needed only if you did not configure the data warehouse in the previous installation and now want to configure it.

Verify the upgrade

After the upgrade process is complete, use this checklist to determine whether each step was successful.

  Verification task More information
Verify that these application configuration files are copied from previous installation to version 5.0.1:
  • For Jazz Team Server: JTS_5.0.1_install_dir/server/conf/jts/teamserver.properties
  • For the Change and Configuration Management application: CCM_5.0.1_install_dir/server/conf/ccm/teamserver.properties
  • For the Quality Management application: QM_5.0.1_install_dir/server/conf/qm/teamserver.properties
  • For the Requirements Management application: RM_5.0.1_install_dir/server/conf/qm/teamserver.properties
  • For the Lifecycle Project Administration application: JTS_5.0.1_install_dir/server/conf/admin/admin.properties
  • For the Lifecycle Project Administration application: JTS_5.0.1_install_dir/server/conf/admin/friends.rdf
 
Verify that each teamserver.properties file contains this information:
  • The properties that were copied from the previous version of the teamserver.properties file.
  • A valid, distinct URL in the com.ibm.repository.server.webapp.url property. The URL for the version 5.0.1 application must be the same as the one that was used in the previous version.
  • Valid database vendor entries. Make sure that the database that is specified in the /conf/jts/teamserver.properties file exists.
 
Verify the application servers:
  • Verify that 5.0.1_install_dir/server/tomcat/conf/tomcat-users.xml contains the information from previous version.
  • If you are using an LDAP registry or you disabled HTTPS or FORM authentication, verify this information:
    • The 5.0.1_install_dir/server/tomcat/conf/server.xml file contains these code snippets:

      <Realm className=org.apache.catalina.realm.JNDIRealm
      ...>
      </Realm>

    • The 5.0.1_install_dir/server/tomcat/conf/server.xml file does not contain these code snippets:

      Realm className=org.apache.catalina.realm.UserDatabaseRealm
      resourceName=UserDatabase
      ...>
      </Realm>

  • If you had other custom settings in the 4.0.0.x_install_dir4.0.1_install_dir4.0.2_install_dir4.0.3_install_dir4.0.4_install_dir4.0.5_install_dir4.0.6_install_dir4.0.7_install_dir5.0_install_dir/server/tomcat/conf/server.xml file, verify that those settings are copied to the 5.0.1_install_dir/server/tomcat/conf/server.xml file.
  • Verify that web.xml file has the correct <security-role> tags:
    • For Jazz Team Server: 5.0.1_install_dir/server/tomcat/webapps/jts/WEB-INF/web.xml
    • For Change and Configuration Management application: 5.0.1_install_dir/server/tomcat/webapps/ccm/WEB-INF/web.xml
    • For Quality Management application: 5.0.1_install_dir/server/tomcat/webapps/qm/WEB-INF/web.xml
  • Make sure that these applications are deployed and started:
    • jts.war
    • ccm.war
    • qm.war
    • rm.war
    • converter.war
    • admin.war
    • clmhelp.war
Deploying and starting the server
Check the server log files: Check these server log files to verify that they contain the post-upgrade information:
  • If you are using a Tomcat server, the log files are in the 5.0.1_install_dir/server/logs directory.
  • If you are using a WebSphere Application Server, the log files are in the WAS_install_dir/profiles/AppSrv01/logs directory.
 
Check the public URLs: If you upgraded Jazz Team Server, the CCM application, or the QM application, make sure that the public URL on the application's status summary page is the same as the URL that was used in the previous version.  
Check the links on the Jazz Team Server Administration page: In a web browser, go to the Administration page of Jazz Team Server at https://hostname.example.com:9443/jts/admin and make sure that no errors are displayed. Jazz Team Server administrative web interface
Check the links on the application's Administration page: In a web browser, go to the Administration page of the application at https://hostname.example.com:9443/application context root/admin and make sure that no errors are displayed. Application administrative web interface
Run diagnostics on each server and verify that the diagnostics completed successfully:
  1. Open a browser and log on to the admin page, for example, https://host.example.com:9443/jts/admin
  2. Click the Diagnostics link.
 
Check users, licenses, and link artifacts:
  • Inspect users and licenses
  • Check linked artifacts
  • Check the web client
  • Check indexing by using search
  • Check Rational Team Concert Eclipse or Visual Studio clients
Verifying users, licenses, and link artifacts
Check application artifacts:
  • Check all projects are listed and can be navigated to
  • Check that all dashboards are available and widgets are working
  • Find and view existing artifacts and verify that the editors open properly
  • In Change and Configuration Management application, verify work items and release plans
  • In Quality Management application, verify test plans, test cases, test suites, and test scripts
  • In Requirements Management application, verify requirements, collections, folders, and graphical artifacts
  • In Requirements Management application, verify that you can display and edit graphical artifacts
 
Run the data collection jobs:
  1. Open a browser and log on to the Administration page. The URL for that page is like this example: https://host.example.com:9443/jts/admin.
  2. On the Reports page, click Data Collection Jobs.
  3. Click Run all data warehouse collection jobs for all applications.
  4. Wait for the data collection jobs to complete and verify that the ETLs completed without errors. To monitor the status of each data collection job, you must access the appropriate application URL. For more information about data collection jobs, see Running the data collection jobs.
Running the data collection jobs

Integrating with other products

Rational Developer for System z

Rational Developer for System z integrates with Rational Team Concert on System z to provide z/OS developers an integrated collaborative application development environment. This integrated solution provides the value of the individual development environment of Rational Developer for System z with the team collaboration capabilities of Rational Team Concert. For more information, see Rational Team Concert and Rational Developer for System z.

For instructions on upgrading Rational Developer for System z, see Upgrading the Rational Developer for System z integration.


Rational ClearQuest

Rational Team Concert includes several tools to help you integrate your work with Rational ClearQuest. Rational ClearQuest Synchronizer, Rational ClearQuest Bridge, and Rational ClearQuest Importer. For more information, see Rational Team Concert and Rational ClearQuest.

You can integrate Rational Quality Manager with the Rational ClearQuest defect tracking system using the ClearQuest Synchronizer (previously called the Connector). For more information, see Rational Quality Manager and Rational ClearQuest.

You can integrate the Requirements management application with Rational ClearQuest and configure the applications to associate requirements with defects, tasks, requests for enhancements, and other record types. For more information, see Integrating the Requirements Management application and Rational ClearQuest.

For instructions on upgrading ClearQuest Synchronizer, see Upgrading ClearQuest Synchronizer.


Rational ClearCase

Rational Team Concert includes ClearCase connectors that support operations between Rational Team Concert and Rational ClearCase. For more information, see Rational Team Concert and Rational ClearCase.


Rational Build Forge

The integration between Rational Team Concert and Rational Build Forge allows to create Rational Build Forge build engines and definitions to integrate with your Build Forge projects. For more information, see Rational Team Concert and Rational Build Forge.


Hudson

The integration between Rational Team Concert and Hudson allows to create Hudson build engines and definitions to integrate with your Hudson projects. For more information, seeRational Team Concert and Hudson.


Subversion

Rational Team Concert provides several ways for teams that use both Subversion and Rational Team Concert source control to collaborate. For more information, see Rational Team Concert and Subversion.


Rational DOORS

You can use Rational DOORS to manage your requirements, and you can use the Rational Team Concert work items capability to place those requirements under change control. For more information, see Rational Team Concert and Rational DOORS.

You can integrate Rational Quality Manager with Rational DOORS to associate and track requirements from Rational DOORS with test plans or test cases. For more information, see Rational Quality Manager and Rational DOORS.


Rational Focal Point

You can use Rational Focal Point to capture and prioritize business needs and export them to Rational Team Concert as a project. For more information, see Rational Team Concert and Rational Focal Point.


Lotus Connections

Rational Team Concert provides an integration to Lotus Connections, which connects change and configuration management resources and artifacts with Lotus Connections community resources and artifacts. For more information, see Rational Team Concert and Lotus Connections.


Rational Developer for Power Systems Software

Rational Team Concert integrates with Rational Developer for Power Systems Software to provide IBM i developers an integrated collaborative application development environment. This integrated solution provides the value of the team collaboration capabilities of Rational Team Concert with the individual development environment of Rational Developer for Power Systems Software. For more information, see Rational Team Concert and Rational Developer for Power Systems Software.


Rational RequisitePro

With the integration between Rational Quality Manager and Rational RequisitePro, you can add requirement views and packages from Rational RequisitePro to test plans in the Quality Management application. For more information, see Rational Quality Manager and Rational RequisitePro.


Rational Change

You can use the IBM Rational Change Open Services for Lifecycle Collaboration Change Management (OSLC-CM) API to submit new change requests and link execution results to them directly from the Quality Management web interface. For more information, see Rational Quality Manager and Rational Change.


Rational test tools

You can use Rational Quality Manager to run automated tests that reside either on your test lab machines or at shared network locations. For more information, see Rational Quality Manager and Rational test tools.


Selenium

Integration with Selenium is implemented by using a JUnit Selenium adapter, with which you can run Selenium version 2.0 WebDriver JUnit4 tests in the Quality Management application. For more information, see Rational Quality Manager and Selenium.


Software inventory and automation tools

You can integrate Rational Quality Manager with software inventory and automation tools such as Rational Build Forge and Software Testing Automation Framework (STAF) Software Testing Automation Framework Execution Engine (STAX). For more information, see Rational Quality Manager and software inventory and automation tools.


Rational Software Architect - Design Management

You can integrate IBM Rational Software Architect - Design Management with the Requirements Management (RM) and Change and Configuration Management (CCM) applications in Rational solution for Collaborative Lifecycle Management (CLM). You can use this integration to link design models and model resources to requirements, requirements-related artifacts, work items, and other development artifacts. For upgrading Rational Software Architect - Design Management, see Upgrading Design Management Server.


Rational Publishing Engine

You can use Rational Publishing Engine to create and generate new reports in Document Studio and to customize available requirements management templates. Each of the applications provides a reportable REST API, which can be used to create and customize reports in the Rational Publishing Engine Report Studio. You can generate reports based on any of the applications’ data using Rational Publishing Engine. For more information, see Authoring document-style reports.