Home
Administering
Learn how to administer the product.
Administering HCL VersionVault
Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
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.
Administrative VOB hierarchies and global types
Managing type objects that are used in a group of related VOBs is greatly simplified by creating administrative VOB hierarchies that can share globally defined type objects.
If an administrative VOB becomes unavailable
When an administrative VOB or PVOB is unavailable, all other VOBs in its administrative hierarchy are affected.

Administering
Learn how to administer the product.
- Administering HCL VersionVault
  Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
  - HCL VersionVault network planning and administration
  - License servers and license administration
    Most HCL VersionVault applications and commands (cleartool commands, for example, or GUIs such as the VersionVault Explorer) require a license to run.
  - Reconfiguring VersionVault to use a different JRE
    When you change the Java Runtime Environment (JRE) for HCL VersionVault, you must reconfigure the product to make it work with the new JRE.
  - Administering the HCL VersionVault registry
    The HCL VersionVault registry is a central repository of information about shared resources such as VOBs and views.
  - HCL VersionVault network administration in mixed environments
    An HCL VersionVault 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 HCL VersionVault deployment.
  - VOB and view access control
    HCL VersionVault supports a rich set of access controls on versioned objects.
  - VOB administration
    Because VOBs are the principal repository for artifacts under HCL VersionVault control, VOB administration is one of the HCL VersionVault 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.
    - VOB datatypes
      A general understanding of VOB datatypes can place many administrative tasks in context.
    - Administrative VOB hierarchies and global types
      Managing type objects that are used in a group of related VOBs is greatly simplified by creating administrative VOB hierarchies that can share globally defined type objects.
      - Adding a VOB to an administrative VOB hierarchy
        Adding a VOB to an administrative VOB hierarchy gives it access to global types defined in the administrative VOB.
      - Listing an AdminVOB hyperlink
        To find out whether a VOB is part of an administrative VOB hierarchy, you can list its AdminVOB hyperlink.
      - Restrictions on administrative VOB hierarchies
      - If an administrative VOB becomes unavailable
        When an administrative VOB or PVOB is unavailable, all other VOBs in its administrative hierarchy are affected.
      - Removing a VOB from an administrative VOB hierarchy
        To remove a VOB from an administrative VOB hierarchy, remove its AdminVOB hyperlink and then remove all of the global definition hyperlinks that support the global types in it. (You cannot use these procedures on a UCM component VOB or PVOB.)
      - Removing an administrative VOB
    - Working with global types
      In general, all operations on a global type or a local copy of a global type apply to the global type and all its local copies.
    - Replicated administrative VOB hierarchies
      When you use administrative VOB hierarchies (including those created by UCM) in an HCL VersionVault MultiSite environment, special considerations apply to replication.
  - Moving VOBs and relocating VOB data
    HCL VersionVault 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 HCL VersionVault control. Views can also contain view-private file system objects (such as ordinary files and directories) that are not under HCL VersionVault control.
  - Backing up critical HCL VersionVault data
    Like all databases, VOBs, views, and the HCL VersionVault registry have special backup and restore requirements.
  - Restoring critical HCL VersionVault data
    If you have implemented a sound backup strategy for HCL VersionVault 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 HCL VersionVault scheduler, which you can use to automate many periodic maintenance chores.
  - Importing data
    HCL VersionVault 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
  - HCL VersionVault and Windows® domains
  - Configuring non-VersionVault access on Linux® or the UNIX system
    You can configure an HCL VersionVault host running Linux® or the UNIX system to support access to VOBs and dynamic views from computers that do not run HCL VersionVault.
  - Configuring HCL VersionVault 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 VersionVault WAN server
  - About VersionVault WAN server parallel view loading
  - Administering and using CMI task-provider integrations
    HCL VersionVault supports integrations with task providers such as HCL Compass through the Change Management Interface (CMI). The integrations require some configuration tasks, after which you can work with UCM activities or base VersionVault branches that are associated with the tasks.
- Administering platforms for HCL VersionVault
  Learn how to perform HCL VersionVault administrative tasks on supported platforms.
- Administering HCL VersionVault MultiSite
  Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.

If an administrative VOB becomes unavailable

When an administrative VOB or PVOB is unavailable, all other VOBs in its administrative hierarchy are affected.

Many operations on global types and their local copies require access to the administrative VOB and will fail if that access cannot be obtained. For example:

Attempts to lock a VOB that has an AdminVOB hyperlink to an unavailable VOB fail.
Attempts at other VOBs in the hierarchy to create instances of a global type defined in an unavailable VOB produce the following error:
cleartool: Error: Unable to access administrative VOB AdminVOB-tag of VOB-tag
The output of cleartool describe for a VOB that has an AdminVOB hyperlink to an unavailable VOB may not show the hyperlink.

Note: An administrative VOB does not have to be mounted to be available for these operations, but it must be registered and must have a tag in the region from which the operation is attempted.

An administrative VOB (like any VOB) can become unavailable for a number of reasons, including the following:

The VOB server host is down or disconnected from the network.
HCL VersionVault has been stopped on the VOB server host.
The VOB is replicated but has no replica in the current registry (see Replicated administrative VOB hierarchies).
The VOB is being reformatted. When reformatting one or more members of an administrative VOB hierarchy, start at the bottom of the hierarchy and work your way up so that no member of the hierarchy is accessible while its administrative VOB is not.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.