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.
MultiSite operation
Mastership
Type object mastership
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.
Shared type objects
Instances of a shared type object can be created in multiple replicas.

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.
  - MultiSite operation
    - Information propagated among VOB replicas
      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.
    - VOB objects and VOB replica objects
      Each replica is a VOB, but the VOB object and VOB-replica object are different objects in the VOB database.
    - Mastership
      - Replica mastership
        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
        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.
      - Type object mastership
        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.
        Unshared type objects
        Instances of an unshared type object can be created only in its master replica.
        Shared type objects
        Instances of a shared type object can be created in multiple replicas.
        Additional restrictions for shared global types
        Additional mastership restrictions exist when you use an administrative VOB hierarchy and its global types.
        Creating an instance of a type
        This section describes the circumstances under which you can create an instance of a type and provides an example.
      - Mastership restrictions for VOB objects
        Many MultiSite operations on VOB objects are subject to mastership restrictions.
    - Conflict resolution
    - The operation log
  - 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.

Shared type objects

Instances of a shared type object can be created in multiple replicas.

To prevent cross-replica conflicts, the following restrictions apply:

The instance restrictions (if any) on the type object must allow creation of the instance.
For all objects except versions and branches, the current replica must master the object to which the instance is being attached.
- For a version, the current replica must master the branch on which the version is located.
  Note: When you apply a label whose instance restriction is one per branch, your current replica must master the branch. When you apply a label whose instance restriction is one per element, your current replica must master the element.
- For a branch with default mastership, the current replica must master the branch type.
- For a branch with explicit mastership, the current replica must master the branch object.

Note: If a hyperlink type is shared, you can create a hyperlink of that type between any two objects, at any replica. If the type is global, the restrictions on creation of the local copy apply.

Restrictions that prevent instance creation in an unreplicated VOB also prevent instance creation in a replica; for example, if there is a lock on the type object, instance creation fails. However, because locks are not replicated (except for locks created with –obsolete), a lock on a shared type object in one replica does not prevent instance creation in another replica.

A shared type cannot be converted to unshared. Instance restrictions (for example, once-per-branch use of a label type) for a shared type object cannot be changed.

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.