Migration from Rational Rhapsody Design Manager to Rhapsody Model Manager

IBM® Engineering Systems Design Rhapsody® provides a wizard for importing Rational® Rhapsody Design Manager models into Rhapsody Model Manager. This process consists of the following steps: 1) construction of a new Rhapsody model from the data that was extracted from the Rational Rhapsody Design Manager model 2) enabling of Rhapsody Model Manager for the new model 3) migration of the imported OSLC links to Rhapsody Model Manager.
Note: This feature is available only if you selected the Rational Rhapsody Design Manager migration option (below Rhapsody Model Manager) during the installation of Rhapsody.

To start the import wizard, select File > Import from Design Manager from the main menu.

Import from Design Manager - first screen

Take the following points into account when importing models from Rational Rhapsody Design Manager:

Migration of OSLC links

Note: Before migrating OSLC links:

When you migrate a project's OSLC links, you are presented with a list of the different types of links that are to be migrated.

OSLC link migration screen
  • For each group of links, there is an indication of whether there are problems that prevent the migration of the links.
  • For each group of links, you can change the type of link to create. In some cases, this will eliminate the problem that was found and you can proceed with the migration.
  • For each group of links, you call also set the action to take: migrate, skip (but leave in model for possible future migration), or discard (remove permanently from model).
  • When you press the Migrate button, the progress of the migration is displayed. When the process has finished, the pane at the bottom of the window displays result messages, and the icon for each group of links changes to reflect the result of the migration.
  • If errors occur during migration of the links, you can fix the underlying cause and then run the migration again.

When link migration is finished, a migration summary table is generated in .html format and stored alongside the .rpyx file for the model. The table contains detailed information for each of the links that was processed.