Rational Rose RealTime Updates

March 1999

The following updates were available at the time of release:

• In order to integrate with the Rational ClearCase configuration management system, you must enable the "preserve case" option in the ClearCase MVFS tab as Rose RealTime is case sensitive when performing file operations. In the ClearCase Homebase tool, select the MVFS tab - ensure the "preserve case" check box is selected.

• Rose RealTime is tightly integrated with leading configuration management systems to perform the majority of CM operations. However, it does not replace the CM tool's interface for advanced configuration operations. In these cases you should use the CM tool directly to take advantage of its full power.

  Examples of operations that are simpler to perform directly through the CM tool are:

  • Reverting to an earlier model configuration that is structurally different from the current version.

  • Moving part of a model forward from an old version to an intermediate version that is not in the latest lineup.

• If you are using batch scripts to perform unattended operations and wish to avoid dialogs which require user response, you should ensure the application is not visible. This can be enabled by including the following line in the batch script: RoseRTApp.Visible = False

• Converting Rose 98 and Rose 98i models that have components of the same name will result in model conversion errors and errors in the component diagrams when these models are brought forward into Rose RealTime. In these cases, resolve the naming conflict in Rose 98 or Rose 98i before attempting the model conversion.

• Prior to converting a Rose 98 or Rose 98i model, it is recommended that model errors are identified and corrected (where possible) through the use of the Check Model utility in Rose.

• Visual Diff for Rational Rose RealTime is designed to be used for generating differences for small files and models. Large models can be managed by checking the "Control All Units" option in the Model Specification dialog. This will create separate files for each significant model element. These files can the be checked individually by the Visual Diff utility. Attempts to run Visual Diff on complete, large models will require large amounts of memory and CPU time.

• If you have updated a model outside of the toolset, e.g. through a file copy or perhaps a CM get outside of the toolset, the modified files will not be regenerated by the toolset. In these cases, a Rebuild All should be run from within the toolset to resynchronize.

• At times, a warning dialog appears when starting the online help using Navigator 4.51 on UNIX. The warning does not affect the functionality or operation of the help system.

• If online help does not start up and you are using Internet Explorer 5, please shutdown any other Internet Explorer sessions and re-launch help.

• With either of the UNIX platforms, a right-click on any of the buttons in a specification dialog will raise a File Menu in the pop-up window. The correct display should be a "What's this?" in the pop-up window. Any selection made after the right-click will still behave as "What's this?".

• Exceed is not a supported X Windows Manager. We recommend either using one of the other supported Window Managers (consult the Release Notes) or installing Rose RealTime locally.

• If you are using an NCD X Terminal, there is a problem with the Java applet for Netscape on this particular configuration which results in not being able to view the online help.

• Note that Rose RealTime workspace exchange between the Windows NT and UNIX platforms is not supported. The various types of model files can be exchanged freely between platforms, but workspace (.rtwks) files can not be shared between UNIX and Windows NT platforms.

Legal Information