The
topics in this section describe how to manage units from within Rational Rhapsody using
a collaboration tool.
Source Code Control (SCC) mode and batch mode defined IBM Rational Rhapsody supports
common configuration management operations, such as Connect to Archive,
Add Member, Check In, and Check Out, for a wide variety of configuration
management tools. The Windows version
of Rational Rhapsody also
supports Microsoft Common
Source Code Control (SCC) operations, such as Get, Un‑Check Out, and
History, for configuration management tools that conform to the SCC
standard.
Configuration management operations
The topics in this section detail a number of configuration
management operations included in the standard IBM Rational Rhapsody interface.
Viewing messages in the Output window IBM Rational Rhapsody captures
messages generated by the configuration management tool and displays
them in the configuration management output window. It is important
to observe messages from the configuration management tool because
the commands sometimes fail. For example, if you try to check out
a unit with a lock when the unit is already locked, the operation
will fail.
Pre- and post- actions for configuration management IBM Rational Rhapsody assumes
a minimal configuration for all configuration management operations
and takes certain actions either before (pre‑actions)
or after (post‑actions) configuration management operations.
Extending the configuration management interface
User‑defined buttons enable you to extend the IBM Rational Rhapsody interface
to support configuration management operations, which are not included
in the standard interface. Using Rational Rhapsody properties,
you can assign commands to these buttons, such as submit, report defect
on a version, extract, send by mail, and so on.
Unresolved references
Every IBM Rational Rhapsody configuration
item can include references to other configuration items (CI cross‑references).
Once a configuration item is moved to another workspace, some of its
references might no longer exist in the new context. These dangling
references are called unresolved references. For example, if
you replace an existing package with a newer version and the new package
does not contain an item that shows in a certain view, references
to that item will be unresolved.
Units added by reference
Configuration management
operations cannot be executed
on units that have been added to the model as references.