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.
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.
Database object mastership
For user database records, mastership information is stored as a field value in a record. Users can change the value of the mastership field to transfer mastership to another replica. Mastership of the record is sent to the new master replica during the next synchronization. For all other database objects, an administrator must change the mastership.

Database object mastership

For user database records, mastership information is stored as a field value in a record. Users can change the value of the mastership field to transfer mastership to another replica. Mastership of the record is sent to the new master replica during the next synchronization. For all other database objects, an administrator must change the mastership.

The following objects have a master replica:

Records
Users and groups
Workspace items (queries, reports, charts, and folders)
Schema repository

When you work in a MultiSite environment, you must adjust your workflow to account for any stage in your software lifecycle that requires a change of mastership for a record or defect.

For example, users in Paris can submit defects that should be worked on by developers in Boston. But without a change of mastership, developers in Boston cannot modify defects entered by users in Paris.