Home
Administering
Learn how to administer the product.
Administering HCL VersionVault MultiSite
Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
Introduction
HCL VersionVault MultiSite adds a powerful capability to HCL VersionVault. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. At any time, changes made in one replica can be sent in update packets to other replicas. You can manage replicas by using the command-line tools.
Supporting serial development in VOB replicas
The standard HCL VersionVault development model is to use branches to develop software in parallel, and the standard HCL VersionVault MultiSite model is to master different branch types at different replicas so that development can proceed concurrently at different replicas. These models require you to merge changes from branch to branch. However, sometimes sites must use serial development (for example, to make changes to elements whose versions cannot be merged).

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.
- 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.
  - Introduction
    HCL VersionVault MultiSite adds a powerful capability to HCL VersionVault. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. At any time, changes made in one replica can be sent in update packets to other replicas. You can manage replicas by using the command-line tools.
    - Replicated VOB databases
      In HCL VersionVault MultiSite, developers at different geographic locations can use the same versioned object base (VOB), because each site has its own copy (replica) of the VOB.
    - HCL VersionVault MultiSite terminology
      HCL VersionVault MultiSite documentation uses the terms described in this section.
    - VOBs and VOB replicas
      In HCL VersionVault MultiSite, a VOB replica is a copy of a VOB, including both file system data (data containers) and metadata (VOB database). At each replica, developers can see all VOB elements and all versions of each element.
    - Replica synchronization in a family
      Because information in a replicated VOBHCL Compass database is modified concurrently at different replicas, the contents of each replica in a family tend to differ. The contents of a particular replica may never be identical to the contents of any other replica. To keep the replicas from differing too much, each replica sends updates to one or more other replicas. Updating a VOB replica changes both its database and its storage pools to reflect the development activity that has taken place in one or more other replicas.
    - Independent development: Mastership Modification management in multiple replicas: Mastership
      Because changes are made independently at multiple replicas, these changes may conflict. In a MultiSite environment, tracking changes and preventing data corruption are accomplished with an exclusive-right-to-modify scheme called Mastership. Mastership determines when a user of a replica is allowed to modify data.
    - Supporting serial development in VOB replicas
      The standard HCL VersionVault development model is to use branches to develop software in parallel, and the standard HCL VersionVault MultiSite model is to master different branch types at different replicas so that development can proceed concurrently at different replicas. These models require you to merge changes from branch to branch. However, sometimes sites must use serial development (for example, to make changes to elements whose versions cannot be merged).
  - MultiSite operation
  - Implementation planning
    Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
  - MultiSite command set
    This section summarizes the commands for HCL VersionVault MultiSite and HCL VersionVault that display HCL VersionVault MultiSite information. There are a series of MultiSite commands and API functions that display or modify MultiSite information.
  - Packet transportation methods and configuration
    The method you choose for transporting packets between replicas depends on connectivity. If your replicas do not have IP connectivity, you must use a file-based transport method. If your replicas have connectivity, you can use the store-and-forward facility.
  - Feature levels
    Feature levels allow different replica hosts in a VOB family to run different versions of HCL VersionVault. You can raise the feature level of either a single replica host or an entire VOB family.
  - Creating VOB replicas
    Before creating a replica, you must make decisions about branching, mastership, identities and permissions preservation, and method of packet delivery.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
  - Administering replicas
  - Using MultiSite for VOB backup and interoperability
    You can use HCL VersionVault MultiSite to back up a VOB and to provide access to VOBs in a heterogeneous network.
  - Troubleshooting MultiSite operations
    When you encounter a situation where running an HCL VersionVault MultiSite command produces an unexpected result, or produces a warning or error message, the information in this section can assist you in troubleshooting the problem.

Supporting serial development in VOB replicas

The standard HCL VersionVault development model is to use branches to develop software in parallel, and the standard HCL VersionVault MultiSite model is to master different branch types at different replicas so that development can proceed concurrently at different replicas. These models require you to merge changes from branch to branch. However, sometimes sites must use serial development (for example, to make changes to elements whose versions cannot be merged).

To support serial development, there are two models for changing mastership:

Push Model
The developer who needs to work on a branch asks the administrator of the master replica to transfer mastership of the branch and send an update packet containing the change.
Pull Model
The developer who needs to work on a branch requests mastership of the branch. This model is not enabled by default, and it requires the MultiSite administrator to enable requests and authorize developers to request mastership. However, after the setup is complete, the administrator does not need to be involved in the mastership request process.

Note: The developer can also request mastership of branch types. For more information, see Implementing requests for mastership.

There are two ways to use requests for mastership:
- If you cannot merge versions of the element, you must request mastership, and after your current replica receives mastership, you can perform a reserved checkout and do your work.
- If you can merge versions of the element, you can perform a nonmastered checkout of the element and do your work. At any time, request mastership. When your current replica receives mastership, merge your work (if required) and check in the element.

For more information about enabling requests for branch mastership, see Implementing requests for mastership.

For more information about the use models for requesting mastership, see "About working on a team" in the Developing Software using Base VersionVault part of the Developing Software help component.

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.