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.
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.
Credentials mapping
Credentials mapping allows HCL VersionVault to authenticate users in mixed networks.
Specifying the Windows® domain for credential mapping of users on hosts running Linux or the UNIX system
On Windows® server hosts, you must specify the Windows domain in which credentials can be mapped when authenticating a request from a host running Linux or the UNIX system.

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.
      - Credentials mapping
        Credentials mapping allows HCL VersionVault to authenticate users in mixed networks.
        Specifying the Windows® domain for credential mapping of users on hosts running Linux or the UNIX system
        On Windows® server hosts, you must specify the Windows domain in which credentials can be mapped when authenticating a request from a host running Linux or the UNIX system.
        Credentials for the HCL VersionVault server process user on Linux and the UNIX system
        Mixed environments in which dynamic views on Windows® access VOBs on Linux or the UNIX system require a special user account on Linux or the UNIX system to which the user credentials for the HCL VersionVault server process can be mapped.
      - Managing identities in an ACL-enabled deployment on heterogeneous platforms
        In this topic, the OS type of the client means the OS type of the full VersionVault local client that is using snapshot or dynamic views, or the OS type of the VersionVault WAN server that is hosting web 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.
    - 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.

Specifying the Windows® domain for credential mapping of users on hosts running Linux or the UNIX system

On Windows® server hosts, you must specify the Windows® domain in which credentials can be mapped when authenticating a request from a host running Linux or the UNIX system.

About this task

To specify the Windows® domain for credential mapping:

Click Start > Settings > Control Panel.
Double-click VersionVault and click the Options page.
In the Use this domain to map UNIX user and group names area, select a Windows® domain in which user and group identities have been defined for all Linux or UNIX system-based users who access these services on this server.

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.