Rational Quality Manager 2.0 to 3.0.1 upgrade process example

The diagram displays the main steps necessary to upgrade Rational® Quality Manager 2.0 to 3.0.1.

Rational Quality Manager 2.0 to 3.0.1 upgrade process example

Planning your upgrade and deployment topology, along with your making sure your existing environment meets the relevant software and hardware requirements is a critical part of a successful upgrade. With your plan in place, you begin the process by downloading CLM to a target location.

At this time, you should stop your existing QM version 2 server and then as a precaution, back up your existing Rational Quality Manager version 2 environment, and then export your data from Rational Quality Manager version 2.

At this point, you need to determine whether you plan to upgrade this application such that it shares an existing JTS v3.0.1 (JTS v3.0.1 already in place), or whether you need to install and configure a new JTS v3.0.1.

If you need to install a new JTS v3.0.1, you will install JTS v3.0.1 and QM v3.0.1 to the appropriate locations based on your intended deployment topology. In this example, we placed the JTS on “machine A”, created a JTS v3.0.1 database (most likely on a database server), and installed the QM application on “machine B”.

If there is an existing JTS v3.0.1 that you plan to connect this upgraded application to, then instead of installing a new JTS v3.0.1, you will install QM in the appropriate location (again, based on your intended deployment topology).

The next set of tasks in the upgrade process leverages a set of automated commands for updating QM configuration files, QM database connections, and importing QM repository data. These commands can be run using a wrapper script, or, they can be run individually. It is a good idea to verify the output of the relevant log files.

When this set of update tasks is completed, you will need to stop all v3.0.1 servers in this environment (JTS and any CLM applications). You should then back up the QM v3.0.1 and JTS v3.0.1 databases and environment.

The next set of tasks in the upgrade process also leverages automated scripts which can be run using a wrapper script, or they can be run individually. These will transfer user and license data, and then update QM repository data. When these are complete, you should review the relevant log files to verify the results, and then again backup the QM v3.0.1 and JTS v3.0.1 DBs and environment.

At this point, you will start the JTS v 3.0.1 and QM v3.0.1 servers (as well as any other CLM application servers that are part of this deployment).

If you installed a new JTS v3.0.1, you will run the JTS Setup wizard, which will connect your new JTS v3.0.1 with the QM v3.0.1, and associated databases.

If you are sharing an existing JTS (JTS v3.0.1 already in place) you will go to the Admin web UI, and connect your upgraded QM v.3.0.1 and associated databases to the existing JTS v3.0.1.

At this point, you should go to the dashboard UI and upgrade your existing dashboards. You can then verify your upgrade by navigating through the UI to examine your artifacts.

Table 1. Key for abbreviations
Abbreviations Name
CLM Rational solution for Collaborative Lifecycle Management
DB Database Management System
HW Hardware
JTS Jazz™ Team Server
QM Quality Management
RQM Rational Quality Manager
SW Software
URI Uniform Resource Identifier (web address)
Note: Latest entries in the jazz.net library on upgrading Rational Quality Manager

Feedback