HCL VersionVault MultiSite consideration

In most cases, developers complete the deliver operations that they start. If your project uses HCL VersionVault MultiSite, you may need to complete some deliver operations before you can build the components. Many customers use HCL VersionVault MultiSite, a product layered on HCL VersionVault, to support parallel software development across geographically distributed project teams. HCL VersionVault MultiSite lets developers work on the same VOB concurrently at different locations. Each location works on its own copy of the VOB, known as a replica.

To avoid conflicts, HCL VersionVault MultiSite uses an exclusive-right-to-modify scheme, called mastership. VOB objects, such as streams and branches, are assigned a master replica. The master replica has the exclusive right to modify or delete these objects.

In an HCL VersionVault MultiSite configuration, a team of developers may work at a remote site, and the integration stream of the project may be mastered at a different replica than the developers' development streams. In this situation, the developers cannot complete deliver operations to the integration stream. As project integrator, you must complete these deliver operations. UCM provides a variation of the deliver operation called a remote delivery. When UCM determines that the integration stream is mastered at a remote site, it makes the deliver operation a remote delivery and posts the delivery, which starts the deliver operation but does not merge any versions. You then find the posted delivery and complete the deliver operation at the remote site.