Content management files for Rational Rhapsody

In an IBM® Rational® Rhapsody® project, some files contain project data and others store local information that does not need to be shared with other team members. Only files that store project data need to be included in a configuration management system.

The following table lists each Rational Rhapsody project file, its purpose, and guidelines for placing it under content management.

Table 1. Project files in Rational Rhapsody
File name Purpose Configuration management guidelines
*.rpy Rational Rhapsody project file Maintain under configuration management.
unit files

(*.sbs, *.omd, *.cls, and so on)

Files that store Rational Rhapsody elements, such as packages, diagrams, and classes Maintain under configuration management.
*.rpw User-specific workspace data Does not require configuration management.
*.ehl Events history list, which stores animation commands, such as event generation Does not require configuration management.
*.vba A binary file that stores Visual Basic for Applications (VBA) macros If the project uses VBA macros, maintain this file from the external configuration management tool.

To archive binary files, most configuration management tools require that you provide a specific signal.

If this file is read-only, when you open the project, the Failed to open document message is displayed. When you save the project, the Failed to save document message is displayed.

If the project does not use VBA macros, you do not need to apply configuration management to this file.

store.log A log that records when the project was saved Does not require configuration management.
load.log A log of files that is loaded into Rational Rhapsody Does not require configuration management.
ReverseEngineering.log A log of reverse engineering activity Does not require configuration management.
*.cg_info Stores information that is related to incremental code generation Does not require configuration management.
*_auto.rpy Autosave file (optional, depends on project settings) Does not require configuration management.
*_bak1.rpy and *_bak2.rpy Backup project files created by Rational Rhapsody (optional, depends on project settings) Does not require configuration management.

Feedback