This topic describes the required steps for migrating work-item-based
requirements from earlier versions of IBM® Rational® Quality Manager.
Prior to Rational Quality Manager version
3.0.1, requirements were managed locally within Rational Quality Manager or
in an external requirements provider, such as IBM Rational RequisitePro®, IBM Rational DOORS®,
or IBM Rational Requirements Composer.
In version 3.0.1, requirements are no longer managed locally. If you
are upgrading from version 2, you must deliberately migrate your local,
work-item-based requirements to the Requirements Management application
that you can install with version 3.0.1.
Before you begin
To migrate work-item-based requirements, the user who migrates
the requirements must meet the following prerequisites:
- The user must have a valid Quality Professional license. This
license grants the user read and write permission to the Quality Management
and Requirements Management project areas.
- If the work item requirement type has been modified with custom
attributes, the user must also have a valid Analyst license for Requirements
Management. Only string-type custom attributes can be migrated. To
enable the ability to migrate user-defined string-type custom attributes,
the user must complete these steps:
- Set Enable custom attributes creation to true in
Quality Management Advanced Properties.
- Verify that he or she is a member of the Requirements Management
project area with a role that has permission to save and modify artifact
types and attributes.
- The user must have JazzAdmins repository group permissions.
- The user must be assigned to a role that has permission to create,
update, and delete requirements in the Requirements Management project
area.
- The user must be assigned to a role that has permission to modify
work items in the Quality Management project area.
- If the user plans to migrate comments in work-item-based requirement,
the user must be assigned to a role that has permission to create,
update, and delete comments in the Requirements Management project
area.
- All user IDs in the Requirements Management application must match
the user IDs in the Quality Management application. This prerequisite
is established because requirements in Rational Quality Manager version
2 have an owner field and an originator field, and those fields store
the user ID. When you migrate those requirements, the Requirements
Management application must be able to recognize that user ID. By
default, this ID matching is handled by the Jazz™ Team Server,
which provides a single user database that is shared by the server
and all the applications registered with the server.
Each Quality Management project area that you want to migrate
requirements from must have a "uses and requirements" association
to a Requirements Management project area. Multiple Quality Management
project areas can be associated with a single Requirements Management
project area.
In addition, the integration between the Quality
Management application and the Requirements Management application
requires two artifact types that are defined in Requirements Management
application: the Requirement type and the Test
Plan Collection type. The migration process makes modifications
to these types. Any manual updates to these types might cause the
migration process and the subsequent integration to fail. For details
about working with artifact types, see Artifact type.
About this task
The following table lists what is supported and not supported
in the migration.
Table 1. | Supported in the version 3 migration |
Not supported in the version 3 migration |
| Attributes that are defined in the Rational Quality Manager version
2 Requirement Type |
Links and attachments |
| String-type custom attributes |
Custom attributes other than string type |
| Comments |
Review (approver, reviewer, and so on) |
| Relationship between a test case and a requirement |
Subscribers |
| Relationship between a test plan and a requirement
(See Note.) |
History |
Note: The migrated requirement becomes part of a test plan
collection in the Requirements Management application. The test plan
collection is linked to a test plan. You create the test plan collection
and the test plan in this procedure.
Procedure
- Install version 3, and migrate your version 2 data as described
in Upgrading Rational Quality Manager to 3.0.1 using the upgrade script.
- Run the Jazz Team Server setup
wizard and register the applications. For details, see Configuring the Jazz Team Server and the first application after the upgrade.
- If necessary, create a requirements project from the Requirements
Management client, using the Base project template, as described in Creating requirements projects.
- Link your Quality Management project area to the Requirements
Management project area.
To set up links between the
project areas:
- Set up a friends relationship between the two project
areas. For details, see Establishing
friends relationships.
- Add an association between the two project areas. See Creating project areas.
- Set the Requirements Management application to import mode
by setting the following property to true in
the <JazzInstallDir>/server/conf/rm/fronting.properties file:
com.ibm.rdm.fronting.server.import.mode=true
After
performing this step, restart the Requirements Management server.
- With both the Quality Management and Requirements Management
applications running, run the repotools-jazz -refactorRequirements command
to migrate the requirements.
Important: Open
separate command-line windows to run the version 2 and version 3 repotools commands.
Separate command-line windows ensure that there are no conflicts between
the environment variables used by the version 2 and version 3 commands.
This
command works on a single Quality Management-Requirements Management
project area pair at a time.
The -refactorRequirements command
has many required arguments. A sample command follows:
repotools-jazz -refactorRequirements adminUserId=admin adminPassword=admin_password projectArea=qm_project_name rmProvider=rm_project_name rmUserId=rm_admin rmPassword=rm_admin_password
For
detailed command syntax, see -refactorRequirements.
- After the migration is complete, restart the Requirements
Management server, reverse step 5, and turn off import mode by setting
the following property to false in the <JazzInstallDir>/server/conf/rm/fronting.properties file:
com.ibm.rdm.fronting.server.import.mode=false