Views and view administration

A view provides a workspace where users access versions of file and directory elements that are under Rational® ClearCase® control. Views can also contain view-private file system objects (such as ordinary files and directories) that are not under Rational ClearCase control.

Any Rational ClearCase development environment requires one or more views. A typical view is created and used by an individual or perhaps by a small group working on a common task. Other views—for example, UCM integration views—may be created by a project leader or administrator and shared by many users. Various administrative responsibilities are associated with views:

View creation and access control
Backing up and recovering views
Moving, removing, and managing the storage used by views

There are three kinds of views:

Dynamic views use the MVFS to provide transparent access to versions of elements in the VOB and also view-private objects. Dynamic views also support Rational ClearCase build auditing and build avoidance tools and can contain derived objects (DOs). Developers work in dynamic views when they want immediate access to the latest versions of elements on a given branch or when they need to take advantage of audited builds and build avoidance. Dynamic views provide more functionality, require more frequent use of the network, and need more administrative support than other views.
Snapshot views use the host's native file system to hold copies of versions of specified elements and also view-private objects. Snapshot views do not support build-auditing and build-avoidance tools. Developers work in snapshot views when they want a simplified environment for editing, compiling, and debugging (even when disconnected from the network), do not need immediate access to the latest versions of elements, and do not need audited builds and build-avoidance. Snapshot views provide less functionality, require less frequent use of the network, and need less administrative support than dynamic views.
Web views are similar to snapshot views, but are created and accessed through the Rational ClearCase Web interface.

The mkview reference page has additional information about views.

Dynamic views
A dynamic view is an MVFS directory that enables dynamic access to VOB elements.
Snapshot views
A snapshot view uses a host's native file system to hold versions of file and directory elements that have been loaded from a VOB. After the snapshot view has been created, versions of file and directory elements must be loaded (copied) into the snapshot view directory.
Creating a view
Views are typically created by users. The process is simple, can be automated by GUIs on all supported operating systems, and does not usually require administrative intervention. In some cases, an administrator may be responsible for creating shared views or for establishing policies that govern view creation.
Moving a view
Because views are easy to remove and re-create, you do not often have to move them. When you do, special procedures must be followed.
Displaying the properties of a view
You can use the Rational ClearCase Administration Console or the cleartool lsview command to display the properties of a view.
Taking a view out of service
To take a view out of service temporarily, stop its view_server process and remove its view tag.
Restoring a view to service
To restore a view to service create a tag for the view by using the Rational ClearCase Administration Console or the cleartool mktag command.
Removing a view
When you remove a view, you must also remove any references to it held by VOBs.

Parent topic: Administering Rational ClearCase