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 UCM
When you use HCL VersionVault UCM and HCL VersionVault MultiSite, some developer and project manager tasks are different.

Use of UCM

When you use HCL VersionVault UCM and HCL VersionVault MultiSite, some developer and project manager tasks are different.

A project’s integration stream is mastered by one of the replicas in the VOB family, and developers at other replicas perform a remote deliver operation of their work to the stream. The project manager at the master replica completes the deliver operations. The Help describes this scenario in more detail.

The following restrictions apply to the use of UCM and HCL VersionVault MultiSite

You cannot request mastership of branches or branch types that are associated with streams.
If you replicate a UCM component, you must replicate its associated UCM project VOB (PVOB).
You must synchronize a UCM component and its associated PVOB at the same time.