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.
Implementation planning
Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
HCL VersionVault use model
Before development work is started in any VOB, the project manager and administrator must define the HCL VersionVault use model. For example, the project manager must specify the branches, labels, and triggers that are used for development and integration work.
Use of administrative VOBs
Using an administrative VOB hierarchy and its global types is subject to additional mastership restrictions.

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
  - Implementation planning
    Before you install and use HCL VersionVaultHCL Compass MultiSite, you need to plan your implementation.
    - MultiSite installation
      MultiSite is installed as an optional product component during the HCL VersionVaultHCL Compass installation.
    - MultiSite licensing
      A MultiSite license is required to access an object in a replica by a MultiSite command or GUI, by an HCL VersionVaultHCL Compass command or GUI, or by a standard operating system command.
    - Shipping server use with HCL VersionVault
      The shipping server is installed when you install HCL VersionVault MultiSite.
    - HCL VersionVault use model
      Before development work is started in any VOB, the project manager and administrator must define the HCL VersionVault use model. For example, the project manager must specify the branches, labels, and triggers that are used for development and integration work.
      - Branching and mastership
        Mastership restrictions affect the choices you make about branching and merging.
      - Use of attributes, labels, and hyperlinks
        Mastership restrictions affect the way you use HCL VersionVault attributes, labels, and hyperlinks.
      - Use of triggers
        Trigger types and triggers are not replicated.
      - Use of multiple replicas of the same VOB at a site
        There are restrictions on how you can maintain multiple replicas of the same VOB at a particular site.
      - Text mode for replicas
        When you create a new replica, it has the same text mode as the replica from which it was exported.
      - Use of administrative VOBs
        Using an administrative VOB hierarchy and its global types is subject to additional mastership restrictions.
      - Use of UCM
        When you use HCL VersionVault UCM and HCL VersionVault MultiSite, some developer and project manager tasks are different.
    - MultiSite use model
      There are different aspects of your MultiSite use model that affect the implementation and deployment of a MultiSite environment.
    - Responsibilities of MultiSite administrators
      The MultiSite administrator must perform the tasks described in this topic.
  - 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.

Use of administrative VOBs

Using an administrative VOB hierarchy and its global types is subject to additional mastership restrictions.

If replicated VOBs use global types, the administrative VOBs must be replicated. Additional mastership restrictions exist when you use an administrative VOB hierarchy and its global types. For more information about global types, see Help.

If a global type is shared, you can create instances of the type in a replica only if one of the following conditions exists:

The replica contains a local copy of the type.
The replica does not contain a local copy of the type, but the type is mastered by the administrative VOB replica at the current site. (If the type is not mastered by the administrative VOB replica, a local copy of the type cannot be created in the replica.)

These restrictions apply even if your current replica masters the object to which you are attaching the instance. These restrictions prevent conflicting, simultaneous creation of a given type with a given name at multiple sites.

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.