Rational® DOORS® version 9.4 and later supports
integration with Rational Quality
Manager based on Open Services for Lifecycle Collaboration (OSLC). Rational DOORS version 9.4 and later includes a migration
utility that ensures that data from a previous version of the integration
is available and compatible with the current version.
Before you begin
You must have administrator privileges
in Rational DOORS to perform this task.
You must
complete the following tasks before migrating integration data:
- Back up your previous Rational DOORS and Rational Quality Manager data.
- Install the Rational DOORS client version 9.4 or later.
An upgrade of the Rational DOORS Database Server is not required
to perform the migration. You can perform the migration in a Rational DOORS client that is located on the Rational DOORS database server machine or on a different
machine.
- Configure the Rational Quality
Manager databases that contain the project areas that were used for
export in the older version of the integration as friendly OSLC QM
V2 repositories in Rational DOORS. See Configure Rational Quality
Manager as an OSLC consumer of Rational DOORS.
- Configure all project areas that were used for export in the older
version of the integration as Service Provider in Rational DOORS.
See Configure Rational DOORS as an OSLC consumer of Rational Quality Manager.
- Confirm that there is data that is ready for migration. Look in
the conf directory on the Rational DOORS database
server. Every export that was performed using the previous integration
created a status file. If any status files are present, then there
is data that is available for migration.
- Notify users or restrict access to the Rational DOORS database
to prevent any use of the database during the migration.
About this task
The migration produces the following results:
- This utility migrates all views and corresponding modules in the Rational DOORS database that were previously integrated
with Rational Quality Manager.
- No new Rational DOORS resources are created, including
no new views and no new requirements.
- Certain Rational Quality
Manager resources are removed:
- All requirements previously exported (copied) to Rational Quality Manager.
- All associations between the copied requirements and related test
cases.
- OSLC traceability is created.
- Rational DOORS views are linked to Rational Quality Manager test plans.
- Rational DOORS requirements are linked to Rational Quality Manager test cases.
- Links are created from the test plans and test cases to the Rational DOORS resources.
- No new Rational Quality
Manager resources are created.
- No new test plans or test cases.
- All associations between requirements that were previously copied
into Rational Quality Manager
and related test plans are removed.
- All associations between these copied requirements and related
test cases are removed.
- The requirements are not permanently deleted from Rational Quality Manager. Users can delete
the requirements permanently using capabilities provided by Rational Quality Manager.
The migration only considers data created using previous
versions of Rational DOORS integration with Rational Quality Manager, and
not other Rational DOORS functionality, such as the
Test Tracking Toolkit.
Procedure
- Log in to Rational DOORS version 9.4 or later as
an administrator.
- In the main Rational DOORS window, click . If this menu command is not present, be sure that you have met
the conditions that are outlined in Before you begin, above. When
you select the Migrate command, a window opens that lists the exports
that were performed in the previous version of the integration. The
following information is listed for each export:
- The name of the Rational DOORS module and the view that
was exported.
- The name of the corresponding Rational Quality
Manager project and the test plan associated with the export.
- The data and time the export was last successfully performed.
- The host name and port number of the Rational Quality Manager host.
- The migration status.
- Click Migrate to begin the migration.
Note: Depending on the size of your data, migration might take
some time to complete.
After the migration
is complete, the migration status of each view is displayed.