Rational ClearCase also contains extended security features, such as user authentication and audit support to meet internal and external compliance requirements.
You can publish a set of file versions from a Rational ClearCase view as an asset in Rational Asset Manager.
The Rational ClearCase snapshot view storage must be in a shared folder. You must use a shared folder for all view storage. When you import files, a snapshot view is created in the shared folder for the asset contents and is linked from your Eclipse workspace. You can use a snapshot view to modify content offline or remotely. When you are connected, you can check in the modified content. When you import an asset, the configuration specification for the snapshot view is read-write. You can change files, check in and deliver the files, and then update the asset in Rational Asset Manager.
Views that are created by Rational Asset Manager for importing assets that use files from views are automatically checked. Views that are not being used in the workspace are removed from Rational ClearCase.
When you integrate Rational Asset Manager with Rational ClearCase, the user who has access to the versioned object base (VOB) must also start the Rational Asset Manager server.
A developer wants to reuse an asset and is already working in a Rational ClearCase view in the Eclipse workspace. The developer imports the asset and changes it while disconnected from the system. Later, the developer connects to the system, checks in the changes, and submits a new or updated asset.