Home
Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
Developing software with HCL VersionVault Explorer
HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
Team software development with VersionVault
HCL VersionVault provides configuration management services that make it easy for development teams to work with resources in a shared repository. With the HCL VersionVault Explorer, developers can access HCL VersionVault from a variety of network connections, including broadband (WAN) and traditional local area networks (LANs).
About ACL authorization
If access control list (ACL) authorization is enabled, the identities and protection modes for some object types are administered through policies, which define permissions for roles; and rolemaps, which map the roles to principals.
Identities for policies and rolemaps
In a policy or rolemap, you specify one or more principals.

Developing
Learn how to develop software with HCL VersionVault and HCL VersionVault Remote Client.
- Developing software with HCL VersionVault
  HCL VersionVault provides a flexible set of tools that your organization uses to implement its development and change management policies.
- Developing software with HCL VersionVault Explorer
  HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
  - Team software development with VersionVault
    HCL VersionVault provides configuration management services that make it easy for development teams to work with resources in a shared repository. With the HCL VersionVault Explorer, developers can access HCL VersionVault from a variety of network connections, including broadband (WAN) and traditional local area networks (LANs).
    - About VersionVault Explorer preferences
      Before you begin working with the HCL VersionVault Explorer, review and, if necessary, change the application's default preferences.
    - Configuring VersionVault Explorer preferences
      Use the VersionVault Windows Explorer preferences page to specify the appearance of the VersionVault Explorer.
    - About the HCL VersionVault WAN server
      If you are running in a WAN environment, the HCL VersionVault WAN server provides the HCL VersionVault Explorer with access to HCL VersionVault repositories and support for HCL VersionVault web views and automatic views.
    - About connecting to servers and user databases
      You must connect to a VersionVault WAN server to create a VersionVault web view or automatic view or to perform certain operations within such views
    - About VOBs and versioned objects
      Versioned Object Bases, or VOBs, are VersionVault repositories that are hosted on an HCL VersionVault server.
    - About VersionVault views
      An HCL VersionVault view provides access to resources in HCL VersionVault repositories.
    - About ACL authorization
      If access control list (ACL) authorization is enabled, the identities and protection modes for some object types are administered through policies, which define permissions for roles; and rolemaps, which map the roles to principals.
      - Policies
        Policies have an Access Control List (ACL) for each controlled VOB metatype (such as element, VOB object, policy, and rolemap).
      - Rolemaps
        You use a rolemap to specify the principals that take on roles listed in a policy, and to apply the access controls to one or more VOB objects.
      - Effective ACLs
        When VersionVault enforces access controls in a VOB, it uses an effective ACL for each metatype.
      - Controlled objects
        The following metatypes are directly controlled by rolemaps: VOB object, policy, rolemap, elements (directory and file).
      - Identities for policies and rolemaps
        In a policy or rolemap, you specify one or more principals.
      - Protected objects and the owner-user and owner-group principals
        An effective ACL can reference an indirect principal: the owner-group or owner-user.
      - Element protection
        The ability to protect directory and file elements with ACLs greatly simplifies authorization administration. The simplification uses multiple groups in element effective ACLs in place of multiple groups in each user's credentials.
    - About VersionVault Unified Change Management (UCM)
      Unified Change Management (UCM) is a structured development process that is based on HCL VersionVault tools.
    - About using the VersionVault Pending Changes view
      The VersionVault Pending Changes view enables you to preview and resolve changes to the current web view or automatic view.
    - About Base VersionVault
      Unstructured access to VersionVault tools is provided by base VersionVault.
    - About the HCL VersionVault Explorer for Eclipse
      The HCL VersionVault Explorer for Eclipse integrates HCL VersionVault with Eclipse team services.
    - About working sets in the HCL VersionVault Navigator view
      Use working sets to limit the items that appear in the VersionVault Navigator view.
  - Working in the team environment with HCL VersionVault
    The HCL VersionVault Explorer supports a variety of team development tasks.
  - Team support for the HCL VersionVault Explorer interface
    The HCL VersionVault Explorer provides graphical user interfaces to VersionVault tools.

Identities for policies and rolemaps

In a policy or rolemap, you specify one or more principals.

The following kinds of principals are supported:

User
Group
Role (granted permission in a policy, mapped to other principal kinds in a rolemap)
Everyone
Owner-user
Owner-group

All kinds of principals, except Role, may appear as the right-hand-side of a role mapping. Roles do not nest.

For users and groups, we allow identities from the VOB server's domain only: you cannot specify a user or group from another domain. Group principals can be any group defined by the operating system of the VOB server; they are not limited to VOB's primary and supplementary groups.

The Owner-User and Owner-Group principal kinds are interpreted relative to the controlled object. For example, if the effective ACL from the rolemap attached to an element grants Owner-Group some permission, then accounts with membership in the element's group are granted that permission.

The User and Group principals are stored in the VOB database using the underlying operating system identity (UID/GID on Linux, SID on Windows). The identities are converted to and from text when displayed, edited, or modified. For interoperation between Windows and Linux, the client system shows users and groups mapped from the VOB server's namespace into the client's namespace.

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.