This section provides details about upgrading to the most
recent release of IBM® Rational® Requirements Composer.
Upgrading Rational Requirements Composer is
a two-step process. The first step is an offline upgrade, which imports
data into the Jazz™ Team Server.
The second step is an online upgrade, which enables the Requirements
Management (RM) application to migrate its resources to the new format
because the application uses the Jazz Team Server for data storage.
Important: Review the following information before starting
the upgrade process.
- You can follow the upgrade instructions by using the upgrade script
if you are using a single-server deployment or if you are using a
distributed deployment, and you can mount a drive from Requirements
Management to the Jazz Team Server.
- You can follow the manual upgrade instructions if you are using
a distributed network deployment and you are not allowed to mount
the drive or if you are an advanced administrator and you plan to
complete the steps manually. The manual steps detail what the scripts
are performing.
- Before you upgrade a production system, always test the upgrade
first in a test environment. If this is a test upgrade, remember to
set the version 2 configuration files to point to the database clone
and not the production database. Rational Requirements Composer uses
the Jazz Team
Server database for data storage. For information about setting up
a staged test environment, see Staging a test environment for the upgrade process.
- For a small-scale deployment or for evaluation purposes, you can
install the Jazz Team Server and
the Requirements Management (RM), Configuration Management (CCM),
and Quality Management (QM) applications together on a single application
server.
- For larger deployments, you can distribute the Jazz Team Server and
other applications on multiple application servers. For more information
about deployment options, see Deployment topology considerations
- Be sure to review the release notes on Jazz.net https://jazz.net/downloads/rational-requirements-composer/releases/3.0.1?p=releasenotes for the latest known technical issues.
Migrating
Rational Requirements Composer from
version 2 to version 3.0.1 supports two migration flows, based on
the original version 2 deployment and the intended version 3.0.1 deployment:
The following table lists the acronyms that might be used in upgrading
instructions.
Table 1. Key for abbreviations| Acronym |
Name |
| JTS |
Jazz Team
Server |
| RM |
Requirements Management application |
| CCM |
Change and Configuration Management application |
| QM |
Quality Management application |
| RRC |
Rational Requirements Composer |
The upgrade process consists of these phases:
- Installing Rational Requirements Composer version
3.0.1
- The Rational Requirements Composer 3.0.1
installation does not overwrite the version 2 installation. Instead,
the two products coexist. Version 2 can be uninstalled later time
if required.
- Use IBM Installation Manager to ensure the RM version 2 context
roots (such as /rdm) are preserved and to enable the installation
of the Jazz Team Server or
other version 3.0.1 applications.
- Exporting data from the Rational Requirements Composer version
2 server and backing up the Jazz Team Server version
2 database.
- Creating a separate database for the Jazz Team Server version
3, if it is a new Jazz Team Server.
- Completing an offline migration to update the configuration files
(using the upgrade script or manually) and importing the Rational Requirements Composer version
2 data.
- Completing an online migration to update the RM application data.
- Verifying that the upgrade was completed.