This tutorial shows how to migrate data from version 3
releases of Design
Management to Design
Management 4.0.1 or later. When you import a Rational® Software Architect model into Design
Management 4.0.1 or later, the migration process re-creates Design
Management comments and links from version 3 releases in version
4.0.1 or later. However, the migration process does not convert Design
Management version 3 databases into Design
Management 4.0.1 or later databases.
With Design
Management, you can upload resources, such as models, to a Design Management Server to enable collaborative discussions of model designs.
Design collaboration involves users creating comments on resources
and creating links between resources. You can also create traceable
links between Design
Management resources and resources in the applications in the Rational solution for Collaborative
Lifecycle Management (CLM), such as the Change and Configuration Management
(CCM), Requirements Management (RM), and Quality Management (QM) applications.
Limitations
The migration of version 3 releases
of
Design
Management to later versions includes the following limitations and
known issues:
- When the Design Management 4.0.1 or later server is set up, the
model resource numbers that were used in version 3 releases of Design
Management are reserved. New Design
Management 4.0.1 or later resources are created beyond the reserved
range of numbers, but imported Design
Management version 3 resources maintain their model number.
- When you migrate a version 3 Design
Management project, the Design
Management 4.0.1 or later project must have the exact same name as
the corresponding version 3 project. The Design
Management administrator must manually create the Design
Management 4.0.1 or later project area and associate the users and
their roles. You can assign users to a project area after the migration.
- The import definitions for a version 3 Design
Management project are not migrated. To perform the import process,
the import definitions must be re-created in the Design
Management 4.0.1 or later project. You must use the same source model
folders that were used to publish the models in the Design
Management version 3 release. If the source folder name and model
file names are not the same, the imported models are assigned new
model numbers that are outside the reserved range for the Design
Management version 3 model. The corresponding comments and links
are created because the target Design
Management version 3 resources do not exist.
- Only comments from version 3 releases of Design
Management are re-created in Design
Management 4.0.1 or later with the same user and modification date. Design
Management version 3 links are created with the owner as the Design
Management administrator.
- Before you migrate any project areas, you should create the Design
Management version 3 users in Design
Management 4.0.1 or later with the same identifier. If a Design
Management version 3 user who made a comment is not created in Design
Management 4.0.1 or later, the migration process attempts to create
that user account with default attributes. The user name, ID, and
mailbox attributes from Design
Management version 3 are used, but only the Contributor license is
assigned and the default password is the same as the user ID. If the
migration process could not create the user account, the corresponding
comments are attributed to the Design Management administrator who
performs the import process.
- In version 3 releases of Design
Management, you could create links between resources in different
projects as long as the source project had an association defined
to the target project. To create the same type of link in Design
Management 4.0.1 or later, the source project must have a dependency
on a snapshot configuration in the target project. However, if a Design
Management cross-project link is created during migration, clicking
on that link should open the appropriate resource editor in the target Design
Management project, but the default workspace configuration is used.
- Custom link types from version 3 releases of Design
Management are not created in Design
Management 4.0.1 or later. You must create them manually.