Before installing the generator

Understand the following before you install Client MSI Generator.

Prerequisites
  • Microsoft .NET Framework 4 or 4.5 must be installed on the machine on which you want to run ALM Client MSI Generator.

  • Uninstall any other versions of this tool.

  • To install and run OpenText Application Quality Management Client MSI Generator, and to run OpenText Application Quality Management client MSI files, you must log in with administrator privileges.

Server version

Client MSI Generator only supports multiple independent servers with the same version installed.

Proxy or web server configurations

Client MSI Generator supports servers with the following proxy or web server configurations:

  • Forward proxy with no authentication or with basic authentication.

  • Reverse proxy with no authentication or with basic authentication.

  • Web server with basic or NTLM authentication.

Double authentication scheme

If a double authentication scheme is used, MSI file generation fails.

HTTPS communication

To enable communication with a server configured for HTTPS, the machine on which you run Client MSI Generator must have a valid SSL certificate.

FDCC workstation

Client MSI Generator cannot run on an FDCC workstation.

External authentication

Client MSI Generator does not fully support external authentication, however the following workaround can be used to bypass external authentication when using MSI Generator:

When external authentication is enabled, Client MSI Generator must be installed on the server. The Server Address field must contain the URL of the server on which Client MSI Generator is installed.

Example:  

The server is installed on a machine that is accessed using http://alm.com/qcbin. Let’s assume that there is some external authentication on this machine.

Generate the MSI file as follows:

  1. Install Client MSI Generator on the alm.com machine.
  2. Set the main URL for MSI generator to http://localhost/qcbin.

    When MSI Generator is deployed, it accesses any server with the same version installed, including alm.com.

Next steps: