When you work in Rational ClearCase® and you compare or merge versions of a model, the ClearCase Type Manager opens Rational Application Developer to complete the model comparison or merge. However, the Compare Editor or Merge Editor might not have focus in the product. To compare or merge the model, click the Compare Editor or the Merge Editor.
On Windows operating systems, where the standard directory hierarchy is translated (for example, French and German versions of Windows), ClearCase cannot automatically open Rational Application Developer.
To work around this issue, copy the non-translated Rational directory, located in C:\Documents and Settings\<username>\Application Data\, (where Application Data is non-translated) and paste it into your translated Application Data directory, located in C:\Documents and Settings\<username>\.
Note that you must copy and not move the non-translated Rational directory. Also note that you must repeat this task any time that you do one of the following things:
- Install the product to a different location
- Update your plug-ins
- Change your auto launch path
When you compare or merge binary files, the state of the files in the configuration management system might not be reflected. To determine which binary files you should carry forward, use the version numbers in the file headers. You can examine the file headers using the ClearCase Version Tree Browser, or an equivalent tool for a Concurrent Version System (CVS).
When a model comparison or merge cannot find a custom profile (.epx file), a window opens that lists the resource path that is used to find the custom profile. The path can have four forms, and each form requries a different workaround.
Relative form - <file name>.epx
In this case, the model comparison or merge is looking for the .epx file in the same directory as the .emx file. To work around this issue using a Concurrent Version System (CVS), base ClearCase, or a view on a shared Unified Change Management (UCM) stream, you must update the view and refresh the custom profile. To work around this issue using a view on a private UCM stream, you must obtain the .epx file and copy it into your workspace.
Platform-relative form - platform:/<resource>/<projectname>/<file name>.epx
In this case, the workspace that started the model comparison or merge must contain the project that contains the .epx file. To work around this issue using CVS, base ClearCase, or a view on a shared UCM stream, you must update the view and refresh or import the project that contains the custom profile. To work around this issue using a view on a private UCM stream, you must obtain the .epx file or project and copy it into your workspace.
Path reference form - file://c:/<file path>/<file name>.epx
In this case, the resource path points to a specific directory for the .epx file. To work around this issue, ensure that the custom profile is located in the specified directory.
Pathmap form - pathmap://MAPVAR/<file name>.epx
In this case, the pathmap variable MAPVAR must point to the directory that contains the .epx file. To set the MAPVAR variable, complete the following steps:
- Click Windows > Preferences.
- Expand Modeling and click Path Maps.
- Click New.
- Create a variable named MAPVAR that points to the directory that contains the profile.
A ClearCase request for a model comparison or merge that is initiated outside of Rational Application Developer automatically opens Rational Application Developer. However, on European versions of Windows the automatic start does not work.
To work around this issue, complete one of the following steps:
- Start Rational Application Developer before your perform any ClearCase operations.
- After the automatic start of Rational Application Developer does not work, start the product and click the Retry button in the failure window.
Return to the main readme file