Rational Requirements Composer 2.0 to 3.0.1 upgrade process example

The diagram displays the main steps necessary to upgrade Rational® Requirements Composer 2.0 to 3.0.1.

Rational Requirements Composer 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 Rational Requirements Composer v2 server and then as a precaution, back up your existing Rational Requirements Composer v2 environment, and then export your data from Rational Requirements Composer v2.

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 RM 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 RM 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 stop the existing JTS v3.0.1, backup the existing environment, and then install RM in the appropriate location (again, based on your intended deployment topology).

The next set of tasks in the upgrade process leverage a set of automated commands for updating RM configuration files, RM database connections, and importing RM repository data. These commands can be run using a wrapper script, or, they can be run individually. After these commands complete, it is a good idea to verify the output of the relevant log files. You should then back up the RM v3.0.1 and JTS v3.0.1 databases and environment.

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

Next, you will go to the RM web UI and visit the online migration wizard. After completing that wizard, you should go to the dashboard UI and upgrade your existing dashboards.

The next task is to fix inbound project area links.

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 RM v3.0.1.

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
RRC Rational Requirements Composer
RM Requirements Management
SW Software
URI Uniform Resource Identifier (web address)
Note: Latest entries in the jazz.net library on upgrading Rational Requirements Composer

Feedback