| Operating System |
| OS |
Windows and Linux |
Windows |
SCC mode is available only on Windows,
while Batch mode is available on both Windows and Linux. This is
the operating system that Rational Rhapsody and
the Rational ClearCase client
are installed on. It is not the operating system that the Rational ClearCase server
is installed on.
|
| Basic Configuration Management
Operations |
| Checkout |
You can specify which version to check out |
You cannot specify the version to check out. It depends on
the configuration specification. |
Check out directly from the version tree and reload the unit
using "synchronize." |
| Fetch |
N/A |
N/A |
N/A (Not Applicable) in Rational ClearCase.
The view concept means that the file is always "fetched." |
| Uncheckout |
Supports uncheckout of multiple items with descendant. |
A single item can be cleared out and descendants are not supported. |
Although Uncheckout is available in both modes, SCC does not
have Uncheckout With Descendants. |
| Exploring History and Past
Views |
| History |
No |
Yes |
History and version tree provide the same information
but in different form. While version tree provides a graphical view,
history just lists the versions. It is possible to switch from one
view to the other in both cases. |
| Version Tree |
Yes |
No |
| Diff with Rhapsody |
Yes |
Yes |
This operation can be performed successfully in SCC only if
the hybrid mode is enabled. Therefore, the ConfigurationManagement::General::
UseHybridModeWhenPossible property must be set to Checked in
this case. |
| Properties |
No |
Yes |
Available only in SCC mode. In Batch mode it is possible through
user‑defined buttons (needs a simple command: describe -graphical). |
| Advanced Configuration Management
Interaction and UCM |
| UCM support and other Advanced Options |
No |
Yes |
If using SCC mode, during the configuration management operations
you can get to advanced options. |
| Customization |
Yes |
No |
While advanced options are not available in Batch mode in the
same way, it is possible to achieve many of those functionalities
through properties customization in Batch mode. |
| Repository Restructuring |
| Rename Member |
Yes |
Yes |
Available in both modes depending on the value of ConfigurationManagement::ClearCase::
RenameActivation (if you are using Batch mode) or ConfigurationManagement::SCC::
RenameActivation (if you are using SCC mode) When
this operation is performed on a package-as-directory in SCC, the
repository can be restructured successfully only if hybrid mode is
enabled. Therefore, the ConfigurationManagement::
General::UseHybridModeWhenPossible property must be set in
this case.
|
| Move Member |
Yes |
Yes |
Available in both modes depending on the value of ConfigurationManagement::ClearCase::
MoveActivation (if you are using Batch mode) or ConfigurationManagement::SCC::
MoveActivation (if you are using SCC mode). When
this operation is performed on a package-as-directory in SCC, the
repository can be restructured successfully only if hybrid mode is
enabled. Therefore, the ConfigurationManagement::
General::UseHybridModeWhenPossible property must be set in
this case.
|
| Delete Member |
Yes |
Yes |
Available in both modes depending on the value of ConfigurationManagement::ClearCase::
DeleteActivation (if you are using Batch mode) or ConfigurationManagement::SCC::
DeleteActivation (if you are using SCC mode). When
this operation is performed on a package-as-directory in SCC, the
repository can be restructured successfully only if hybrid mode is
enabled. Therefore, the ConfigurationManagement::
General::UseHybridModeWhenPossible property must be set in
this case.
|
| Set a package to be stored in its own directory |
Yes |
Yes |
Available in both modes depending on the value of ConfigurationManagement::ClearCase::
StoreInSeparateDirectoryActivation (if you are using Batch
mode) or ConfigurationManagement::SCC:: StoreInSeparateDirectoryActivation (if
you are using SCC mode). The corresponding directory
is created in configuration management archive as well, and the relevant
.sbs file with its entire descendants are moved to this directory.
In SCC, this operation is executed in hybrid mode.
Therefore, in addition to the above-mentioned property, the ConfigurationManagement::
General::UseHybridModeWhenPossible property must be set as
well.
|
| Set a package not to be stored in its own directory |
Yes |
Yes |
Available in both modes depending on the value of ConfigurationManagement::ClearCase::
StoreInSeparateDirectoryActivation (if you are using Batch
mode) or ConfigurationManagement::SCC:: StoreInSeparateDirectoryActivation (if
you are using SCC mode). The relevant .sbs file
with its entire descendants are moved to the parent directory, and
the directory created for this package are removed from the archive.
In SCC, this operation is executed in hybrid mode.
Therefore, in addition to above-mentioned property, the ConfigurationManagement::
General::UseHybridModeWhenPossible property must be set as
well.
|
| Configuration Management Commands
Execution Mode |
| User interaction and feedback |
Commands are executed in a shell as batch commands. Errors
or other messages are shown to the user in the Rational Rhapsody Output
window.Rational ClearCase is
not able to react to configuration management errors. |
Interacts directly with configuration management tool using
their UI and API. Rational ClearCase is
aware of configuration management errors and reacts accordingly. |
The user interacts directly with the configuration management
tool GUI elements to perform SCC-supported operations. Return status
information, or error information in the case of failure, comes directly
from the configuration management tool. In this way, Rational ClearCase has
direct configuration management tool interaction, and receives more
complete feedback on configuration management operations, in SCC mode. |
| Configuration Management State
Awareness |
| CM State Awareness |
No |
Yes |
CM State Awareness is available in SCC if ConfigurationManagement::SCC::
ShowCMStatus is set to Checked (check box is selected). |