The complete instructions to upgrade your product to version 6.0.2 are generated based on the selections and inputs that you provided on the previous page.
| Deployment topology |
|
| Applications to upgrade |
|
| Previous installation path |
|
| New installation path |
|
| Upgrade method |
|
| Previous product version |
|
| Operating system |
|
| Application server |
|
| Database server |
|
| Configured data warehouse |
|
| Installing Jazz Authorization Server |
|
| Integration with other products |
|
Important: Before you upgrade, read these important notes.
- To upgrade to version 6.0.2, 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 6.0.2 applications, ensure to apply the latest interim fix to your installation before you continue with the upgrade. This ensures that your new version 6.0.2 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.
- Before you can upgrade your Data Collection Component to version 6.0.2, you must have the version 6.0.1, 6.0, 5.0.2, 5.0.1, or 5.0 with the HotFix installed. In addition, Jazz Team Server and any CLM applications that you want to collect data must be upgraded to version 6.0.2.
- 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 6.0.2, you create project baselines instead of module baselines. If you migrate from a version 5 release to the 6.0.2 release, all module baselines are converted to project baselines. Note that you cannot copy a module from a project baseline.
- Adjust the Java virtual machine arguments. For more information about JVM settings, see Setting up WebSphere Application Server.
- The upgrade process to version 6.0.2 uses your existing databases. The addTables and upgradeWarehouse command will update the databases to the version 6.0.2 formats.
- If you installed multiple Jazz applications on the same application server profile, you must upgrade those applications to version 6.0.2 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.
- 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.
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 6.0.2, and a few older versions are deprecated. To learn about the new requirements and to see whether your system meets the minimum requirements, click the System requirements link. | System requirements |
|
Get the product installation media: For a local repository download, you need approximately 5 GB of hard drive space to download and extract your product installation media. | You can download the server installation files from jazz.net |
|
Review an upgrade topology example. | |
|
Synchronize the clocks on all servers: In a distributed environment, ensure that the clocks on all servers are synchronized by using the Network Time Protocol (NTP). | For more information about NTP, visit ntp.org |
|
Understand the upgrade process: Learn about the upgrade process and how the upgrade might affect your deployment. | Understanding the deployment and upgrade process |
|
Plan for your applications to be unavailable: Your applications will be unavailable for a brief period while you back up everything and update your applications to version 6.0.2. 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:
IBM DB2i database is preconfigured on your IBM i system.
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_STAT |
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. | Managing licensing |
|
Check the browser compatibility:
|
|
|
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.
|
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 application
- QM: Quality Management application
- RM: Requirements Management application
- 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
- GCM: Global Configuration Management
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.
- Log on to WebSphere Application Server Integrated Solutions Console.
- Expand Servers > Server types, and then click WebSphere Application Servers.
- Record the server name and node name.
- Click server1, expand Java and Process Management and then click Process definition > Java Virtual Machine.
- Record the values under Generic JVM arguments.
- Expand Applications > Application types, and then click WebSphere Enterprise Application.
- 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)
Install the new version 6.0.2 applications
Install the new version 6.0.2 applications including the trial license keys into a new package group, but do not run the setup wizard after the installation. For distributed configurations, install the version 6.0.2 applications that correspond to the previously installed applications.
For information about installing the server, see Installing by using IBM Installation Manager or Installing by using command-line commands.
Note: In a distributed environment, the trial license keys must only be installed on Jazz Team Server.
Install the CLM version 6.0.2 applications, but do not run the setup wizard. For distributed configurations, install the version 6.0.2 applications that correspond to the previously installed applications. For information about installing the server, see Installing on IBM i using licensed programs.
Important: After you install the new version 6.0.2 applications, ensure to apply the latest interim fix to your installation before you continue with the upgrade. This ensures that your new version 6.0.2 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.
Install the Apache Tomcat server
Starting in version 6.0.1, Apache Tomcat is not provided as a default application server. However, Apache Tomcat is supported and you can use it. Complete the following steps to download and install Apache Tomcat.
Note: In the following examples, the default webapps location is used. If you used a different location during the installation of CLM version 6.0.2 to copy the application WAR files, change the path accordingly.
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy all application WAR files to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy all application WAR files to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
In a distributed environment, do 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.c. to copy the ldx.war file.
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the ldx.war, jts.war and clmhelp.war files to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the ldx.war, jts.war and clmhelp.war files to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Change and Configuration Management server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the ccm.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the ccm.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Requirements Management server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the rm.war and converter.war files to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the rm.war and converter.war files to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Quality Management server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the qm.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the qm.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Rational Engineering Lifecycle Management server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the relm.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the relm.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Data Collection Component server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the dcc.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the dcc.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Global Configuration Management server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the gc.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the gc.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Lifecycle Query Engine server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the lqe.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the lqe.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Report Builder server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the rs.war file to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the rs.war file to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
Installing Apache Tomcat on the Design Manager server
- Open a browser, go to the Apache Tomcat website, and download a supported version of Apache Tomcat application server. The supported version of Apache Tomcat is 7.0.59.
- Extract the downloaded .zip file to /server\server.
- Extract the downloaded .zip file to .
- The extract procedure creates a directory named apache-tomcat-7.0.59. Rename this directory to tomcat.
- Go to /server/webapps\server\webapps and copy the dm.war, rsadm.war, and rdmhelp.war files to /server/tomcat/webapps\server\tomcat\webapps.
- Go to /server/webapps\server\webapps and copy the dm.war, rsadm.war, and rdmhelp.war files to /webapps\webapps.
- Go to /server/tomcat\server\tomcat and copy ibm-team-ssl.keystore or any custom .keystore file you were using in previous version to /server/tomcat\server\tomcat.
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
- 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
For information about the DB2 database REORGCHK command, see the DB2 website.EXEC DBMS_STATS.GATHER_DATABASE_STAT
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.
- 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.logcd /server
./repotools-qm.sh -onlineMigrateEstimate teamserver.properties=/server/conf/qm/teamserver.properties logFile=repotools_onlineMigrateEstimate.logFor more information about the -onlineMigrateEstimate command and its parameters, see Repository tools command for evaluating the online migration process.
- 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=50cd /server/
./repotools-qm.sh -onlineMigrate teamserver.properties=/server/conf/qm/teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50For more information about the -onlineMigrate command and its parameters, see Repository tools command for online migration.
You can stop the online migration or revert to a previous state by using other repository tools commands.
To safely stop the online migration at any time, use the -onlineMigrateStop command. For more information, see Repository tools command for stopping online migration.
To revert the database to a previous state, use the -onlineMigrateRevert command. For more information, see Repository tools command for reverting online migration.
Optional: Online migration of change and configuration management data
The Change and Configuration Management application online migration is an optional upgrade step that is done while the old server is still running. It migrates data in the live repository to reduce the amount of downtime incurred during normal migration. The data is migrated in such a way as to not affect users on the existing server.
Procedure
- 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 sp_updatestats
For information about the DB2 database REORGCHK command, see the DB2 website.EXEC DBMS_STATS.GATHER_DATABASE_STAT
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.
- 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.logcd /server/
./repotools-ccm.sh -onlineMigrateEstimate teamserver.properties=/server/conf/ccm/teamserver.properties logFile=repotools_onlineMigrateEstimate.logFor more information about the -onlineMigrateEstimate command and its parameters, see Repository tools command for evaluating the online migration process.
- 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=50cd /server/
./repotools-ccm.sh -onlineMigrate teamserver.properties=/server/conf/ccm/teamserver.properties logFile=repotools_onlineMigrate.log numStatesPerRun=100 priority=50For 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
- Rational Software Architect Design Management application
- Global Configuration Management application
Note: The command shuts down the server before starting the backup process.
- Open a command prompt and change to the bin folder of the WebSphere Application Server profiles directory. For example, cd \bin.
- 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.
backupConfig.bat Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password
For example:
backupConfig.bat C:\WAS_backup\CLM_5.0.xCLM_6.0.x_profile.zip -username WAS admin -password WAS admin password
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
- Open a command shell and change to the bin folder of the WebSphere Application Server profiles directory. For example, cd /bin
- 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.
./backupConfig.sh Path_to_a_new_compressed_file_to_create_backup_of_profile -username WAS_primary_administrative_user_name -password WAS_administrative_password
For example:
./backupConfig.sh /root/WAS_backup/CLM_5.0.xCLM_6.0.x_profile.zip -username admin -password password
Note: The directory path to the compressed file must exist before running the backup command.
Tip: You can restore the backed-up profile by running the ./restoreConfig.sh command. For example, ./restoreConfig.sh /root/WAS_backup/CLM_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 6.0.2.
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:
adminUserId=yourAdminUserId
adminPassword=yourAdminPassword
repositoryURL=https://hostname.example.com:9443/dm
smartCard=<none>
certificateFile=<none>
kerberos=<none>
Procedure
- 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.
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 6.0.2. Complete the following steps to export the VVC data.
- Ensure that the version 6 VVC server is shut down.
- Ensure that the version 5.0.2 VVC server is shut down.
- Update your version 6.0 to interim fix 2 if not already updated. Go to the Design Management download page on Jazz.net and download Design Management 6.0 interim fix 2.
- Update your version 5.0.2 to interim fix 11 if not already updated. Go to the Design Management download page on Jazz.net and download Design Management 5.0.2 interim fix 11.
- Go to \server/server directory and if not present create a directory named patch.
- Go to \server/server directory and if not present create a directory named patch.
- Copy the downloaded patch file to the \server\patch/server/patch directory.
- Copy the downloaded patch file to the \server\patch/server/patch directory.
- Start the version 6 VVC server.
- Start the version 5.0.2 VVC server.
- Create a file named credentials.txt under the \/server directory with the following content:
- Create a file named credentials.txt under the \/server directory with the following content:
- Create a folder on your drive to export the VVC migration data. For example: C:\temp\vvcMigration/opt/tmp/vvcMigration.
- Open a command windowshell as an administrator and enter the following commands:
adminUserId=yourAdminUserId
adminPassword=yourAdminPassword
repositoryURL=https://hostname.example.com:9443/vvc
smartCard=<none>
certificateFile=<none>
kerberos=<none>
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
- Rational Software Architect Design Management application
- Global Configuration Management application
- 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.
- Click Applications > Application Types > WebSphere enterprise applications.
- 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 6.0.2 counterpart.
- 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 6.0.2 counterpart.
- 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 6.0.2 counterpart.
- Click the Enterprise Applications link and then stop and uninstall the following installed applications:
- jts_war
- clmhelp_war
- admin_war
- ccm_war
- qm_war
- rm_war
- converter_war
- relm_war
- lqe_war
- ldx_war
- dcc_war
- rs_war
- dm_war
- rdmhelp_war
- vvc_war
- vvchelp_war
- rsadm_war
- gc_war
- 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.
- Start the server by opening a command windowshell and entering the following commands. Replace server1 with the name of your server:
cd \bin
startServer.bat server1
cd /bin
./startServer.sh server1
Continue with the following steps to remove previous installed applications.
- 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:
- 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.
- On the server that hosts Jazz Team Server / Link Index Provider enter the following command:
- On the server that hosts the Change and Configuration Management application, enter the following command:
- On the server that hosts the Quality Management application, enter the following command:
- On the server that hosts the Requirements Management application, enter the following command:
- On the server that hosts the Rational Engineering Lifecycle Manager application, enter the following command:
- On the server that hosts the Data Collection Component application, enter the following command:
- On the server that hosts the Report Builder application, enter the following command:
- On the server that hosts the Lifecycle Query Engine application, enter the following command:
- On the server that hosts the Rational Software Architect Design Management application, enter the following command:
- On the server that hosts the Rational Rhapsody Design Manager application, enter the following command:
- On the server that hosts the Global Configuration Management application, enter the following command:
cd \bin
startServer.bat server1
cd /bin
./startServer.sh server1
Note: On Windows platforms you must use forward slash in the paths for the location of the Jython script.
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy.py /server/webapps JazzInstallDirOldVersion/server/webapps
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.
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py jts,clmhelp,ldx
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py ccm
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py qm
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py rm,converter
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py relm
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py dcc
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py rs
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py lqe
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py dm,rdmhelp,vvc,vvchelp,rsadm
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py dm,rdmhelp,vvc,vvchelp
wsadmin.bat./wsadmin.sh -lang jython -user WAS_username -password WAS_password -f JazzInstallDir6.0.2/server/was/clm_undeploy_distributed.py gc
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
- If your Jazz Team Server is installed on a Windows platform, but you are using the DB2 for z/OS database server, open the JazzInstallDir6.0.2/server/was/config.py for editing.
- 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.
- To configure the Oracle JDBC driver location open the JazzInstallDir6.0.2/server/was/config.py for editing.
- 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.
- To configure the SQL Server JDBC driver location open the JazzInstallDir6.0.2/server/was/config.py for editing.
- 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.
- Save and close the config.py file.
Procedure
- Open a command window as administrator and enter the following commands:
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
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/JazzInstallDir6.0.2/server/was/clm_was_config.py C:/JazzInstallDir6.0.2/server/conf -config C:/JazzInstallDir6.0.2/server/was - Open a command shell as administrator and enter the following commands:
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf-config /server/was - Open a command window as administrator and enter the following commands:
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
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f C:/JazzInstallDir6.0.2/server/was/clm_was_config.py C:/JazzInstallDir6.0.2/server/conf -config C:/JazzInstallDir6.0.2/server/was - On the server that host Jazz Team Server / Link Index Provider enter the following commands:
- On the server that host the Change and Configuration Management application, enter the following commands:
- On the server that host the Quality Management application, enter the following commands:
- On the server that host the Requirements Management application, enter the following commands:
- On the server that host the Rational Engineering Lifecycle Manager application, enter the following commands:
- On the server that host the Data Collection Component application, enter the following commands:
- On the server that host the Report Builder application, enter the following commands:
- On the server that host the Lifecycle Query Engine application, enter the following commands:
- On the server that host the Global Configuration Management application, enter the following commands:
- On the server that host the Rational Rhapsody Design Manager application, enter the following commands:
- On the server that host the Rational Software Architect Design Management application, enter the following commands:
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f /server/was/clm_was_config.py /server/conf -config /server/was
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
- Rational Software Architect Design Management application
- Global Configuration Management application
- Log on to the WebSphere Application Server Integrated Solutions Console at https://hostname:9043/ibm/console/logon.jsp.
- Click Servers > Server Types > WebSphere application servers.
- Click the server name to open it. The default server name is server1.
- Under Server Infrastructure section, click Java and Process Management > Process definition.
- Under Additional Properties, click Java Virtual Machine.
- Under Additional Properties, click Custom properties.
- Click JAZZ_HOME and update its value to file:///6.0.2_install_dir/server/conf. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_6.0.2/server/conffile:///opt/IBM/JazzTeamServer_6.0.2/server/conffile:///usr/IBM/JazzTeamServer_6.0.2/server/conf.
- Click log4j.configuration and update its value to file:///6.0.2_install_dir/server/conf/startup_log4j.properties. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_6.0.2/server/conf/startup_log4j.propertiesfile:///opt/IBM/JazzTeamServer_6.0.2/server/conf/startup_log4j.propertiesfile:///usr/IBM/JazzTeamServer_6.0.2/server/conf/startup_log4j.properties.
- Click lqe.config.location and update its value to file:///6.0.2_install_dir/server/conf/lqe. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_6.0.2/server/conf/lqefile:///opt/IBM/JazzTeamServer_6.0.2/server/conf/lqefile:///usr/IBM/JazzTeamServer_6.0.2/server/conf/lqe.
- Click ldx.config.location and update its value to file:///6.0.2_install_dir/server/conf/ldx. For example, file:///C:/PROGRA~1/IBM/JazzTeamServer_6.0.2/server/conf/ldxfile:///opt/IBM/JazzTeamServer_6.0.2/server/conf/ldxfile:///usr/IBM/JazzTeamServer_6.0.2/server/conf/ldx.
- If you are connecting to an Oracle database, ensure that ORACLE_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file in .
- If you are connecting to SQL Server database, ensure that SQLSERVER_JDBC_DRIVER_FILE is pointing to the correct JDBC driver file in .
- Save the changes to the master configuration when prompted.
Update the JRS shared library classpath
- In WebSphere Integrated Solutions Console navigation pane click Environment > Shared libraries.
- Click the JRS shard library name in the list to open it.
- In the Classpath field, update the path to the new installation directory. For example:
- Click Apply and then Save directly to the master configuration.
\server\conf\rs\WAS_SharedLibrary/server/conf/rs/WAS_SharedLibrary
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
- Rational Software Architect Design Management application
- Open a command prompt and change to the \bin directory.
- Enter the following command:
stopServer.bat server1 -user admin_userid -password admin_password
- Open a command prompt and change to the /bin directory.
- Enter the following command:
./stopServer.sh server1 -user admin_userid -password admin_password
- In QShell, navigate to the old configuration directory, for example, /QIBM/UserData/Old_JazzTeamServer/server
- Enter the following command:
./serverShutdown.sh profileName wasVersion wasOption adminId adminPwd
In addition to QShell, you can use the CL command. Enter QJTS50/STPJAZZSVR on the 5250 command prompt, then press PF4 to prompt for parameters. The following table shows the default values:
| Command name | Default value | Possible values |
|---|---|---|
| WAS PROFILE NAME | JTS | Name |
| WAS VERSION | V85 | V8, V85 |
| WAS OPTION | BASE | Name |
| WAS ADMIN USER ID | JTSADMIN | Name |
| WAS ADMIN PASSWORD | None | Name |
Clean up the WebSphere Application Server temp directories
In a distributed topology, you must complete 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
- 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:
- admin_war
- jts_war
- ccm_war
- qm_war
- rm_war
- converter_war
- clmhelp_war
- relm_war
- lqe_war
- ldx_war
- dcc_war
- rs_war
- dm_war
- rdmhelp_war
- vvc_war
- vvchelp_war
- rsadm_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
- Rational Software Architect Design Management application
- Global Configuration Management application
Remove the application-related log files form 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
- 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 to be cleared, the JVM's cache and the OSGi cache. Complete the following steps to clear these caches:
- Stop WebSphere Application Server if it is running.
- To clear the OSGi class cache, open a command windowshell and enter the following command:
cd \bin
osgiCfgInit.bat/bin
./osgiCfgInit.sh - To clear the JVM's class cache, enter the following command:
cd \bin
clearClassCache.bat/bin
./clearClassCache.sh
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:
- 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
- Rational Rhapsody Design Manager application
- Rational Software Architect Design Management application
- Global Configuration Management application
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 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 shell and enter the following command:
cd /server
./server.shutdown
On the CCM 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
Copy the Lifecycle Query Engine (LQE) configuration files
- Before copying the LQE configuration files, go to the directory where you just installed the version 6.0.2 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.
- Enter the following commands to copy the configuration files to the new installation directory:
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
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
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\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
- Before copying the LDX configuration files, go to the directory where you just installed the version 6.0.2 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.
- Enter the following commands to copy the configuration files to the new installation directory:
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
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\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
- Before copying the Derby database, go to the directory where you just installed the version 6.0.2 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 6.0.2 Derby directories.
- Go to the directory where you previously installed the CLM applications, copy the Derby database, and paste it in the equivalent directory for version 6.0.2. You can also open a command prompt and enter the following commands to copy the Derby database.
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 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 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
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 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
Enter the following command to copy the Link Index Provider database:
xcopy /s \server\conf\ldx\derbyDB \server\conf\ldx\derbyDB
Enter the following command to copy the Data Warehouse database:
xcopy /s \server\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 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
Enter the following command to copy the Link Index Provider database:
xcopy /s \server\conf\ldx\derbyDB \server\conf\ldx\derbyDB
Enter the following command to copy the Data Warehouse database:
xcopy /s \server\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 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
Enter the following command to copy the Data Warehouse database:
cp -R /server/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 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
Enter the following command to copy the Data Warehouse database:
cp -R /server/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 6.0.2 (purgeCache command)
After you export your version 5.0.26 VVC data, now you can import them into version 6.0.2. 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.
- Open a command windowshell as an administrator and enter the following commands:
- After the purging cache command is complete, continue with the next step to upgrade your Design Management application.
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
Copy the index files
Attention: Do these steps only if the index files in the teamserver.properties files are located on relative paths or on absolute paths to unstable directories. An example of an unstable directory is old_install_dir. If the index files are in that directory and the directory is uninstalled, you will lose your index files.
Copy your JFS/text indices from previous installation directory to 6.0.2. For distributed systems go to the appropriate server and copy the files.
- Open a command prompt and enter this command to clear the default version 6.0.2 indices directory:
del /s /f \server\conf\jts\indicesdel /s /f \server\conf\ccm\indicesdel /s /f \server\conf\qm\indicesdel /s /f \server\conf\rm\indicesdel /s /f \server\conf\dcc\indicesdel /s /f \server\conf\relm\indicesdel /s /f \server\conf\gc\indices
Enter Y to confirm the delete operationrm -rf /server/conf/jts/indicesrm -rf /server/conf/ccm/indicesrm -rf /server/conf/qm/indicesrm -rf /server/conf/rm/indicesrm -rf /server/conf/dcc/indicesrm -rf /server/conf/relm/indicesrm -rf /server/conf/gc/indices - Open a command prompt and enter this command to copy the indices from the previous installation to version 6.0.2:
xcopy /s \server\conf\jts\indices \server\conf\jts\indicesxcopy /s \server\conf\ccm\indices \server\conf\ccm\indicesxcopy /s \server\conf\qm\indices \server\conf\qm\indicesxcopy /s \server\conf\rm\indices \server\conf\rm\indicesxcopy /s \server\conf\dcc\indices \server\conf\dcc\indicesxcopy /s \server\conf\relm\indices \server\conf\relm\indicesxcopy /s \server\conf\gc\indices \server\conf\gc\indicesxcopy /s \server\conf\dm\indices \server\conf\dm\indicesxcopy /s \server\conf\dm\indices \server\conf\dm\indicescp -R /server/conf/jts/indices /server/conf/jts/indicescp -R /server/conf/ccm/indices /server/conf/ccm/indicescp -R /server/conf/qm/indices /server/conf/qm/indicescp -R /server/conf/rm/indices /server/conf/rm/indicescp -R /server/conf/dcc/indices /server/conf/dcc/indicescp -R /server/conf/relm/indices /server/conf/relm/indicescp -R /server/conf/gc/indices /server/conf/gc/indicescp -R /server/conf/dm/indices /server/conf/dm/indicescp -R /server/conf/dm/indices /server/conf/dm/indices
To copy your JFS/text indices from a previous installation to version 6.0.2, follow these steps. For distributed systems, go to the appropriate server and copy the files.
- Open a command prompt and enter this command to clear the default version 6.0.2 indices directory:
Del /s /f \server\conf\jts\indicesDel /s /f \server\conf\ccm\indicesDel /s /f \server\conf\qm\indicesDel /s /f \server\conf\rm\indicesDel /s /f \server\conf\dcc\indicesDel /s /f \server\conf\relm\indicesDel /s /f \server\conf\gc\indicesrm -rf /server/conf/jts/indicesrm -rf /server/conf/ccm/indicesrm -rf /server/conf/qm/indicesrm -rf /server/conf/rm/indicesrm -rf /server/conf/dcc/indicesrm -rf /server/conf/relm/indicesrm -rf /server/conf/gc/indices
- In the following location open the teamserver.properties file and search for com.ibm.team.fulltext.indexlocation:
- \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\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
If the property com.ibm.team.fulltext.indexLocation is 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 full text indices 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 in the CLM 6.0.2 application's teamserver.properties file. An example of absolute stable location looks like this: com.ibm.team.fulltext.indexLocation=6.0.2_install_dir/server/conf/application_context_root/indices/workitemindex where 6.0.2_install_dir is the location where CLM 6.0.2 application is installed.
If the com.ibm.team.fulltext.indexLocation property is pointing to a unstable absolute path, such as path to the old_install_dir directory that might be uninstalled and deleted, change the path to an absolute path that points to a stable location.
An example of an absolute stable location looks like this example: com.ibm.team.fulltext.indexLocation=6.0.2_install_dir/server/conf/application_context_root/indices/workitemindex, where 6.0.2_install_dir is the location where the CLM version 6.0.2 application is installed.
Open a command prompt and enter the following command to copy the full text indices from previous version to 6.0.2. Change the source directory according to the location of the index files:
Undo custom performance optimization
A performance optimization for SQL Server was introduced in version 6.0 for the Requirements Management Design Mansgement 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
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN CONCEPT NVARCHAR(1000)
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN STORAGE NVARCHAR(1000)
Run the upgrade commands
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:
repotools-jts.bat -migration_jts_updateConfigurationFiles oldJTSHome=\server\conf updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newTomcatHome=
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:
./repotools-jts.sh -migration_jts_updateConfigurationFiles oldJTSHome=/server/conf updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newTomcatHome=
./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.
Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. For more information, see Migrating the data warehouse.
Upgrading 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 -oldApplicationHome and -ignoreJTSVersionCheck:
cd \/server
upgrade\rs\rs_upgrade.batupgrade/rs/rs_upgrade.sh -oldApplicationHome \server\conf/server/conf -ignoreJTSVersionCheck
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:
Note: If your previous installation originated from version 2.x, repotools-ccm.bat will be repotools-jazz.bat instead. Also the default application context root is /ccm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command.
repotools-ccm.bat -migration_ccm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-ccm.bat -addTables
To upgrade the CCM application configuration files, open a command shell and enter the following commands:
Note: If your previous installation originated from version 2.x, repotools-ccm.sh will be repotools-jazz.sh instead. Also the default application context root is /ccm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command.
./repotools-ccm.sh -migration_ccm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./repotools-ccm.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:
repotools-relm.bat -migration_relm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-relm.bat -addTables
To upgrade the RELM application configuration files, open a command shell and enter the following commands:
./repotools-relm.sh -migration_relm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./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:
repotools-dm.bat -migration_dm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck applicationContextRoot=dm updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-dm.bat -addTables
repotools-dm.bat -fixVersionTable
To upgrade the DM application configuration files, open a command shell and enter the following commands:
./repotools-dm.sh -migration_dm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck applicationContextRoot=dm updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./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:
repotools-gc.bat -migration_gc_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-gc.bat -addTables
To upgrade the GC application configuration files, open a command shell and enter the following commands:
./repotools-gc.sh -migration_gc_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./repotools-gc.sh -addTables
Upgrading the Data Collection Component application
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:
repotools-dcc.bat -migration_dcc_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-dcc.bat -addTables
To upgrade the DCC application configuration files, open a command shell and enter the following commands:
./repotools-dcc.sh -migration_dcc_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./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_STAT
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:
Note: If your previous installation originated from version 2.x, repotools-qm.bat will be repotools-jazz.bat instead. Also the default application context root is /qm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command.
repotools-qm.bat -migration_qm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-qm.bat -addTables
To upgrade the QM application configuration files, open a command shell and enter the following commands:
Note: If your previous installation originated from version 2.x, repotools-qm.sh will be repotools-jazz.sh instead. Also the default application context root is /qm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command.
./repotools-qm.sh -migration_qm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./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_STAT
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:
repotools-rm.bat -migration_rm_updateConfigurationFiles oldApplicationHome=\server\conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
repotools-rm.bat -addTables
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.
To upgrade the RM application configuration files, open a command shell and enter the following commands:
./repotools-rm.sh -migration_rm_updateConfigurationFiles oldApplicationHome=/server/conf ignoreJTSVersionCheck updateTomcatFiles=no updateAppServerFiles=no updateTomcatFiles=yes newApplicationTomcatHome=
./repotools-rm.sh -addTables
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 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:
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 6.0.2. 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_6.0.2_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:
upgrade\jts\jts_upgrade.bat -oldJTSHome "\server\conf" -updateTomcatFiles yes -newTomcatHome -updateTomcatFiles no -updateAppServerFiles no -noPrompt -noVerify -noStepPrompt -noEditor
upgrade\jts\jts_upgrade.bat -oldJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/jts/indices/workitemindex, where JTS_6.0.2_install_dir is the location where Jazz Team Server 6.0.2 is installed.
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.
Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.
Upgrading the Change and Configuration Management application
To upgrade Change and Configuration Management application open a command prompt with administrative privileges and enter the following commands:
Note: If your previous installation originated from version 2.x, the upgrade path will be upgrade\jazz\ccm_upgrade.bat instead of upgrade\ccm\ccm_upgrade.bat. Also the default application context root is /ccm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command. In a single server topology, applications cannot share the same context root.
upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/ccm/indices/workitemindex where CCM_6.0.2_install_dir is the location where Change and Configuration Management application 6.0.2 is installed.
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:
upgrade\relm\relm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\relm\relm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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. 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=RELM_6.0.2_install_dir/server/conf/relm/indices/workitemindex where RELM_6.0.2_install_dir is the location where the Rational Engineering Lifecycle Manager application 6.0.2 is installed.
Upgrading the Design Management application
To upgrade the Design Management application open a command prompt with administrative privileges and enter the following commands:
upgrade\dm\dm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\dm\dm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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_6.0.2_install_dir/server/conf/dm/indices/workitemindex where DM_6.0.2_install_dir is the location where the Design Management application 6.0.2 is installed.
Upgrading the Data Collection Component application
To upgrade the Data Collection Component application open a command prompt with administrative privileges and enter the following commands:
upgrade\dcc\dcc_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\dcc\dcc_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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_6.0.2_install_dir/server/conf/dcc/indices/workitemindex where DCC_6.0.2_install_dir is the location where the Data Collection Component application 6.0.2 is installed.
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:
upgrade\gc\gc_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\gc\gc_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/gc/indices/workitemindex where GC_6.0.2_install_dir is the location where the Global Configuration Management application 6.0.2 is installed.
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.
upgrade\rs\rs_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\rs\rs_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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:
upgrade\lqe\lqe_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\lqe\lqe_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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:
upgrade\ldx\ldx_upgrade.bat -oldApplicationHome "\server\conf" -newApplicationHome "\server\conf"
upgrade\ldx\ldx_upgrade.bat -oldApplicationHome "\server\conf" -newApplicationHome "\server\conf"
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_STAT
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:
Note: If your previous installation originated from version 2.x, the upgrade path will be upgrade\jazz\qm_upgrade.bat instead of upgrade\qm\qm_upgrade.bat. Also the default application context root is /qm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command. In a single server topology, applications cannot share the same context root.
upgrade\qm\qm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\qm\qm_upgrade.bat -oldApplicationHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/qm/indices/workitemindex where QM_6.0.2_install_dir is the location where Quality Management application 6.0.2 is installed.
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_STAT
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:
upgrade\rm\rm_upgrade.bat -oldApplicationHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade\rm\rm_upgrade.bat -oldApplicationHome "\server\conf" -oldJTSHome "\server\conf" -newJTSHome "\server\conf" -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
During the upgrade, after the configuration files are merged, an editor opens in which you can check the Requirements Management teamserver.properties file.
Upgrading Jazz Team Server
To upgrade Jazz Team Server open a command shell and enter the following commands:
upgrade/jts/jts_upgrade.sh -oldJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
upgrade/jts/jts_upgrade.sh -oldJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/jts/indices/workitemindex where JTS_6.0.2_install_dir is the location where Jazz Team Server 6.0.2 is installed.
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.
Note: If you are integrating with Rational Insight, you must first run the Rational Insight migrateDW command. Enter [S] to skip the CLM data warehouse upgrade. For more information, see Migrating the data warehouse.
Upgrading the Change and Configuration Management application
To upgrade the Change and Configuration Management application open a command shell and enter the following commands:
Note: If your previous installation originated from version 2.x, the upgrade path will be upgrade/jazz/ccm_upgrade.sh instead of upgrade/ccm/ccm_upgrade.sh. Also the default application context root is /ccm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command. In a single server topology, applications cannot share the same context root.
upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/ccm/indices/workitemindex where CCM_6.0.2_install_dir is the location where Change and Configuration Management application 6.0.2 is installed.
Upgrading the Rational Engineering Lifecycle Manager application
To upgrade the Rational Engineering Lifecycle Manager application open a command shell and enter the following commands:
upgrade/relm/relm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/relm/relm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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_6.0.2_install_dir/server/conf/relm/indices/workitemindex where RELM_6.0.2_install_dir is the location where the Rational Engineering Lifecycle Manager application 6.0.2 is installed.
Upgrading the Design Management application
To upgrade the Design Management application open a command shell and enter the following commands:
upgrade/dm/dm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/dm/dm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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_6.0.2_install_dir/server/conf/dm/indices/workitemindex where DM_6.0.2_install_dir is the location where the Design Management application 6.0.2 is installed.
Upgrading the Data Collection Component application
To upgrade the Data Collection Component application open a command shell and enter the following commands:
upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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_6.0.2_install_dir/server/conf/dcc/indices/workitemindex where DCC_6.0.2_install_dir is the location where Data Collection Component application 6.0.2 is installed.
Upgrading the Global Configuration Management application
To upgrade the Global Configuration Management application open a command shell and enter the following commands:
upgrade/gc/gc_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/gc/gc_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/gc/indices/workitemindex where GC_6.0.2_install_dir is the location where Global Configuration Management application 6.0.2 is installed.
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.
upgrade/rs/rs_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/rs/rs_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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:
upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -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:
upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /server/conf -newApplicationHome /server/conf
upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /server/conf -newApplicationHome /server/conf
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_STAT
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:
Note: If your previous installation originated from version 2.x, the upgrade path will be upgrade/jazz/qm_upgrade.sh instead of upgrade/qm/qm_upgrade.sh. Also the default application context root is /qm. To enter a different context root such as /jazz, use the applicationContextRoot=jazz switch in the command. In a single server topology, applications cannot share the same context root.
upgrade/qm/qm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/qm/qm_upgrade.sh -oldApplicationHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
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_6.0.2_install_dir/server/conf/qm/indices/workitemindex where QM_6.0.2_install_dir is the location where Quality Management application 6.0.2 is installed.
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_STAT
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:
upgrade/rm/rm_upgrade.sh -oldApplicationHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
Ensure that you can connect to Jazz Team Server with the network path you use in the -newJTSHome argument.
upgrade/rm/rm_upgrade.sh -oldApplicationHome /server/conf -oldJTSHome /server/conf -newJTSHome /server/conf -updateTomcatFiles no -updateAppServerFiles no -updateTomcatFiles yes -newApplicationTomcatHome -noPrompt -noVerify -noStepPrompt -noEditor
During the upgrade, after the configuration files are merged, an editor opens in which you can check the Requirements Management teamserver.properties file.
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.
Apply performance optimization for VVCMODEL.VERSION
A performance optimization has been identified for the VVCMODEL.VERSION table which must be applied manually. After you upgrade your server, open a sqlcmd command line tool and enter the following commands to apply the optimization to the Requirements Management Design Management database:
DROP INDEX VERSION_CONCEPT_DX ON VVCMODEL.VERSION
DROP INDEX VERSION_STORAGE_DX ON VVCMODEL.VERSION
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN CONCEPT NVARCHAR(450) NOT NULL
ALTER TABLE VVCMODEL.VERSION ALTER COLUMN STORAGE NVARCHAR(450) NULL
CREATE Â INDEX VERSION_CONCEPT_DX ON VVCMODEL.VERSION (CONCEPT)
CREATE Â INDEX VERSION_STORAGE_DX ON VVCMODEL.VERSION (STORAGE)
Import the version 5.0.26 VVC data into version 6.0.2 (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 6.0.2.
- Open a command windowshell as an administrator and enter the following commands:
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
- Log on to IBM i operating system using a user ID that has QSECOFR authority.
- In QShell, navigate to the Jazz Team Server 6.0.2 configuration directory /QIBM/UserData/JazzTeamServer601/server.
- Enter this command to upgrade Jazz Team Server:
upgrade/jts/jts_upgrade.sh -oldJTSHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Change and Configuration Management application:
upgrade/ccm/ccm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Quality Management application:
upgrade/qm/qm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Requirements Management application:
upgrade/rm/rm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Rational Engineering Lifecycle Manager application:
upgrade/relm/relm_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Global Configuration Management application:
upgrade/gc/gc_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Report Builder application:
upgrade/rs/rs_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Lifecycle Query Engine application:
upgrade/lqe/lqe_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Link Index Provider application:
upgrade/ldx/ldx_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Enter this command to upgrade the Data Collection Component application:
upgrade/dcc/dcc_upgrade.sh -oldApplicationHome /QIBM/UserData/JazzTeamServer<old_version>/server/conf
- Review the index file locations. Adjust the locations and copy index files if you prefer.
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/JazzTeamServer602/server/conf. You can recursively copy these files to a new location and modify the teamserver.properites file. This is not required. - Run the next command to update the previous version WebSphere Application Server and deploy the .war files for the version 6.0.2 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.
- 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.
Note: If you installed option 20 (Liberty support), run the CFGJAZZSVR command to configure a Liberty server. Specify the same port previously configured for WebSphere Application Server. For more information, see Configuring the server on IBM i systems.
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:
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
- 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 JRE6 JDBC driver 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 JRE6 JDBC driver located in the directory. For more information, see Setting up an SQL Server database.
- Open a command prompt and enter the following commands:
cd \bin
startServer.bat server1
- Open a command shell and enter the following commands:
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.
- Open the JazzInstallDir6.0.2/server/was/config.py script in a text editor for editing.
- Go to the RoleMapping section of the script and replace default with your application name, such as jts, ccm, qm. Replace None with your user or repository group. When replacing None with the gropu mapping, ensure that the value is enclosed in quotation marks. See the following example for the JTS application:
- Save and close the file.
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'
}
},
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:
- 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:
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 JazzInstallDir6.0.2/server/was/clm_deploy.py nodeName server1 JazzInstallDir6.0.2/server/webapps -config JazzInstallDir6.0.2/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.
- On the server that hosts Jazz Team Server / Link Index Provider, open a command window and enter these commands:
- On the server that hosts the Change and Configuration Management application, open a command window and enter these commands:
- On the server that hosts the Quality Management application, open a command window and enter these commands:
- On the server that hosts the Requirements Management application, open a command window and enter these commands:
- On the server that hosts the Rational Engineering Lifecycle Manager application, open a command window and enter these commands:
- On the server that hosts the Data Collection Component application, open a command window and enter these commands:
- On the server that hosts the Report Builder application, open a command window and enter these commands:
- On the server that hosts the Lifecycle Query Engine application, open a command window and enter these commands:
- On the server that hosts the Rational Rhapsody Design Manager application, open a command window and enter these commands:
- On the server that hosts the Rational Software Architect Design Management application, open a command window and enter these commands:
- On the server that hosts the Global Configuration Management application, open a command window and enter these commands:
- To start the deployed applications, restart the application server. Replace server1 with the name of your application server:
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/server/webapps jts,clmhelp,ldx -config JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/server/webapps ccm -config JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/server/webapps qm -config JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/server/webapps dm,rdmhelp
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps dm,rdmhelp
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/server/webapps dm,rdmhelp,rsadm
cd /bin
./wsadmin.sh -lang jython -user WAS_USER -password WAS_PASSWORD -f nodeName server1 /server/was/clm_deploy_distributed.py /server/webapps dm,rdmhelp,rsadm
cd \bin
wsadmin.bat -lang jython -user WAS_USER -password WAS_PASSWORD -f JazzInstallDir6.0.2/server/was/clm_deploy_distributed.py nodeName server1 JazzInstallDir6.0.2/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
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 6.0.2 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
- 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 6.0.2_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.
- Open a browser and login to WebSphere Integrated Solutions Console at https://hostname.example.com:9043/ibm/console/logon.jsp.
- Click Applications > New Application > New Enterprise Application.
- 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
- relm.war
- qm.war
- rm.war
- converter.war
- dm.war
- rdmhelp.war
- rsadm.war
- dcc.war
- lqe.war
- ldx.war
- rs.war
- gc.war
- Select Fast Path, and then click Next.
- For the Lifecycle Query Engine module, expand Choose to generate default bindings and mappings, and then select the Generate Default Bindings check box.
- For the Link Index Provider module, expand Choose to generate default bindings and mappings, and then select the Generate Default Bindings check box.
- 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.
- 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.
- Click Next to accept all default options until you reach the Map context roots for web modules page.
- 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
- 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 /rdmhelp
- Data Collection Component to /dcc
- Report Builder to /rs
- Lifecycle Query Engine to /lqe
- Link Index Provider to /ldx
- Global Configuration to /gc
- Click Finish.
- 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 6.0.2 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 6.0.2 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, qm_war, and ccm_war applications must have the same authentication methods for their users and use the same security group mapping.
- In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
- For Jazz Team Server, click the jts_war application to open it for editing.
- For Change and Configuration Management, click the ccm_war application to open it for editing.
- For Quality Management, click the rqm_war application to open it for editing.
- In the Detail Properties section, click Security role to user/group mapping.
- 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.
- Enter a search string to return your users or group names. Click Search to run the query.
- From the list of available users or groups that is returned, select the particular user or group and move it to the Selected column.
- Click OK to map the users or groups to the Jazz repository groups.
- 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:
- Ensure that Jazz Team Server is shut down. This step must be completed while Jazz Team Server is off-line.
- Open a command windowshell and enter the following commands:
cd \server
repotools-jts.bat -unregisterApp appName=/vvc noPromptcd \server
repotools-jts.bat -unregisterApp appName=/vvc noPromptcd /server
./repotools-jts.sh -unregisterApp appName=/vvc noPromptcd /server
./repotools-jts.sh -unregisterApp appName=/vvc noPrompt
Configure the Report Builder application
- In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
- On the Enterprise Applications page, in the list of resources, click rs_war.
- On the Configuration page, in the References section, click Shared library references.
- Select the rs_war check box and click Reference shared libraries.
- In the Available list, select JRS Shared Library and click the right arrow.
- Click OK. Click OK again and then click Save.
- In the list of resources, click rs_war.
- On the Configuration page, under Detail Properties, click Class loading and update detection.
- 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
- In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
- Click lqe_war to open it and then click Manage Modules.
- Click lqe, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
- Click OK and save your changes.
- Go back to the lqe_war application and click Class loading and update detection.
- On the Class loader page, select Classes loaded with local class loader first (parent last).
- Click Apply and Save directly to the master configuration.
Configure the Link Index Provider application
- In WebSphere Integrated Solutions Console click Applications > Application Types > WebSphere enterprise applications.
- Click ldx_war to open it and then click Manage Modules.
- Click ldx, locate the Class loader order field and select Classes loaded with local class loader first (parent last).
- Click OK and save your changes.
- Go back to the ldx_war application and click Class loading and update detection.
- On the Class loader page, select Classes loaded with local class loader first (parent last).
- Click Apply and Save directly to the master configuration.
Start the 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
- 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
- qm_war
- rm_war
- dcc_war
- rs_war
- relm_war
- dm_war
- rdmhelp_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.
Start the servers
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
- 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
Before you begin: Ensure that you have a JDBC environment variable that points to the JRE6 JDBC driver 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 JRE6 JDBC driver located in the directory. For more information, see Setting up an SQL Server database.
Start all of the version 6.0.2 application servers:
Start the version 6.0.2 application server:
- Open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts Jazz Team Server/Link Index Provider, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Change and Configuration Management application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Quality Management application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Requirements Management application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Data Collection Component application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Global Configuration Management application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Report Builder application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Rational Engineering Lifecycle Manager application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Design Management application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat - On the computer that hosts the Lifecycle Query Engine application, open a command prompt and enter:
cd \server
server.startup.bat -tomcat
- Open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts Jazz Team Server/Link Index Provider, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Change and Configuration Management application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Quality Management application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Requirements Management application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Data Collection Components application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Global Configuration Management application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Report Builder application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Rational Engineering Lifecycle Manager application, open a command shell and enter:
cd /server
./server.startup -tomcat - On the computer that hosts the Design Management application, open a command shell and enter:
cd /server
./server.startup -tomcat - 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
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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:
- 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.
- Go to the /server/liberty/servers/clm\server\liberty\servers\clm directory and open server.xml file for editing.
- 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 6.0.2.
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
- Open a browser and login to https://host.example.com:9443/rs/setup.
- Click Import ready-to-use reports.
Migrating the Lifecycle Query Engine application
- 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.
- 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:
- 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:
- Open a command windowshell and enter the following commands:
cd \server
repotools-dm.bat -migration_dm_runUpgradeManager credentialsFile=credentials.txtcd \server
repotools-dm.bat -migration_dm_runUpgradeManager credentialsFile=credentials.txtcd /server
./repotools-dm.sh -migration_dm_runUpgradeManager credentialsFile=credentials.txtcd /server
./repotools-dm.sh -migration_dm_runUpgradeManager credentialsFile=credentials.txt
adminUserId=yourAdminUserId
adminPassword=yourAdminPassword
repositoryURL=https://hostname.example.com:9443/dm
smartCard=<none>
certificateFile=<none>
kerberos=<none>
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 6.0.2 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 indormation 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. For details on how to perform this task, see Archiving and restoring configurations.
Obtain licenses
You must obtain new licenses for version 6.0.2 applications if you are upgrading from any release of version 5. Version 6.0.2 applications do not work with version 5.0.x licenses. However, version 5.0.x applications work with version 6.0.2 licenses.
If you previously used floating, token, or authorized user single install licenses, install their version 6.0.2 counterparts. Your existing user license assignments will be kept during installation of version 6.0.2 licenses.
To update your token licenses:
- Log into https://hostname.example.com:9443/jts/admin and click Server > License Key Management.
- In the Floating License Server section, click Add and upload your version 6.0.2 license file.
- 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.
- 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 Establishing cross-server communication.
Configure data warehouse
If you did not configure the data warehouse in your previous installation and want to configure a data warehouse for version 6.0.2, follow these steps:
- Create a database to use as your data warehouse. For more information, see Setting up the database.
- 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 6.0.2 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
If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Requirements Management application. These steps are only required if you are planning to use Lifecycle Query Engine. Note that these steps might take some time to complete depending on the size of your repository.
- Do TRS 2.0 full rebase:
- Open a web browser and navigate to https://RM_Server:9443/rm/admin#action=com.ibm.rdm.fronting.server.web.trs.
- 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.
- 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.
- Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources.
- 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.
- Click Add Data Source, and in the wizard that opens select the TRS 2.0 for DNG Process Resources data source. Click Finsh.
- Repeat the previous step and add the TRS 2.0 for DNG Resources data source.
- Click TRS 2.0 for DNG Process Resources and TRS 2.0 for DNG Resources and then click Reindex and in the dialog that opens, click Reindex again.
- Click OK to confirm the reindex operation.
The URL for TRS 2.0 for DNG Process Resources is https://RM_Server:9443/rm/process-trs2 and the URL for TRS 2.0 for DNG Resources is https://RM_Server:9443/rm/trs2. After the data sources are added, Lifecycle Query Engine starts building the initial indices.
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. These steps are only required if you are planning to use Lifecycle Query Engine. Note that these steps might take some time to complete depending on the size of your repository.
- Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources.
- Under Data Source, click Change and Configuration Management.
- Click Reindex and in the dialog that opens, click Reindex again.
- Click OK to confirm the reindex operation.
Reindex Quality Management data sources
If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Quality Management application. These steps are only required if you are planning to use Lifecycle Query Engine. Note that these steps might take some time to complete depending on the size of your repository.
- Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources.
- If the TRS 1.0 for QM Resources exists, remove it. To remove the data source, select it and then click Remove.
- Click Add Data Source, and in the wizard that opens select the TRS 2.0 for QM Process Resources data source. Click Finsh.
- Repeat the previous step and add the TRS 2.0 for QM Resources data source.
- Under Data Source, click TRS 2.0 for QM Resources and TRS 2.0 for QM Process Resources.
- Click Reindex and in the dialog that opens, click Reindex again.
- Click OK to confirm the reindex operation.
Reindex Design Management data sources
If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Design Management application. These steps are only required if you are planning to use Lifecycle Query Engine. Note that these steps might take some time to complete depending on the size of your repository.
- Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources.
- If the TRS 1.0 for DM Resources exists, remove it. To remove the data source, select it and then click Remove.
- Click Add Data Source, and in the wizard that opens select the TRS 2.0 for DM Process Resources data source. Click Finsh.
- Repeat the previous step and add the TRS 2.0 for DM Resources data source.
- Under Data Source, click TRS 2.0 for DM Resources and TRS 2.0 for DM Process Resources.
- Click Reindex and in the dialog that opens, click Reindex again.
- Click OK to confirm the reindex operation.
Reindex Global Configuration Management data sources
If you are using Lifecycle Query Engine, complete the following steps after you upgrade your Global Configuration Management application. These steps are only required if you are planning to use Lifecycle Query Engine. Note that these steps might take some time to complete depending on the size of your repository.
- Open a web browser and navigate to https://LQE_Server:9443/lqe/web/admin/data-sources.
- Under Data Source, click TRS 2.0 for GC Resources and TRS 2.0 for GC Process Resources.
- Click Reindex and in the dialog that opens, click Reindex again.
- 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
- Stop the Jazz Authorization Server before performing the update.
- Make a backup copy of the entire Jazz Authorization Server installation directory and rename it to C:\JazzAuthorizationServer_OLD/opt/JazzAuthorizationServer_OLD.
- Ensure that you have a discoverable repository location set in the Installation Manager Preferences window.
- In Installation Manager go to File > Preferences and click Add Repository.
- Browse for a local .zip file or online link that contains the Jazz Authorization Server offerings repository.config file.
- Click Test Connections to ensure you can connect to the repository location.
- Click Apply and then OK to close the Preferences window.
Procedure
- In IBM Installation Manager click Update.
- Select the Jazz Authorization Server package and click Next on all panels until you reach the Summary page.
- Review the summary information and click Update to start the upgrade process.
- 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.
- 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.
Verify the upgrade
After the upgrade process is complete, use this checklist to determine whether each step was successful.
| Verification task | More information | |
|---|---|---|
|
Verify that these application configuration files are copied from previous installation to version 6.0.2:
Verify that the application configuration files are copied from previous configuration directory to version 6.0.2:
|
|
|
Verify that each teamserver.properties file contains this information:
|
|
|
Verify the application servers:
|
Deploying and starting the server |
|
Check the server log files: Check these server log files to verify that they contain the post-upgrade information:
|
|
|
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. | Create server-side certificates for Collaborative Lifecycle Management |
|
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. | Application administrative web interface |
|
Run diagnostics on each server and verify that the diagnostics completed successfully:
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. |
|
|
Check users, licenses, and link artifacts:
|
Verifying users, licenses, and link artifacts |
|
Check application artifacts:
|
Integrating with other products
Rational Developer for System z
Rational Developer for System z integrates with Rational Team Concert on System z to provide z/OS developers an integrated collaborative application development environment. This integrated solution provides the value of the individual development environment of Rational Developer for System z with the team collaboration capabilities of Rational Team Concert. For more information, see Rational Team Concert and Rational Developer for System z.
For instructions on upgrading Rational Developer for System z, see Upgrading the Rational Developer for System z integration.
Rational ClearQuest
Rational Team Concert includes several tools to help you integrate your work with Rational ClearQuest. Rational ClearQuest Synchronizer, Rational ClearQuest Bridge, and Rational ClearQuest Importer. For more information, see Rational Team Concert and Rational ClearQuest.
You can integrate Rational Quality Manager with the Rational ClearQuest defect tracking system using the ClearQuest Synchronizer (previously called the Connector). For more information, see Rational Quality Manager and Rational ClearQuest.
You can integrate the Requirements management application with Rational ClearQuest and configure the applications to associate requirements with defects, tasks, requests for enhancements, and other record types. For more information, see Integrating the Requirements Management application and Rational ClearQuest.
For instructions on upgrading ClearQuest Synchronizer, see Upgrading ClearQuest Synchronizer.
Rational ClearCase
Rational Team Concert includes ClearCase connectors that support operations between Rational Team Concert and Rational ClearCase. For more information, see Rational Team Concert and Rational ClearCase.
Rational Build Forge
The integration between Rational Team Concert and Rational Build Forge allows to create Rational Build Forge build engines and definitions to integrate with your Build Forge projects. For more information, see Rational Team Concert and Rational Build Forge.
Hudson/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 Power Systems Software
Rational Team Concert integrates with Rational Developer for Power Systems Software to provide IBM i developers an integrated collaborative application development environment. This integrated solution provides the value of the team collaboration capabilities of Rational Team Concert with the individual development environment of Rational Developer for Power Systems Software. For more information, see Rational Team Concert and Rational Developer for Power Systems Software.
Rational 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.