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.
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.
Using automount with non-VersionVault access
Certain considerations apply when creating automount map entries for exported views.

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.
  - 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.
    - Setting up an export view for non-VersionVault access
      An export view for non-VersionVault access exports a view-extended pathname to the VOB mount point.
    - Using automount with non-VersionVault access
      Certain considerations apply when creating automount map entries for exported views.
    - NFS problems with non-VersionVault access
      Depending on the NFS implementation on the non-VersionVault host, you might encounter various problems when using non-VersionVault access.
  - 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.

Using automount with non-VersionVault access

Certain considerations apply when creating automount map entries for exported views.

After an HCL VersionVault view and VOB pair has been exported from an HCL VersionVault host by using NFS, any properly authorized NFS client system can access the files in the VOB that are selected by the view. If the NFS client can mount the view and VOB pair directly with a mount command, you can also put that pair (explicitly or implicitly) into a map used by the NFS client’s automounter. Explicit entries name the exported view and VOB pair directly. Implicit entries may arise from wildcard syntax or other advanced automount features.

For example, suppose an indirect map is configured (using typical automount wildcard syntax) at /remote/viewname with a map file listing server:/view/viewname/vobs/&. When a process on the NFS client accesses a subdirectory of /remote/viewname, the automounter performs an NFS mount from the corresponding subdirectory of server:/view/viewname/vobs.

Note: Listing the directory /remote/viewname usually shows active mounts only, not all possible mounts. This is similar to the result of listing /net for a hosts map.

If this type of map does not work correctly, try running an explicit mount command; if it works properly, the problem might lie in the client automounter. For full details about automounter map syntax, see the documentation for your platform.

Note: Using the –hosts map for automount access does not work properly on hosts that also export their root directory. Suppose an NFS client host tries to access /net/cchost/view/viewname/vobs/vobpath. The automounter mounts the server’s root directory on /net/cchost, then tries to mount the view and VOB on /net/cchost/view/viewname/vobs/vobpath. However, /net/cchost/view has no subdirectories, because NFS exports do not follow local file-system mounts such as /view. This mount fails because the local client cannot find a directory on which to mount the view and VOB pair.

For more information about HCL VersionVault and the automounter, see HCL VersionVault and the NFS automounter.

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.