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 and Windows® domains
Domain user and group accounts
Any HCL VersionVault community must define a group to which all users who perform routine HCL VersionVault operations using a common set of VOBs and views belong.
Defining required domain accounts manually

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
    - Domain configurations compatible with HCL VersionVault
      HCL VersionVault is compatible with a wide variety of domain configurations. The simplest configuration is a single domain that includes all users, groups, and computers; this configuration entails the least administrative overhead, but other common configurations work equally well.
    - Domain user and group accounts
      Any HCL VersionVault community must define a group to which all users who perform routine HCL VersionVault operations using a common set of VOBs and views belong.
      - Setting the HCL VersionVault primary group
      - Defining required domain accounts manually
    - Multiple user account domain support
      If your existing domain configuration requires it, you can enable HCL VersionVault access for users and computers in multiple domains. Active Directory provides native support for this capability. HCL VersionVault also has a proxy group feature that you can use to provide this capability in Windows NT domains.
    - Conversion to Active Directory
      As with any enterprise-scale application in a Windows® network, HCL VersionVault is affected when the network is converted from Windows NT® domains to Active Directory domains. These topics explain how this conversion affects HCL VersionVault and how to manage users, groups, hosts, and data during and after the conversion.
  - 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.

Defining required domain accounts manually

About this task

The HCL VersionVault Site Preparation wizard attempts to create domain accounts for the HCL VersionVault administrators group and HCL VersionVault server process user if they do not already exist. The account and group names specified during site preparation are presented as the defaults when users run the HCL VersionVault installation program on individual hosts.

If the user running the HCL VersionVault Site Preparation wizard does not have Domain Administrator privileges, the wizard cannot create these accounts. A domain administrator must create them by using the following procedure.

Procedure

Log on as a domain administrator.
Using the appropriate domain user and group account management tool, create a new global group called versionvault (or another group name the community has chosen).
In the Description field, type the following text: Used exclusively by VersionVault server processes and administrators.
Note: In Active Directory, the type of the group must be security (not distribution).
Create a new user, versionvault_albd (or another user name the community has chosen), and put the group name defined in Step 2 in the new user's group list.
1. Select the Password never expires check box.
2. In the Description field, type the following text: Used exclusively by VersionVault servers
3. On each HCL VersionVault host that is configured to support local VOBs and views, the versionvault_albd user must have rights to Log on as a service. In addition, this user (as with any HCL VersionVault user) must have rights to Access this computer from the network or be a member of a group that has these rights. Do not give this user right to Log on locally unless there is a specific need to do so (such as having to change the default ACL on the HCL VersionVault job scheduler).

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.