Jump to main content
Product Documentation
Administering Learn how to administer the product. Administering HCL VersionVault HCL VersionVault network planning and administrationLicense 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 environmentsAn 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® domainsConfiguring 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 . 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 Administering HCL VersionVault MultiSite
How to disable parallel loading of web views for a single client
About this task On the client, edit the initialization file for the GUI to
set a Java property that disables parallel loading:
Procedure Locate the .ini file:
On VersionVault
Explorer
GUI, navigate to the RemoteClient subdirectory within the VersionVault installation directory (the UNIX system and
Linux default is /opt/hcl /ccm /versionvault /RemoteClient ; the Windows default
is C:\Program Files\HCL\CCM\VersionVault \RemoteClient ).
On the Eclipse shell or other Eclipse-based GUI extended with VersionVault
Explorer plugin, find the .ini file in
the same directory as the executable file that runs the GUI.
Open the .ini file for editing:
On VersionVault
Explorer
GUI, the file is ctexplorer.ini
On the Eclipse shell or other Eclipse-based GUI extended with the VersionVault
Explorer plugin, the file is
eclipse.ini
Edit the .ini file:
On VersionVault
Explorer
GUI, add two lines to the end of the file. As the first line, add -vmargs
. As the
second line, add -Dcom.hcl .ccm .ccrc.disableParallelLoad
.
On the Eclipse shell or other Eclipse-based GUI extended with VersionVault
Explorer plugin, if there is no -vmargs
line in the file, add one at the end, on a line by itself. After the line containing
-vmargs
, add this line: -Dcom.hcl .ccm .ccrc.disableParallelLoad
.
Restart the client:
On VersionVault
Explorer
GUI, restart VersionVault
Explorer .
On the Eclipse shell or other Eclipse-based GUI extended with VersionVault
Explorer plugin, restart Eclipse.