Upgrading Design Management to version 4.0.5

Use this guide to upgrade the following Rational Design Management (DM) to version 4.0.5:

Select options that best describe your installation environment

Select an applications to upgrade:

Note: In Rational Design Management, Jazz Team Server must be upgraded first. In a distributed topology, select one application at a time to upgrade.

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:

The complete instructions to upgrade your product to version 4.0.5 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. Upgrade data sheet
Verify that your hardware and software meet the minimum system requirements: New requirements exist for version 4.0.3 and later, including a requirement to use a 64-bit server operating system. To learn about these new requirements and to see if your current system meets the minimum requirements, click the System requirements link. System requirements
Get the product installation media: For 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 4.0.3. 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 4.0.3 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 4.0.3 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.
Learn about licensing: you indicated that you are upgrading from Design Management 3.0. You must obtain version 4.0.3 licenses. you indicated that you are upgrading from Design Management 3.0.1.x. You must obtain version 4.0.3 licenses. you indicated that you are upgrading from Design Management 4.0.0.x. You are not required to obtain new licenses for version 4.0.3. you indicated that you are upgrading from Design Management 4.0.1. You are not required to obtain new licenses for version 4.0.3. you indicated that you are upgrading from Design Management 4.0.2. You are not required to obtain new licenses for version 4.0.3. 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)

Upgrade Rational Reporting for Development Intelligence

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

For upgrading Rational Reporting for Development Intelligence, see any of the following links:

After you upgrade to version 4.0.5 of the applications for the Rational solution for CLM, download the latest report samples and resources and load them to the report server. For complete instructions, see Upgrading reporting artifacts.

Install Rational Design Management version 4.0.5

Install Rational Design Management version 4.0.5 applications, but do not run the setup wizard. For distributed configurations, install the version 4.0.5 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.

Previous releases of Design Management automatically installed additional required applications such as Configuration Management (/vvc). These applications are now separate installable components that are installed in addition to the Design Management components Design Management for Rational Software Architect (RSA-DM) or Design Management for Rhapsody (Rhapsody-DM). The extra components that may need to be installed are:

  • The Configuration Management component (VVC) must always be installed and registered with the Jazz Team Server (JTS). Do not confuse this component with Change and Configuration Management (CCM/RTC).
  • If you are installing RSA-DM you must also install IBM Rational Software Architect Extension for Design Management Domain Extension.

Install the CLM 4.0.5 applications on the node that will be used for upgrading the server, for example, node 1. Do not run the setup wizard. For information about installing the server, see Installing by using IBM Installation Manager or Installing by using command-line commands.

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

Back up the WebSphere Application Server profile

Optionally create a back up of your WebSphere Application Server profile so that it can be restored in case the upgrade fails.

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

  • Jazz Team Server
  • Change and Configuration 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. Run the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password.
  3. Note: The command shuts down the server before starting the back up process.

    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

    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.bat command. For example, restoreConfig.bat C:\WAS_backup\RTC_3.0_profile.zip restoreConfig.bat C:\WAS_backup\CLM_3.0.1.x_profile.zip 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

  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. Run the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password.
  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

    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/RTC_3.0_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_3.0.1.x_profile.zip./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

  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. Run the following command. If WebSphere Application Server security is turned on, you must also supply the user name and password.
  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

    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/RTC_3.0_profile.zip./restoreConfig.sh /root/WAS_backup/CLM_3.0.1.x_profile.zip./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

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
  • Design Management application
  • Quality Management application
  • Configuration Management application

  1. If you carried out the previous step to back up your WebSphere Application Server profile, the command shut down your server. Start the server the server to continue.
  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 4.0.4 counterpart.
  5. 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 4.0.4 counterpart.
  6. Click the Enterprise Applications link and then stop and uninstall the following installed applications:
    • jts_war
    • clmhelp_war
    • admin_war
    • dm_war
    • rdmhelp_war
    • qm_war
    • vvc_war
    • vvchelp_war
  7. When you are prompted to save the changes to the master configuration, save them.

Update 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
  • Design Management application
  • Quality Management application
  • Configuration 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:///4.0.5_install_dir/server/conf. For example, file:///C:/PROGRA~2/IBM/JazzTeamServer_4.0.5/server/conf.
  8. Click JAZZ_HOME and update its value to file:////4.0.5_install_dir/server/conf. For example, file:////opt/IBM/JazzTeamServer_4.0.5/server/conf.
  9. Click JAZZ_HOME and update its value to file:////4.0.5_install_dir/server/conf. For example, file:////usr/IBM/JazzTeamServer_4.0.4/server/conf.
  10. Click log4j.configuration and update its value to file:///4.0.5_install_dir/server/conf/startup_log4j.properties. For example, file:///C:/PROGRA~2/IBM/JazzTeamServer_4.0.5/server/conf/startup_log4j.properties.
  11. Click log4j.configuration and update its value to file:////4.0.5_install_dir/server/conf/startup_log4j.properties. For example, file:////opt/IBM/JazzTeamServer_4.0.5/server/conf/startup_log4j.properties.
  12. Click log4j.configuration and update its value to file:////4.0.5_install_dir/server/conf/startup_log4j.properties. For example, file:////usr/IBM/JazzTeamServer_4.0.5/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
  • Design Management application
  • Quality Management application
  • Configuration Management application
  • Any application that is registered with Jazz Team Server

Note: When upgrading Requirements Management application, you must make sure that both Jazz Team Server (including any application that is registered with Jazz Team Server) and Requirements Management application servers are stopped.

  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

Update WebSphere eXtreme Scale

Make sure WebSphere eXtreme Scale is updated with the latest interim fix. To download the latest interim fix, see Installing WebSphere eXtreme Scale.

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
  • Design Management application
  • Quality Management application
  • Configuration 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
  • dm_war
  • rdmhelp_war
  • qm_war
  • vvc_war
  • vvchelp_war
  • admin_war
  • clmhelp_war

WAS_profile_dir\wscache location example:

C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\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/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/wscache

WAS_profile_dir/temp example:

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

Clean up the logs directory

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

  • Jazz Team Server
  • Design Management application
  • Quality Management application
  • Configuration 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
  • Design Management application
  • Quality Management application
  • Configuration Management application
  • Any application that is registered with Jazz Team Server

Note: When upgrading Requirements Management application, you must make sure that both Jazz Team Server (including any application that is registered with Jazz Team Server) and Requirements Management application servers are stopped.

  1. Open a command prompt and change to the DM_4.0.0.x_install_dir\server directory.
  2. Open a command prompt and change to the DM_4.0.1_install_dir\server directory.
  3. Open a command prompt and change to the DM_4.0.2_install_dir\server directory.
  4. Open a command prompt and change to the DM_4.0.3_install_dir\server directory.
  5. Open a command prompt and change to the DM_4.0.4_install_dir\server directory.
  6. Enter the following command:
  7. server.shutdown.bat

  1. Open a command shell and change to the DM_4.0.0.x_install_dir/server directory.
  2. Open a command shell and change to the DM_4.0.1_install_dir/server directory.
  3. Open a command shell and change to the DM_4.0.2_install_dir/server directory.
  4. Open a command shell and change to the DM_4.0.3_install_dir/server directory.
  5. Open a command shell and change to the DM_4.0.4_install_dir/server directory.
  6. Enter the following command:
  7. ./server.shutdown

Copy the Derby databases from the Design Management 3.0 Design Management version 3.0.1.x Design Management version 4.0.0.x Design Management version 4.0.1 Design Management version 4.0.2 Design Management version 4.0.3 Design Management version 4.0.4 installation directory

  1. Before copying the Derby databases, go to the directory where you just installed the version 4.0.5 applications and delete the Derby repositoryDB directories for each application. Alternatively, you can open a command prompt and enter the following commands to clear the default version 4.0.5 Derby repositoryDB directory:
  2. del /s /f 4.0.5_install_dir\server\conf\jts\derby\repositoryDB
    del /s /f 4.0.5_install_dir\server\conf\dm\derby\repositoryDB
    del /s /f 4.0.5_install_dir\server\conf\vvc\derby\repositoryDB
    rm -rf 4.0.5_install_dir/server/conf/jts/derby/repositoryDB
    rm -rf 4.0.5_install_dir/server/conf/dm/derby/repositoryDB
    rm -rf 4.0.5_install_dir/server/conf/vvc/derby/repositoryDB
  3. Go to the directory where you previously installed the Design Management, copy the Derby database, and paste it in the equivalent directory for version 4.0.5. You can also open a command prompt and enter the following commands to copy the Derby database.
  4. Note: The following commands work if you are using Derby databases that are provided with the packaged product. If you changed your Derby databases location, update the path accordingly.

    xcopy /s DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir\server\conf\jts\derby\repositoryDB 4.0.4_install_dir\server\conf\jts\derby\repositoryDBDM_4.0.4_install_dir\server\conf\jts\derby\repositoryDB 4.0.5_install_dir\server\conf\jts\derby\repositoryDB
    xcopy /s DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir\server\conf\jts\derby\warehouseDB 4.0.5_install_dir\server\conf\jts\derby\warehouseDB
    xcopy /s DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir\server\conf\dm\derby\repositoryDB 4.0.5_install_dir\server\conf\dm\derby\repositoryDB
    xcopy /s DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir\server\conf\vvc\derby\repositoryDB 4.0.5_install_dir\server\conf\vvc\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\AppServerHost4.xIntall\jts\derby\conf\repositoryDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\jts\derby\conf\warehouseDB WAS_install_dir\AppServerHost4.xIntall\jts\derby\conf\warehouseDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\dm\derby\conf\repositoryDB WAS_install_dir\AppServerHost4.xIntall\dm\derby\conf\repositoryDB
    xcopy /s WAS_install_dir\OldAppServerHostIntall\vvc\derby\conf\repositoryDB WAS_install_dir\AppServerHost4.xIntall\vvc\derby\conf\repositoryDB
    cp -R DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf/jts/derby/repositoryDB 4.0.5_install_dir/server/conf/jts/derby/repositoryDB
    cp -R DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf/jts/derby/warehouseDB 4.0.5_install_dir/server/conf/jts/derby/warehouseDB
    cp -R DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf/dm/derby/repositoryDB 4.0.5_install_dir/server/conf/dm/derby/repositoryDB
    cp -R DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf/vvc/derby/repositoryDB 4.0.5_install_dir/server/conf/vvc/derby/repositoryDB
    cp -R DM_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf/jts/derby/warehouseDB 4.0.5_install_dir/server/conf/jts/derby/warehouseDB

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

    cp -R WAS_install_dir/AppServerHost3.xIntall/jts/derby/conf/repositoryDB WAS_install_dir/AppServerHost4.xIntall/jts/derby/conf/repositoryDB
    cp -R WAS_install_dir/OldAppServerHostIntall/jts/derby/conf/warehouseDB WAS_install_dir/AppServerHost4.xIntall/jts/derby/conf/warehouseDB
    cp -R WAS_install_dir/OldAppServerHostIntall/dm/derby/conf/repositoryDB WAS_install_dir/AppServerHost4.xIntall/dm/derby/conf/repositoryDB
    cp -R WAS_install_dir/OldAppServerHostIntall/vvc/derby/conf/repositoryDB WAS_install_dir/AppServerHost4.xIntall/vvc/derby/conf/repositoryDB

Back up the database

Back up your DB2 databases including the data warehouse database. For information about backing up a DB2 database, see Backing up and Restoring a DB2 database.

Back up your Oracle databases including the data warehouse database. For instructions to back up the database, see the Oracle documentation.

Back up your SQL Server databases including the data warehouse database. For instructions to back up the database, see the SQL Server documentation.

Run the upgrade Repository Tools command

To upgrade Jazz Team Server configuration files, go to the JTS_4.0.5_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=RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir/server/conf

repotools-jts.bat -addTables

repotools-jts.bat -upgradeWarehouse

repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir/server/conf updateTomcatFiles=no

repotools-jts.bat -addTables

repotools-jts.bat -upgradeWarehouse

./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir/server/conf

./repotools-jts.sh -addTables

./repotools-jts.sh -upgradeWarehouse

./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir/server/conf updateTomcatFiles=no

./repotools-jts.sh -addTables

./repotools-jts.sh -upgradeWarehouse

To upgrade the DM application configuration files, go to the DM_4.0.4_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=dm switch in the command.

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

repotools-dm.bat -migration_dm_updateConfigurationFiles oldApplicationHome=RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=dm

repotools-dm.bat -addTables

repotools-dm.bat -migration_dm_updateConfigurationFiles oldApplicationHome=RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=dm updateTomcatFiles=no

repotools-dm.bat -addTables

./repotools-dm.sh -migration_dm_updateConfigurationFiles oldApplicationHome=RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=dm

./repotools-dm.sh -addTables

./repotools-dm.sh -migration_dm_updateConfigurationFiles oldApplicationHome=RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dirDM_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=ccm updateTomcatFiles=no

./repotools-dm.sh -addTables

To upgrade the Configuration Managment application configuration files, go to the QM_4.0.4_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=vvc switch in the command.

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

repotools-vvc.bat -migration_vvc_updateConfigurationFiles oldApplicationHome=VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=vvc

repotools-vvc.bat -addTables

repotools-vvc.bat -migration_vvc_updateConfigurationFiles oldApplicationHome=VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=qm updateTomcatFiles=no

repotools-vvc.bat -addTables

./repotools-vvc.sh -migration_qm_updateConfigurationFiles oldApplicationHome=VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=vvc

./repotools-vvc.sh -addTables

./repotools-vvc.sh -migration_qm_updateConfigurationFiles oldApplicationHome=VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf ignoreJTSVersionCheck applicationContextRoot=vvc updateTomcatFiles=no

./repotools-vvc.sh -addTables

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

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

  1. Go to the physical server where both the old version and version 4.0.4 of the RM applications are installed.
  2. Copy the content of the RM_4.0.3_install_dir/server directory and the RM_3.0.1.x_install_dirRM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dir/server directory to two different directories on a portable drive.
  3. Go to the physical server where Jazz Team Server version 4.0.3 is installed, and copy the content of the portable drive to a temp directory. Make sure that you have a directory for each RM application version. For example: C:\Temp\RM4.0.3 and C:\Temp\RM3.0.1.xRM4.0.0.xRM4.0.1RM4.0.2.
  4. Open a command prompt and change the directory to C:\Temp\RM4.0.3\server.
  5. Enter this command:

    upgrade\rm\rm_upgrade.bat -oldApplicationHome C:\Temp\RM3.0.1.xRM4.0.0.xRM4.0.1\server\conf -oldJTSHome JTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir\server\conf -newJTSHome JTS_4.0.3_install_dir\server\conf applicationContextRoot=rm

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

  6. After the upgrade is complete on the JTS server, copy the content of the C:\Temp\RM4.0.3 directory to a portable drive.
  7. Go to the physical server where the RM application is installed and overwrite the existing content by pasting the content of the portable drive to the RM4.0.3_install_dir/server directory.
  1. Go to the physical server where both the old version and version 4.0.4 of the RM applications are installed.
  2. Copy the content of the RM4.0.3_install_dir/server directory and the RM_3.0.1.x_install_dirRM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dir/server directory to two different directories on a portable drive.
  3. Go to the physical machine where Jazz Team Server version 4.0.3 is installed and copy the content of the portable drive to a temp directory. Make sure that you have a directory for each RM version. For example: C:\Temp\RM4.0.3 and C:\Temp\RM3.0.1.xRM4.0.0.xRM4.0.1RM4.0.2.
  4. Open a command prompt and change the directory to C:\Temp\RM4.0.3\server.
  5. Enter this command:

    upgrade\rm\rm_upgrade.bat -oldApplicationHome C:\Temp\RM3.0.1.xRM4.0.0.xRM4.0.1RM4.0.2\server\conf -oldJTSHome JTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir\server\conf -newJTSHome JTS_4.0.3_install_dir\server\conf -updateTomcatFiles=no applicationContextRoot=rm

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

  6. After the upgrade is complete on the JTS server, copy the content of the C:\Temp\RM4.0.3 directory to a portable drive.
  7. Go to the physical machine where the RM application is installed and overwrite the existing content by pasting the content of the portable drive to the RM4.0.3_install_dir/server directory.
  1. Go to the physical server where both the old version and version 4.0.3 of the RM applications are installed.
  2. Copy the content of the RM4.0.3_install_dir/server directory and the RM_3.0.1.x_install_dirRM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dir/server directory to two different directories on a portable drive.
  3. Go to the physical server where Jazz Team Server version 4.0.3 is installed and copy the content of the portable drive to a temp directory. Make sure that you have a directory for each RM application version. For example: opt/tmp/rm4.0.3 and opt/tmp/rm3.0.1.xrm4.0.0.xrm4.0.1rm4.0.2.
  4. Open a command shell and change the directory to opt/tmp/rm4.0.2/server.
  5. Enter this command:

    upgrade/rm/rm_upgrade.sh -oldApplicationHome opt/tmp/rm3.0.1.xrm4.0.0.xrm4.0.1rm4.0.2/server/conf -oldJTSHome JTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir/server/conf -newJTSHome JTS_4.0.3_install_dir/server/conf applicationContextRoot rm

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

  6. After the upgrade is complete on the JTS server, copy the content of the opt/tmp/rm4.0.3 directory to a portable drive.
  7. Go to the physical server where the RM application is installed and overwrite the existing content by pasting the content of the portable drive to the 4.0.3RM_install_dir/server directory.
  1. Go to the physical server where both the old version and version 4.0.3 of the RM applications are installed.
  2. Copy the content of the RM_4.0.3_install_dir/server directory and the RM_3.0.1.x_install_dirRM_4.0.0.x_install_dirRM_4.0.1_install_dirRM_4.0.2_install_dir/server directory to two different directories on a portable drive.
  3. Go to the physical server where Jazz Team Server version 4.0.3 is installed and copy the content of the portable drive to a temp directory. Make sure that you have a directory for each RM application version. For example: opt/tmp/rm4.0.3 and opt/tmp/rm3.0.1.xrm4.0.0.xrm4.0.1rm4.0.2.
  4. Open a command shell and change the directory to opt/tmp/rm4.0.3/server.
  5. Enter this command:

    upgrade/rm/rm_upgrade.sh -oldApplicationHome opt/tmp/rm3.0.1.xrm4.0.0.xrm4.0.1rm4.0.2/server/conf -oldJTSHome JTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir/server/conf -newJTSHome JTS_4.0.3_install_dir/server/conf updateTomcatFiles no applicationContextRoot rm

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

  6. After the upgrade is complete on the JTS server, copy the content of the opt/tmp/rm4.0.3 directory to a portable drive.
  7. Go to the physical server where the RM application is installed and overwrite the existing content by pasting the content of the portable drive to the RM_4.0.3_install_dir/server directory.

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

  • Update the version 4.0.3 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 4.0.3
  • Copy the content of the older version's fronting.properties file to version 4.0.3
  • Copy the content of the older version's friendsconfig.rdf file to version 4.0.3

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

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 4.0.5. For more information, see Upgrade script files.

To use the upgrade script in a distributed environment where you install Rational Design Management separately from Jazz Team Server, the upgrade script must be able to access the drive or file system where the application is installed. 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_4.0.5_install_dir\server\conf, will not work. The mounted drive must be configured with read-write-execute privileges for the administrator account.

Important: Although the script file is in the upgrade/application context root directory, the file must be run from the server directory. If your path contains spaces, ensure that you enclose the path name in double-quotation marks.

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

upgrade\jts\jts_upgrade.bat -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir\server\conf

upgrade\jts\jts_upgrade.bat -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_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_4.0.5_install_dir/server/conf/jts/indices/workitemindex, where JTS_4.0.5_install_dir is the location where Jazz Team Server 4.0.5 is installed.

Important: As part of step 0 in the dm_upgrade.xxx script, the command "repotools-dm -version" is executed for the source installation. In Design Management 4.0, the repotools-dm command would not run because of unresolved dependencies. Before running the dm_upgrade.xx script, you must edit the file DM4.0_InstallDir/server/repotools-dm.xx and uncomment the line that defines the property "-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true". If step 0 of the dm_upgrade script failed because it could not determine the version of the source installation, fix the 4.0 repotools-dm.xxx file and run the upgrade/dm/dm_upgrade.xx script again, starting over at step 0.

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

upgrade\dm\dm_upgrade.bat -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir\server\conf

upgrade\dm\dm_upgrade.bat -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir\server\conf -ignoreJTSVersionCheck

During the upgrade, after the configuration files are merged, a window opens in which you can check the Design Management teamserver.properties file.

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

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_3.0.1.x_install_dirQM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dir\server\conf

upgrade\qm\qm_upgrade.bat -oldApplicationHome QM_3.0.1.x_install_dirQM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dir\server\conf -newJTSHome JTS_4.0.3_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 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_4.0.3_install_dir/server/conf/qm/indices/workitemindex where QM_4.0.3_install_dir is the location where Quality Management application 4.0.3 is installed.

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

upgrade\vvc\vvc_upgrade.bat -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir\server\conf

upgrade\vvc\vvc_upgrade.bat -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir\server\conf -ignoreJTSVersionCheck

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

upgrade/jts/jts_upgrade.sh -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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.4_install_dir/server/conf

upgrade/jts/jts_upgrade.sh -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_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 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_4.0.5_install_dir/server/conf/jts/indices/workitemindex where JTS_4.0.5_install_dir is the location where Jazz Team Server 4.0.5 is installed.

Important: As part of step 0 in the dm_upgrade.xxx script, the command "repotools-dm -version" is executed for the source installation. In Design Management 4.0, the repotools-dm command would not run because of unresolved dependencies. Before running the dm_upgrade.xx script, you must edit the file DM4.0_InstallDir/server/repotools-dm.xx and uncomment the line that defines the property "-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true". If step 0 of the dm_upgrade script failed because it could not determine the version of the source installation, fix the 4.0 repotools-dm.xxx file and run the upgrade/dm/dm_upgrade.xx script again, starting over at step 0.

To upgrade Design Management application, open a command shell, go to the DM_4.0.5_install_dir/server directory, and enter this command:

upgrade/dm/dm_upgrade.sh -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir/server/conf

upgrade/ccm/ccm_upgrade.sh -oldApplicationHome RTC_3.0_install_dirCCM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir/server/conf -ignoreJTSVersionCheck

During the upgrade, after the configuration files are merged, an editor opens in which you can check Design Management teamserver.properties file. 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=DM_4.0.4_install_dir/server/conf/dm/indices/workitemindex where DM_4.0.4_install_dir is the location where the Design Management application 4.0.5 is installed.

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

upgrade/vvc/vvc_upgrade.sh -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf

upgrade/vvc/vvc_upgrade.sh -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dirVVC_4.0.4_install_dir/server/conf -ignoreJTSVersionCheck

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

upgrade\jts\jts_upgrade.bat -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_dir\server\conf -updateTomcatFiles no

upgrade\jts\jts_upgrade.bat -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_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_4.0.5_install_dir/server/conf/jts/indices/workitemindex where JTS_4.0.5_install_dir is the location where Jazz Team Server 4.0.5 is installed.

Important: As part of step 0 in the dm_upgrade.xxx script, the command "repotools-dm -version" is executed for the source installation. In Design Management 4.0, the repotools-dm command would not run because of unresolved dependencies. Before running the dm_upgrade.xx script, you must edit the file DM4.0_InstallDir/server/repotools-dm.xx and uncomment the line that defines the property "-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true". If step 0 of the dm_upgrade script failed because it could not determine the version of the source installation, fix the 4.0 repotools-dm.xxx file and run the upgrade/dm/dm_upgrade.xx script again, starting over at step 0.

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

upgrade\dm\dm_upgrade.bat -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir\server\conf -updateTomcatFiles no

upgrade\dm\dm_upgrade.bat -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir\server\conf -ignoreJTSVersionCheck -updateTomcatFiles no

During the upgrade, after the configuration files are merged, a window opens in which you can verify the Design 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=DM_4.0.5_install_dir/server/conf/dm/indices/workitemindex where DM_4.0.5_install_dir is the location where the Design Management application 4.0.5 is installed.

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

upgrade\vvc\vvc_upgrade.bat -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dir\server\conf -updateTomcatFiles no

upgrade\vvc\vvc_upgrade.bat -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dir\server\conf -ignoreJTSVersionCheck -updateTomcatFiles no

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

upgrade/jts/jts_upgrade.sh -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_dir/server/conf -updateTomcatFiles no

upgrade/jts/jts_upgrade.sh -oldJTSHome RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_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_4.0.5_install_dir/server/conf/jts/indices/workitemindex where JTS_4.0.5_install_dir is the location where Jazz Team Server 4.0.5 is installed.

Important: As part of step 0 in the dm_upgrade.xxx script, the command "repotools-dm -version" is executed for the source installation. In Design Management 4.0, the repotools-dm command would not run because of unresolved dependencies. Before running the dm_upgrade.xx script, you must edit the file DM4.0_InstallDir/server/repotools-dm.xx and uncomment the line that defines the property "-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true". If step 0 of the dm_upgrade script failed because it could not determine the version of the source installation, fix the 4.0 repotools-dm.xxx file and run the upgrade/dm/dm_upgrade.xx script again, starting over at step 0.

To upgrade the Design Management application, open a command shell, go to the DM_4.0.5_install_dir/server directory, and enter this command:

upgrade/dm/dm_upgrade.sh -oldApplicationHome RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir/server/conf -updateTomcatFiles no

upgrade/dm/dm_upgrade.sh -oldApplicationHome RTC_3.0_install_dirCCM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir/server/conf -ignoreJTSVersionCheck -updateTomcatFiles no

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

upgrade/vvc/vvc_upgrade.sh -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dir/server/conf -updateTomcatFiles no

upgrade/vvc/vvc_upgrade.sh -oldApplicationHome VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_install_dir/server/conf -ignoreJTSVersionCheck -updateTomcatFiles no

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 4.0.5 configuration directory /QIBM/UserData/JazzTeamServer404/server.
  3. Enter this command to upgrade Jazz Team Server:

    upgrade/jts/jts_upgrade.sh -oldJTSHome /QIBM/UserData/RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_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_dir/server/conf

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

    upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /QIBM/UserData/RTC_3.0_install_dirCCM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dirDM_4.0.3_install_dirDM_4.0.4_install_dir/server/conf

  5. Enter this command to upgrade Quality Management application:

    upgrade/qm/qm_upgrade.sh -oldApplicationHome /QIBM/UserData/QM_3.0.1.x_install_dirQM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dir/server/conf

  6. Enter this command to upgrade Configuration Management application:

    upgrade/vvc/vvc_upgrade.sh -oldApplicationHome /QIBM/UserData/RM_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dirVVC_4.0.3_install_dirVVC_4.0.4_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 4.0.5 CLM applications. The command also does a back up, 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 (V7 or V8).
    • 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 Design Management application.
    • jtsAppName is the name of Jazz Team Server.
    • qmAppName is the name of Quality Management application.
    • vvcAppName is the name of Configuration Management application.
    • clmHelpAppName is the name of the CLM help application.
    • adminAppName is the name of the Lifecycle Project Administration application.

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 4.0.3. 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 4.0.3 indices directory:
  2. Del /s /f JTS_4.0.3_install_dir\server\conf\jts\indices
    Del /s /f DM_4.0.3_install_dir\server\conf\dm\indices
    Del /s /f VVC_4.0.3_install_dir\server\conf\vvc\indices
    rm -rf JTS_4.0.3_install_dir/server/conf/jts/indices
    rm -rf DM_4.0.3_install_dir/server/conf/dm/indices
    rm -rf VVC_4.0.3_install_dir/server/conf/vvc/indices
  3. Open a command prompt and enter this command to copy the indices from the previous installation to version 4.0.3:
  4. copy RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir\server\conf\jts\indices JTS_4.0.3_install_dir\server\conf\jts\indices
    copy RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dir\server\conf\dm\indices DM_4.0.3_install_dir\server\conf\dm\indices
    copy QM_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dir\server\conf\qm\indices VVC_4.0.3_install_dir\server\conf\vvc\indices
    cp -R RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir/server/conf/jts/indices JTS_4.0.3_install_dir/server/conf/jts/indices
    cp -R RTC_3.0_install_dirCCM_3.0.1.x_install_dirCCM_4.0.0.x_install_dirCCM_4.0.1_install_dirCCM_4.0.2_install_dir/server/conf/ccm/indices CCM_4.0.3_install_dir/server/conf/ccm/indices
    cp -R QM_3.0.1.x_install_dirQM_4.0.0.x_install_dirQM_4.0.1_install_dirQM_4.0.2_install_dir/server/conf/qm/indices QM_4.0.3_install_dir/server/conf/qm/indices

To copy your JFS/text indices from a previous installation to version 4.0.3, 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 4.0.3 indices directory:
  2. Del /s /f JTS_4.0.3_install_dir\server\conf\jts\indices
    Del /s /f DM_4.0.3_install_dir\server\conf\dm\indices
    Del /s /f VVC_4.0.3_install_dir\server\conf\vvc\indices
    rm -rf JTS_4.0.3_install_dir/server/conf/jts/indices
    rm -rf DM_4.0.3_install_dir/server/conf/dm/indices
    rm -rf VVC_4.0.3_install_dir/server/conf/vvc/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/dm/indices/workitemindex the full text indices will be located relative to the WebSphere Application Server profile hosting the applications. For example: WAS_install_dir/AppServer/profiles/Appsrv01.

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

    Open a command prompt and enter the following command to copy the full text indices from previous version to 4.0.3:

  5. copy WAS_profile_dir\conf\jts\indices JTS_4.0.3_install_dir\server\conf\jts\indices
    copy WAS_profile_dir\conf\dm\indices DM_4.0.3_install_dir\server\confdm\indices
    copy WAS_profile_dir\conf\vvc\indices VVC_4.0.3_install_dir\server\conf\vvc\indices
    cp -R WAS_profile_dir/conf/jts/indices JTS_4.0.3_install_dir/server/conf/jts/indices
    cp -R WAS_profile_dir/conf/dm/indices DM_4.0.3_install_dir/server/conf/dm/indices
    cp -R WAS_profile_dir/conf/vvc/indices VVC_4.0.3_install_dir/server/conf/vvc/indices
  6. 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=4.0.3_install_dir/server/conf/dm/indices/workitemindex, where 4.0.3_install_dir is the location where the Design Management version 4.0.3 application is installed.

    Open a command prompt and enter this command to copy the full text indices from previous installation to 4.0.3:

  7. copy RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir\server\conf\jts\indices JTS_4.0.3_install_dir\server\conf\jts\indices
    copy RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dir\server\conf\dm\indices DM_4.0.3_install_dir\server\conf\dm\indices
    copy QM_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dir\server\conf\vvc\indices VVC_4.0.3_install_dir\server\conf\vvc\indices
    cp -R RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir/server/conf/jts/indices JTS_4.0.3_install_dir/server/conf/jts/indices
    cp -R RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dir/server/conf/dm/indices DM_4.0.3_install_dir/server/conf/dm/indices
    cp -R QM_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dir/server/conf/vvc/indices VVC_4.0.3_install_dir/server/conf/vvc/indices
  8. Open a command prompt and enter this command to copy the JFS indices from the previous version to version 4.0.3:
  9. copy RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir\server\conf\jts\indices JTS_4.0.3_install_dir\server\conf\jts\indices
    copy RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dir\server\conf\dm\indices DM_4.0.3_install_dir\server\conf\dm\indices
    copy QM_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dir\server\conf\vvc\indices VVC_4.0.3_install_dir\server\conf\vvc\indices
    cp -R RTC_3.0_install_dirJTS_3.0.1.x_install_dirJTS_4.0.0.x_install_dirJTS_4.0.1_install_dirJTS_4.0.2_install_dir/server/conf/jts/indices JTS_4.0.3_install_dir/server/conf/jts/indices
    cp -R RTC_3.0_install_dirDM_3.0.1.x_install_dirDM_4.0.0.x_install_dirDM_4.0.1_install_dirDM_4.0.2_install_dir/server/conf/dm/indices DM_4.0.3_install_dir/server/conf/dm/indices
    cp -R VVC_3.0.1.x_install_dirVVC_4.0.0.x_install_dirVVC_4.0.1_install_dirVVC_4.0.2_install_dir/server/conf/vvc/indices VVC_4.0.3_install_dir/server/conf/vvc/indices

Start the WebSphere Application Server

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

  • Jazz Team Server
  • Design Management application
  • Quality Management application
  • Configuration 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.

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

Deploy the version 4.0.3 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
  • Design Management application
  • Quality Management application
  • Configuration Management application

WAR file locations: If you used Installation Manager to install Rational Design Management, and during the installation you cleared the check box for the Tomcat 7 application server, the WAR files were copied into the 4.0.3_install_dir/server/webapps directory by default. If you selected the Tomcat 7 application server, the WAR files were copied into the 4.0.3_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
    • dm_war
    • rdmhelp_war
    • rsadm_war
    • qm_war
    • vvc_war
    • vvchelp_war
    • clmhelp_war
    • admin_war
  4. Map the security roles appropriately for:
    • jts_war
    • dm_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 4.0.3 version of the converter.war on the dedicated converter. For detailed information see, Requirements Management Converter Application Configuration and Troubleshooting Guide.

Disable the cluster

Make sure only node 1 (the node that you installed the CLM 4.0.5 applications on) is started and all other nodes are stopped. For instructions on how to disable the cluster, see Disabling the cluster.

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
  • Design Management application
  • Quality Management application
  • Configuration Management application

Logon to the Integrated Solutions Console and start these applications:

  • jts_war
  • dm_war
  • rdmhelp_war
  • rsadm_war
  • qm_war
  • vvc_war
  • vvchelp_war
  • admin_war
  • clmhelp_war

Start the servers

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

  • Jazz Team Server
  • Design Management application
  • Quality Management application
  • Configuration 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 4.0.5 application servers:

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

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

Migrate the Configuration Management and Design Management applications

When upgrading Configuration Management application, you must make sure that both Jazz Team Server (including any application that is registered with Jazz Team Server) and Configration Management application servers are started.

If you are also upgrading the Requirements Management application, you must perform the online RM migration step before attempting to run the repotools-vvc migration command below.

Ensure there are credentials that exists with the following content:

  1. adminUserId
  2. adminPassword
  3. repositoryURL
  4. smartCard
  5. certificateFile

Here is an example

  1. Open a command prompt and change to the VVC_4.0.5_install_dir\server directory depending on applications installed.
  2. Enter this command:
  3. ./repotools-vvc.sh -migration_vvc_updateResourcesCommand credentialsFile=credentials.txt

  1. Open a command prompt and change to the Configuration Management install directory VVC_4.0.5_install_dir\server.
  2. Enter this command:
  3. repotools-vvc.bat -migration_vvc_updateResourcesCommand credentialsFile=credentials.txt

For WebSphere, use the WAS admin console to verify that you mapped the security roles for the jts_war application.

The VVC repotools migration command sends a request to the running VVC application and waits for a response. If this repotools-vvc command stops immediately with an authorization error, verify that the server is running and that the user Id and password in the credentials file are correct.

When the VVC repotools migration command completes, you must then run another migration command for Design Management. The DM repotools command also requires a credentials.txt file with similar properties to the one used for the VVC repotools command, where only the repositoryURL property will be different. You can either modify the credentials.txt file above or create a new one for DM. In either case, the repository URL property should be defined using the DM root context as follows: repositoryURL=https://yourserver.com:9443/dm

Ensure there are credentials that exists with the following content:

  1. adminUserId
  2. adminPassword
  3. repositoryURL
  4. smartCard
  5. certificateFile

Here is an example

  1. Open a command prompt and change to the DM_4.0.5_install_dir\server directory depending on applications installed.
  2. Enter this command:
  3. ./repotools-dm.sh -migration_dm_runUpgradeManager credentialsFile=credentials.txt

  1. Open a command prompt and change to the DM_4.0.5_install_dir\server directory depending on applications installed.
  2. Enter this command:
  3. repotools-dm.bat -migration_dm_runUpgradeManager credentialsFile=credentials.txt

This command will instruction the DM Upgrade Manager to perform each of the upgrade steps. Information will be displayed as each upgrade step is started and when it finishes with its termination status; completed, not needed or failed. If an upgrade step fails you must examine the dm.log file to determine what caused the failure. If the problem can be fixed, simply run the DM repotools migration command again. This command can be run multiple times. Upgrade steps that were previously completed will show as not needed when the command is subsequently run. For upgrade steps that take a long time, such as re-indexing, a message will be displayed by the repotools command every 5 minutes to indicate the upgrade manager is still working.

The upgrade step Migrate Shadow Index Resources requires every DM model resource to be read, modified and written. This resource migration performs bulk reads and writes where the default is 200 resources at a time. During this shadow index resource migration an out-of-memory error can occur. If this happens, you must shut down the server and reduce the bulk processing size by defining a new JVM system property -Dcom.ibm.xtools.rmps.IndexResourceMigrator.bulkSize=10.

For a Tomcat application server, modify the JAVA_OPTS variable in the server/server.startup script file.
For a WebSphere application server, add another customer JVM property called com.ibm.xtools.rmps.IndexResourceMigrator.bulkSize with a value of 10. This custom property can be defined using the WebSphere Administrator console, in the same place that JAZZ_HOME is defined.

After this new JVM property is defined, restart the application server and run the DM repotools migration command again. Previously completed steps should be skipped and the migration of the shadow index resources should continue where it left off.

In Design Management for Rational Software Architect, if the new RSA-DM domain extension application was installed it must be registered with Design Management. One of the upgrade steps will look for the application running on the same application server and if found, will register it. If the domain extension application is running on a different application server, you will need to manually register that application with DM. To verify the domain extension was registered or to register it, log into <serverURL>/dm/admin and in the menubar click Domain Extension Servers. If the domain server is registered, it will appear on the page as being enabled and online. If it does not appear, click the Add New Server link. The URL has the format "https://host:port/rsadm". Ensure to check the enabled control in the dialog.

Version 4.0.5 and licenses

Version 4.0.5 applications will work with version 4.0.x licenses but do not work with version 3.0.1.x licenses. However, version 3.0.1.x applications work with version 4.0.5 licenses. In the form you indicated that you are upgrading from Rational Team Concert 3.0. You must obtain version 4.0.3 licenses. In the form you indicated that you are upgrading from CLM 3.0.1.x. You must obtain version 4.0.3 licenses. In the form you indicated that you are upgrading from Design Management 4.0.0.x. You are not required to obtain new licenses for version 4.0.3. In the form you indicated that you are upgrading from Design Management 4.0.1. You are not required to obtain new licenses for version 4.0.3. In the form you indicated that you are upgrading from Design Management 4.0.2. You are not required to obtain new licenses for version 4.0.3.In the form you indicated that you are upgrading from Design Management 4.0.3. You are not required to obtain new licenses for version 4.0.4.

Install version 4.0.5 floating, token, or authorized user single install licenses if their previous version counterparts had been used. Your existing user license assignments will be kept during installation of version 4.0.3 licenses.

Before starting the online migration of RM application, make sure that you have an active version 4.0 of the RM Application-Internal license assigned to the rm_user. For more information, see the "Migrating the Requirements Management application" step.

For more information about licenses, see Managing licenses.

Redeploying predefined templates

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

Enable the cluster

To enable the cluster, shut down the cluster member and application server on node 1. For detailed instructions, see Re-enabling the cluster.

Configure data warehouse

If you did not configure the data warehouse in your previous installation and want to configure a data warehouse for version 4.0.3, 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 4.0.3 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.

Verification checklist

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 4.0.4:
  • For Jazz Team Server: JTS_4.0.4_install_dir/server/conf/jts/teamserver.properties
  • For Lifecycle Project Administration application: JTS_4.0.4_install_dir/server/conf/admin/admin.properties
  • For Lifecycle Project Administration application: JTS_4.0.4_install_dir/server/conf/admin/friends.rdf
  • For Design Management application: DM_4.0.4_install_dir/server/conf/dm/teamserver.properties
 
Verify that each teamserver.properties file contains this information:
  • The properties copied from previous version of teamserver.properties
  • The com.ibm.team.repository.server.webapp.url property contains a valid, distinct public URL. The URL for version 4.0.4 application must be the same as the one used in 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 4.0.4_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 4.0.4_install_dir/server/tomcat/conf/server.xml file contains these code snippets:

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

    • The 4.0.4_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 RTC_3.0_install_dir3.0.1.x_install_dir4.0.0.x_install_dir4.0.1_install_dir4.0.2_install_dir4.0.3_install_dir/server/tomcat/conf/server.xml file, verify that those settings are copied to the 4.0.4_install_dir/server/tomcat/conf/server.xml file.
  • Verify that web.xml file has the correct <security-role> tags:
    • For Jazz Team Server: 4.0.4_install_dir/server/tomcat/webapps/jts/WEB-INF/web.xml
    • For Change and Configuration Management application: 4.0.4_install_dir/server/tomcat/webapps/ccm/WEB-INF/web.xml
    • For Quality Management application: 4.0.4_install_dir/server/tomcat/webapps/qm/WEB-INF/web.xml
  • Make sure that these applications are deployed and started:
    • jts_war
    • dm_war
    • rdmhelp_war
    • rsadm_war
    • vvc_war
    • vvchelp_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 4.0.3_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 DM or VVC 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:
  • Open a browser and log on to the admin page, for example, https://host.example.com:9443/jts/admin
  • 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 viewlets are working
  • Find and view existing artifacts and verify that the editors open properly
  • In Design Management application, verify folders, domain elements, graphical elements, RSA-domain elements.
  • In Configuration Management application, verify workspaces, snapshots, changesets.
 
Run the data collection jobs:
  • 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.
  • On the Reports page, click Data Collection Jobs.
  • Click Run all data warehouse collection jobs for all applications.
  • 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 Rational Requirements Composer with Rational ClearQuest and configure the applications to associate requirements with defects, tasks, requests for enhancements, and other record types. For more information, see Rational Requirements Composer 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 Manager

You can integrate IBM Rational Software Architect Design Manager 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 more information, see Rational Requirements Composer and Rational Software Architect Design Manager.