Migrating data to Rational DOORS Next Generation

You can use a migration package to move data to IBM® Rational® DOORS® Next Generation.

Before you begin

To migrate data, you must upgrade the IBM Rational DOORS client where you do these migration tasks to version 9.6.1.3 or later.

About this task

Rational DOORS Next Generation provides a web browser-based alternative to the thick client installation and maintenance that is associated with Rational DOORS. As part of the IBM Rational solution for Collaborative Lifecycle Management (CLM), Rational DOORS Next Generation provides a rich, highly collaborative environment for integration, common administration, traceability, and reporting. For more information, see Overview of Rational DOORS Next Generation. To take advantage of these capabilities, your team might choose to migrate some existing Rational DOORS modules to Rational DOORS Next Generation. You can migrate data selectively and incrementally over an extended period as you identify project content that can benefit from the capabilities in Rational DOORS Next Generation.

You can migrate modules from Rational DOORS to Rational DOORS Next Generation. This one-way migration moves requirements management into the CLM environment. Historical data is not migrated; however, the migration creates links in Rational DOORS Next Generation that link back to the corresponding records in Rational DOORS. The links provides access to history, baselines, and other non-migrated data. By migrating only current data, you preserve all history and audit information in Rational DOORS and eliminate the cost of migrating and revalidating audits and historical data in Rational DOORS Next Generation.

This migration capability has these characteristics:
  • One-way. The data is permanently moved to Rational DOORS Next Generation and is not intended to be exchanged or updated.
  • Non-destructive. The default solution does not require data modification or deletion.
  • Incremental. You can include one or more modules in a migration package with minimal disruption to an entire project.
  • Simple. Migration is series of export and import operations with minimal manual steps.
  • Optimized. The migration automatically harmonizes your module type systems and creates corresponding artifact types in Rational DOORS Next Generation.
  • Safe. After you export a migration package, the corresponding data is locked in Rational DOORS to prevent further editing.
  • Complete. All of your important Rational DOORS data is considered, including folders, modules, objects, views, and links.
In addition to the requirements content, the migration includes the following data:
  • Project structure
  • Attributes and types
  • Attribute DXL and Layout DXL content as calculated values
  • Views
  • Tables as XHTML renderings
  • Internal links
  • Outbound OSLC links
  • External links to web URLs
  • OLE objects
  • Pictures
  • Text styling, such as bold, italic, and underline

One or more modules can be included in a migration package. Only the current version of modules is migrated. Because the migration of project data can be incremental, do not assume that you need to migrate everything. Migrate only data that is relevant in the context of your business needs and Rational DOORS Next Generation. By focusing on necessary data only, you can reduce effort, disruption, and cost. This approach also prevents the proliferation of irrelevant data in Rational DOORS Next Generation.

Treat migrated data as read-only during the migration process. Maintain the locks on migrated data in Rational DOORS after a package is exported to avoid conflicting changes in both tools. Unlock only data if the migration process is abandoned.