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 and view access control
DevOps Code ClearCase® supports a rich set of access controls on versioned objects.
Users and groups
A user's name and group memberships are the principal credentials evaluated by DevOps Code ClearCase® when access is requested.
Privileged users and groups
DevOps Code ClearCase® recognizes certain users and groups as privileged.
The DevOps Code ClearCase® server process user
On Windows®, the DevOps Code ClearCase® albd_server program runs with the identity of a special user account known as the DevOps Code ClearCase server process user.

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.
    - Users and groups
      A user's name and group memberships are the principal credentials evaluated by DevOps Code ClearCase® when access is requested.
      - The primary group
        A user can be a member of one or more groups, one of which is distinguished by DevOps Code ClearCase® as the user’s primary group.
      - Privileged users and groups
        DevOps Code ClearCase® recognizes certain users and groups as privileged.
        The DevOps Code ClearCase® server process user
        On Windows®, the DevOps Code ClearCase® albd_server program runs with the identity of a special user account known as the DevOps Code ClearCase server process user.
        Preventing privileged VOB access by remote users
        DevOps Code ClearCase® allows you to prevent privileged access by users who are not logged on to the local host.
        Restricted view access privileges for remote root
        On Linux or the UNIX system, the root user account has restricted access privileges to dynamic views on remote hosts.
    - ACL authorization
      If access control list (ACL) authorization is enabled, the identities and protection modes for some object types are administered through policies, which define permissions for roles; and rolemaps, which map the roles to principals.
    - Non-ACL authorization
      If ACL authorization is not enabled, the identities and protection modes that are defined by the operating system are administered directly.
    - DevOps Code ClearCase® and native file-system permissions
      DevOps Code ClearCase® requires specific file-system permissions on storage directories for VOBs and dynamic views. These permissions are established when the directories are created and must not be changed.
    - Windows shares for VOB and view storage
      On Windows platforms, VOBs and views that are accessed over the network must be created in a folder that is shared. Windows share permissions control access to shared folders, and must be configured to provide adequate rights to users of VOBs and views.
    - Locks on VOB objects
      Access controls on VOB objects are intended to provide a long-lived access-control mechanism. Temporary access control is also provided through explicit locks on individual VOB 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.
  - 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

The DevOps Code ClearCase® server process user

On Windows®, the DevOps Code ClearCase® albd_server program runs with the identity of a special user account known as the DevOps Code ClearCase® server process user.

The DevOps Code ClearCase® server process user account is usually created during site preparation. This user is a member of the DevOps Code ClearCase® administrators group, which grants privileged user status. For more information about the DevOps Code ClearCase® server process user, see Domain user and group accounts.