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.
Creating VOB replicas
Before creating a replica, you must make decisions about branching, mastership, identities and permissions preservation, and method of packet delivery.
Replicating a VOB between Windows® and another platform
When setting up replicas on Windows® and other platforms (specifically Linux®) at different sites, there are configuration issues that must be addressed.

Administering
Learn how to administer the product.
- Administering HCL VersionVault
  Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
- Administering platforms for HCL VersionVault
  Learn how to perform HCL VersionVault administrative tasks on supported platforms.
- Administering HCL VersionVault MultiSite
  Learn to configure and manage the HCL VersionVault MultiSite environment to support development activities at different locations.
  - Introduction
    HCL VersionVault MultiSite adds 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 VersionVaultHCL 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.
    - Overview of replica creation
      You can use a three-phase procedure to create a new replica: export, transport, and import.
    - Replica-creation scenario for a VOB
      To define an example scenario, let's say that a company’s software development takes place in Boston, Massachusetts and in a new development office in San Francisco, California.
    - Replicating a VOB between Windows® and another platform
      When setting up replicas on Windows® and other platforms (specifically Linux®) at different sites, there are configuration issues that must be addressed.
  - Replica synchronization
    Replica synchronization uses the same export-transport-import procedure that is used during replica creation.
  - Administering replicas
  - 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 an 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.

Replicating a VOB between Windows® and another platform

When setting up replicas on Windows® and other platforms (specifically Linux®) at different sites, there are configuration issues that must be addressed.

Note: If you plan to use MultiSite at a single site for interoperability between these different platforms, see Using MultiSite for VOB backup and interoperability. This information is not intended to address that issue, but to describe issues involved in setting up replicas on Windows® and other platforms (specifically Linux®) at different sites.

If your sites do not have an IP connection, you must use electronic mail, CDs, tapes, or diskettes to transfer packets. You may have to solve compatibility problems if you choose to use tapes or diskettes. With electronic mail, you can use compatible encoding and compression methods. However, differences between VOBs on Windows® and on the other platforms are handled automatically during packet import.

The most important problems you must prevent are file names that differ only in how they are capitalized and differences in use of line terminators. If file names that are case-sensitive are used at one replica and file names are not case-sensitive are used at another replica, errors can occur during synchronization. Differences in use of line terminators by text editors on various platforms can cause unexpected behavior during file comparisons and merges. Even if the contents of the files are identical, different line terminators indicate differences in the files and require a merge.

For detailed information about these problems and their solutions, see the Help.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.