Welcome
Administering
Learn how to administer the product.
Administering DevOps Code ClearCase®
Learn about performing administrative tasks for a DevOps Code ClearCase® community including managing software licenses, user and group accounts, ClearCase server and client hosts, shared data, and the network that connects them.
VOB administration
Because VOBs are the principal repository for artifacts under DevOps Code ClearCase® control, VOB administration is one of the DevOps Code ClearCase administrator’s most important tasks.
Automounting VOBs
DevOps Code ClearCase® supports automounting Versioned Object Bases (VOBs). This feature is relevant to users of ClearCase dynamic views only. VOB automounting can be configured on Linux, Solaris, and AIX systems only.
VOB automounting configuration: Administrator actions
The steps to configure VOB automounting are listed here.
Start-time configuration files
To prevent all public VOBs from being mounted during DevOps Code ClearCase® startup, create a var/adm/clearcase/no_vob_mount_on_startup file.

Overview
Learn general information about the product.
Installing
Learn how to install the product.
Upgrading and migrating
Learn how to upgrade and migrate data for the product.
Administering
Learn how to administer the product.
- Administering DevOps Code ClearCase®
  Learn about performing administrative tasks for a DevOps Code ClearCase® community including managing software licenses, user and group accounts, ClearCase server and client hosts, shared data, and the network that connects them.
  - DevOps Code ClearCase® network planning and administration
  - License servers and license administration
    Most DevOps Code ClearCase® applications and commands (cleartool commands, for example, or GUIs such as the ClearTeam Explorer) require a license to run.
  - Reconfiguring ClearCase® to use a different JRE
    When you change the Java Runtime Environment (JRE) for DevOps Code ClearCase®, you must reconfigure the product to make it work with the new JRE.
  - Administering the DevOps Code ClearCase® registry
    The DevOps Code ClearCase® registry is a central repository of information about shared resources such as VOBs and views.
  - DevOps Code ClearCase® network administration in mixed environments
    A DevOps Code ClearCase® environment that includes hosts that run Windows and hosts that run the UNIX system or Linux is said to be a mixed environment.
  - Overview of security considerations
    As an administrator, you are responsible for the security of your DevOps Code ClearCase® deployment.
  - VOB and view access control
    DevOps Code ClearCase® supports a rich set of access controls on versioned objects.
  - VOB administration
    Because VOBs are the principal repository for artifacts under DevOps Code ClearCase® control, VOB administration is one of the DevOps Code ClearCase administrator’s most important tasks.
    - Access to VOB data and metadata
      VOB data must be accessed through a view. Most VOB metadata can be accessed directly by using DevOps Code ClearCase® GUIs and cleartool commands.
    - VOB types
      All VOBs have the same on-disk directory structure, and all have similar administrative requirements. However, certain VOBs might perform special functions.
    - Enabling atomic checkin operations
      When enabled, atomic checkin operations allow VOB users to specify that if a checkin operation should fail for one element specified by the checkin command, then it is to fail for all elements specified by the command.
    - Managing "evil twins"
      "Evil twins" are two elements of the same name that have been created in different versions of the same directory element. When the directory versions are merged, it is not clear which twin has been lost, nor even that the twins may be different versions that need to be merged.
    - VOB schema versions
      Each VOB has a database schema version that defines the format of the VOB database and therefore determines the types of data and metadata that the VOB can store.
    - VOB feature levels
      A VOB feature level is an integer that enables certain features in a release.
    - VOB host configuration guidelines
      Properly configured VOB hosts are essential to obtaining satisfactory DevOps Code ClearCase® performance.
    - Creating VOBs
      Any user with access to a suitable server host can create a VOB.
    - Automounting VOBs
      DevOps Code ClearCase® supports automounting Versioned Object Bases (VOBs). This feature is relevant to users of ClearCase dynamic views only. VOB automounting can be configured on Linux, Solaris, and AIX systems only.
      - Automouting VOBs overview
        Automounting filesystems is a familiar concept for most Linux and UNIX users. Typically, access to NFS filesystems is configured though the automounter. Examples include /net and automounted home directories. Automounting VOBs provides similar behavior, which is based on an automount map that is defined and associated with one or more specific VOB tag prefixes.
      - Behavior of automounted VOBs
        Users will notice little or no difference when VOB automounting is enabled. Whenever a VOB is referred to, it is automatically mounted if it is not already mounted. VOB mounts that have not been accessed for the default timeout period are unmounted automatically.
      - VOB automounting configuration: Administrator actions
        The steps to configure VOB automounting are listed here.
        Update the system's master automount configuration file
        These instructions require that autofs and the automount services of the host operating system are already configured and enabled. If this is not the case, consult the documentation for the host operating system for details about enabling these requirements.
        Mount point information in the Auto.mvfs file
        The entry added to the auto.master file associates the specific mount point path name with a map file that contains the supporting details for autofs to mount the VOBs.
        Start-time configuration files
        To prevent all public VOBs from being mounted during DevOps Code ClearCase® startup, create a var/adm/clearcase/no_vob_mount_on_startup file.
        Restarting autofs and ClearCase®
        After you modify the system's auto.master file or change the auto.mvfs file, you must restart autofs for those changes to go into effect.
        VOB mount options
        When a VOB tag is created, options such as ro or exportid might be defined. In the default configuration in which the cleartool mount -all command mounts all public VOBs when DevOps Code ClearCase® is started, those options are read from the ClearCase registry and applied to the VOB mount.
    - Replacing a VOB server host for a NAS device
      When you locate VOB storage on a NAS device, you can easily replace the VOB host for any VOB on the NAS device with another VOB host of the same architecture without actually moving the VOB storage.
    - Troubleshooting VOB access problems
      Several common problems can prevent access to VOBs.
    - Making a VOB inaccessible
      To make a VOB inaccessible, lock it or remove its tag.
    - Removing a VOB
      Removing a VOB destroys all of its data. Do not remove a VOB unless the data that it contains is no longer valuable.
    - The VOB storage directory
      This topic describes the contents of a VOB storage directory. An understanding of these contents can be useful to anyone responsible for VOB storage maintenance.
    - VOB storage management
      VOB storage grows in proportion to the number of developers who use the VOB and the rate at which they create and change artifacts in it.
    - Creating additional storage for a VOB
      After you have created a VOB, you can create as many additional storage pools as you need and adjust their contents as necessary. On hosts running Linux or the UNIX system, you can also create remote storage pools.
  - VOB datatypes and administrative VOB hierarchies
    There are many types of VOB metadata. Some are unique to a particular VOB, but many must be managed consistently across a group of VOBs that store related artifacts (components of a UCM project, for example). These topics introduce VOB metadata and describe how to use administrative VOB hierarchies to simplify sharing of type objects among related VOBs.
  - Moving VOBs and relocating VOB data
    DevOps Code ClearCase® includes tools for moving data and metadata to another VOB and for moving entire VOBs to another disk or host. You may need to use these tools to reorganize VOB directories, redistribute data storage, or rebalance server loads.
  - Views and view administration
    A view provides a workspace where users access versions of file and directory elements that are under DevOps Code ClearCase® control. Views can also contain view-private file system objects (such as ordinary files and directories) that are not under DevOps Code ClearCase control.
  - Backing up critical DevOps Code ClearCase® data
    Like all databases, VOBs, views, and the DevOps Code ClearCase® registry have special backup and restore requirements.
  - Restoring critical DevOps Code ClearCase® data
    If you have implemented a sound backup strategy for DevOps Code ClearCase® data, it should be easy to restore that data, if necessary.
  - Periodic maintenance
    Periodic attention to storage management and repository integrity is an important administrative function. These topics describe VOB and view storage management tasks, the checkvob utility, and the DevOps Code ClearCase® scheduler, which you can use to automate many periodic maintenance chores.
  - Importing data
    DevOps Code ClearCase® includes several utilities for importing data from other configuration management systems or directly from the file system itself.
  - Troubleshooting
    These topics cover a variety of procedures that administrators might need to follow to find and fix problems.
  - Improving client host performance
  - Improving VOB host performance
  - Configuring cross-platform file-system access
  - DevOps Code ClearCase® and Windows domains
  - Configuring non-ClearCase® access on Linux® or the UNIX system
    You can configure a DevOps Code ClearCase® host running Linux® or the UNIX system to support access to VOBs and dynamic views from computers that do not run DevOps Code ClearCase.
  - Configuring DevOps Code ClearCase® for high availability
  - Estimating VOB size
    If you can estimate the number of elements, versions, and derived objects that a VOB will ultimately contain, you can compute a very rough estimate of the size of a VOB that can accommodate them. VOB storage includes a database and pools. On Windows®, the database and pools must reside on a single disk partition. On Linux® or the UNIX system, the pools can be located on a different partition or host, using symbolic links.
  - Administering the CCRC WAN server
  - About CCRC WAN server parallel view loading
  - Administering and using CMI task-provider integrations
    DevOps Code ClearCase® supports integrations with task providers such as Rational® ClearQuest®, Rational Team Concert (RTC), and Atlassian Jira through the Change Management Interface (CMI).
- Administering platforms for DevOps Code ClearCase®
  Learn how to perform DevOps Code ClearCase® administrative tasks on supported platforms.
- Administering DevOps Code ClearCase® MultiSite
  Learn to configure and manage the DevOps Code ClearCase® MultiSite and Rational® ClearQuest® MultiSite environments to support development activities at different locations.
Developing
Learn how to develop software with DevOps Code ClearCase® and ClearCase Remote Client.
Managing change and releases
Learn how to manage change and release in the product.
Integrating
Learn how to integrate DevOps Code ClearCase® with other products.
Tutorials
Complete tutorials with specific learning objectives for the product.
Extending product function
Learn how to extend the product.
Reference
Review reference information for the product.
Glossary

Start-time configuration files

To prevent all public VOBs from being mounted during DevOps Code ClearCase® startup, create a var/adm/clearcase/no_vob_mount_on_startup file. The start script checks for the existence of this file and skips the VOB mounting step, if it exists. Ensure that the file is empty.