Deploy HCL VersionVault

Read these topics for information about planning, installing, and configuring your HCL VersionVault deployment.

Important: If you are migrating to HCL VersionVault from IBM Rational ClearCase, see the migration guide provided with the download of the HCL VersionVault product before you try to install the product. You must uninstall the ClearCase product before installing HCL VersionVault. The products cannot be installed on the same system. Additionally, VersionVault WAN server cannot share a load balancer across brands.
Note: HCL VersionVault provides two clients for software developers: local and remote. Each client supports different mechanisms for accessing source-controlled filesystem objects. Both clients provide graphical and command-line interfaces.
The table that follows summarizes some important characteristics of the two clients.
Table 1. Characteristics of VersionVault clients for software developers
Client Network connection type Connection to repository of source-controlled objects View types User interfaces
VersionVault Local Client LAN only RPC connection to a Versioned Object Base (VOB)
  • Dynamic
  • Snapshot
  • GUI: VersionVault Explorer
  • CLI: cleartool
VersionVault Remote Client WAN and LAN http(s) connection to a VOB through a VersionVault WAN server
  • Automatic
  • Web
  • GUI: VersionVault Explorer
  • CLI: rcleartool

The term view, as used in this table, refers to the mechanism for accessing versions in a VOB. For example, snapshot, automatic and web views provide copy-based mechanisms, whereas the dynamic view provides a mechanism to directly access versions in real time.

Another use of the term view refers to the configuration management model that governs the development of software. The two models are called Base VersionVault and Unified Change Management (UCM):
  • In a Base VersionVault view, you specify the configuration explicitly by rules for version selection, branching, and so on.
  • In a UCM view, the configuration is generated by VersionVault operations such as creating a development stream.
For more information, see the "Developing software with HCL VersionVault Explorer" topic.
Note: VersionVault security depends on host and network security. For details about security requirements for your deployment infrastructure as well as those for VersionVault itself, see Overview of security considerations.