Select the options that apply to your environment to generate a customized guide to upgrade from a version 5 or version 6 release to version .

Upgrading from version 4 to a version 6 release: Upgrading from version 4 to any release of version 6 is a two-step process. You must first upgrade your server to the latest fix pack of the version 5 release, start the server, ensure that the version 5 upgrade was successful, and then upgrade to the version 6 release.

Important: If you use the reporting capabilities, after you upgrade to version 5, you must run an ETL job at least once before you upgrade to . Running the ETL job ensures that your reports will be migrated to . Starting in version 6.0, Data Collection Component replaced the Java ETL. Ensure that you install Data Collection Component in your environment.

### Select the applications to upgrade:

Note: You must upgrade Jazz Team Server first. In a distributed topology where Jazz Team Server and other CLM applications are installed on separate servers, upgrade Jazz Team Server first, and then upgrade each other application one at a time.

• #### Jazz Reporting Service

Note: Jazz Reporting Service first became available with CLM in version 6. If you are upgrading from version 5.x and had the Reporting applications installed as part of RRDI, you can select the applications here and upgrade them to the current release.

The Reporting applications must be at the same level as Jazz Team Server. If you upgrade Jazz Team Server at this time and leave the Reporting applications at previous version, the Reporting Service will not work until it is upgraded to the same level as Jazz Team Server.

The complete instructions to upgrade your product to version are generated based on the selections and inputs that you provided on the previous page.

• To upgrade to version , you must fully install the CLM application that you want to upgrade. The Update feature of IBM Installation Manager is not supported to upgrade server applications. When you start the installation, a warning might be displayed in IBM Installation Manager® about an existing package named Jazz Team Server. Continue with the installation into a new directory and a package group. On the context root selection page, select an option to align the context roots of installed applications with context root values that you used in your deployment of previous versions. For example, if you installed a CLM application with a custom context root, you must use the same context root in the current upgraded version as well.
• After you install the new version applications, ensure to apply the latest interim fix to your installation before you continue with the upgrade. This ensures that your new version applications are up-to-date. To check if there are any interim fixes available for your product, visit Fix Central on IBM Support Portal page.
• For larger repositories (greater than 100K artifacts), the default heap size in the repotools-app (where app is the application that you are upgrading) is too small. You must increase the heap size to 8 GB (up to a maximum of 24 GB) to avoid issues during the upgrade. Increasing the heap size, also improves the upgrade performance by up to 20% for smaller repositories.

To increase the heap size, in the repotools-app file search for :default_mx_size and update its value as follow:

set VMARGS=%VMARGS% -Xmx8G

VMARGS="$VMARGS -Xmx8G" For information about performance testing and benchmarks, see this deployment wiki article. • Before you start the upgrade, make sure to clean up the /tmp/ directory and remove any CLM related files and directories such as, -JazzRepo, rrc_reports, contentservice, and so on. • Before you can upgrade your Data Collection Component to version , all versions of Rational DOORS Next Generation older than version 6.0.4 must have the latest interim fix installed. In addition, Jazz Team Server must also be upgraded to version . • Every six hours, the Report Builder database is backed up so that you can restore the data if an error occurs. The database backup is created in the Jazz_install_dir/server/conf/rs/db_backup directory. Ensure that you have enough disk space for the backup procedure. For more information, see Changing the database backup interval. • The user who runs the upgrade scripts or repository tools commands must be a member of an administrative account and must be able to write to the installation directory of the application that is being upgraded and to the Jazz Team Server installation directory. These permissions are required so that during the upgrade log files can be written to the installation directories. Otherwise, the upgrade fails. • In Rational DOORS Next Generation , you create project baselines instead of module baselines. If you migrate from a version 5 release to the release, all module baselines are converted to project baselines. Note that you cannot copy a module from a project baseline. • On IBM i, if you upgrade from a version 5 release to , the upgrade takes longer than previous upgrades because the database includes structural changes to support new features. • Starting in version 6.0.6.1, the required Java version is 8. • Adjust the Java virtual machine arguments. For more information about JVM settings, see Setting up WebSphere Application Server. • The upgrade process to version uses your existing databases. The addTables and upgradeWarehouse command will update the databases to the version formats. • If you installed multiple Jazz applications on the same application server profile, you must upgrade those applications to version at the same time. If you deployed each application into a separate application server profile, you can upgrade the applications independently. • Changes in authentication methods such as switching from Tomcat users to LDAP must be treated as a separate effort, before or after the upgrade. • Starting in version 6.0.4, Data Collection Component no longer collects trend metrics broken down by users (owners or creators). This change was necessary to avoid metric data growth which contributes to performance degradation over time. This new behavior can be disabled by following the steps outlined in the readme file at server_installdir/server/conf/dcc/mapping/legacy. • The Report Builder application cannot be upgraded by using individual repotools commands. You must use the upgrade-rs wrapper script to upgrade. The wrapper script is not supported in a configuration where you can upgrade the Report Builder application from another server, such as Jazz Team Server that cannot access the network drive where the Report Builder application is installed on. • Starting in version 6.0.3 of Rational solution for Collaborative Lifecycle Management, Apache Geronimo project javax.mail library is used instead of Oracle javax.mail library for email settings. This might have an impact if your system has a firewall between the SMTP server and Jazz Team Server, and also you have a monitoring solution such as MailGaurd that monitors the SMTP traffic. For details, see Troubleshooting the SMTP server. ### 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 Gather required information: Before starting the upgrade process, you must gather and record specific data that is required during the upgrade process, such as URLs, user IDs and passwords, database locations, name of databases installed, and so on. Verify that your hardware and software meet the minimum system requirements: New requirements exist for version , and a few older versions might be 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 or Passport Advantage. 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 . 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. • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command. • You backed up your database before you started the upgrade process. IBM Db2i database is preconfigured on your IBM i system. • You have the correct user name and password. • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command. • You backed up your database before you started the upgrade process. For more information about backing up databases, see your database vendor documentation. • The required Java Database Connectivity (JDBC) driver is ojdbc8.jar. • Restriction: Because of a defect in Oracle JDBC driver 12.1.0.2.0, this version of the driver cannot be used. For details, see repotools -createTables command fails with ORA-01000 on Oracle 12 on the IBM Support portal page. • You created an environment variable named ORACLE_JDBC_DRIVER_FILE and pointed to the JDBC driver. • To avoid performance issues, ensure that Oracle Bug ID 13077335.8 is applied and enabled on the Oracle system hosting Rational DOORS Next Generation. See the Oracle documentation for details. • You have the correct user name and password. • Before you start the upgrade process, verify the integrity of the database by running the -verify repotools command. • 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 sqljdbc42.jar. • You created an environment variable named SQLSERVER_JDBC_DRIVER_FILE and pointed to the JDBC driver. • The SQL service is started. Important: Before you start the Quality Management - Requirements Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK 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. For information about the verify command, see Repository tools command to verify the integrity of a database Learn about licensing: Click the link to learn about licenses in this release. Important: You must obtain new licenses from the License Key Center and update your current licenses. See the "Update license files" step for details. Managing licensing Check the 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 the client and server compatibility: Jazz Team Server must be at the same level as or newer than the applications that are registered with it, but the applications cannot have a newer version than Jazz Team Server. For more information, see Client and server version compatibility Check your Java Virtual Machine options: Make sure that the Java Virtual Machine has the appropriate heap size setting. If you are installing all applications on one server for trial or demo, ensure you have enough memory installed. The JVM settings for the LibertyTomcat server can be adjusted in the server.startup file. 1. To set these properties in WebSphere Integrated Solutions Console, click Servers > Server Types > WebSphere application servers > server1. 2. Under Server Infrastructure, click Java and Process Management > Process definition. 3. Under Additional Properties, click Java Virtual Machine. 4. In the Generic JVM arguments field, check that the following lines exist: -Xmx4g -Xms4g -Xmn1g -Xgcpolicy:gencon -Xnocompressedrefs -Xmx4g -Xms4g -Xmn1g -Xgcpolicy:gencon -Xcompressedrefs -Xgc:preferredHeapBase=0x100000000 Tip: If you need more heap size, then you can use the following setting, replacing {N} with the amount of memory to be used and {N/4} with 1/4 of the total memory. For example, if -Xmx is set to 8g, -Xmn should be set to 2g. -Xmx{N} -Xms{N} -Xmn{N/4} For Lifecycle Query Engine only: If Lifecycle Query Engine application pages become unresponsive as a result of memory issues, see this technote for troubleshooting. For Rational DOORS Next Generation only: The -Xmn value should be 33% of the -Xmx value. For example, if the -Xmx size is 4gb, the -Xmn should be 1365m. In addition, for large deployments you should increase the Xmx value in the repotools files from the default 1500M to 8192M or higher. This increase in the Xmx value is necessary to improve performance and avoid out of memory errors during the execution of repotools -reindex all command. For more information on how to adjust the repotools command, see the technote link in the More information column. 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 These abbreviations refer to applications: • CLM: The Rational solution for Collaborative Lifecycle Management • JTS: Jazz Team Server • CCM: Change and Configuration Management • QM: Quality Management • RM: Requirements Management • RELM: Rational Engineering Lifecycle Manager • LQE: Lifecycle Query Engine • JRS: Jazz Reporting Service • RB: Report Builder • DCC: Data Collection Component • LDX: Link Index Provider • DM: Design Management • AM: Architecture Management • RMM: Rhapsody Model Manager • GCM: Global Configuration Management • DCM: Distributed Cache Microservice ### Stage a test environment for the upgrade process ### Special instructions for upgrading on IBM i ### 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 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) • Lifecycle Project Administration (admin_war) • Change and Configuration Management (ccm_war) • Quality Management (qm_war) • Requirements Management (rm_war) • Rational Engineering Lifecycle Manager (relm_war) • Global Configuration Management (gc_war) • Link Index Provider (ldx_war) • Report Builder (rs_war) • Lifecycle Query Engine (lqe_war) • Data Collection Component (dcc_war) ### Repair multiple versions of an artifact marked as current in the configuration If you used Configuration Management in 6.0.2 and earlier versions of Rational DOORS Next Generation, Design Management, Quality Management, if multiple users updated an artifact in a configuration at the same time, inconsistent versions of the artifact might be displayed in the configuration. This problem occurs because multiple versions of the artifact are internally marked as the current version. For example, you might experience the following issues: • Different views show different versions of an artifact for the same configuration. • An artifact cannot be found. This issue no longer occurs in version 6.0.3 and later, but might be present in those versions if you upgraded from an earlier release. You can run the following query to detect if a configuration has more than one current version of an artifact: SELECT DISTINCT CONFIGURATION_ITEM_ID FROM VVCMODEL.VERSION WHERE CURRENT_COL = 1 GROUP BY CONFIGURATION_ITEM_ID, CONCEPT HAVING COUNT(CONCEPT) > 1 SELECT DISTINCT CONFIGURATION_ITEM_ID FROM VVCMODEL_VERSION WHERE CURRENT_COL = 1 GROUP BY CONFIGURATION_ITEM_ID, CONCEPT HAVING COUNT(CONCEPT) > 1 If the query finds more than one current version, open a command windowshell and enter the following commands: Important: The -repairMultipleVersionsMarkedAsCurrent repository tools command is available in the latest Interim Fix of each release. You must apply the latest iFix before you can use the command. If you run the query and there are more than one current version of an artifact but the -repairMultipleVersionsMarkedAsCurrent repository tools command is not available, do not upgrade to version . For Rational DOORS Next Generation cd \/server repotools-rm.bat./repotools-rm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/rm smartCard=<none> certificateFile=<none> kerberos=<none> For Quality Management cd \/server repotools-qm.bat./repotools-qm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/qm smartCard=<none> certificateFile=<none> kerberos=<none> For Design Management cd \/server repotools-dm.bat./repotools-dm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/dm smartCard=<none> certificateFile=<none> kerberos=<none> For Rational DOORS Next Generation cd \/server repotools-rm.bat./repotools-rm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/rm smartCard=<none> certificateFile=<none> kerberos=<none> For Quality Management cd \/server repotools-qm.bat./repotools-qm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/qm smartCard=<none> certificateFile=<none> kerberos=<none> For Design Management cd \/server repotools-dm.bat./repotools-dm.sh -repairMultipleVersionsMarkedAsCurrent credentialsFile=credentials.properties Sample credentials.properties file: adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/dm smartCard=<none> certificateFile=<none> kerberos=<none> For more information about the repairMultipleVersionsMarkedAsCurrent repository tools command, see Repository tools command to repair multiple versions of an artifact marked as current. Depending on the size of your database, the utility might take a while to scan the entire database. The server must be running when you run the repository tools command and no restart is required after the command is complete. If you are prompted for the following message, you can safely ignore it: repair: YYYY-MM-DD HH:MM:SS,### [Number of configurations] Configurations Modified. Please shutdown the server and run the reindex command. ### Update license files Important: If you are not upgrading all applications to at the same time, you must apply an interim fix to the applications at earlier versions. The following releases contain the compatible version of Java: > 6.0.5 or later > 6.0.4 interim fix 007 or later > 6.0.3 interim fix 010 or later > 6.0.2 interim fix 015 or later > 5.0.2 interim fix 027 or later If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues. If you are using WebSphere Liberty, the new Java version that is shipped with version is not compatible and blocks the access to MD5 signed license files. The licenses have been updated in the IBM Rational License Key Center to use a newer signature algorithm. Complete the following steps to update your current license files: If you are using WebSphere Application ServerApache Tomcat and you updated your Java, the new Java version might not be compatible and blocks the access to MD5 signed license files. The licenses have been updated in the IBM Rational License Key Center to use a newer signature algorithm. Complete the following steps to update your current license files: For Term (Floating or Authorized User) or Token licenses: 1. Before you upgrade, log into Jazz Team Server and go to Server > License Key Management and make a note of what licenses you have on your server. 2. Log into the IBM Rational License Key Center and under License Management, click Return Keys. 3. Click the product link that you want to return the license keys for, and then click Return. 4. After the license is returned, click Get Keys. 5. Click the product link that you want to generate licenses for. 6. When prompted, fill in the required information and click Generate. 7. Download the new file that contains your new licenses. 8. Note: For Token licenses, you are only required to download the jazztokens.zip file. Because there are no changes in the license.dat file, you are not required to download this file. 9. In Jazz Team Server, go to Server > License Key Management and reimport the new license files; click Add to add a license and accept the license agreement and complete the wizard. 10. Note: You can also perform this step after you upgrade your server. For Non-Term Floating and Authorized User licenses: 1. Before you upgrade, log into Jazz Team Server and go to Server > License Key Management and make a note of what licenses you have on your server. 2. Log into the IBM Rational License Key Center and go to View keys by host or View keys by user. 3. Enter the information about the host or the user. 4. Select the product you want to generate the license for. 5. Click View Licenses for Selected Product Lines. 6. Select the license and click View Details. 7. Click Download Keys. 8. In Jazz Team Server, go to Server > License Key Management and reimport the new license files; click Add to add a license and accept the license agreement and complete the wizard. 9. Note: You can also perform this step after you upgrade your server. ### Install the new version applications Install the new version applications into a new package group, but do not run the setup wizard after the installation. For distributed configurations, install the version applications that correspond to the previously installed applications. At this point, you can also install the new applications that you did not have in your previous deployment, such as Jazz Reporting Service, Global Configuration Management, and so on. After the upgrade is complete, run the setup wizard to register these new applications with Jazz Team Server. For information about installing the server, see Installing by using IBM Installation Manager or Installing by using command-line commands. Install the CLM version applications, but do not run the setup wizard after the installation. For distributed configurations, install the version applications that correspond to the previously installed applications. For information about installing the server, see Installing on IBM i using licensed programs. Note: You must also install the trial license keys if you use the Enterprise Extension builds. Important: After you install the new version applications, ensure to apply the latest interim fix to your installation before you continue with the upgrade. This ensures that your new version applications are up-to-date. To check if there are any interim fixes available for your product, visit Fix Central on IBM Support Portal page. Note: In a clustered environment, you can install a new Change and Configuration Management (CCM) application on each node and modify the properties files, or install a new CCM application on the first node and, after modifying the files, copy the entire installation directory to the other nodes and change the node ID. ### Increase temporary table space in Oracle for large repositories If you have a large Quality Management application repository with millions of artifacts, the default temporary QM_TEMP table space is not sufficient to handle the temporary files. To avoid issues, you must add an additional temporary table space. To create an additional temporary table space, open a SQL *Plus window, log in as SYSTEM or SYSDBA, and enter the following command: alter tablespace QM_TEMP add tempfile 'ORACLE_BASE/oradata/CLMDB/QM_TEMP2.DBF' size 20m reuse autoextend on next 1m maxsize unlimited; In the command, QM_TEMP is the temporary table space name, ORACLE_BASE is the absolute path where Oracle is installed, CLMDB is the database name, and QM_TEMP2.DBF is the additional temporary file name that you want to create. ### Optional: Increase the Db2 configuration settings for large repositories If you have a large Quality Management repository with millions of artifacts, you can increase the Db2 configuration settings to ensure successful data migration. To increase the configuration settings, open a Db2 command window and enter the following commands: Note: These examples are for a repository with approximately ten million artifacts. Adjust the values according to the size of your data repository. db2 update db cfg for QM using APPLHEAPSZ 60000 db2 update db cfg for QM using LOGFILSIZ 4096 db2 update db cfg for QM using LOGPRIMARY 50 db2 update db cfg for QM using LOGSECOND 100 ### Optional: Maximize upgrade performance and execution for the Quality Management application If you have a large Quality Manager repository with millions of artifacts, you can minimize upgrade time and maximize upgrade performance by adding the following Java system variables to the repotools-qm script file: • Number of threads for migrating the version table records: You can increase the number of threads for migrating the version table records. The default value is 30. Example: • DEFINE="$DEFINE -Dcom.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.ThreadPoolCount4MigratingVTables=40"

• Thread timeout duration: You can also set the timeout duration for thread execution in hours. The default value is 12 hours. Example:
• DEFINE="$DEFINE -Dcom.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.ThreadTimeoutHours4MovingRecords=16" set DEFINE=%DEFINE% -Dcom.ibm.team.repository.service.internal.rdb.AbstractDatabaseService.ThreadTimeoutHours4MovingRecords="16" • Increase the default heap size: For large repositories, the default heap size in the repotools-qm is too small. To avoid issues during an upgrade, you must increase the heap size to 8 GB (up to a maximum of 24 GB). • To increase the heap size, in the repotools-qm file, search for :default_mx_size and increase its value to set VMARGS=%VMARGS% -Xmx8GVMARGS="$VMARGS -Xmx8G".

### Remove the Data Collection Component application friend relationship

If you manually defined friend relationships between the Data Collection Component (DCC) application and other CLM applications in version 5.x, this might cause DCC to fail populating the resource group automatically after the upgrade.

Before you upgrade the Data Collection Component application, remove all friend relationships to other applications except for Jazz Team Server. You must also remove the matching friend relationships from other applications to DCC. For details about removing friend relationships, see Deleting servers from the friends list.

### Install the Apache Tomcat server

Starting in version 6.0.1, Apache Tomcat is not provided as a default application server. For production environments, the preferred application servers are WebSphere Liberty or WebSphere Application Server. Apache Tomcat is an open-source tool that is not commercially supported. However, if you choose to use Apache Tomcat, complete the following steps to download and install version 7.0.59. If you are considering a complex deployment topology with Apache Tomcat, consult the Apache Tomcat documentation.

Note: In the following examples, the file paths use the default webapps location. If you copied the application WAR files to a different location when you installed CLM version 6.0.6.1, change the path accordingly.

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy all application WAR files to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy all application WAR files to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.

In a distributed environment, complete the following steps on each CLM application server.

#### Installing Apache Tomcat on Jazz Team Server / Link Index Provider

The Link Index Provider application must be installed on Jazz Team Server. If you have already installed Apache Tomcat on Jazz Team Server, follow step d. to copy the ldx.war file.

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the ldx.war, jts.war and clmhelp.war files to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the ldx.war, jts.war and clmhelp.war files to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version, to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Change and Configuration Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the ccm.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the ccm.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Architecture Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the am.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the am.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Requirements Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the rm.war and converter.war files to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the rm.war and converter.war files to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Quality Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the qm.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the qm.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Rational Engineering Lifecycle Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the relm.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the relm.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Data Collection Component server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the dcc.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the dcc.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Global Configuration Management server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the gc.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the gc.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you uded in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Lifecycle Query Engine server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the lqe.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the lqe.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Report Builder server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the rs.war file to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the rs.war file to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

#### Installing Apache Tomcat on the Design Manager server

1. Open a browser, go to the Apache Tomcat website, and download Apache Tomcat version 7.0.59.
4. The extraction process creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
5. Go to /server/webapps\server\webapps and copy the dm.war, rsadm.war, and clmhelp.war files to this location: /server/tomcat/webapps\server\tomcat\webapps.
6. Go to /server/webapps\server\webapps and copy the dm.war, rsadm.war, and clmhelp.war files to this location: /webapps\webapps.
7. Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file that you used in the previous version to this location: /server/tomcat\server\tomcat.
8. When you install CLM applications in a distributed environment, do not use the session cookie attribute because it can cause problems with cross-server authentication. Go to /server/tomcat/conf\server\tomcat\conf, open the context.xml file and ensure that the <Context> element does not include sessionCookiePath=/.

### 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, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours.

Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows:

DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL

EXEC DBMS_STATS.GATHER_DATABASE_STATS

For information about the Db2 database REORGCHK 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 \server\
repotools-qm.bat -onlineMigrateEstimate teamserver.properties=\server\conf\qm\teamserver.properties logFile=repotools_onlineMigrateEstimate.log

cd /server
./repotools-qm.sh -onlineMigrateEstimate teamserver.properties=/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 \server\
repotools-qm.bat -onlineMigrate teamserver.properties=\server\conf\qm\teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

cd /server/
./repotools-qm.sh -onlineMigrate teamserver.properties=/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.

Note: In a clustered environment, do this procedure only on the first node. You will replicate this node to other nodes in a later step.

Procedure

1. Before you start the Change and Configuration Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours.

Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows:

DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL

EXEC DBMS_STATS.GATHER_DATABASE_STATS

For information about the Db2 database REORGCHK 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 \server\
repotools-ccm.bat -onlineMigrateEstimate teamserver.properties=\server\conf\ccm\teamserver.properties logFile=repotools_onlineMigrateEstimate.log

cd /server/
./repotools-ccm.sh -onlineMigrateEstimate teamserver.properties=/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 \server\
repotools-ccm.bat -onlineMigrate teamserver.properties=\server\conf\ccm\teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50

cd /server/
./repotools-ccm.sh -onlineMigrate teamserver.properties=/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.

### Optional: Back up the WebSphere Application Server profile

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 this step on the application server that hosts:

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application

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

1. Open a command prompt and change to the bin folder of the WebSphere Application Server profiles directory. For example, cd \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.

For example:

Tip: You can restore the backed-up profile by running the restoreConfig.bat command. For example, restoreConfig.bat C:\WAS_backup\CLM_5.0.xCLM_6.0.x_profile.zip

1. Open a command shell and change to the bin folder of the WebSphere Application Server profiles directory. For example, cd /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.

For example:

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_5.0.xCLM_6.0.x_profile.zip

### Check server compatibility for upgrade

You can run the following repotools command before starting the upgrade process to determine if your server can be upgraded directly to version .

Before you begin

• Ensure your Design Management version 5.0.2 server is running.
• Ensure you have a credentials.txt file with the following content:

repositoryURL=https://hostname.example.com:9443/dm
smartCard=<none>
certificateFile=<none>
kerberos=<none>

Procedure

1. Open a command windowshell as an administrator and enter the following commands:

If the credentials.txt file is not located in the server directory, provide the absolute path to the file in the command line.

2. cd \server
repotools-dm.bat -migrate_dm_canMigrateDirectlyTo60x credentialsFile=credentials.txt

cd \server
repotools-dm.bat -migrate_dm_canMigrateDirectlyTo60x credentialsFile=credentials.txt

cd /server
./repotools-dm.sh -migrate_dm_canMigrateDirectlyTo60x credentialsFile=credentials.txt

cd /server
./repotools-dm.sh -migrate_dm_canMigrateDirectlyTo60x credentialsFile=credentials.txt

### Export the version 5.0.26 Configuration Management (VVC) data

Starting in version 6.0.1, Design Management application is based on local versioning instead of VVC to be aligned with other CLM applications. As a result, you must export your version 5.0.26 VVC, and then import it into version . Complete the following steps to export the VVC data.

1. Ensure that the version 6 VVC server is shut down.
2. Ensure that the version 5.0.2 VVC server is shut down.
5. Go to \server/server directory and if not present create a directory named patch.
6. Go to \server/server directory and if not present create a directory named patch.
9. Start the version 6 VVC server.
10. Start the version 5.0.2 VVC server.
11. Create a file named credentials.txt under the \/server directory with the following content:
12. Create a file named credentials.txt under the \/server directory with the following content:
repositoryURL=https://hostname.example.com:9443/vvc
smartCard=<none>
certificateFile=<none>
kerberos=<none>

14. Create a folder on your drive to export the VVC migration data. For example: C:\temp\vvcMigration/opt/tmp/vvcMigration.
15. Open a command windowshell as an administrator and enter the following commands:
16. cd \server
repotools-vvc.bat -clean -exportForMigration credentialsFile=credentials.txt exportPath=C:\temp\vvcMigration

cd \server
repotools-vvc.bat -clean -exportForMigration credentialsFile=credentials.txt exportPath=C:\temp\vvcMigration

cd /server
./repotools-vvc.sh -clean -exportForMigration credentialsFile=credentials.txt exportPath=/opt/tmp/vvcMigration

cd /server
./repotools-vvc.sh -clean -exportForMigration credentialsFile=credentials.txt exportPath=/opt/tmp/vvcMigration

### Stop and uninstall the previously installed applications from WebSphere Application Server

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

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application

1. Make sure the server is started and then log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
2. Click Applications > Application Types > WebSphere enterprise applications.
3. 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 counterpart.
4. 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 counterpart.
5. Click am_war and then under Detail Properties click Security role to user/group mapping. Write down the security roles mapping for am_war application. You will use this information to remap the application for its version 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 counterpart.
7. Click the Enterprise Applications link and then stop and uninstall the following installed applications:
• jts_war
• clmhelp_war
• ccm_war
• am_war
• qm_war
• rm_war
• converter_war
• relm_war
• lqe_war
• ldx_war
• dcc_war
• rs_war
• dm_war
• clmhelp_war
• vvc_war
• vvchelp_war
• gc_war
8. When you are prompted to save the changes to the master configuration, save them.

### Uninstall the previously installed applications from WebSphere Application Server

You can use the clm_undeploy.py script to remove all application WAR files that are installed on a single WebShpere Application Server.

You can use the clm_undeploy_distributed.py script to remove all application WAR files that you specify in your command argument as a comma-separated value.

1. Start the server by opening a command windowshell and entering the following commands. Replace server1 with the name of your server:
2. cd \bin
startServer.bat server1

cd /bin
./startServer.sh server1

Continue with the following steps to remove previous installed applications.

1. If you backed up your WebSphere Application Server profile in the previous step, the command shut down the server. Restart the server by opening a command windowshell and entering the following commands. Replace server1 with the name of your server:
2. cd \bin
startServer.bat server1

cd /bin
./startServer.sh server1

3. Enter the following command to remove the application WAR files. The clm_undeploy.py script removes all application WAR files that are installed in the profile. You must also provide the location of WAR files. The default directory for the WAR files during the installation is webapps. If you used a different directory, provide that location in the command syntax.
4. Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script.

Enter the following command to remove the application WAR files. The clm_undeploy_distributed.py script removes all application WAR files that you specify as a comma-separated value in the command argument. Ensure there are no spaces between the application names.

5. On the server that hosts Jazz Team Server / Link Index Provider enter the following command:

7. On the server that hosts the Change and Configuration Management application, enter the following command:

9. On the server that hosts the Rhapsody Model Manager application, enter the following command:

11. On the server that hosts the Quality Management application, enter the following command:

13. On the server that hosts the Requirements Management application, enter the following command:

15. On the server that hosts the Rational Engineering Lifecycle Manager application, enter the following command:

17. On the server that hosts the Data Collection Component application, enter the following command:

19. On the server that hosts the Report Builder application, enter the following command:

21. On the server that hosts the Lifecycle Query Engine application, enter the following command:

23. On the server that hosts the Rational Software Architect Design Management application, enter the following command:

25. On the server that hosts the Rational Rhapsody Design Manager application, enter the following command:

27. On the server that hosts the Global Configuration Management application, enter the following command:

### Update the JAZZ_HOME and configuration location custom properties

You can use the clm_was_config.py script to update JAZZ_HOME and configuration location custom properties.

Before you begin

1. If your Jazz Team Server is installed on a Windows platform, but you are using the Db2 for z/OS database server, open the JazzInstallDir/server/was/config.py for editing.
2. Search for db2zDriverPath=None and replace None with the file path to the location of the Db2z JDBC driver. For example: db2zDriverPath="/etc/jazz/server/db2z". Note the forward slash and also ensure that the driver path is enclosed in quotation marks.
3. To configure the Oracle JDBC driver location open the JazzInstallDir/server/was/config.py for editing.
4. Search for oracleDriverPath=None and replace None with the file path to the location of the Oracle JDBC driver. For example: oracleDriverPath="". Ensure that the driver path is enclosed in quotation marks.
5. To configure the SQL Server JDBC driver location open the JazzInstallDir/server/was/config.py for editing.
6. Search for sqlDriverPath=None and replace None with the file path to the location of the SQL Server JDBC driver. For example: sqlDriverPath="". Ensure that the driver path is enclosed in quotation marks.
7. Save and close the config.py file.

Procedure

1. Open a command window as administrator and enter the following commands:
2. Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the conf directory.

cd \bin

3. Open a command shell as administrator and enter the following commands:

cd /bin

4. Open a command window as administrator and enter the following commands:
5. Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the conf directory.

cd \bin

6. On the server that host Jazz Team Server / Link Index Provider enter the following commands:
7. cd /bin

8. On the server that host the Change and Configuration Management application, enter the following commands:
9. cd /bin

10. On the server that host the Rhapsody Model Manager application, enter the following commands:
11. cd /bin

12. On the server that host the Quality Management application, enter the following commands:
13. cd /bin

14. On the server that host the Requirements Management application, enter the following commands:
15. cd /bin

16. On the server that host the Rational Engineering Lifecycle Manager application, enter the following commands:
17. cd /bin

18. On the server that host the Data Collection Component application, enter the following commands:
19. cd /bin

20. On the server that host the Report Builder application, enter the following commands:
21. cd /bin

22. On the server that host the Lifecycle Query Engine application, enter the following commands:
23. cd /bin

24. On the server that host the Global Configuration Management application, enter the following commands:
25. cd /bin

26. On the server that host the Rational Rhapsody Design Manager application, enter the following commands:
27. cd /bin

28. On the server that host the Rational Software Architect Design Management application, enter the following commands:
29. cd /bin

### Update the JAZZ_HOME and configuration location custom properties

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

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global 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:///_install_dir/server/conf. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_/server/conffile:///opt/IBM/JazzTeamServer_/server/conffile:///usr/IBM/JazzTeamServer_/server/conf.
8. Click log4j.configuration and update its value to file:///_install_dir/server/conf/startup_log4j.properties. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_/server/conf/startup_log4j.propertiesfile:///opt/IBM/JazzTeamServer_/server/conf/startup_log4j.propertiesfile:///usr/IBM/JazzTeamServer_/server/conf/startup_log4j.properties.
9. Click lqe.config.location and update its value to file:///_install_dir/server/conf/lqe. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_/server/conf/lqefile:///opt/IBM/JazzTeamServer_/server/conf/lqefile:///usr/IBM/JazzTeamServer_/server/conf/lqe.
10. Click ldx.config.location and update its value to file:///_install_dir/server/conf/ldx. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_/server/conf/ldxfile:///opt/IBM/JazzTeamServer_/server/conf/ldxfile:///usr/IBM/JazzTeamServer_/server/conf/ldx.
11. If you are connecting to an Oracle database, ensure that ORACLE_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file in .
12. If you are connecting to SQL Server database, ensure that SQLSERVER_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file in .
13. Save the changes to the master configuration when prompted.

### Update the JRS shared library classpath

1. In WebSphere Integrated Solutions Console navigation pane click Environment > Shared libraries.
2. Click the JRS shard library name in the list to open it.
3. In the Classpath field, update the path to the new installation directory. For example:
4. \server\conf\rs\WAS_SharedLibrary/server/conf/rs/WAS_SharedLibrary

5. Click Apply and then Save directly to the master configuration.

### Stop WebSphere Application Server

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

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Any application that is registered with Jazz Team Server
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Global Configuration Management application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application

1. Open a command prompt and change to the \bin directory.
2. Enter the following command:

1. Open a command prompt and change to the /bin directory.
2. Enter the following command:

1. In QShell, navigate to the old configuration directory, for example, /QIBM/UserData/Old_JazzTeamServer/server
2. Enter the following command:

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

### Clean up the WebSphere Application Server temp directories

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

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application

Remove the application-related contents from the following directories in the profile:

Node_Name is the application server node name, for example, ADMINIB-SAQDV6VNode01.

• \temp\Node_Name\server1
• \temp\wscache
• /temp/Node_Name/server1
• /temp/wscache

Depending on which applications were installed, these directories might be in the profile and can be removed:

• jts_war
• ccm_war
• am_war
• qm_war
• rm_war
• converter_war
• clmhelp_war
• relm_war
• lqe_war
• ldx_war
• dcc_war
• rs_war
• dm_war
• clmhelp_war
• vvc_war
• vvchelp_war
• gc_war

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 this step on the application server that hosts:

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application

Remove the application-related log files from the following logs directory in the profile:

• \logs
• /logs

### Clear the WebSphere Application Server class cache

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

• Jazz Team Server/Link Index Provider
• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application

You must clear the WebSphere Application Server class cache to ensure that after the upgrade, the server is not using the previous versions of the classes. There are two types of class cache that must be cleared, the JVM's cache and the OSGi cache. Complete the following steps to clear these caches:

1. Stop WebSphere Application Server if it is running.
2. To clear the OSGi class cache, open a command windowshell and enter the following command:

cd \bin
osgiCfgInit.bat
/bin
./osgiCfgInit.sh

3. To clear the JVM's class cache, enter the following command:

cd \bin
clearClassCache.bat
/bin
./clearClassCache.sh

4. Note: If you are using the Windows service to start WebSphere Application Server, the command to clear the class cache might not work. In this case you must manually empty the content of the javasharedresources directory. Make sure the service is stopped before attempting to delete the files. Here is an example of the location of the javasharedresources directory: C:\Users\USER_NAME\AppData\Local\javasharedresources. Also note that AppData might be a hidden directory.

### Stop the servers

Open a command prompt and enter the following commands:

cd \server
server.shutdown.bat

Open a command shell and enter the following command:

cd /server
./server.shutdown

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

• Change and Configuration Management application
• Quality Management application
• Requirements Management application
• Any application that is registered with Jazz Team Server
• Rational Engineering Lifecycle Manager application
• Lifecycle Query Engine application
• Data Collection Component application
• Report Builder application
• Rational Rhapsody Design Manager application
• Rhapsody Model Manager application
• Rational Software Architect Design Management application
• Global Configuration Management application
• Jazz Team Server/Link Index Provider

Stop all applications first before stopping Jazz Team Server.

On the CCM server, open a command prompt and enter the following command:

Note: In a clustered environment, shut down all CCM nodes. You can leave the load-balancer (HAProxy) running unless changes are specifically needed for the new version.

cd \server
server.shutdown.bat

On the AM server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the QM server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the RM server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the RELM server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the DM server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the LQE server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the DCC server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the JRS server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the GC server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On Jazz Team Server, open a command prompt and enter the following command:

cd \server
server.shutdown.bat

On the CCM server, open a command shell and enter the following command:

Note: In a clustered environment, shut down all CCM nodes. You can leave the load-balancer (HAProxy) running unless changes are specifically needed for the new version.

cd /server
./server.shutdown

On the AM server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the QM server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the RM server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the RELM server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the DM server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the LQE server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the DCC server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the JRS server, open a command shell and enter the following command:

cd /server
./server.shutdown

On the GC server, open a command shell and enter the following command:

cd /server
./server.shutdown

On Jazz Team Server, open a command shell and enter the following command:

cd /server
./server.shutdown

### Stop the Distributed Cache Microservice (DCM)

To stop the microservice, open a command windowshell and enter the following commands:

cd Path_To_DCM_Folder
distributedCache.stop.bat JRE_Bin_Path

cd Path_To_DCM_Folder
./distributedCache.stop.sh JRE_Bin_Path

In these commands, Path_To_DCM_Folder is the location where the Distributed Cache Microservice is installed and JRE_Bin_Path is the location of the JRE/Bin folder. The path to the Bin folder is optional. If you do not specify a path, the system uses the default location for the microservice and uses the JRE that is provided by the CLM application.

### Delete persisted data

Starting in version 6.0.6, persistence is enabled by default for the Distributed Cache Microservice. When persistence is enabled, the microservice backs up in-memory distributed caches to disk. This persisted backup is used to initialize local caches on a node that is brought online after going offline in an unplanned manner. The persisted backup enables the node to initialize to the current state.

Also, in version 6.0.6 and later, the Distributed Cache Microservice monitors the online status of the applications' nodes. When a server on a node is shut down, a signal is sent to the microservice. After all nodes of a cluster are offline, the microservice clears all persisted distributed data for that cluster.

Cluster-specific data is stored in a subfolder of the clustering folder, which is specified in the configuration file as shown in the following example:

[Cache]

# Relative or absolute location on the file system to save cache data when the microservice is offline.
# This persisted data is only needed if DCM is restarted while clustered applications are running.
# When a planned shutdown of a clustered application using the cache is underway, it is advisable to delete the persisted data.
-persistentStore = $E{PERSISTENT_STORE, distributedData} By default, the subfolder is called distributedData. The subfolder contains a directory for each cluster with data on the Distributed Cache Microservice. After a planned shutdown of ALL nodes in a cluster occurs, delete the folder at this location: server/clustering/cache/<distributedData>/<clusterName>. This deletion allows distributed objects to reinitialize as expected when the nodes come back online. ### Copy the Lifecycle Query Engine (LQE) configuration files 1. Before copying the LQE configuration files, go to the directory where you just installed the version application and delete the following directories if they exist. In a fresh installation, these directories should not exist. Alternatively, you can open a command prompt and enter the following commands to delete the directories. 2. del /s /frm -rf \server\conf\lqe\indexTdb Enter Y to confirm the delete operation /server/conf/lqe/indexTdb del /s /frm -rf \server\conf\lqe\textIndex Enter Y to confirm the delete operation /server/conf/lqe/textIndex del /s /frm -rf \server\conf\lqe\shapeText Enter Y to confirm the delete operation /server/conf/lqe/shapeText del /s /frm -rf \server\conf\lqe\shapeTdb Enter Y to confirm the delete operation /server/conf/lqe/shapeTdb del /s /frm -rf \server\conf\lqe\historyText Enter Y to confirm the delete operation /server/conf/lqe/historyText del /s /frm -rf \server\conf\lqe\historyTdb Enter Y to confirm the delete operation /server/conf/lqe/historyTdb 3. Enter the following commands to copy the configuration files to the new installation directory: 4. xcopy /scp -R \server\conf\lqe\indexTdb/server/conf/lqe/indexTdb \server\conf\lqe\indexTdb If prompted, enter D to copy the directory structure /server/conf/lqe/indexTdb xcopy /scp -R \server\conf\lqe\textIndex/server/conf/lqe/textIndex \server\conf\lqe\textIndex If prompted, enter D to copy the directory structure /server/conf/lqe/textIndex xcopy /scp -R \server\conf\lqe\shapeText/server/conf/lqe/shapeText \server\conf\lqe\shapeText If prompted, enter D to copy the directory structure /server/conf/lqe/shapeText xcopy /scp -R \server\conf\lqe\shapeTdb/server/conf/lqe/shapeTdb \server\conf\lqe\shapeTdb If prompted, enter D to copy the directory structure /server/conf/lqe/shapeTdb xcopy /scp -R \server\conf\lqe\historyText/server/conf/lqe/historyText \server\conf\lqe\historyText If prompted, enter D to copy the directory structure /server/conf/lqe/historyText xcopy /scp -R \server\conf\lqe\historyTdb/server/conf/lqe/historyTdb \server\conf\lqe\historyTdb If prompted, enter D to copy the directory structure /server/conf/lqe/historyTdb copy cp \server\conf\lqe\lqe.properties/server/conf/lqe/lqe.properties \server\conf\lqe Enter Y to overwrite the existing file /server/conf/lqe copy cp \server\conf\lqe\lqe.node.id/server/conf/lqe/lqe.node.id \server\conf\lqe Enter Y to overwrite the existing file /server/conf/lqe copy cp \server\conf\lqe\lqe.key/server/conf/lqe/lqe.key \server\conf\lqe Enter Y to overwrite the existing file /server/conf/lqe copy cp \server\conf\lqe\dbconnection.properties/server/conf/lqe/dbconnection.properties \server\conf\lqe Enter Y to overwrite the existing file /server/conf/lqe If prompted, confirm that you want to overwrite the files. ### Copy the Link Index Provider (LDX) configuration files 1. Before copying the LDX configuration files, go to the directory where you just installed the version application and delete the following directories if they exist. In a fresh installation, these directories should not exist. Alternatively, you can open a command prompt and enter the following commands to delete the directories. 2. del /s /frm -rf \server\conf\ldx\indexTdb Enter Y to confirm the delete operation /server/conf/ldx/indexTdb del /s /frm -rf \server\conf\ldx\textIndex Enter Y to confirm the delete operation /server/conf/ldx/textIndex 3. Enter the following commands to copy the configuration files to the new installation directory: 4. xcopy /scp -R \server\conf\ldx\indexTdb/server/conf/ldx/indexTdb \server\conf\ldx\indexTdb If prompted, enter D to copy the directory structure /server/conf/ldx/indexTdb xcopy /scp -R \server\conf\ldx\textIndex/server/conf/ldx/textIndex \server\conf\ldx\textIndex If prompted, enter D to copy the directory structure /server/conf/ldx/textIndex copy cp \server\conf\ldx\lqe.properties/server/conf/ldx/lqe.properties \server\conf\ldx Enter Y to overwrite the existing file /server/conf/ldx copy cp \server\conf\ldx\lqe.node.id/server/conf/ldx/lqe.node.id \server\conf\ldx Enter Y to overwrite the existing file /server/conf/ldx copy cp \server\conf\ldx\lqe.key/server/conf/ldx/lqe.key \server\conf\ldx Enter Y to overwrite the existing file /server/conf/ldx copy cp \server\conf\ldx\dbconnection.properties/server/conf/ldx/dbconnection.properties \server\conf\ldx Enter Y to overwrite the existing file /server/conf/ldx If prompted, confirm that you want to overwrite the files. ### Copy the Derby databases from the previous installation directory to the new installation directory 1. Before copying the Derby database, go to the directory where you just installed the version applications and delete the content of Derby directory. Alternatively, you can open a command prompt and enter the following commands to clear the default version Derby directories. 2. Note: In a fresh installation, there is no derbyDB under the lqe ldx directory. But if you have already started the server, there might be a derbyDB directory that should be deleted. Enter the following command to delete the Jazz Team Server Derby database: del /s /f \server\conf\jts\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Change and Configuration Management Derby database: del /s /f \server\conf\ccm\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Rhapsody Model Manager Derby database: del /s /f \server\conf\am\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Quality Management Derby database: del /s /f \server\conf\qm\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Requirements Management Derby database: del /s /f \server\conf\rm\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Rational Engineering Lifecycle Manager Derby database: del /s /f \server\conf\relm\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Design Management Derby database: del /s /f \server\conf\dm\derby\repositoryDB Enter Y to confirm the delete operation del /s /f \server\conf\dm\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Global Configuration Management Derby database: del /s /f \server\conf\gc\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Data Collection Component Derby database: del /s /f \server\conf\dcc\derby\repositoryDB Enter Y to confirm the delete operation Enter the following command to delete the Lifecycle Query Engine Derby database if exists: del /s /f \server\conf\lqe\derbyDB Enter Y to confirm the delete operation Enter the following command to delete the Link Index Provider Derby database if exists: del /s /f \server\conf\ldx\derbyDB Enter Y to confirm the delete operation Enter the following command to delete the Jazz Team Server Derby database: rm -rf /server/conf/jts/derby/repositoryDB Enter the following command to delete the Change and Configuration Management Derby database: rm -rf /server/conf/ccm/derby/repositoryDB Enter the following command to delete the Rhapsody Model Manager Derby database: rm -rf /server/conf/am/derby/repositoryDB Enter the following command to delete the Quality Management Derby database: rm -rf /server/conf/qm/derby/repositoryDB Enter the following command to delete the Requirements Management Derby database: rm -rf /server/conf/rm/derby/repositoryDB Enter the following command to delete the Rational Engineering Lifecycle Manager Derby database: rm -rf /server/conf/relm/derby/repositoryDB Enter the following command to delete the Design Management Derby database: rm -rf /server/conf/dm/derby/repositoryDB rm -rf /server/conf/dm/derby/repositoryDB Enter the following command to delete the Global Configuration Management Derby database: rm -rf /server/conf/gc/derby/repositoryDB Enter the following command to delete the Data Collection Component Derby database: rm -rf /server/conf/dcc/derby/repositoryDB Enter the following command to delete the Lifecycle Query Engine Derby database if exists: rm -rf /server/conf/lqe/derbyDB Enter the following command to delete the Link Index Provider Derby database if exists: rm -rf /server/conf/ldx/derbyDB 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 . 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 the Derby database that is provided with the packaged product. If you changed your Derby database location, update the path accordingly. Enter the following command to copy the Jazz Team Server database: xcopy /s \server\conf\jts\derby\repositoryDB \server\conf\jts\derby\repositoryDB Enter the following command to copy the Change and Configuration Management database: xcopy /s \server\conf\ccm\derby\repositoryDB \server\conf\ccm\derby\repositoryDB Enter the following command to copy the Rhapsody Model Manager database: xcopy /s \server\conf\am\derby\repositoryDB \server\conf\am\derby\repositoryDB Enter the following command to copy the Quality Management database: xcopy /s \server\conf\qm\derby\repositoryDB \server\conf\qm\derby\repositoryDB Enter the following command to copy the Requirements Management database: xcopy /s \server\conf\rm\derby\repositoryDB \server\conf\rm\derby\repositoryDB Enter the following command to copy the Rational Engineering Lifecycle Manager database: xcopy /s \server\conf\relm\derby\repositoryDB \server\conf\relm\derby\repositoryDB Enter the following command to copy the Design Management database: xcopy /s \server\conf\dm\derby\repositoryDB \server\conf\dm\derby\repositoryDB Enter the following command to copy the Global Configuration Management database: xcopy /s \server\conf\gc\derby\repositoryDB \server\conf\gc\derby\repositoryDB Enter the following command to copy the Data Collection Component database: xcopy /s \server\conf\dcc\derby\repositoryDB \server\conf\dcc\derby\repositoryDB Enter the following command to copy the Lifecycle Query Engine database: xcopy /s \server\conf\lqe\derbyDB \server\conf\lqe\derbyDB If prompted, enter D to choose directory. Enter the following command to copy the Link Index Provider database: xcopy /s \server\conf\ldx\derbyDB \server\conf\ldx\derbyDB If prompted, enter D to choose directory. The Derby Data Warehouse database for Liberty will be located under the Liberty server. At this point, the Liberty server has not been created. Run the following command to create the Liberty server and then copy the Data Warehouse database: cd \server server.startup -create Enter the following command to copy the Data Warehouse database: xcopy /s \server\conf\jts\derby\warehouseDB\server\liberty\servers\clm\conf\jts\derby\warehouseDB \server\liberty\servers\clm\conf\jts\derby\warehouseDB\server\conf\jts\derby\warehouseDB Enter the following command to copy the Jazz Team Server database: xcopy /s \server\conf\jts\derby\repositoryDB \server\conf\jts\derby\repositoryDB Enter the following command to copy the Requirements Management database: xcopy /s \server\conf\rm\derby\repositoryDB \server\conf\rm\derby\repositoryDB Enter the following command to copy the Change and Configuration Management database: xcopy /s \server\conf\ccm\derby\repositoryDB \server\conf\ccm\derby\repositoryDB Enter the following command to copy the Rhapsody Model Manager database: xcopy /s \server\conf\am\derby\repositoryDB \server\conf\am\derby\repositoryDB Enter the following command to copy the Quality Management database: xcopy /s \server\conf\qm\derby\repositoryDB \server\conf\qm\derby\repositoryDB Enter the following command to copy the Rational Engineering Lifecycle Manager database: xcopy /s \server\conf\relm\derby\repositoryDB \server\conf\relm\derby\repositoryDB Enter the following command to copy the Design Management database: xcopy /s \server\conf\dm\derby\repositoryDB \server\conf\dm\derby\repositoryDB Enter the following command to copy the Global Configuration Management database: xcopy /s \server\conf\gc\derby\repositoryDB \server\conf\gc\derby\repositoryDB Enter the following command to copy the Data Collection Component database: xcopy /s \server\conf\dcc\derby\repositoryDB \server\conf\dcc\derby\repositoryDB Enter the following command to copy the Lifecycle Query Engine database: xcopy /s \server\conf\lqe\derbyDB \server\conf\lqe\derbyDB If prompted, enter D to choose directory. Enter the following command to copy the Link Index Provider database: xcopy /s \server\conf\ldx\derbyDB \server\conf\ldx\derbyDB If prompted, enter D to choose directory. The Derby Data Warehouse database for Liberty will be located under the Liberty server. At this point, the Liberty server has not been created. Run the following command to create the Liberty server and then copy the Data Warehouse database: cd \server server.startup -create Enter the following command to copy the Data Warehouse database: xcopy /s \server\conf\jts\derby\warehouseDB\server\liberty\servers\clm\conf\jts\derby\warehouseDB \server\liberty\servers\clm\conf\jts\derby\warehouseDB\server\conf\jts\derby\warehouseDB In a WebSphere Application Sever deployment, the default data warehouse database location is under WebSphere installation directory. Enter the following command to copy the Data Warehouse database: xcopy /s WAS_install_dir\OldAppServerHostIntall\jts\derby\conf\warehouseDB WAS_install_dir\AppServerHost6Intall\jts\derby\conf\warehouseDB Enter the following command to copy the Jazz Team Server database: cp -R /server/conf/jts/derby/repositoryDB /server/conf/jts/derby/repositoryDB Enter the following command to copy the Change and Configuration Management database: cp -R /server/conf/ccm/derby/repositoryDB /server/conf/ccm/derby/repositoryDB Enter the following command to copy the Rhapsody Model Manager database: cp -R /server/conf/am/derby/repositoryDB /server/conf/am/derby/repositoryDB Enter the following command to copy the Quality Management database: cp -R /server/conf/qm/derby/repositoryDB /server/conf/qm/derby/repositoryDB Enter the following command to copy the Requirements Management database: cp -R /server/conf/rm/derby/repositoryDB /server/conf/rm/derby/repositoryDB Enter the following command to copy the Rational Engineering Lifecycle Manager database: cp -R /server/conf/relm/derby/repositoryDB /server/conf/relm/derby/repositoryDB Enter the following command to copy the Design Management database: cp -R /server/conf/dm/derby/repositoryDB /server/conf/dm/derby/repositoryDB Enter the following command to copy the Global Configuration Management database: cp -R /server/conf/gc/derby/repositoryDB /server/conf/gc/derby/repositoryDB Enter the following command to copy the Data Collection Component database: cp -R /server/conf/dcc/derby/repositoryDB /server/conf/dcc/derby/repositoryDB Enter the following command to copy the Lifecycle Query Engine database: cp -R /server/conf/lqe/derbyDB /server/conf/lqe/derbyDB Enter the following command to copy the Link Index Provider database: cp -R /server/conf/ldx/derbyDB /server/conf/ldx/derbyDB The Derby Data Warehouse database for Liberty will be located under the Liberty server. At this point, the Liberty server has not been created. Run the following command to create the Liberty server and then copy the Data Warehouse database: cd /server ./server.startup -create Enter the following command to copy the Data Warehouse database: cp -R /server/conf/jts/derby/warehouseDB/server/liberty/servers/clm/conf/jts/derby/warehouseDB /server/liberty/servers/clm/conf/jts/derby/warehouseDB/server/conf/jts/derby/warehouseDB Enter the following command to copy the Jazz Team Server database: cp -R /server/conf/jts/derby/repositoryDB /server/conf/jts/derby/repositoryDB Enter the following command to copy the Requirements Management database: cp -R /server/conf/rm/derby/repositoryDB /server/conf/rm/derby/repositoryDB Enter the following command to copy the Change and Configuration Management database: cp -R /server/conf/ccm/derby/repositoryDB /server/conf/ccm/derby/repositoryDB Enter the following command to copy the Rhapsody Model Manager database: cp -R /server/conf/am/derby/repositoryDB /server/conf/am/derby/repositoryDB Enter the following command to copy the Quality Management database: cp -R /server/conf/qm/derby/repositoryDB /server/conf/qm/derby/repositoryDB Enter the following command to copy the Rational Engineering Lifecycle Manager database: cp -R /server/conf/relm/derby/repositoryDB /server/conf/relm/derby/repositoryDB Enter the following command to copy the Design Management database: cp -R /server/conf/dm/derby/repositoryDB /server/conf/dm/derby/repositoryDB Enter the following command to copy the Global Configuration Management database: cp -R /server/conf/gc/derby/repositoryDB /server/conf/gc/derby/repositoryDB Enter the following command to copy the Data Collection Component database: cp -R /server/conf/dcc/derby/repositoryDB /server/conf/dcc/derby/repositoryDB Enter the following command to copy the Lifecycle Query Engine database: cp -R /server/conf/lqe/derbyDB /server/conf/lqe/derbyDB Enter the following command to copy the Link Index Provider database: cp -R /server/conf/ldx/derbyDB /server/conf/ldx/derbyDB The Derby Data Warehouse database for Liberty will be located under the Liberty server. At this point, the Liberty server has not been created. Run the following command to create the Liberty server and then copy the Data Warehouse database: cd /server ./server.startup -create Enter the following command to copy the Data Warehouse database: cp -R /server/conf/jts/derby/warehouseDB/server/liberty/servers/clm/conf/jts/derby/warehouseDB /server/liberty/servers/clm/conf/jts/derby/warehouseDB/server/conf/jts/derby/warehouseDB In a WebSphere Application Sever deployment, the default data warehouse database location is under WebSphere installation. Enter the following command to copy the Data Warehouse database: cp -R WAS_install_dir/OldAppServerHostIntall/jts/derby/conf/warehouseDB WAS_install_dir/AppServerHost6Intall/jts/derby/conf/warehouseDB ### Import the version 5.0.26 VVC data into version (purgeCache command) After you export your version 5.0.26 VVC data, now you can import them into version . There are 2 repotools commands used for this operation. The first command is -migration_dm_purgeCache that must be entered at this step before the database tables are updated, and the second command is -migration_dm_importvvc which must be entered after the database tables are updated. 1. Open a command windowshell as an administrator and enter the following commands: 2. cd \server repotools-dm.bat -migration_dm_purgeCache teamserver.properties=\server\conf\dm\teamserver.properties cd \server repotools-dm.bat -migration_dm_purgeCache teamserver.properties=\server\conf\dm\teamserver.properties cd /server ./repotools-dm.sh -migration_dm_purgeCache teamserver.properties=/server/conf/dm/teamserver.properties cd /server ./repotools-dm.sh -migration_dm_purgeCache teamserver.properties=/server/conf/dm/teamserver.properties 3. After the purging cache command is complete, continue with the next step to upgrade your Design Management 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. Important: In the 6.0.6.1 release, the Apache Lucene full-text search engine was upgraded to a more recent version. This upgrade requires all existing full-text search indexes that were created in 6.0.6 or earlier to be rebuilt. By default, the workitemindex folder contains the full-text index files and is located under JazzInstallDir/server/conf/app/indices. If the workitemindex folder is configured in a different location, such as the WebSphere Application Server profile directory, do not copy the old files. If the workitemindex folder is located at the default location under JazzInstallDir/server/conf/app/indices, after copying the JFS index files, ensure to delete all files in the workitemindex folder. Copy your JFS/text indices from previous installation directory to . 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 indices directory: del /s /f \server\conf\jts\indices del /s /f \server\conf\ccm\indices del /s /f \server\conf\am\indices del /s /f \server\conf\qm\indices del /s /f \server\conf\rm\indices del /s /f \server\conf\dcc\indices del /s /f \server\conf\relm\indices del /s /f \server\conf\gc\indices Enter Y to confirm the delete operation rm -rf /server/conf/jts/indices rm -rf /server/conf/ccm/indices rm -rf /server/conf/am/indices rm -rf /server/conf/qm/indices rm -rf /server/conf/rm/indices rm -rf /server/conf/dcc/indices rm -rf /server/conf/relm/indices rm -rf /server/conf/gc/indices 2. Open a command prompt and enter this command to copy the indices from the previous installation to version : xcopy /s \server\conf\jts\indices \server\conf\jts\indices xcopy /s \server\conf\ccm\indices \server\conf\ccm\indices xcopy /s \server\conf\am\indices \server\conf\am\indices xcopy /s \server\conf\qm\indices \server\conf\qm\indices xcopy /s \server\conf\rm\indices \server\conf\rm\indices xcopy /s \server\conf\dcc\indices \server\conf\dcc\indices xcopy /s \server\conf\relm\indices \server\conf\relm\indices xcopy /s \server\conf\gc\indices \server\conf\gc\indices xcopy /s \server\conf\dm\indices \server\conf\dm\indices xcopy /s \server\conf\dm\indices \server\conf\dm\indices cp -R /server/conf/jts/indices /server/conf/jts/indices cp -R /server/conf/ccm/indices /server/conf/ccm/indices cp -R /server/conf/am/indices /server/conf/am/indices cp -R /server/conf/qm/indices /server/conf/qm/indices cp -R /server/conf/rm/indices /server/conf/rm/indices cp -R /server/conf/dcc/indices /server/conf/dcc/indices cp -R /server/conf/relm/indices /server/conf/relm/indices cp -R /server/conf/gc/indices /server/conf/gc/indices cp -R /server/conf/dm/indices /server/conf/dm/indices cp -R /server/conf/dm/indices /server/conf/dm/indices 3. Ensure to delete the content of the workitemindex folder. To copy your JFS/text indices from a previous installation to version , 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 indices directory: Del /s /f \server\conf\jts\indices Del /s /f \server\conf\ccm\indices Del /s /f \server\conf\am\indices Del /s /f \server\conf\qm\indices Del /s /f \server\conf\rm\indices Del /s /f \server\conf\dcc\indices Del /s /f \server\conf\relm\indices Del /s /f \server\conf\gc\indices rm -rf /server/conf/jts/indices rm -rf /server/conf/ccm/indices rm -rf /server/conf/am/indices rm -rf /server/conf/qm/indices rm -rf /server/conf/rm/indices rm -rf /server/conf/dcc/indices rm -rf /server/conf/relm/indices rm -rf /server/conf/gc/indices 2. In the following location open the teamserver.properties file and search for com.ibm.team.fulltext.indexlocation and com.ibm.team.jfs.index.root.directory: • \server\conf\jts\/server/conf/jts/teamserver.properties • \server\conf\qm\/server/conf/qm/teamserver.properties • \server\conf\ccm\/server/conf/ccm/teamserver.properties • \server\conf\am\/server/conf/am/teamserver.properties • \server\conf\dcc\/server/conf/dcc/teamserver.properties • \server\conf\relm\/server/conf/relm/teamserver.properties • \server\conf\gc\/server/conf/gc/teamserver.properties • \server\conf\dm\/server/conf/dm/teamserver.properties • \server\conf\dm\/server/conf/dm/teamserver.properties 3. If the com.ibm.team.fulltext.indexLocation and com.ibm.team.jfs.index.root.directory properties are pointing to a relative path, for example, com.ibm.team.fulltext.indexLocation=conf/application_context_root/indices/workitemindex, depending on how the previous version of the application was installed or customized, the work item index and JFS index root might be located relative to the WebSphere Application Server profile hosting the applications. For example: , or relative to the application's installation directory. Change this relative path to an absolute path to a stable location. An example of absolute stable location for work item index looks like this: com.ibm.team.fulltext.indexLocation=_install_dir/server/conf/application_context_root/indices/workitemindex where _install_dir is the location where CLM application is installed. An example of absolute stable location for JFS index root looks like this: com.ibm.team.jfs.index.root.directory=_install_dir/server/conf/application_context_root/indices where _install_dir is the location where CLM application is installed. If the com.ibm.team.fulltext.indexLocation or com.ibm.team.jfs.index.root.directory properties are pointing to an 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 as mentioned previously. 4. Open a command prompt and enter the following command to copy the full text indices from previous version to . Change the source directory according to the location of the index files: 5. xcopy /s \server\conf\jts\indices \server\conf\jts\indices xcopy /s \server\conf\ccm\indices \server\conf\ccm\indices xcopy /s \server\conf\am\indices \server\conf\am\indices xcopy /s \server\conf\qm\indices \server\conf\qm\indices xcopy /s \server\conf\rm\indices \server\conf\rm\indices xcopy /s \server\conf\dcc\indices \server\conf\dcc\indices xcopy /s \server\conf\relm\indices \server\conf\relm\indices xcopy /s \server\conf\gc\indices \server\conf\gc\indices xcopy /s \server\conf\dm\indices \server\conf\dm\indices xcopy /s \server\conf\dm\indices \server\conf\dm\indices cp -R /server/conf/jts/indices /server/conf/jts/indices cp -R /server/conf/ccm/indices /server/conf/ccm/indices cp -R /server/conf/am/indices /server/conf/am/indices cp -R /server/conf/qm/indices /server/conf/qm/indices cp -R /server/conf/rm/indices /server/conf/rm/indices cp -R /server/conf/dcc/indices /server/conf/dcc/indices cp -R /server/conf/relm/indices /server/conf/relm/indices cp -R /server/conf/gc/indices /server/conf/gc/indices cp -R /server/conf/dm/indices /server/conf/dm/indices cp -R /server/conf/dm/indices /server/conf/dm/indices 6. Ensure to delete the content of the workitemindex folder. ### Undo custom performance optimization A performance optimization for SQL Server was introduced in version 6.0 for the Requirements Management Design Management database which might result in a failed upgrade if left in place. Open a sqlcmd command line tool and enter the following commands to return the database to an expected state before running the upgrade scripts. DROP INDEX VERSION_CONCEPT_DX ON VVCMODEL.VERSION DROP INDEX VERSION_STORAGE_DX ON VVCMODEL.VERSION Note: You might be prompted for the following error message if the optimization has never been applied before, or you do not have permission to drop index on the database. If you do have permission and you are prompted for the error, you can skip the DROP INDEX command. "Msg 3701, Level 11, State 7, Line 1 Cannot drop the index 'VVCMODEL.VERSION.VERSION_CONCEPT_DX', because it does not exist or you do not have permission. Msg 3701, Level 11, State 7, Line 2 Cannot drop the index 'VVCMODEL.VERSION.VERSION_STORAGE_DX', because it does not exist or you do not have permission." ALTER TABLE VVCMODEL.VERSION ALTER COLUMN CONCEPT NVARCHAR(1000) ALTER TABLE VVCMODEL.VERSION ALTER COLUMN STORAGE NVARCHAR(1000) ### Run the upgrade commands 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__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. #### Upgrading Jazz Team Server Note: The -mergeLPAJTS command is only required if the /admin application was previously installed. If you did not install the /admin application in previous versions, do not run the -mergeLPAJTS command. To upgrade Jazz Team Server configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=\server\conf updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newTomcatHome= jtsContextRoot= repotools-jts.bat -addTables repotools-jts.bat -mergeLPAJTS oldJTSHome=\server\conf repotools-jts.bat -upgradeWarehouse repotools-jts.bat -updateLPASampleTemplates To upgrade Jazz Team Server configuration files, open a command shell and enter the following commands: cd /server ./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=/server/conf updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newTomcatHome= jtsContextRoot= ./repotools-jts.sh -addTables ./repotools-jts.sh -mergeLPAJTS oldJTSHome=/server/conf ./repotools-jts.sh -upgradeWarehouse ./repotools-jts.sh -updateLPASampleTemplates #### Communicate Tomcat users temporary passwords Tomcat user registry only: If you used a Tomcat user registry in your previous installation, the migration command creates a file named passwords.txt in the /\server directory that contains all repository users from the tomcat-users.xml file. Because the tomcat-users.xml file stores one-way-encrypted passwords, it is not possible to migrate these user passwords. Instead, the passwords.txt file contains temporary passwords for each user, which the server administrator must communicate to the users. After the server is started, users can change their temporary passwords. #### Upgrading Report Builder You can use the rs_upgrade wrapper script to upgrade the Report Builder application in this configuration with the -ignoreJTSVersionCheck flag so that the script does not try to connect to Jazz Team Server to check its version. You must make sure that Jazz Team Server is already upgraded before you attempt to upgrade the Report Builder application. Open a command prompt and enter the following commands. Note that wrapper script command arguments are different from repotools commands. You do not need an equal sign (=) for -oldApplicationHome, but you need to add a dash sign (-) before each argument, such as -oldApplicationHome or -ignoreJTSVersionCheck: cd \/server upgrade\rs\rs_upgrade.batupgrade/rs/rs_upgrade.sh -oldApplicationHome \server\conf/server/conf -ignoreJTSVersionCheck -applicationContextRoot -jtsContextRoot #### Upgrading the Change and Configuration Management application To upgrade the CCM application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-ccm.bat -migration_ccm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-ccm.bat -addTables To upgrade the CCM application configuration files, open a command shell and enter the following commands: cd /server ./repotools-ccm.sh -migration_ccm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-ccm.sh -addTables Note: In a clustered environment, upgrade only the first CCM node. You will replicate this node in a later step. #### Upgrading the Rhapsody Model Manager application To upgrade the Rhapsody Model Manager application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-am.bat -migration_am_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-am.bat -addTables To upgrade the Rhapsody Model Manager application configuration files, open a command shell and enter the following commands: cd /server ./repotools-am.sh -migration_am_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-am.sh -addTables #### Upgrading the Rational Engineering Lifecycle Manager application To upgrade the RELM application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-relm.bat -migration_relm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-relm.bat -addTables To upgrade the RELM application configuration files, open a command shell and enter the following commands: cd /server ./repotools-relm.sh -migration_relm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-relm.sh -addTables #### Upgrading the Design Management application To upgrade the Design Management application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-dm.bat -migration_dm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck applicationContextRoot=dm updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-dm.bat -addTables repotools-dm.bat -fixVersionTable To upgrade the DM application configuration files, open a command shell and enter the following commands: cd /server ./repotools-dm.sh -migration_dm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck applicationContextRoot=dm updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-dm.sh -addTables ./repotools-dm.sh -fixVersionTable #### Upgrading the Global Configuration Management application To upgrade the GC application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-gc.bat -migration_gc_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-gc.bat -addTables To upgrade the GC application configuration files, open a command shell and enter the following commands: cd /server ./repotools-gc.sh -migration_gc_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-gc.sh -addTables #### Upgrading the Data Collection Component application Note: If you are not upgrading your Requirements Management application at this time, you must have one of the following versions installed for the ETLs to run successfully: Rational DOORS Next Generation version 6.0.1 iFix11 Rational DOORS Next Generation version 6.0.2 iFix9 Rational DOORS Next Generation version 6.0.3 iFix2 Rational DOORS Next Generation version 6.0.4 GA Rational DOORS Next Generation version 6.0.5 GA Rational DOORS Next Generation version 6.0.6 GA To upgrade the DCC application configuration files, open a command window and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-dcc.bat -migration_dcc_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-dcc.bat -addTables To upgrade the DCC application configuration files, open a command shell and enter the following commands: cd /server ./repotools-dcc.sh -migration_dcc_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-dcc.sh -addTables #### Upgrading the Quality Management application Before you start the Quality Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade the QM application configuration files, open a command prompt and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-qm.bat -addTables cd /server ./repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-qm.sh -addTables #### Upgrading the Requirements Management application Before you start the Requirements Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade the RM application configuration files, open a command window and enter the following commands. If the path contains spaces, make sure that the path is enclosed in double-quotation marks: cd \server repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= repotools-rm.bat -addTables Run this command to remove the RM friend relationship with /admin: Important: The -mergeLPAJTS command must be able to access oldJTSHome. If the server that the old JAZZ Team Server is installed on is not reachable, the -mergeLPAJTS command would do nothing. In this case you must manually remove the /admin friend relationship. After the upgrade is complete and the server is started, log on to the Rational DOORS Next Generation administration page. On the Friend (Outbound) tab, remove the /admin friend entry. repotools-rm.bat -mergeLPAJTS lpaContextRoot=admin oldJTSHome=\server\conf onlyRemoveFriend=true oldApplicationHome=\server\conf oldApplicationVersion=5.05.0.1 applicationContextRoot= jtsContextRoot= To upgrade the RM application configuration files, open a command shell and enter the following commands: cd /server ./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome= applicationContextRoot= jtsContextRoot= ./repotools-rm.sh -addTables Run this command to remove the RM friend relationship with /admin: Important: The -mergeLPAJTS command must be able to access oldJTSHome. If the server that the old JAZZ Team Server is installed on is not reachable, the -mergeLPAJTS command would do nothing. In this case you must manually remove the /admin friend relationship. After the upgrade is complete and the server is started, log on to the Rational DOORS Next Generation administration page. On the Friend (Outbound) tab, remove the /admin friend entry. ./repotools-rm.sh -mergeLPAJTS lpaContextRoot=admin oldJTSHome=/server/conf onlyRemoveFriend=true oldApplicationHome=/server/conf oldApplicationVersion=5.05.0.1 applicationContextRoot= jtsContextRoot= #### Repotools commands usage The commands that you entered in the previous steps do these tasks: • Update the new configuration files based on the information from the older version. • Add tables to the databases. • The fixVersionTable command converts the version table information created in Design Management version 6.0.1 to later versions. • Starting in version 5.0.2 of the Rational solution for CLM, the Lifecycle Project Administration (LPA) application became part of Jazz Team Server. The mergeLPAJTS command migrates the LPA storage areas, indexes, and registrations. • Upgrade the data warehouse schema. • Update the Lifecycle Project Administration (LPA) sample templates. For more information about these Repository Tools commands, see these help topics: ### Optional: Create an environment variable to change the default verification level There is a migration verification done for Rational DOORS Next Generation after the upgrade that generates a report in the server directory. By default, this report contains 10% (value of 1) of the migration verification. You can create an environment variable and set the verification to the level that you want. A value of 0 does not validate anything and no report is generated. A value of 10 produces a report with all data validation. The higher the percentage of the data to be validated, the more time is required to complete the upgrade. To create an environment variable follow these steps: 1. Open Control Panel and click System. 2. Click Advanced system settings and then click Environment Variables. 3. Under System variables click New. 4. In the Variable name field enter validateData and in the Variable value field enter a number between 0 and 10. Note: The variable name must be typed exactly as shown. 5. Restart your system for the environment variable to take effect. 6. The report generation is automatic and a report named MigrationValidation.html is created in the _install_dir\server directory. Subsequent generated reports will have a time stamped after the file name. 1. Open a command shell and enter: 2. export validateData=a number between 0 and 10 Note: The variable name must be typed exactly as shown. The report generation is automatic and a report named MigrationValidation.html is created in the _install_dir/server directory. Subsequent generated reports will have a time stamped after the file name. ### 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 . 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__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. Also if your path includes spaces, ensure that is enclosed in double quotation marks. #### Upgrading Jazz Team Server To upgrade Jazz Team Server open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\jts\jts_upgrade.bat -oldJTSHome "\server\conf" -updateTomcatFiles yes -newTomcatHome -updateTomcatFiles no -updateAppServerFiles no -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt cd \server upgrade\jts\jts_upgrade.bat -oldJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt 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__install_dir/server/conf/jts/indices/workitemindex, where JTS__install_dir is the location where Jazz Team Server is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Communicate Tomcat users temporary passwords Tomcat user registry only: If you used a Tomcat user registry in your previous installation, the migration command creates a file named passwords.txt in the \server directory that contains all repository users from the tomcat-users.xml file. Because the tomcat-users.xml file stores one-way-encrypted passwords, it is not possible to migrate these user passwords. Instead, the passwords.txt file contains temporary passwords for each user, which the server administrator must communicate to the users. After the server is started, users can change their temporary passwords. #### Upgrading the Change and Configuration Management application To upgrade Change and Configuration Management application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, a window opens in which you can check the Change and Configuration teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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__install_dir/server/conf/ccm/indices/workitemindex where CCM__install_dir is the location where Change and Configuration Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. Note: In a clustered environment, upgrade only the first CCM node. You will replicate this node in a later step. #### Upgrading the Rhapsody Model Manager application To upgrade the Rhapsody Model Manager application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\am\am_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\am\am_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, a window opens in which you can check the Rhapsody Model Manager teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=RMM__install_dir/server/conf/am/indices/workitemindex where RMM__install_dir is the location where Rhapsody Model Manager application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Rational Engineering Lifecycle Manager application To upgrade the Rational Engineering Lifecycle Manager application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\relm\relm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\relm\relm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Rational Engineering Lifecycle Manager 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=RELM__install_dir/server/conf/relm/indices/workitemindex where RELM__install_dir is the location where the Rational Engineering Lifecycle Manager application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Design Management application To upgrade the Design Management application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\dm\dm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\dm\dm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Design Management application teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=DM__install_dir/server/conf/dm/indices/workitemindex where DM__install_dir is the location where the Design Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Data Collection Component application Note: If you are not upgrading your Requirements Management application at this time, you must have one of the following versions installed for the ETLs to run successfully: Rational DOORS Next Generation version 6.0.1 iFix11 Rational DOORS Next Generation version 6.0.2 iFix9 Rational DOORS Next Generation version 6.0.3 iFix2 Rational DOORS Next Generation version 6.0.4 GA Rational DOORS Next Generation version 6.0.5 GA Rational DOORS Next Generation version 6.0.6 GA To upgrade the Data Collection Component application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\dcc\dcc_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\dcc\dcc_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Data Collection Component 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=DCC__install_dir/server/conf/dcc/indices/workitemindex where DCC__install_dir is the location where the Data Collection Component application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Global Configuration Management application To upgrade the Global Configuration Management application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\gc\gc_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\gc\gc_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, a window opens in which you can check the Global Configuration Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=GC__install_dir/server/conf/gc/indices/workitemindex where GC__install_dir is the location where the Global Configuration Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Report Builder application To upgrade the Report Builder application open a command prompt with administrative privileges and enter the following commands: If you used any ready-to-use reports in the previous release and want to import them during the upgrade, use the importReportsOnStartup parameter. cd \server upgrade\rs\rs_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\rs\rs_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Report Builder app.properties file. #### Upgrading the Lifecycle Query Engine application To upgrade the Lifecycle Query Engine application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\lqe\lqe_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\lqe\lqe_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Lifecycle Query Engine lqe.properties file. #### Upgrading the Link Index Provider application To upgrade the Link Index Provider application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\ldx\ldx_upgrade.bat -oldApplicationHome "\server\conf" -newApplicationHome "\server\conf" -applicationContextRoot -jtsContextRoot cd \server upgrade\ldx\ldx_upgrade.bat -oldApplicationHome "\server\conf" -newApplicationHome "\server\conf" -applicationContextRoot -jtsContextRoot #### Upgrading the Quality Management application Before you start the Quality Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade Quality Management application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\qm\qm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\qm\qm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, a window opens in which you can check the Quality Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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__install_dir/server/conf/qm/indices/workitemindex where QM__install_dir is the location where Quality Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Requirements Management application Before you start the Requirements Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade the Requirements Management application open a command prompt with administrative privileges and enter the following commands: cd \server upgrade\rm\rm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd \server upgrade\rm\rm_upgrade.bat -oldApplicationHome "\server\conf" -oldJTSHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, an editor opens in which you can check the Requirements Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading Jazz Team Server To upgrade Jazz Team Server open a command shell and enter the following commands: cd /server upgrade/jts/jts_upgrade.sh -oldJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt cd /server upgrade/jts/jts_upgrade.sh -oldJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt 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__install_dir/server/conf/jts/indices/workitemindex where JTS__install_dir is the location where Jazz Team Server is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Communicate Tomcat users temporary passwords Tomcat user registry only: If you used a Tomcat user registry in your previous installation, the migration command creates a file named passwords.txt in the /server directory that contains all repository users from the tomcat-users.xml file. Because the tomcat-users.xml file stores one-way-encrypted passwords, it is not possible to migrate these user passwords. Instead, the passwords.txt file contains temporary passwords for each user, which the server administrator must communicate to the users. After the server is started, users can change their temporary passwords. #### Upgrading the Change and Configuration Management application To upgrade the Change and Configuration Management application open a command shell and enter the following commands: cd /server upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt 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. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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__install_dir/server/conf/ccm/indices/workitemindex where CCM__install_dir is the location where Change and Configuration Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. Note: In a clustered environment, upgrade only the first CCM node. You will replicate this node in a later step. #### Upgrading the Rhapsody Model Manager application To upgrade the Rhapsody Model Manager application open a command shell and enter the following commands: cd /server upgrade/am/am_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/am/am_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, an editor opens in which you can check the Rhapsody Model Manager teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=RMM__install_dir/server/conf/am/indices/workitemindex where RMM__install_dir is the location where the Rhapsody Model Manager application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Rational Engineering Lifecycle Manager application To upgrade the Rational Engineering Lifecycle Manager application open a command shell and enter the following commands: cd /server upgrade/relm/relm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/relm/relm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, an editor opens in which you can check the Rational Engineering Lifecycle Manager teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=RELM__install_dir/server/conf/relm/indices/workitemindex where RELM__install_dir is the location where the Rational Engineering Lifecycle Manager application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Design Management application To upgrade the Design Management application open a command shell and enter the following commands: cd /server upgrade/dm/dm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/dm/dm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, an editor opens in which you can check the Design Management application teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=DM__install_dir/server/conf/dm/indices/workitemindex where DM__install_dir is the location where the Design Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Data Collection Component application Note: If you are not upgrading your Requirements Management application at this time, you must have one of the following versions installed for the ETLs to run successfully: Rational DOORS Next Generation version 6.0.1 iFix11 Rational DOORS Next Generation version 6.0.2 iFix9 Rational DOORS Next Generation version 6.0.3 iFix2 Rational DOORS Next Generation version 6.0.4 GA Rational DOORS Next Generation version 6.0.5 GA Rational DOORS Next Generation version 6.0.6 GA To upgrade the Data Collection Component application open a command shell and enter the following commands: cd /server upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, an editor opens in which you can check the Data Collection Component 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=DCC__install_dir/server/conf/dcc/indices/workitemindex where DCC__install_dir is the location where Data Collection Component application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Global Configuration Management application To upgrade the Global Configuration Management application open a command shell and enter the following commands: cd /server upgrade/gc/gc_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/gc/gc_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, an editor opens in which you can check the Global Configuration Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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=GC__install_dir/server/conf/gc/indices/workitemindex where GC__install_dir is the location where Global Configuration Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Report Builder application To upgrade the Report Builder application open a command shell and enter the following commands: If you used any ready-to-use reports in the previous release and want to import them during the upgrade, use the importReportsOnStartup parameter. cd /server upgrade/rs/rs_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/rs/rs_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Report Builder app.properties file. #### Upgrading the Lifecycle Query Engine application To upgrade the Lifecycle Query Engine application open a command prompt with administrative privileges and enter the following commands: cd /server upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor During the upgrade, after the configuration files are merged, a window opens in which you can check the Lifecycle Query Engine lqe.properties file. #### Upgrading the Link Index Provider application To upgrade the Link Index Provider application open a command prompt with administrative privileges and enter the following commands: cd /server upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /server/conf -newApplicationHome /server/conf -applicationContextRoot -jtsContextRoot cd /server upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /server/conf -newApplicationHome /server/conf -applicationContextRoot -jtsContextRoot #### Upgrading the Quality Management application Before you start the Quality Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade Quality Management application open a command shell and enter the following commands: cd /server upgrade/qm/qm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/qm/qm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, an editor opens in which you can check the Quality Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. 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__install_dir/server/conf/qm/indices/workitemindex where QM__install_dir is the location where Quality Management application is installed. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. #### Upgrading the Requirements Management application Before you start the Requirements Management application upgrade, ensure that the database statistics are up-to-date. Otherwise, the migration might take several hours. Databases generally manage statistics automatically; for example, in a scheduled overnight operation. However, to ensure that the database is fully optimized, you can manually run the statistics as follows: DB2 REORGCHK UPDATE STATISTICS ON TABLE ALL EXEC sp_updatestats EXEC DBMS_STATS.GATHER_DATABASE_STATS For information about the Db2 database REORGCHK command, see the Db2 website. For information about the Oracle database DBMS_STATS command, see the Oracle documentation. For information about the SQL Server database Update Statistics command, see the SQL Server documentation. To upgrade the Requirements Management application open a command shell and enter the following commands: cd /server upgrade/rm/rm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument. cd /server upgrade/rm/rm_upgrade.sh -oldApplicationHome /server/conf -oldJTSHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -applicationContextRoot -jtsContextRoot -noPrompt -noVerify -noStepPrompt -noEditor -noResumePrompt During the upgrade, after the configuration files are merged, an editor opens in which you can check the Requirements Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, and then the application teamserver.properties opens for review. Also, if the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, delete it. 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. ### Import the version 5.0.26 VVC data into version (importVVC command) After you export your version 5.0.26 VVC data, run the -migration_dm_purgeCache command, and run the upgrade script to update database tables, now you can import your VVC data into version . 1. Open a command windowshell as an administrator and enter the following commands: 2. cd \server repotools-dm.bat -migration_dm_importvvc teamserver.properties=\server\conf\dm\teamserver.properties importPath=C:\temp\vvcMigration cd \server repotools-dm.bat -migration_dm_importvvc teamserver.properties=\server\conf\dm\teamserver.properties importPath=C:\temp\vvcMigration cd /server ./repotools-dm.sh -migration_dm_importvvc teamserver.properties=/server/conf/dm/teamserver.properties importPath=/opt/tmp/vvcMigration cd /server ./repotools-dm.sh -migration_dm_importvvc teamserver.properties=/server/conf/dm/teamserver.properties importPath=/opt/tmp/vvcMigration ### 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 configuration directory /QIBM/UserData/JazzTeamServer6061/server. 3. Enter this command to upgrade Jazz Team Server: upgrade/jts/jts_upgrade.sh -oldJTSHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 4. Enter this command to upgrade the Change and Configuration Management application: upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 5. Enter this command to upgrade the Quality Management application: upgrade/qm/qm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 6. Enter this command to upgrade the Requirements Management application: upgrade/rm/rm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 7. Enter this command to upgrade the Rational Engineering Lifecycle Manager application: upgrade/relm/relm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 8. Enter this command to upgrade the Global Configuration Management application: upgrade/gc/gc_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 9. Enter this command to upgrade the Report Builder application: upgrade/rs/rs_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 10. Enter this command to upgrade the Lifecycle Query Engine application: upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 11. Enter this command to upgrade the Link Index Provider application: upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 12. Enter this command to upgrade the Data Collection Component application: upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf 13. Note: As an alternative, you can run the QJTS6061/UPGJAZZSVR CL command to upgrade the server. 14. Review the index file locations. Adjust the locations and copy index files if you prefer. 15. Note: After running the update configuration files repository tools commands for Jazz Team Server and CLM applications, some of the directory references in the teamserver.properties files point to the prior version work directory. You can keep the indices in the prior version directory, if you do not plan to delete or clean up that directory. You could also copy the indices to a new location in the new work directory and modify the teamserver.properties file. For example, suppose the updated Jazz Team Server teamserver.properties file includes com.ibm.team.jfs.index.root.directory=/QIBM/UserData/JazzTeamServer502/server/conf/jts/indices but your new work directory is /QIBM/UserData/JazzTeamServer6061/server/conf. You can recursively copy these files to a new location and modify the teamserver.properites file. This is not required. 16. Run the next command to update the previous version Application Server and deploy the .war files for the version 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: • If you are using WebSphere Application Server, enter the following command: upgrade/was_upgrade.sh profileName serverName nodeName wasVersion wasOption maxHeapSize adminId adminPwd jvmVersion jazzAppName jtsAppName clmHelpAppName qmAppName rmAppName adminAppName gcAppName jrsAppName dccAppName lqeAppName ldxAppName relmAppName 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 previous Jazz Team 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. • clmHelpAppName is the name of the CLM help application. • qmAppName is the name of Quality Management application. • adminAppName is the name of Lifecycle Project Administration application. • rmAppName is the name of Requirements Management application. • gcAppName is the name of Global Configuration Management application. • jrsAppName is the name of Report Builder application. • dccAppName is the name of Data Collection Component application. • lqeAppName is the name of Lifecycle Query Engine application. • ldxAppName is the name of Link Index Provider application. • relmAppName is the name of Rational Engineering Lifecycle Manager application. • If you are upgrading WebSphere Liberty server (option 20), enter this command: upgrade/liberty_upgrade.sh serverName /QIBM/UserData/JazzTeamServer<old_version>/server/conf • If you are switching from WebSphere Application Server to Liberty or from Liberty to WebSphere Application Server, run the QJTS6061/CFGJAZZSVR command and specify the same port number it was used in your previous installation. For more information, see Configuring the server on IBM i systems. ### Optional: Copy the Quality Management application custom adapters If you have any custom adapters in your Quality Management application such as the, NI Test Integration Adapter, MGEN CANoe Adapter, or the HP Unified Functional Testing (UFT) Adapter, you must manually copy these adapters to the new installation directory after the upgrade. For example, to manually copy the HP Unified Functional Testing (UFT) Adapter, go to \server\conf\qm\provision_profiles/server/conf/qm/provision_profiles and copy the com.ibm.rqm.adapter.qtp.web.ini file to the \server\conf\qm\provision_profiles/server/conf/qm/provision_profiles directory. ### Start the WebSphere Application Server In a distributed topology, you must complete this step on the application server that hosts: • Jazz Team Server/Link Index Provider • Change and Configuration Management application • Rhapsody Model Manager application • Quality Management application • Data Collection Component application • Report Builder application • Rational Engineering Lifecycle Manager application • Lifecycle Query Engine application • Requirements Management application • Any application that is registered with Jazz Team Server • Design Management application • Global Configuration Management application 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: Ensure that you have a JDBC environment variable that points to the ojdbc8.jar located in the directory. For more information, see Setting up an Oracle database. Before you begin: Ensure that you have a JDBC environment variable to point to the JRE8 JDBC driver located in the directory. For more information, see Setting up an SQL Server database. 1. Open a command prompt and enter the following commands: 2. cd \bin startServer.bat server1 1. Open a command shell and enter the following commands: 2. cd /bin ./startServer.sh server1 ### Deploy web application (WAR files) by using the Jython script You can use clm_deploy.pyclm_deploy_distributed.py deploy application WAR files. This script also maps the security roles for the appropriate applications for non-external user registries. If you are using LDAP, complete the following steps to map the security roles to your LDAP groups. Note that the groups must be setup on the LDAP server prior to completing this mapping. 1. Open the JazzInstallDir/server/was/config.py script in a text editor for editing. 2. Go to the RoleMapping section of the script and replace default with your application name, such as jts, ccm, am, qm. Replace None with your user or repository group. When replacing None with the group mapping, ensure that the value is enclosed in quotation marks. See the following example for the JTS application: 3. RoleMapping = { 'jts' : { 'JazzAdmins' : { 'mappedUser': None, 'mappedGroup': "cn=JazzAdmins,cn=members,o=ldap.server.com", 'AllowAccessToEveryone':'No', 'AllowAccessToAllAuthenticatedUsers':'No' }, 'JazzUsers' : { 'mappedUser': None, 'mappedGroup': "cn=JazzUsers,cn=members,o=ldap.server.com", 'AllowAccessToEveryone':'No', 'AllowAccessToAllAuthenticatedUsers':'No' }, 'JazzGuests' : { 'mappedUser':None, 'mappedGroup': "cn=JazzGuests,cn=members,o=ldap.server.com", 'AllowAccessToEveryone':'No', 'AllowAccessToAllAuthenticatedUsers':'No' }, 'JazzProjectAdmins' : { 'mappedUser': None, 'mappedGroup': "cn=JazzProjectAdmins,cn=members,o=ldap.server.com", 'AllowAccessToEveryone':'No', 'AllowAccessToAllAuthenticatedUsers':'No' } }, 4. Save and close the file. About this task The clm_deploy.py script installs all application WAR files that are available in the webapps directory into a single WebSphere Application Server node. The clm_deploy_distributed.py script can be used to install any application WAR files that are available in the webapps directory, if you specify them in your command argument as a comma-separated list. Note: The web archive applications must have a .war extension. Procedure To deploy applications on a single WebSphere Application Server, complete this step: 1. Open a command window as administrator and enter the following commands. Replace nodeName and server1 with your WebSphere Application Server node name and server name: 2. Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy.py nodeName server1 JazzInstallDir/server/webapps -config JazzInstallDir/server/was cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_deploy.py nodeName server1 /server/webapps -config /server/was To deploy applications in a distributed WebSphere Application Server environment, complete these steps. Replace nodeName and server1 with your WebSphere Application Server node name and server name: Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script and the webapps directory. 1. On the server that hosts Jazz Team Server / Link Index Provider, open a command window and enter these commands: 2. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps jts,clmhelp,ldx -config JazzInstallDir/server/was cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps jts,clmhelp,ldx -config /server/was 3. On the server that hosts the Change and Configuration Management application, open a command window and enter these commands: 4. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps ccm -config JazzInstallDir/server/was cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps ccm -config /server/was 5. On the server that hosts the Rhapsody Model Manager application, open a command window and enter these commands: 6. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps am -config JazzInstallDir/server/was cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps am -config /server/was 7. On the server that hosts the Quality Management application, open a command window and enter these commands: 8. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps qm -config JazzInstallDir/server/was cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps qm -config /server/was 9. On the server that hosts the Requirements Management application, open a command window and enter these commands: 10. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps rm,converter cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps rm,converter 11. On the server that hosts the Rational Engineering Lifecycle Manager application, open a command window and enter these commands: 12. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps relm cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps relm 13. On the server that hosts the Data Collection Component application, open a command window and enter these commands: 14. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps dcc cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps dcc 15. On the server that hosts the Report Builder application, open a command window and enter these commands: 16. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps rs cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps rs 17. On the server that hosts the Lifecycle Query Engine application, open a command window and enter these commands: 18. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps lqe cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps lqe 19. On the server that hosts the Rational Rhapsody Design Manager application, open a command window and enter these commands: 20. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps dm,clmhelp cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps dm,clmhelp 21. On the server that hosts the Rational Software Architect Design Management application, open a command window and enter these commands: 22. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps dm,clmhelp cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps dm,clmhelp 23. On the server that hosts the Global Configuration Management application, open a command window and enter these commands: 24. cd \bin wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir/server/webapps gc cd /bin ./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps gc 25. To start the deployed applications, restart the application server. Replace server1 with the name of your application server: 26. cd WAS_Profile_Dir\bin stopServer.bat server1 -user WAS_USER -password WAS_PASSWORD startServer.bat server1 cd WAS_Profile_Dir/bin ./stopServer.sh server1 -user WAS_USER -password WAS_PASSWORD ./startServer.sh server1 ### Deploy the version WAR files in WebSphere Application Server In a distributed topology, you must complete this step on the application server that hosts: • Jazz Team Server/Link Index Provider • Change and Configuration Management application • Rhapsody Model Manager application • Quality Management application • Requirements Management application • Data Collection Component application • Report Builder application • Rational Engineering Lifecycle Manager application • Design Management application • Lifecycle Query Engine application • Global Configuration Management application WAR file locations: By default, the WAR files are copied into the _install_dir/server/webapps directory by Installation Manager, unless you specified a different directory. Also note that starting in version 5.0.2, Lifecycle Project Administration became part of Jazz Team Server. As a result, there is no admin.war application to deploy. Starting in version 6.0.1, the Configuration Management application that was included with the Design Management application is removed. As a result, there is no vvc.war application to deploy. 1. Open a browser and login to WebSphere Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp. 2. Click Applications > New Application > New Enterprise Application. 3. On the Path to the new application page, select Remote file system and browse for the application.war file. Click Next. Depending on the CLM applications that you installed, the following web applications might be available for deployment: • jts.war • clmhelp.war • ccm.war • am.war • relm.war • qm.war • rm.war • converter.war • dm.war • clmhelp.war • rsadm.war • dcc.war • lqe.war • ldx.war • rs.war • gc.war 4. Select Fast Path, and then click Next. 5. For the Lifecycle Query Engine module, expand Choose to generate default bindings and mappings, and then select the Generate Default Bindings check box. 6. For the Link Index Provider module, expand Choose to generate default bindings and mappings, and then select the Generate Default Bindings check box. 7. On the Map modules to servers page, select the check box next to lqe to specify the target scope on the server for the lqe module. 8. On the Map modules to servers page, select the check box next to ldx to specify the target scope on the server for the ldx module. 9. Click Next to accept all default options until you reach the Map context roots for web modules page. 10. In the Map context roots for web modules, set the following Context Root for applications: • Jazz Team Server to /jts • IBM Knowledge Center to /clmhelp • Change and Configuration Management to /ccm • Rhapsody Model Manager to /am • Rational Engineering Lifecycle Manager to /relm • Quality Management to /qm • Requirements Management to /rm • Converter application to /converter • Design Management to /dm • Design Management Knowledge Center to /clmhelp • Data Collection Component to /dcc • Report Builder to /rs • Lifecycle Query Engine to /lqe • Link Index Provider to /ldx • Global Configuration to /gc 11. Click Finish. 12. Verify that your application was installed correctly and then click Save directly to the master configuration. Important: If you work in an environment such as AIX that does not support converter, you must install the 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 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. ### Map security roles to a user or repository group The jts_war, am_war, qm_war, and ccm_war applications must have the same authentication methods for their users and use the same security group mapping. 1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications. 2. For Jazz Team Server, click the jts_war application to open it for editing. 3. For Change and Configuration Management, click the ccm_war application to open it for editing. 4. For Rhapsody Model Manager, click the am_war application to open it for editing. 5. For Quality Management, click the qm_war application to open it for editing. 6. In the Detail Properties section, click Security role to user/group mapping. 7. Select a specific repository group, such as JazzAdmins or JazzUsers, and click Map groups. These repository groups are associated with every Jazz implementation and must be mapped to a particular group that contains the authorized users. If you are using LDAP, these groups must be set up on the LDAP server prior to completing this mapping. If you are mapping these repository groups to individual users, select the repository group and click Map Users. 8. Enter a search string to return your users or group names. Click Search to run the query. 9. From the list of available users or groups that is returned, select the particular user or group and move it to the Selected column. 10. Click OK to map the users or groups to the Jazz repository groups. 11. Save the changes. Note: If in the future there will be changes to the LDAP configuration level, you must remap the security roles to the user or repository group for JTS and other installed applications. ### Unregister the VVC application Because the VVC application is removed in version 6.0.1, the friend relationship between Jazz Team Server and the VVC application must also be removed. The Design Management upgrade procedure that you performed previously cannot unregister the VVC application, and you must manually perform this step before you can start using the Design Management application. To unregister the VVC application, complete these steps: 1. Ensure that Jazz Team Server is shut down. This step must be completed while Jazz Team Server is off-line. 2. Open a command windowshell and enter the following commands: cd \server repotools-jts.bat -unregisterApp appName=/vvc noPrompt cd \server repotools-jts.bat -unregisterApp appName=/vvc noPrompt cd /server ./repotools-jts.sh -unregisterApp appName=/vvc noPrompt cd /server ./repotools-jts.sh -unregisterApp appName=/vvc noPrompt ### Configure the Report Builder application 1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications. 2. On the Enterprise Applications page, in the list of resources, click rs_war. 3. On the Configuration page, in the References section, click Shared library references. 4. Select the rs_war check box and click Reference shared libraries. 5. In the Available list, select JRS Shared Library and click the right arrow. 6. Click OK. Click OK again and then click Save. 7. In the list of resources, click rs_war. 8. On the Configuration page, under Detail Properties, click Class loading and update detection. 9. In the Class loader order group, ensure that Classes loaded with local class loader first (parent last) is selected. Click Apply and then click Save. ### Configure the Lifecycle Query Engine application 1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications. 2. Click lqe_war to open it and then click Manage Modules. 3. Click lqe, locate the Class loader order field and select Classes loaded with local class loader first (parent last). 4. Click OK and save your changes. 5. Go back to the lqe_war application and click Class loading and update detection. 6. On the Class loader page, select Classes loaded with local class loader first (parent last). 7. Click Apply and Save directly to the master configuration. ### Configure the Link Index Provider application 1. In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications. 2. Click ldx_war to open it and then click Manage Modules. 3. Click ldx, locate the Class loader order field and select Classes loaded with local class loader first (parent last). 4. Click OK and save your changes. 5. Go back to the ldx_war application and click Class loading and update detection. 6. On the Class loader page, select Classes loaded with local class loader first (parent last). 7. Click Apply and Save directly to the master configuration. ### Run the repairUnreferencedVersions repository tools command Before you start the Requirements Management server, run the repairUnreferencedVersions repository tools command to ensure that unreferenced versions of artifacts do not exist in the Jena index files. Open a command window and change to the server directory where the Requirements Management application is installed and enter the following command: repotools-rm.bat -repairUnreferencedVersions ./repotools-rm.sh -repairUnreferencedVersions If the repair utility finds errors and repairs them, run the following command to reindex the index files: repotools-rm.bat -reindex all ./repotools-rm.sh -reindex all ### Run the -rebuildIndices repository tools command Before you start the Rhapsody Model Manager application and run diagnostics, you must run the -rebuildIndices repository tools command to prevent errors in the Database Indices section of the diagnostics. The error is caused by the mismatch of primary key indexes in the database after the upgrade. To resolve the issue, run the -rebuildIndices repository tools command after the upgrade and before you run diagnostics. 1. Open a command windowprompt and enter the following commands: 2. cd \server/server repotools-am.bat -rebuildIndices./repotools-am.sh -rebuildIndices ### Start the applications On the Enterprise Applications page, start these applications: In a distributed topology, you must complete this step on the application server that hosts: • Jazz Team Server/Link Index Provider • Change and Configuration Management application • Rhapsody Model Manager application • Quality Management application • Requirements Management application • Data Collection Component application • Report Builder application • Rational Engineering Lifecycle Manager application • Design Management application • Lifecycle Query Engine application • Global Configuration Management application Log on to the Integrated Solutions Console and start these applications: • jts_war • ccm_war • am_war • qm_war • rm_war • dcc_war • rs_war • relm_war • dm_war • clmhelp_war • rsadm_war • gc_war • lqe_war • ldx_war • converter_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. ### Upgrading the Distributed Cache Microservice (DCM) The Distributed Cache Microservice was first introduced in version 6.0.5. If you are upgrading your clustered environment from version 6.0.4, follow the procedures in the Interactive Installation Guide to install and register a new DCM. When you install the new version of the CCM application, a new version of Distributed Cache Microservice is installed at the default location, JazzInstallDir/server/clustering/cache. • If your DCM is at the default location, you must merge all your configuration settings you had in the old distributedCache.cfg file with the new distributedCache.cfg file in the new installation directory. • If your DCM was moved to a dedicated server in the previous installation, make a backup copy of the entire clustering/cache directory. Move the new version of DCM from JazzInstallDir/server/clustering/cache to its dedicated server, and then make sure to merge all your configuration settings. In particular, ensure the following configuration properties in the distributedCache.cfg file are merged: • Ensure the path to the keystore file in the keyStorePath property is correct. • Check the [REST] section and update the properties if necessary. • Ensure to update the [AuthServer] properties if authentication is set to OIDC for DCM. The URL you use in the as_trusted_url, must match the URL you specified in the Advanced Properties of the server. Do not append the context root (/dcm) to this property. • If authentication is done through an LDAP server, ensure to update the [UserRegistry] properties. • If you plan to monitor the performance counters that the microservice publishes, under [Counters], set the Enabled property to true and provide an MQTT broker URL in the broker property. DCM publishes its counters via an MQTT Broker. When this is enabled, counters can be seen in the cluster application's administrative UI internal Counters Page. Alternatively, when counters are enabled in the configuration file, the http://DCM_HOST_NAME:10001/dcm/counters URL displays counter data on demand, (port is applicable only if it is not masked). Publishing frequency is controlled by snapshotFrequency property under the [Logging] section. It is also possible to locally log the usage statistics of DCM. To do this, set logSnapshotStats to true. Note: Starting in version 6.0.6.1, the version of Jetty that is used for DCM has changed. As a result, the allowRenegotiate property in the distributedCache.cfg file changed to renegotiationAllowed with the default value still being false. ### Replicate the upgraded CCM application to all other nodes To replicate the upgraded CCM application to all other nodes in the clustered environment: Note: Copying the entire CCM installation directory works if an HAProxy is used. If you use IBM HTTP Server for load balancing, to avoid problems only copy the conf directory. 1. Copy the entire CCM installation directory from the first node to the other nodes. 2. Important: The upgrade command does not upgrade the server.startup file. If you customized this file in your previous installation, you must manually merge your customized settings. 3. Ensure that the server/conf/ccm/teamserver.properties file has the following property: com.ibm.team.repository.servlet.sso_clientId 4. Ensure that the server/server.startup file has the following properties: JAVA_OPTS="$JAVA_OPTS -Dcom.ibm.team.repository.cluster.nodeId="ccm1""
JAVA_OPTS="$JAVA_OPTS -Dcom.ibm.team.repository.service.internal.db.allowConcurrentAccess=true" JAVA_OPTS="$JAVA_OPTS -Dretry.count=0"
JAVA_OPTS="$JAVA_OPTS -Dretry.wait=10" 5. Replace ccm1 example with the name or ID of the node. This name must be unique across all the nodes. When you copy the CCM installation directory to the other nodes, if you are using HAProxy as a load balancer, you must open each server/server.startup file and change the ID to a unique node ID, for example, ccm2, ccm3, and so on. If you are using IBM HTTP Server as a load balancer, in addition to node ID in the server/server.startup file, cloneId in the /server/liberty/servers/clm/server.xml file must also be unique. Important: Examine the /server/clustering/cache/distributedCache.cfg file and merge any customized settings that you made in the previous instance of the file. Do not use the microservice from a previous release with a newer version of CLM. Always merge customized settings from an existing instance of the Distributed Cache Microservice into the new instance that you install with CLM. ### Restart the IBM IoT MessageSight Before starting the servers in your clustered CCM environment, restart IBM IoT MessageSight by using the CleanStore button. The CleanStore button ensures that the store is cleaned as part of the shutdown process. ### Start the servers Note: If you customized your server.startup script in the previous installation, you must manually MERGE your customized settings into the new server.startup file. Ensure to have a backup of the new server.startup file before customizing it. In a distributed topology, you must complete this step on the application server that hosts: • Jazz Team Server/Link Index Provider • Change and Configuration Management application • Rhapsody Model Manager application • Quality Management application • Data Collection Component application • Report Builder application • Rational Engineering Lifecycle Manager application • Design Management application • Global Configuration Management application • Lifecycle Query Engine application • Requirements Management application • Any application that is registered with Jazz Team Server Note: In a clustered environment, start the Distributed Cache Microservice and Jazz Team Server first, verify that they are working properly by logging in to the servers, and then start all the other CCM application nodes. Before you Begin: Ensure that you have a JDBC environment variable that points to the ojdbc8.jar located in the directory. For more information, see Setting up an Oracle database. Before you begin: Ensure that you have a JDBC environment variable to point to the JRE8 JDBC driver located in the directory. For more information, see Setting up an SQL Server database. Start all of the version application servers: Start the version application server: 1. Open a command prompt and enter: cd \server server.startup.bat -tomcat 2. On the computer that hosts Jazz Team Server/Link Index Provider, open a command prompt and enter: cd \server server.startup.bat -tomcat 3. On the computer that hosts the Change and Configuration Management application, open a command prompt and enter: cd \server server.startup.bat -tomcat 4. On the computer that hosts the Rhapsody Model Manager application, open a command prompt and enter: cd \server server.startup.bat -tomcat 5. On the computer that hosts the Quality Management application, open a command prompt and enter: cd \server server.startup.bat -tomcat 6. On the computer that hosts the Requirements Management application, open a command prompt and enter: cd \server server.startup.bat -tomcat 7. On the computer that hosts the Data Collection Component application, open a command prompt and enter: cd \server server.startup.bat -tomcat 8. On the computer that hosts the Global Configuration Management application, open a command prompt and enter: cd \server server.startup.bat -tomcat 9. On the computer that hosts the Report Builder application, open a command prompt and enter: cd \server server.startup.bat -tomcat 10. On the computer that hosts the Rational Engineering Lifecycle Manager application, open a command prompt and enter: cd \server server.startup.bat -tomcat 11. On the computer that hosts the Design Management application, open a command prompt and enter: cd \server server.startup.bat -tomcat 12. On the computer that hosts the Lifecycle Query Engine application, open a command prompt and enter: cd \server server.startup.bat -tomcat 1. Open a command shell and enter: cd /server ./server.startup -tomcat 2. On the computer that hosts Jazz Team Server/Link Index Provider, open a command shell and enter: cd /server ./server.startup -tomcat 3. On the computer that hosts the Change and Configuration Management application, open a command shell and enter: cd /server ./server.startup -tomcat 4. On the computer that hosts the Rhapsody Model Manager application, open a command shell and enter: cd /server ./server.startup -tomcat 5. On the computer that hosts the Quality Management application, open a command shell and enter: cd /server ./server.startup -tomcat 6. On the computer that hosts the Requirements Management application, open a command shell and enter: cd /server ./server.startup -tomcat 7. On the computer that hosts the Data Collection Components application, open a command shell and enter: cd /server ./server.startup -tomcat 8. On the computer that hosts the Global Configuration Management application, open a command shell and enter: cd /server ./server.startup -tomcat 9. On the computer that hosts the Report Builder application, open a command shell and enter: cd /server ./server.startup -tomcat 10. On the computer that hosts the Rational Engineering Lifecycle Manager application, open a command shell and enter: cd /server ./server.startup -tomcat 11. On the computer that hosts the Design Management application, open a command shell and enter: cd /server ./server.startup -tomcat 12. On the computer that hosts the Lifecycle Query Engine application, open a command shell and enter: cd /server ./server.startup -tomcat ### Migrate your self-signed certificate If you had a self-signed certificate in your previous Tomcat installation, you can import and use it with your new WebSphere Liberty server. Before you begin You must at least start and stop the server one time before you can complete this procedure. Procedure 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Jazz Team Server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Change and Configuration Management application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Rhapsody Model Manager application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Quality Management application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Requirements Management application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Rational Engineering Lifecycle Manager application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Data Collection Component application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Report Builder application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Lifecycle Query Engine application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Rational Rhapsody Design Manager application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Rational Software Architect Design Management application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> Complete these steps on the Global Configuration Management application server: 1. Copy the keystore file you were using with Tomcat in previous version to the /server/liberty/servers/clm/resources/security\server\liberty\servers\clm\resources\security directory. 2. Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing. 3. Update the <keyStore> element in the following line with your keystore information: <keyStore id="defaultKeyStore" location="ibm-team-ssl.keystore" type="JCEKS" password="{xor}Nj0ycis6PjI="/> For more information, see Enabling SSL communication for the Liberty profile. ### Import the ready-to-use reports Jazz Reporting Service version 5.x included some ready-to-use reports. If you used those reports that were included in the application, you must reimport them after you upgrade to version . Note: The following steps are not required if you used the importReportsOnStartup parameter during the upgrade. The reports will be imported after the server is started. Procedure 1. Open a browser and login to https://host.example.com:9443/rs/setup. 2. Click Import ready-to-use reports. ### Migrating the Lifecycle Query Engine application 1. When the LQE application is started after the upgrade, a migration takes place in the background. Open a browser and go to the LQE admin page at https://host.example.com:9443/lqe/web. If the server migration has completed, you will be redirected to the LQE home page. If the migration is still in progress, the migration status page opens. In this case, wait for the migration to complete and then you will be redirected to the LQE home page. ### Design Management application online migration Before you start the Design Management online migration, ensure that the Design Management application, Jazz Team Server, and any application that is registered with Jazz Team Server is started. 1. As an administrator log in to the Design Management server administration page at https://hostname.example.com:9443/dm. 2. If you do not already have a credentials file, create a file named credentials.txt under the \/server directory with the following content. If you are using an existing credentials file, ensure that the repository URL is pointing to the /dm server: 3. If you do not already have a credentials file, create a file named credentials.txt under the \/server directory with the following content. If you are using an existing credentials file, ensure that the repository URL is pointing to the /dm server: 4. adminUserId=yourAdminUserId adminPassword=yourAdminPassword repositoryURL=https://hostname.example.com:9443/dm smartCard=<none> certificateFile=<none> kerberos=<none> 5. Open a command windowshell and enter the following commands: cd \server repotools-dm.bat -migration_dm_runUpgradeManager credentialsFile=credentials.txt cd \server repotools-dm.bat -migration_dm_runUpgradeManager credentialsFile=credentials.txt cd /server ./repotools-dm.sh -migration_dm_runUpgradeManager credentialsFile=credentials.txt cd /server ./repotools-dm.sh -migration_dm_runUpgradeManager credentialsFile=credentials.txt This command instructs 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 Design Management 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 Design Management 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 WebSphere Application Server, add another custom 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 Design Management 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 looks for the application running on the same application server and if found, registers it. If the domain extension application is running on a different application server, you must manually register that application with Design Management. To verify the domain extension was registered or to register it, log into https://hostname.example.com:9443/dm/admin and in the menu bar click Domain Extension Servers. If the domain server is registered, it appears on the page as being enabled and online. If it does not appear, click the Add New Server link and add https://hostname.example.com:9443/rsadm. Ensure to check the enabled control in the dialog. ### New applications in version 6 If you installed the new applications that ship with CLM version such as Global Configuration Management or Link Index Provider, after the upgrade is complete run the setup wizard to register these new applications with Jazz Team Server. For more information about the -registerApp command, see Repository tools command to register an application. ### Restoring baselines The Requirements Management project baselines are archived during the upgrade to gain performance. If after the upgrade you need to access these baselines, you must restore them. To restore the baselines, complete the following steps: 1. Log on to the Requirements Management application server. 2. Select a project area with a baseline that you want to restore. 3. Click Administration > Manage Baselines, and then click the Show the archived configurations button. 4. Find the baseline you want to restore and from the Actions menu of that baseline, select Restore. ### Obtain licenses You must obtain new licenses for version applications if you are upgrading from any release of version 5. Version applications do not work with version 5.0.x licenses. However, version 5.0.x applications work with version licenses. If you previously used floating, token, or authorized user single install licenses, install their version counterparts. Your existing user license assignments will be kept during installation of version licenses. Important: You must obtain new licenses from the License Key Center and update your licenses. You must obtain new licenses for version 6.0.5 applications if you are upgrading from any release of version 5. Version 6.0.5 applications do not work with version 5.0.x licenses. However, version 5.0.x applications work with version 6.0.5 licenses. If you previously used floating, token, or authorized user single install licenses, install their version 6.0.5 counterparts. Your existing user license assignments will be kept during installation of version 6.0.5 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 6.0.5 license file. 3. After upload is complete, there will be 2 entries in the Floating License Server section. Hover over the version 5.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 5.x licenses is present. For more information about licenses, see Managing licenses. ### Migrate Cognos reports to a Cognos Business Intelligence server To migrate your Cognos reports to a Cognos Business Intelligence server, you must first install Cognos Business Intelligence. See the Cognos Business Intelligence product page for download and documentation links. After installing Cognos Business Intelligence, install and configure ALM Cognos Connector to migrate your Cognos reports to Cognos Business Intelligence. For more information, see Installing ALM Cognos Connector. ### Configure the CCM application as a defect provider If you are using the Change and Configuration Management application as your defect provider, after you upgrade your Quality Management application, you must associate a functional user (qm_user) to the consumer entry in the Administrative page of the CCM application. For more details, see Configuring the CCM application as your defect provider. ### Configure data warehouse If you did not configure the data warehouse in your previous installation and want to configure a data warehouse for version , 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 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. ### Rebase TRS and reindex Requirements Management data sources Note: The following steps are NOT required if you are upgrading from version 6.0.3 iFix10 or later, or version 6.0.4 iFix2 or later. If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Requirements Management application. Note that these steps might take some time to complete depending on the size of your repository. 1. Do TRS 2.0 full rebase: 1. Open a web browser and navigate to https://RM_Server:9443/rm/admin#action=com.ibm.rdm.fronting.server.web.trs. 2. Click TRS 2.0 Full Rebase. Wait for the operation to complete before proceeding to the next step. It may take some time depending on the data size. 2. Replace the DNG TRS 1.0 data source with the TRS 2.0 data source in Lifecycle Query Engine: Note: If the DNG TRS 2.0 data sources already exist in Lifecycle Query Engine, you do not need to remove and add them back again. You can just reindex the data sources. 1. Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources. 2. If the DNG TRS 1.0 data source exists, remove it. The DNG TRS 1.0 data source is usually named DOORS Next Generation TRS and points to https://RM_Server:9443/rm/trs. To remove the data source, select it and then click Remove. 3. Click Add Data Source, and in the wizard that opens select the DNG Process Resources (TRS 2.0) data source. Click Finish. 4. Repeat the previous step and add the DNG Resources (TRS 2.0) data source. 5. The URL for DNG Process Resources (TRS 2.0) is https://RM_Server:9443/rm/process-trs2 and the URL for DNG Resources (TRS 2.0) is https://RM_Server:9443/rm/trs2. After the data sources are added, Lifecycle Query Engine starts building the initial indices. 6. Click DNG Process Resources (TRS 2.0) and DNG Resources (TRS 2.0) and then click Reindex and in the dialog that opens, click Reindex again. 7. Click OK to confirm the reindex operation. ### Reindex Change and Configuration Management data sources If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Change and Configuration Management application. Note that these steps might take some time to complete depending on the size of your repository. 1. Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources. 2. If the TRS 1.0 for CCM Resources exists, remove it. The TRS 1.0 data source is called Change and Configuration Management and the URL is https://localhost:9443/ccm/oslc/workitems/trs. To remove the data source, select it and then click Remove. 3. Click Add Data Source, and in the wizard that opens select the RTC Process Resources (TRS 2.0) data source. Click Finish. 4. If you encounter an invalid update issue (see work item 469658), repeat the above steps and add the following data source: • RTC SCM Change Sets (TRS 2.0) 5. If you encounter out-of-sync resources issue (see work item 472058), repeat the above steps and add the following data source. This is applicable only if the link archiving is enabled: • RTC SCM Change Set Link Resources (TRS 2.0) 6. Under Data Source, click each data source you just added. 7. Click Reindex and in the dialog that opens, click Reindex again. 8. Click OK to confirm the reindex operation. ### Rebuild and reindex Quality Management data sources Note: The following steps are NOT required if you are upgrading from version 6.0.3 or laterversion 6.0.4 or later. If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Quality Management application. Note that these steps might take some time to complete depending on the size of your repository. 1. To rebuild the TRS base, open a browser and log into the Quality Management application at https://QM_Server:9443/qm/admin. 2. Click Application > Advanced Properties and then search for Audit History Component. 3. Click the current value of the TRS Base Lifetime property and change it from 1440 to 1. 4. Scroll up the page and click Save. 5. Wait > 1 minute. 6. Complete a full reindex of the RQM Resources (TRS 2.0) data source: 1. Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources. 2. If the TRS 1.0 for QM Resources exists, remove it. To remove the data source, select it and then click Remove. 3. If the RQM Resources (TRS 2.0) does not exist, add it. To add the data source, click Add Data Source, and in the wizard that opens select the RQM Resources (TRS 2.0) data source. Click Finish. 4. Under Data Source, click RQM Resources (TRS 2.0). 5. Click Reindex and in the dialog that opens, click Reindex again. 6. Click OK to confirm the reindex operation. 7. Now reset the setting back to the default value of 1440 for the TRS Base Lifetime property in the Audit History Component section of the QM server. Save your changes. ### Reindex Design Management data sources Note: The following steps are NOT required if you are upgrading from version 6.0.3 or later. If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Design Management application. Note that these steps might take some time to complete depending on the size of your repository. 1. Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources. 2. If the TRS 1.0 for DM Resources exists, remove it. To remove the data source, select it and then click Remove. 3. Click Add Data Source, and in the wizard that opens select the TRS 2.0 for DM Process Resources data source. Click Finish. 4. Repeat the previous step and add the TRS 2.0 for DM Resources data source. 5. Under Data Source, click TRS 2.0 for DM Resources and TRS 2.0 for DM Process Resources. 6. Click Reindex and in the dialog that opens, click Reindex again. 7. Click OK to confirm the reindex operation. ### Reindex Global Configuration Management data sources Note: The following steps are NOT required if you are upgrading from version 6.0.3 or later. If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Global Configuration Management application. Note that these steps might take some time to complete depending on the size of your repository. 1. Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources. 2. Under Data Source, click GCM Resources (TRS 2.0) and GCM Process Resources (TRS 2.0). 3. Click Reindex and in the dialog that opens, click Reindex again. 4. Click OK to confirm the reindex operation. ### Upgrade and enable Jazz Authorization Server If you used IBM Installation Manager to install Jazz Authorization Server, you can use the Update feature of Installation Manager to upgrade your Jazz Authorization Server. Before you begin 1. Stop the Jazz Authorization Server before performing the update. 2. Make a backup copy of the entire Jazz Authorization Server installation directory and rename it to C:\JazzAuthorizationServer_OLD/opt/JazzAuthorizationServer_OLD. 3. Ensure that you have a discoverable repository location set in the Installation Manager Preferences window. 1. In Installation Manager go to File > Preferences and click Add Repository. 2. Browse for a local .zip file or online link that contains the Jazz Authorization Server offerings repository.config file. 3. Click Test Connections to ensure you can connect to the repository location. 4. Click Apply and then OK to close the Preferences window. Procedure 1. In IBM Installation Manager click Update. 2. Select the Jazz Authorization Server package and click Next on all panels until you reach the Summary page. 3. Review the summary information and click Update to start the upgrade process. 4. Copy the asDB folder from the backup you created earlier C:\JazzAuthorizationServer_OLD\derby\asDB/opt/JazzAuthorizationServer_OLD/derby/asDB and place it in the C:\JazzAuthorizationServer\derby\asDB/opt/JazzAuthorizationServer/derby/asDB replacing the existing asDB folder. 5. Restart the Jazz Authorization Server. To use Jazz Security Architecture single sign-on (SSO) authentication for existing deployments, it must first be enabled in all Jazz applications. There are different procedures for enabling different types of applications for Jazz Security Architecture SSO. All applications do not need to be enabled at the same time. However, the login experience is not single sign-on until all applications are enabled. For more information and related task topic, see Enabling CLM applications for Jazz Security Architecture single sign-on. ### Reindex all data sources If you are upgrading your Global Configuration Management server from version 6.0.1 and earlier, after the upgrade is complete you must reindex all data sources. 1. Make sure the server is started and then log in as an administrator. 2. On the Server Administrator page under Manage Application Artifacts > Lifecycle Query Engine, click Manage data sources. 3. On the Lifecycle Query Engine Data Sources page, click Reindex All. 4. On the dialog box that opens, click Reindex All. 5. Click OK to confirm the reindexing process. ### Deploy predefined templates To ensure you have the latest project templates available on your server, after the upgrade is complete do the following steps to import predefined templates: 1. Make sure the server is started and then log in as an administrator. 2. On the Server Administrator page, click Manage Lifecycle Projects. 3. On the Lifecycle Project Administration page, click Templates and then click Deploy Predefined Templates. 4. Click OK at the prompt to overwrite any existing templates with the same identifiers. 5. After a few moments a message is displayed that the predefined templates were deployed successfully. ### Clear browser cache After you upgrade the Report Builder application, you must clear your browser cache including the cookies in order for the dashboard widgets to display correctly. ### Migrate your custom themes If you had any custom themes in your 5.x installation, you must manually migrate them to the new version as the upgrade process does not automatically migrate those themes. For more information about custom themes, see Configuring themes. ### Enable the CleanupUnusedIndexesVersionsTask on the Requirements Management server If you are upgrading from an older version of the Requirements Management application, the CleanupUnusedIndexesVersionsTask might be disabled by default. Follow the steps in this task to enable the CleanupUnusedIndexesVersionsTask. 1. Ensure the server is started. 2. Open a browser and log in to the Requirements Management appliction administrative page at https://hostname.example.com:9443/rm/admin. 3. Click Application > Advanced Properties and search for CleanupUnusedIndexesVersionsTask. 4. If the hour when the task is run is set to -1, the task is disabled. To enable the task choose a number between 0 and 23 that represents the hour of the day. At this time you can also adjust the other values to set the day of the week when the task runs and set the frequency to daily or weekly. 5. After making changes, scroll up the page and click Save to save your changes. 6. Restart the server for changes to take effect. ### Enable the CleanupUnusedIndexesVersionsTask on the Design Management server If you are upgrading from an older version of the Design Management application, the CleanupUnusedIndexesVersionsTask might be disabled by default. Follow the steps in this task to enable the CleanupUnusedIndexesVersionsTask. 1. Ensure the server is started. 2. Open a browser and log in to the Design Management appliction administrative page at https://hostname.example.com:9443/dm/admin. 3. Click Application > Advanced Properties and search for CleanupUnusedIndexesVersionsTask. 4. If the hour when the task is run is set to -1, the task is disabled. To enable the task choose a number between 0 and 23 that represents the hour of the day. At this time you can also adjust the other values to set the day of the week when the task runs and set the frequency to daily or weekly. 5. After making changes, scroll up the page and click Save to save your changes. 6. Restart the server for changes to take effect. ### Registering Rhapsody Model Manager with Jazz Team Server If you installed a new Rhapsody Model Manager version in your upgraded CLM environment, you must complete the following steps before you can register the Rhapsody Model Manager application with Jazz Team Server. If you upgraded Rhapsody Model Manager to this release, the following steps are not required. 1. Stop Jazz Team Server. 2. Go to the Jazz_Install_Dir/server/liberty/servers/clm/conf directory and open the application.xml file for editing. 3. Add the following content under <!--Applications that rely on container authentication-->. 4. <application type="war" id="am" name="am" location="${server.config.dir}/apps/am.war">
<application-bnd>
</security-role>
</security-role>
<security-role name="JazzUsers">
<group name="JazzUsers" />
</security-role>
<security-role name="JazzGuests">
<group name="JazzGuests" />
</security-role>
</application-bnd>
</application>

Note: The line <application type="war" id="am" name="am" location="\${server.config.dir}/apps/am.war"> contains the default application name. If during the installation you changed the application context root, replace am in the id, name, and am.war attributes accordingly.

5. Save and close the application.xml file.
6. Restart the server.
7. Log into Jazz Team Server and register and configure the Rhapsody Model Manager application.

### Remote help settings after the upgrade

After you upgrade your CLM applications to , the upgrade procedure sets the remote help settings to use the version of the knowledge center. If in your previous installation you customized your remote help settings, you must manually update the settings. To learn about remote help configuration see, Installing help on your computer and Changing help content connections.

### Run statistics on the Db2 database

In Db2, the runstats utility updates statistics on the physical characteristics of a table and its associated indexes. These characteristics include the number of records, the number of pages, and the average record length. The optimizer uses these statistics to determine access paths to the data. Call this utility if a table has had many updates or after you reorganize a table in a large-scale Quality Management application database.

To run the runstats utility, open a Db2 command window and enter the following commands:

db2 connect to qm
db2 runstats on table "REPOSITORY"."VERSION" with distribution and detailed indexes all
db2 disconnect qm

### Optional: Enable database table partitioning

To determine whether you need to enable database table partitioning, see Leveraging Database Partitioning in RQM for Data Growth on the Deployment wiki.

In version 6.0.6.1 and later, you can use the partitioning repotools command to partition a non-partitioned REPOSITORY.VERSIONREPOSITORY_VERSION<SchemaPrefix>_REPOSITORY.VERSIONRPSTR_VRSN table in a configuration-enabled system. The command partitions by range based on item types. Database table partitioning helps manage the performance, availability, and scalability of large amounts of data (millions of artifacts) in a repository. To use the partitioning features, you must install an Enterprise edition of a Db2Db2 for z/OSDb2 for iOracleSQL Server database. Standard, Workgroup, Personal, or Express editions of the database, or the default Apache Derby database, do not support partitioning. The command fails if the underlying database does not support partitioning.

Important: Back up the database before you use this command. After the successful completion of this command, database administrators should collect statistics for the REPOSITORY.VERSIONREPOSITORY_VERSION<SchemaPrefix>_REPOSITORY.VERSIONRPSTR_VRSN table and its indexes to help improve the performance of the database.

During data migration, the original table is duplicated until the end of the migration process, when the old table is dropped. Ensure that you have adequate disk space for data migration and for growing partitions after the initial copy and cleanup.

To enable the Quality Management application database table partitioning, open a command window and enter the following commands:

cd /server
./repotools-qm.sh -partitioning teamserver.properties=conf/qm/teamserver.properties enable

cd \server
repotools-qm.bat -partitioning teamserver.properties=conf\qm\teamserver.properties enable

For details about the partitioning repotools command, see Repository tools command to partition a database table.

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

Verify that these application configuration files are copied from previous installation to version :
• For Jazz Team Server: JTS__install_dir/server/conf/jts/teamserver.properties
• For the Change and Configuration Management application: CCM__install_dir/server/conf/ccm/teamserver.properties
• For the Rhapsody Model Manager application: RMM__install_dir/server/conf/am/teamserver.properties
• For the Quality Management application: QM__install_dir/server/conf/qm/teamserver.properties
• For the Requirements Management application: RM__install_dir/server/conf/rm/teamserver.properties
• For the Rational Engineering Lifecycle Manager application: RELM__install_dir/server/conf/relm/teamserver.properties
• For the Design Management application: DM__install_dir/server/conf/dm/teamserver.properties
• For the Global Configuration Management application: GC__install_dir/server/conf/gc/teamserver.properties
• For the Data Collection Component application: DCC__install_dir/server/conf/dcc/teamserver.properties
• For the Report Builder application: JRS__install_dir/server/conf/rs/app.properties
• For the Lifecycle Query Engine application: LQE__install_dir/server/conf/lqe/lqe.properties
• For the Link Index Provider application: JTS__install_dir/server/conf/ldx/lqe.properties
Verify that the application configuration files are copied from previous configuration directory to version :
• /QIBM/UserData/JazzTeamServer6061/server/conf/teamserver.properties

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.team.repository.server.webapp.url property. The URL for the version application must be the same as the one that was used in the previous version.
• Valid database vendor entries. Ensure the database that is specified in each application's teamserver.properties file exists.

Verify the application servers:
• Verify that _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 _install_dir/server/tomcat/conf/server.xml file contains these code snippets:

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

• The _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 server.xml file, verify that those settings are copied to the _install_dir/server/tomcat/conf/server.xml file.
• Verify that web.xml file has the correct <security-role> tags:
• For Jazz Team Server: JTS__install_dir/server/tomcat/webapps/jts/WEB-INF/web.xml
• For Change and Configuration Management application: CCM__install_dir/server/tomcat/webapps/ccm/WEB-INF/web.xml
• For Rhapsody Model Manager application: RMM__install_dir/server/tomcat/webapps/am/WEB-INF/web.xml
• For Quality Management application: QM__install_dir/server/tomcat/webapps/qm/WEB-INF/web.xml
• For Requirements Management application: RM__install_dir/server/tomcat/webapps/rm/WEB-INF/web.xml
• For Rational Engineering Lifecycle Manager application: RELM__install_dir/server/tomcat/webapps/relm/WEB-INF/web.xml
• For Data Collection Component application: DCC__install_dir/server/tomcat/webapps/dcc/WEB-INF/web.xml
• For Global Configuration Management application: GC__install_dir/server/tomcat/webapps/gc/WEB-INF/web.xml
• Ensure that these applications are deployed and started:
• jts.war
• clmhelp.war
• ccm.war
• am.war
• qm.war
• rm.war
• converter.war
• relm.war
• dm.war
• dcc.war
• rs.war
• gc.war
• lqe.war
• ldx.war
Deploying and starting the server
Check the server log files: Check the 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 _install_dir/server/logs directory.
• If you are using a WebSphere Liberty server, the log files are in the _install_dir/server/logs directory.
• If you are using a WebSphere Application Server, the log files are in the /logs\logs directory.
• A new log file called rm_addTablesProgress.log is generated when you upgrade the Requirements Management server to a new version. This new log tracks the progress of project migration, it displays the number of formal reviews, URIs, review baselines, module baselines, and project baselines grouped by projects.

Regenerate your self-signed keystore: Your previous version self-signed certificate might not work after you upgrade because of the potential cypher changes in the new version. If you are not able to login to the server after the upgrade with the following error: ssl_error_no_cypher_overlap, you might just need to regenerate your self-signed keystore by using the newer JDK that is bundled with the product.

Installing a security certificate

Check the public URLs: If you upgraded Jazz Team Server, or any of the CLM applications, 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.

For Report Builder, go to https://hostname.example.com:9443/application context root/setup and make sure that no errors are displayed.

For Lifecycle Query Engine, go to https://hostname.example.com:9443/application context root/web/admin/home and make sure that no errors are displayed.

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

It is also a good practice to run the database statistics after the upgrade to help with server performance. For more information about the database stats command, see the planning checklist table in this document.

Note: Lifecycle Query Engine and Report Builder do not have a diagnostics section.

• Check the web client
• Check indexing by using search
• Check Rational Team Concert Eclipse or Visual Studio clients
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 Rhapsody Model Manager application, verify Rhapsody models.
• 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
• The Requirements Management application requires the following Windows server dependency package installed on the server to be able to display the file previews correctly. If you are prompted for "CRSSS0980W A preview of the file is not available because of a server-side configuration issue." error message, you must obtain the Visual C++ Redistributable Packages for Visual Studio 2013 from Microsoft website and install it on your Windows server.
• In Report Builder, check that any pre-existing reports are present. Run a couple of the reports to verify that they show the expected data.

### 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.

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/Jenkins

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

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.

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 i

Rational Team Concert integrates with Rational Developer for i 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 i. For more information, see Rational Team Concert and Rational Developer for i.

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 Integrating 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 the product documentation.

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.