Opening models from a different language version

IBM® Rational® Rhapsody® allows you to open models created in a different language version of the product. This capability is also referred to as migration of projects.

When you try to open a project that was created in a different language version of Rational Rhapsody, you are notified that the project will be converted to the language of the current version, and you are asked whether you would like to continue with the conversion of the project.

Note: When you migrate a project, you do not lose any language-specific features of model elements that are not supported in the language version of Rational Rhapsody that you are running. These language-specific characteristics will not be displayed, for example, in the Features window, and any code generation will be in the language of the current version not the version with which the model was originally created. However, the product maintains this information. If, at a later stage, you reopen the model in the original language, you will once again see these language-specific characteristics.

When a project is migrated, bodies of operations and any other code entered manually in Rational Rhapsody are not converted to the target language. If you already have such code in your model before the migration, make sure to convert the code in order to avoid compilation errors.

If you use Add by reference to add a unit whose language differs from that of the version of Rational Rhapsody you are running, a non-persistent conversion is performed (since these elements are read-only). This non-persistent conversion will be performed each time you open the model.

Note: If you have a license for multiple-language projects, no conversion is performed when you open a model from another language version of Rational Rhapsody. If you would like to convert an entire project, change the unit language at the project level. For details, see Determining the language of a unit in multiple-language projects.

Feedback