Other changes in version 7.5.3

The following miscellaneous changes were made in version 7.5.3 of Rational® Rhapsody®.

Unit name conflicts

Prior to version 7.5.3, if you tried creating a unit with the same name as an existing unit, Rational Rhapsody would view this as a naming conflict even if the two units were in different directories. As a result, it would give the new unit a different name, for example filename_1.txt. This behavior was fixed in version 7.5.3. Now, you can create units with the same name in different directories, and Rational Rhapsody will not consider this a naming conflict.

Working with the Android profile

While the previous version of IBM® Rational Rhapsody supported development with version 2.1 of the Android SDK, the current version supports only version 2.2 of the Android SDK.

If you have models that use version 2.1 of the Android SDK and you want to use these models with version 7.5.3 of Rational Rhapsody, you must copy the directory that contains the Android21 profile from your previous Rational Rhapsody installation to your new installation location. The profile can be found under [installation directory]\Share\Profiles\Android. Copy the entire Android21 directory.

If you have models that use version 2.1 of the Android SDK and you would like to migrate these models to use version 2.2 of the Android SDK, follow these steps:

  1. Open the existing model.

  2. Select the Android21 profile in the browser and select Delete from Model from the pop-up menu.

  3. Add the Android22 profile to your model (File > Add to Model). The file to add is [installation directory]\Share\Profiles\Android\Android22\Android22.sbs. In the Add to Model window, select the Add Dependents and As Reference options.

Generating reports with Rational Publishing Engine (RPE)

In the REST schema for Rational Rhapsody 7.5.3, the Queries container (under Projects and Packages) was renamed to PredefinedQueries. If you have an existing RPE template that you want to upgrade to the 7.5.3 schema, you must perform the following steps if the template has references to the Queries container.

  1. Delete all references to Queries in the RPE template.
  2. Replace the schema.
  3. Recreate the deleted references in the template using PredefinedQueries instead.

For example, let's assume you have an RPE template that has a container for Projects.Project.Queries.AllClasses.Class with two text elements within the context, Projects.Project.Queries.AllClasses.Class.metaclass and Projects.Project.Queries.AllClasses.Class.fullPathName. Before upgrading the schema, you would have to remove all references to Projects.Project.Queries. This can be done in RPE Document Studio by selecting Data > Clear from the container's pop-up menu. This clears the container but preserves the report structure. After replacing the schema, the container's data context should be set to Projects.Project.PredefinedQueries.AllClasses.Class, and the text elements' values should be set to Projects.Project.PredefinedQueries.AllClasses.Class.metadata and Projects.Project.PredefinedQueries.AllClasses.Class.fullPathName.

Changes to Rational Rhapsody profiles also have implications for existing RPE templates. In the AUTOSAR_31 and AUTOSAR_40 profiles, two new terms were deleted: CanClusterAndChannel and LinClusterAndChannel. If you have RPE templates that refer to these elements, delete all such references before replacing the schema.


Feedback