Jump to main content
Product Documentation
Customer Support
HCL VersionVault V2.0.1
HCL VersionVault V2.0.1
Overview
Installing
Upgrading
Administering
Developing
Managing change and releases
Integrating
Tutorials
Extending product function
Reference
Glossary
Search
Home
Administering
Learn how to administer the product.
Administering
HCL VersionVault MultiSite
Administering replicas
Implementing requests for mastership
To support development of VOB elements that cannot be merged, you can give developers the ability to request mastership of branches and branch types.
Serial development scenario
This is an example of serial development using requests for mastership.
Administering
Learn how to administer the product.
Administering
HCL VersionVault
Administering platforms for
HCL VersionVault
Administering
HCL VersionVault MultiSite
Introduction
HCL VersionVault MultiSite
add
s
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 VersionVault
HCL
Compass
MultiSite
, you need to plan your implementation.
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 the CLI and native GUIs
Managing mastership
Implementing requests for mastership
To support development of VOB elements that cannot be merged, you can give developers the ability to request mastership of branches and branch types.
Overview of a request for mastership
When a developer requests mastership of a branch, the branch's mastership is transferred to the developer's current replica. When a developer requests mastership of a branch type, mastership of the branch type, along with mastership of all the instances of the branch type that have default mastership, is transferred to the developer's current replica.
Requirements and recommendations
In order to enable requests for mastership in one or more replicas and for those requests to be handled efficiently, specific conditions must be met.
Planning your implementation
Before enabling requests for mastership, the project managers and administrators at the different sites must make specific planning decisions about whether requests for mastership are allowed for specific replicas, branches, and branch types, and which developers are authorized to make requests for mastership.
Enabling requests for mastership
To enable requests for mastership for the replicas in a VOB family, you must verify the feature level, add developers to the access control list, specify any objects for which you want to deny requests, and then enable requests at the replica level for each replica in the VOB family.
Enabling synchronous requests for mastership (SRFM)
Synchronous request for mastership (SRFM) means that a request for mastership of a branch is issued synchronously with a checkout of that remotely mastered branch, providing a writable branch before branch mastership is acquired.
Customizing synchronization updates for mastership requests
After a mastership request is processed at the master replica,
sync_export_list
is invoked to export an update packet to the replica at the requester's site. You can customize the export by specifying one or more of the options and arguments that are valid for
sync_export_list
, except for
–replicas
, which is always the replica at the requester's site.
Displaying mastership request settings
To display the mastership request setting for a replica, branch type, or branch, use the
describe
command or the
Mastership
page in the Properties Browser (Windows®). These settings are also displayed in the Request Mastership Window on Windows®.
Troubleshooting mastership requests
MultiSite
provides commands you can use to troubleshoot failed mastership requests. When a request fails, the error messages provide an indication of what happened and what can be done to fix the problem.
Serial development scenario
This is an example of serial development using requests for mastership.
Planning the implementation
In the serial development example, the company PurpleDoc develops documentation at three sites, using two VOB families.
Setting up access controls
Based on decisions made by administrators and project managers, the
MultiSite
administrators at each site configure access control for their site.
Writing config specs
Each location has rules for creating site-specific branches in
/vobs/html
and selecting the latest version on that branch. The
/main/LATEST
rule is used in all the config specs for development in
/vobs/doc
and all other VOBs.
Requesting mastership
This scenario provides examples of how the writers use mastership requests to do their work.
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 a
n
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.
Serial development scenario
This is an example of serial development using requests for mastership.
Planning the implementation
In the serial development example, the company PurpleDoc develops documentation at three sites, using two VOB families.
Setting up access controls
Based on decisions made by administrators and project managers, the
MultiSite
administrators at each site configure access control for their site.
Writing config specs
Each location has rules for creating site-specific branches in
/vobs/html
and selecting the latest version on that branch. The
/main/LATEST
rule is used in all the config specs for development in
/vobs/doc
and all other VOBs.
Requesting mastership
This scenario provides examples of how the writers use mastership requests to do their work.