Content management files for Rhapsody

Edit online

In a 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 Rhapsody project file, its purpose, and guidelines for placing it under content management.

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

(For example, *.sbs or *.sbsx, *.omd or *.omdx, *.cls or *.clsx)

 Files that store Rhapsody elements, such as packages, diagrams, and classes Maintain under configuration management.
*.rpw or *.rpwx User-specific workspace data Configuration management is not required.
*.ehl Events history list, which stores animation commands, such as event generation Configuration management is not required.
store.log A log that records when the project was saved Configuration management is not required.
load.log A log of files that is loaded into Rhapsody Configuration management is not required.
ReverseEngineering.log A log of reverse engineering activity Configuration management is not required.
filestable.dat A table of files that are contained in the project Configuration management is not required.
Important: To avoid compromising the model, do not delete this file.
*.cg_info Files of this type *.cg_info store information about when specific files were generated, and this information is used to decide whether code for specific elements must be generated or roundtripped. If you store your source files in a source control system, you must also maintain the *.cg_info files in the source control system. If you only store the model itself in a source control system (but not generated source files), no need to put the *.cg_info files into the source control system.
*_auto_rpy (folder) Folder containing Autosaved files (optional, depends on project settings) Configuration management is not required.
*_bak1.rpy or *_bak1.rpyx and *_bak2.rpy or *_bak2.rpyx Backup project files that are created by Rhapsody (optional, depends on project settings) Configuration management is not required.

You can configure your Engineering Workflow Management client to ignore the resources that must not be shared when you are working with Rhapsody Model Manager. For more information, see Installing Rhapsody Model Manager on individual computers.