Migrating ETM integration data

IBM® Engineering Requirements Management DOORS® (DOORS) version 9.4 and later supports integration with IBM Engineering Test Management (ETM) based on Open Services for Lifecycle Collaboration (OSLC). 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 DOORS to perform this task.

You must complete the following tasks before migrating integration data:
  • Back up your previous DOORS and ETM data.
  • Install the DOORS client version 9.4 or later. An upgrade of the DOORS Database Server is not required to perform the migration. You can perform the migration in a DOORS client that is located on the DOORS database server machine or on a different machine.
  • Configure the ETM 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 DOORS. See Configuring the ETM server.
  • Configure all project areas that were used for export in the older version of the integration as Service Provider in DOORS. See Configuring the DOORS server.
  • Confirm that there is data that is ready for migration. Look in the conf directory on the 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 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 DOORS database that were previously integrated with ETM.
  • No new DOORS resources are created, including no new views and no new requirements.
  • Certain ETM resources are removed:
    • All requirements previously exported (copied) to ETM.
    • All associations between the copied requirements and related test cases.
  • OSLC traceability is created.
    • DOORS views are linked to ETM test plans.
    • DOORS requirements are linked to ETM test cases.
    • Links are created from the test plans and test cases to the DOORS resources.
  • No new ETM resources are created.
    • No new test plans or test cases.
    • All associations between requirements that were previously copied into ETM 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 ETM. Users can delete the requirements permanently using capabilities provided by ETM.

The migration only considers data created using previous versions of DOORS integration with ETM, and not other DOORS functionality, such as the Test Tracking Toolkit.

Procedure

  1. Log in to DOORS version 9.4 or later as an administrator.
  2. In the main DOORS window, click RQMI > Migrate. 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 DOORS module and the view that was exported.
    • The name of the corresponding ETM 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 ETM host.
    • The migration status.
  3. 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.


Feedback