|
|
In the next steps of the Join Project Wizard, you set up your development view and integration view by specifying the following information:
Which type of view to create for your development view and integration view
Locations for snapshot views
View-tags for dynamic views
Locations for dynamic view storage directories
We recommend that you accept the defaults the Join Project Wizard presents until you are familiar with UCM. For example, the default naming conventions for your views are intended to distinguish your development view from your integration view.
As described in Views, you can use either a snapshot view or a dynamic view to create a directory tree of source files. Your project manager determines the default view types that the Join Project Wizard presents.
Work in a snapshot view when any of these conditions is true:
Your workstation does not support dynamic views.
You want to work with source files under ClearCase control when you are disconnected from the network that hosts the VOBs.
You want to simplify accessing a view from a workstation that is not a ClearCase host.
Your development project doesn't use the ClearCase build auditing and build avoidance features.
Work in a dynamic view when any of these conditions is true:
Your development project uses build auditing and build avoidance.
You want to access elements in VOBs without copying them to your workstation.
Because a dynamic view can show changes in its attached stream at all times without requiring an update, we recommend that you use dynamic views for your integration views whenever they are available.
The two view types behave slightly differently (for example, the way you access a snapshot view is different from the way you access a dynamic view), so remember the type of view you create (Figure 13).
For a detailed comparison of snapshot views and dynamic views, see the ClearCase online help and the view reference page in the Administrator's Guide for Rational ClearCase.
When creating a snapshot view, you must specify a view directory into which ClearCase loads, or copies, versions of source files from VOBs into the snapshot view at the directory you specify.
When choosing a directory, consider these constraints:
The view's root directory must be located on a disk with enough space for the files loaded into the view and any other files you add.
Your organization may restrict where you can create a view. For example, you may be required to use a disk that is part of a data-backup scheme.
If you want to access the view from other workstations, it must be located in a directory that is accessible to other workstations; that is, choose a disk partition that is exported.
Every snapshot view has a view storage directory in addition to the directory tree of source files that it loads from VOBs. ClearCase uses the view storage directory to keep track of such information as which files are loaded into your view and which versions are checked out to it. The view storage directory is for ClearCase administrative purposes only. Do not modify anything in it.
For every 1,000 elements loaded into the view, ClearCase uses about 400 KB of disk space for the view storage directory.
Usually, your ClearCase administrator sets up a storage location, which is a directory on a ClearCase server host on UNIX or Windows, and by default ClearCase locates snapshot view storage directories in the storage location. If your ClearCase administrator sets up more than one storage location, ClearCase selects one of these locations as the default location when you create a view.
If your ClearCase administrator does not set up storage locations, ClearCase sets a directory under the root directory of the snapshot view as the default location for the view storage directory.
You can override the default location. If your administrator sets up multiple storage locations, you can select one explicitly. You can place the view storage directory under the root directory of the snapshot view.
If you place the view storage directory under the root directory of the view, be aware of the following recommendations:
Do not choose this configuration if you use the view when disconnected from the network. You can corrupt the data in the view storage directory if you disconnect it from the network while the view's view_server process is running.
Make sure that the view storage directory is accessible to any data backup schemes your organization institutes.
NOTE: If you plan to work while disconnected from the network, your administrator must set up storage locations.
When you create a snapshot view, ClearCase creates or modifies the file .ccase_svreg in your home directory. Do not remove or relocate this file; some ClearCase operations require it.
If you inadvertently delete or corrupt this file, see Regenerating the .ccase_svreg file.
If you choose to create a dynamic view, take note of the view-tag. You must use the view-tag to start and access the view. The wizard presents the default view-tag based on the following conventions:
For a development view, the view name is the same as the stream name.
For an integration view, the view name is user-ID_integration-stream-name
If you change the name of the view, we recommend that you choose a name that indicates the view's owner and the stream to which the view is attached.
The first time you create a dynamic view, the wizard provides a default pathname for the storage directory. Click Advanced Options to provide a different pathname for the view storage directory. The location you choose becomes the default for other dynamic views that you create. ClearCase uses this directory to keep track of which versions are checked out to your view and to store view-private objects. The view storage directory is for ClearCase administrative purposes only. Do not modify anything in it.
The size of the view storage directory depends on the following factors:
Whether you use the clearmake build auditing and build avoidance features
The size and number of view-private files
For more information, see the clearmake reference page in the Command Reference.
Consider the following restrictions when choosing a dynamic view storage directory:
The directory must be located on a ClearCase host. View processes (specifically, view_server processes) run on the computer that physically stores the view storage directory, and only ClearCase hosts can run view processes.
To maintain data integrity, the view storage directory must remain connected to the network. For example, do not locate the view storage directory on a removable storage device.
If you locate the view storage directory on a laptop and then disconnect the laptop from the network, all of the following restrictions apply:
You cannot use the dynamic view.
Team members who try to start your view from their hosts will receive error messages from ClearCase.
Any clearmake process that attempts to wink in a derived object from your view will spend some amount of time trying to contact your view. If it cannot contact your view, it will not consider derived objects in your view as winkin candidates for 60 minutes. (You can change the amount of time by setting the CCASE_DNVW_RETRY environmental variable.) For more information, see the clearmake reference page.
If you use the view on several hosts, make sure that the location can be accessed by all those hosts; that is, choose a disk partition that is exported.
If your ClearCase administrator sets up storage locations (which are directories on ClearCase server hosts), you can locate your dynamic view storage directory in a storage location (with mkview -stgloc). However, for best performance, we recommend that you locate dynamic view storage directories on your local host.
We recommend that you make the view storage directory accessible to any data backup schemes that your organization institutes.
|
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |
