Plan your deployment of HCL VersionVault
Review a checklist of required and optional tasks with links to additional information for planning the installation and deployment process for HCL VersionVault and HCL VersionVault MultiSite.
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: 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.
The following table summarizes the planning tasks for installing HCL VersionVault.
Requirements | Client Server |
Information | Comments |
---|---|---|---|
Review the release notes | Client Server |
See the release notes document provided with the product. | |
Check system requirements | Client Server |
Hardware and software requirements | The requirements listing includes information about operating system and file system support, basic hardware requirements, required operating system patches, and miscellaneous software support information. |
Determine the installation strategy to use for making HCL VersionVault available for users to install to their workstations | Client Server |
Enterprise software installation strategies | Before you install HCL VersionVault, you must determine which installation strategy is most appropriate for your deployment. |
Optional. Install and configure IBM® HTTP Server and IBM® WebSphere® Application Server | Server | Prepare the WebSphere Application Server environment for HCL VersionVault web servers | IBM® HTTP Server and IBM® WebSphere® Application Server are required to support HCL VersionVault Remote Client. |
Optional. Plan for installation of HCL VersionVault Remote Client | Client Server |
HCL VersionVault Explorer installation planning | Determine whether your users are going to use the HCL VersionVault Remote Client. Use of the clients requires some pre-installation and post-installation configuration. If the VersionVault environment supported previous versions of the HCL VersionVault Remote Client, you must upgrade your existing hosts and views. |
Optional. Plan for installation of HCL VersionVault MultiSite | Client Server |
HCL VersionVault MultiSite installation | In an HCL VersionVault environment that is to support HCL VersionVault MultiSite, you do not need to install HCL VersionVault MultiSite on all HCL VersionVault computers. |
Plan for installation of VersionVault for Microsoft Visual Studio | Client | VersionVault for Microsoft Visual Studio installation planning | Decide whether to deploy VersionVault for Microsoft Visual Studio with the VersionVault for Windows client or the HCL VersionVault Explorer Remote client. |
Optional. For Linux and Solaris systems: Configure automounting of VOBs | Client Server |
Automounting VOBs | Decide whether to automount VOBs. |
Plan support for ACL-enabled VOBs and ACL enforcement for VOBs and VOB objects | Server | Planning support for ACL-enabled VOBs and VOB objects | |
Identify hosts for the license server and registry server | Server | Selecting the HCL VersionVault registry server | Before you run any of the installation programs, you must specify license server host and registry server host. |
Configure licensing for your deployment | Client Server |
Managing licensing for HCL VersionVault | |
Identify the default registry region | Client Server |
Specifying the default registry region | A registry region is a conceptual partition of a local area network. |
Establish service account that meets the installation requirements | Client Server |
The requirements for the VersionVault account
are as follows:
|
If all service account requirements are not
met, the installer blocks users that do not have administrative access
to the domain. However, the installer allows users with domain administrative
privileges to continue if the requirements are not met. Note: To avoid
problems during a mass deployment, ask the domain administrator to
confirm that the service account exists. |
Prepare shared locations for enterprise deployments of the VersionVault client | Client | Preparing shared locations for an enterprise deployment | If you are using an enterprise deployment strategy, prepare a shared location. Users can install the HCL VersionVault client from the shared location to their workstations. This method might require setting up repositories and a location for users to get the Installation Manager or making an electronic image of the product installation files available to users. |
Verify that the required software packages are installed | Client Server |
Verify that the required Linux software packages are installed | This requirement applies only to Linux™ operating systems. |