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.
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.
Cross-platform file-system access
Dynamic views must use a network file system to access artifacts such as constructed versions and derived objects in VOB storage directories or files in remote view storage. When the view and VOB are on the same platform, its native network file system is used. When they are on different platforms, cross-platform file-system access is required.
The HCL VersionVault File Service
The HCL VersionVault File Service is a TCP/IP-based file transfer mechanism.

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.
    - Common user and group names
      The identity with which a user logs on to the operating system of an HCL VersionVault host establishes the credentials that determine the users's access rights to artifacts in VOBs and views.
    - Cross-platform file-system access
      Dynamic views must use a network file system to access artifacts such as constructed versions and derived objects in VOB storage directories or files in remote view storage. When the view and VOB are on the same platform, its native network file system is used. When they are on different platforms, cross-platform file-system access is required.
      - The HCL VersionVault File Service
        The HCL VersionVault File Service is a TCP/IP-based file transfer mechanism.
        Enabling the VersionVault File Service on Windows® hosts
      - Network-attached storage and cross-platform file access tools
        HCL supports several network-attached storage (NAS) devices that can be configured to host VOB or view storage and provide native file system access to computers running any supported operating system, without the need to install any other software on HCL VersionVault client or server hosts.
    - Case-sensitivity
    - Configuring text modes for views
    - Differences in supported character sets
  - 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.
  - 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.

The HCL VersionVault File Service

The HCL VersionVault File Service is a TCP/IP-based file transfer mechanism.

When the VersionVault File Service is in use, file transfers between a VOB and snapshot view (for example, operations such as adding a file to source control, updating it in the view, and checking it out or in) take place over a standard TCP/IP connection created by the VersionVault File Service.

The VersionVault File Service is used whenever a snapshot view accesses VOB data. The VersionVault File Service is used by HCL VersionVault to enable cross-platform file transfers between VOBs and snapshot views.

On Linux and on the UNIX system, the VersionVault File Service is used to support access by snapshot views to VOBs on Windows®.
On Windows®, the native network file system is typically used to support access by snapshot views to VOBs on Windows®. You can enable the VersionVault File Service to support access by snapshot views to VOBs on Linux and on the UNIX system.

VersionVault File Service and remote Windows® view server hosts

HCL VersionVault hosts that use snapshot views but cannot run a local view_server process use the VersionVault File Service as their sole file-transfer mechanism when accessing VOBs on Linux and the UNIX system. Snapshot views on these clients require another Windows® computer to run the view_server processes and host the view storage directories associated that support these views.

The VersionVault File Service must be enabled on any Windows® computer that performs this role. A Windows® computer configured to use an NFS client product to access VOBs hosted on Linux or the UNIX system cannot provide view_server support for HCL VersionVault clients that cannot run a local view_server process.

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.