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.
Troubleshooting
These topics cover a variety of procedures that administrators might need to follow to find and fix problems.
Fixing problems with existing views after relocating elements
Although the relocate command creates symbolic links to preserve a VOB’s historical namespace, you might need to make additional adjustments after relocating elements so that existing views and tools can access them.
Updating directory versions manually
You can modify the results of a relocate operation by adding and removing VOB symbolic links to specific directory versions manually. However, these operations alter the intended results of the relocate command, and they are rarely necessary.
Fixing symbolic links created by relocate

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.
  - 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.
    - Repairing storage directory ACLS on NTFS
      ACLs for VOB and view storage directories are established when VOBs and views are created. These ACLs have a particular form that HCL VersionVault relies on.
    - Fixing problems with existing views after relocating elements
      Although the relocate command creates symbolic links to preserve a VOB’s historical namespace, you might need to make additional adjustments after relocating elements so that existing views and tools can access them.
      - Updating directory versions manually
        You can modify the results of a relocate operation by adding and removing VOB symbolic links to specific directory versions manually. However, these operations alter the intended results of the relocate command, and they are rarely necessary.
        Fixing symbolic links created by relocate
        Modifying old target directory versions to see relocated elements
        Modifying newest version of source directory to catalog relocated elements
    - Locating MVFS data containers
      You can use standard operating system utilities and the mvfsstorage command to find where MVFS files are physically stored. Locating this storage may help resolve file access problems in dynamic views.
    - Preventing recursive traversal of the view root directory on Linux® or the UNIX system
      When the MVFS is installed on Linux® or the UNIX system, the /view directory functions as the mount point for the MVFS namespace. Because this /view directory causes the root directory to contain itself recursively, commands that traverse the entire directory, starting at the system root, loop infinitely.
  - 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.

Fixing symbolic links created by relocate

About this task

In some cases, the VOB symbolic links that relocate creates might have to be modified to point to their intended targets. An incorrect symbolic link in a specific directory version can be removed with cleartool rmname –nco and replaced with cleartool ln –nco.

The relocate command makes an educated guess about the relationship between the source and target VOB roots and about the relationship between the source and target directories. Site-specific factors such as the contents of the NIS host map, VOB mounting and naming conventions on Linux® or the UNIX® system, plus the drive assignment, disk sharing, and naming conventions on Windows® can sometimes lead to an incorrect guess.

To help identify the sources and targets for symbolic links, the relocate command connects a symbolic link object to the target element object with a hyperlink of type HyperSlink. Use the cleartool describe command on the symbolic link to display information about this hyperlink, which can help to repair it if necessary.

Example

The following commands replace a relative symbolic link created during a relocate operation with an alternative absolute pathname to the target VOB.

cd \bigdir cleartool rmname –nco \bigdir@@\main\2\dir1
Modify non-checkedout directory version "\bigdir@@\main\2"? [no] yes
Link removed: "\bigdir@@\main\2\dir1"
cleartool ln –nco \new\proj2\dir1 \bigdir@@\main\2\dir1
Modify non-checkedout directory version "\bigdir@@\main\2"? [no] yes
Link created: "\bigdir@\main\2\dir1"

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.