Home
Administering
Learn how to administer the product.
Administering HCL Compass Multisite
Administering HCL Compass Multisite
Introduction
HCL VersionVault MultiSiteHCL Compass MultiSite adds a powerful capability to HCL VersionVaultHCL Compass. With MultiSite, developers at different locations can use the same HCL VersionVault versioned object base (VOB) HCL Compass database set (a schema repository and its associated user databases). For HCL VersionVault, each location (site) has its own copy (replica) of the VOB. For HCL Compass, each location has its own copies, or replicas, of the schema repository and user databases. 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.
Database object conflict resolution
Mastership restrictions prevent most inconsistent changes in different replicas, but some are unavoidable. To avoid many naming conflicts, the administrators for a family must create and enforce naming rules for objects. A use model that is enforced consistently across sites reduces the potential for conflicts.

Database object conflict resolution

Mastership restrictions prevent most inconsistent changes in different replicas, but some are unavoidable. To avoid many naming conflicts, the administrators for a family must create and enforce naming rules for objects. A use model that is enforced consistently across sites reduces the potential for conflicts.

For example, the administrators for a family follow these rules:

All location-specific objects must include a location identifier.
Objects that will be used at multiple replicas are all created at one replica.

When naming conflicts occur, MultiSite displays the name of the originating replica (the keysite) in the names. If this happens, you should rename the conflicting objects as soon as possible.