You can migrate comments and links to the latest version
of Design
Management. This tutorial provides steps to migrate data from version
3 releases of Design
Management to the latest version of Design
Management. This lesson shows how to install a basic migration feature
into an existing version 3 Design Management Server. The feature extracts the data that is required to migrate
the comments and links, and saves the data in a file that the latest
version of Design
Management requires for the migration process.
These prerequisites must be met before you can migrate comments
and links from version 3 releases of
Design
Management:
- The source application must be Design
Management version 3.0, 3.01, or 3.0.1.1
- Design
Management 4.0.1 or later or later must be installed on the same
computer as the version 3 release of Design
Management, and it must be configured to use the same host name and
port numbers. The version 4 Design
Management installation must not be set up before starting the migration
process.
- You must have administrator privileges to perform the migration.
- You must perform the migration process before any server rename
operation, including the renaming of any applications in the Rational® solution for
Collaborative Lifecycle Management (CLM), such as the Change and Configuration Management
(CCM), Quality Management (QM), or Requirements Management (RM) applications.
Important: - User information is not migrated from the version 3 release of Design
Management. The migration process attempts to create that user with
minimal attributes such as the user name, user ID, and mailbox. The
user is assigned the Contributor license, which you can modify after
migration.
- Project area information is not migrated from the version 3 release
of Design
Management. Before you perform the migration, record the project
areas, users, and project members for which you want to migrate comments
and links. During the migration process, you re-create these project
areas in the later version of Design
Management.
- The source model import information, such as Rational Software Architect import definitions,
are not migrated. For each project that you migrate, record the source
folders of the models that were published in Design
Management, and any additional import data such as library paths.
During the migration process, you re-create the import definitions
with the same source folders.
- On the computer that contains the version 3 release of Design
Management, extract the compressed file for the migration update
site named DM3.x_BasicMigrationUpdateSite.zip into
the /server/conf/dm directory. This process creates
the file named basic-migration-profile.ini in the
provision profiles directory and adds the basic-migration-update-site folder to the sites directory.
- In a browser, log on to the version 3 Design Management Server.
- In a separate browser window, enter the following URL: https://<hostname>:<port>/dm/provision.
- In the same browser window, enter the following URL: https://<hostname>:<port>/dm/basicMigration.
- The server starts the migration process and when it is
complete, the browser prompts you to save the dm3-migration.zip file. Save this output file on the server computer.
- Stop the version 3 Design Management Server.