Enterprise software installation strategies

HCL VersionVault can be installed by using an enterprise strategy.

Note: Before installing HCL VersionVault, make sure you are familiar with installation, administration, and operating procedures for IBM Installation Manager and IBM Packaging Utility, see Use IBM installation and packaging utilities for details. Complete documentation for both products is available in the Installation Manager documentation.

Enterprise installation strategies

An enterprise installation strategy involves making product packages available on a shared drive. Users in your enterprise can access the installation files for the product from a single location. If you choose an enterprise strategy, you must complete the tasks relevant to that strategy before users begin any installation tasks. See Preparing shared locations for an enterprise deployment.

Note: Silent installation is supported for both shared location options. For details, see Installing silently.

Shared location options include:

  • Setting up repositories and making Installation Manager available to users

    In this scenario, you place product package files in a repository on an HTTP or HTTPS web server or a shared drive where users can download them to install Installation Manager and other product packages. If you create a customized response file, users can install Installation Manager and use Installation Manager to run a silent install of HCL VersionVault. A customized response file contains repository, license information, product settings and other values that are specific to your organization deployment. You can create a response file manually or you can use Installation Manager to record the response file for you. If you do not create a response file, you must inform users of the repository location and other information or values that they must enter into the pages of the Installation Manager Install wizard to install HCL VersionVault.

    Use this strategy to set up a single location from which users can install a single product or multiple products at the same time. You can also add future updates to the repository that users can access the same way they accessed the files for the initial product installation. For more information about installation repositories, see Installation repositories.

    Steps for preparing the HTTP or HTTPS web server or shared drive are provided in Placing the product package on an HTTP Web server.
    Note: To place product package files for the product on an HTTP or HTTPS web server, you must use IBM Packaging Utility to copy the installation files to the server in a package format. The directory on the server that contains the product package is called a repository. IBM Packaging Utility is provided with the product.
  • Placing an electronic image with the product installation file on a shared directory or drive

    In this scenario, you place the electronic image on a shared drive so that users in your enterprise can access the installation files for the product from a single location. For more information, see Placing the electronic image on a shared directory.