Learn how to administer the product.
Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
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.
Learn how to perform HCL VersionVault administrative tasks on supported platforms.
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.
Not all information is replicated across replicas. (For example, in general, site-specific information is not replicated.) This section shows what information is and is not propagated among replicas.
Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.
When you create a new replica, its replica object (the database object that records the replica’s existence) is mastered by the creating replica. Therefore, you can modify or delete the replica object only at the creating replica, unless you transfer mastership to another replica.
Branch mastership is the scheme that supports independent development work at different VOB replicas. Every branch type defined in a VOB (including the main branch type) has a master replica.
There are mastership issues to consider when creating attribute, hyperlink, and label type objects, particularly when creating instances of those type objects across replicas is required.
Many MultiSite operations on VOB objects are subject to mastership restrictions.
Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
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.
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 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.
Before creating a replica, you must make decisions about branching, mastership, identities and permissions preservation, and method of packet delivery.
Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
You can use HCL VersionVault MultiSite to back up a VOB and to provide access to VOBs in a heterogeneous network.
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.
The following sections describe how mastership applies to objects in databases.