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
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.
Domain upgrade scenarios
In a domain upgrade, you convert a Windows NT® domain controller to an Active Directory domain controller. During an upgrade, the primary domain controller is unavailable briefly.
Upgrading multiple master and resource domains
Use this procedure when HCL VersionVault users and groups are members of more than one Windows NT® domain and you use proxy groups to enable users from these domains to access a common set of VOBs and views. The domains can include resources, users, and groups or can be master domains trusted by resource domains.

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.
    - 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.
      - Preparing HCL VersionVault hosts
      - Domain upgrade scenarios
        In a domain upgrade, you convert a Windows NT® domain controller to an Active Directory domain controller. During an upgrade, the primary domain controller is unavailable briefly.
        Upgrading a single domain
        Use this procedure when all HCL VersionVault users, groups, and hosts are members of a single Windows NT® domain:
        Upgrading a master domain and its resource domains
        Use this procedure if all HCL VersionVault users and groups are members of a single Windows NT® domain (the master domain) that is trusted by one or more Windows NT resource domains to which HCL VersionVault hosts belong.
        Upgrading multiple master and resource domains
        Use this procedure when HCL VersionVault users and groups are members of more than one Windows NT® domain and you use proxy groups to enable users from these domains to access a common set of VOBs and views. The domains can include resources, users, and groups or can be master domains trusted by resource domains.
        Converting proxy groups
      - Domain migration scenarios
        If a domain upgrade is impossible, you can use a domain migration process.
      - Using vob_sidwalk to change or update VOB users and groups
        The vob_sidwalk command provides a flexible means of reassigning ownership of objects in a VOB, updating the SIDS that represent the groups in a VOB’s group list, and correcting VOB storage directory protections.
  - 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.

Upgrading multiple master and resource domains

Use this procedure when HCL VersionVault users and groups are members of more than one Windows NT® domain and you use proxy groups to enable users from these domains to access a common set of VOBs and views. The domains can include resources, users, and groups or can be master domains trusted by resource domains.

About this task

To upgrade multiple master and resource domains:

Procedure

Prepare HCL VersionVault hosts, as described in Preparing HCL VersionVault hosts.
If you do not have a backup domain controller online for each of the master and resource domains during the upgrade, stop HCL VersionVault on all server hosts to prevent HCL VersionVault operations during the upgrade process.
Use the procedures defined by Microsoft® to perform an in-place upgrade of the first Windows NT® master domain to an Active Directory domain.
Upgrade the domain in which the HCL VersionVault users group is defined before you upgrade the domains in which the proxy groups are defined.
Upgrade the remaining master domains.
After the master domains are upgraded, you can begin to upgrade the resource domains.
If you do not alter existing trust relationships between domains that have been upgraded and those that have not, you can upgrade the resource domains in any order and on any schedule that is appropriate for your organization. Make all upgraded domains members of the same forest. This allows you to use Active Directory universal groups, as described in Using active directory universal groups.
After the upgrade of a resource domain is complete, shut down and restart all HCL VersionVault hosts in that resource domain.
After all domains have been upgraded and the Active Directory domain has been converted to native mode, follow the procedure in Converting proxy groups to eliminate proxy groups and domain mapping.

What to do next

Convert the Active Directory domains to native mode after the upgrade is complete, so that you can use an Active Directory universal group to eliminate the need for proxy groups and domain mapping.

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.