Home
Installing
Learn how to install the product.
Deploy HCL VersionVault
Read these topics for information about planning, installing, and configuring your HCL VersionVault deployment.
Plan your deployment
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.
Preparing shared locations for an enterprise deployment
If you are using an enterprise deployment strategy, you must prepare your shared locations before users can install the product packages.

Installing
Learn how to install the product.
- HCL VersionVault Release Notes
  To learn about the changes in the product, see the release notes.
- Deploy HCL VersionVault
  Read these topics for information about planning, installing, and configuring your HCL VersionVault deployment.
  - Requirements
    Review the requirements information to identify system requirements, prerequisite tasks, and other information needed to successfully install or upgrade HCL VersionVault and HCL VersionVault MultiSite
  - Plan your deployment
    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.
    - Enterprise software installation strategies
      HCL VersionVault can be installed by using an enterprise strategy.
    - HCL VersionVault Explorer installation planning
      Install the HCL VersionVault Explorer web client to access and modify resources under HCL VersionVault source control through dynamic views or web views.
    - HCL VersionVault MultiSite installation
      Review requirements and other considerations to consider when planning the installation of the HCL VersionVault MultiSite.
    - VersionVault for Microsoft Visual Studio installation planning
      VersionVault for Visual Studio can be deployed with the VersionVault for Windows™ client or with the VersionVault Explorer. After deployment, HCL VersionVault for Visual Studio provides an interface to complete HCL VersionVault operations from the Microsoft™ Visual Studio IDE.
    - Selecting the HCL VersionVault registry server
      Before running any of the installation programs, you must select a host to be your HCL VersionVault registry server. As the installation prompts you for this information, you must prepare this host beforehand.
    - Planning VersionVault support for ACL-enabled VOBs and VOB objects
      If you plan to include ACL-enabled VOBs in your HCL VersionVault environment, review important information about planning installation and upgrade for clients and servers, preparing VOBs, cross-version compatibility, and operating in a mixed version environment.
    - Managing licensing for HCL VersionVault
      Products in the HCL VersionVault product family implement an active-user floating-license scheme.
    - Specifying the default registry region
      An HCL VersionVault registry region (or network region) is a conceptual partition of a local area network required to install the product. During the installation process, you must specify a default region name for your site.
    - Preparing shared locations for an enterprise deployment
      If you are using an enterprise deployment strategy, you must prepare your shared locations before users can install the product packages.
      - Placing the product package on an HTTP web server
        There are several steps to follow to place the product package on an HTTP web server.
      - Placing the electronic image on a shared directory
        In this scenario, you place the electronic image on a shared directory or drive so that users in your enterprise can access the installation files for the product from a single location.
    - Verify that the required Linux™ software packages are installed
      Instructions for verifying whether the required software packages are installed on your system depend on which version of Linux™ you are running.
  - Install HCL VersionVault clients and servers
    The method that is used to install HCL VersionVault depends on the target platform and on your installation strategy.
  - Configuring your environment after deploying
    For some types of HCL VersionVault and HCL VersionVault MultiSite hosts, you must complete some configuration tasks after you have installed the products.
- Use IBM® installation and packaging utilities
  Use IBM installation and packaging utilities to download and install software.

Preparing shared locations for an enterprise deployment

If you are using an enterprise deployment strategy, you must prepare your shared locations before users can install the product packages.

For enterprise deployment, you share files with the users in your organization so that they can install HCL VersionVault or HCL VersionVault Remote Client from a single shared location. Determine the installation strategy during the planning stage: Enterprise software installation strategies. The strategy that is chosen determines how you share the files and what steps users must complete to install the product.

If you are using a silent installation for your enterprise deployment, you must create a customized response file as described in Creating a response file with Installation Manager while installing. The customized response file includes repository, license information, product settings, package groups and shared resource directory, and other values that are specific to your deployment. You must include this response file with the version of IBM Installation Manager that you provide to users.

You can make the product packages available for installation from one of these shared locations using the associated task flow:

A repository on HTTP or HTTPS web servers
1. Use the IBM® Packaging Utility to copy the installation files to a repository. Then copy Installation Manager to a shared location. See Placing the product package on an HTTP Web server.
2. Notify users of where they can install the Installation Manager from the shared location. If you do not include a response file, notify users of the repository location and values that must be entered in the Installation Manager.
  Users download the Installation Manager and use it to install from the repository location. See Installing from a repository on an HTTP or HTTPS Web server.
A shared location in a directory or drive
1. Place the installation image on the directory or drive. See Placing the electronic image on a shared directory.
2. Notify users of the shared location where they can access the files and the method to access the files.
3. Users download the Installation Manager and use it to install from the repository location.

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.