Enterprise deployment

When installing OpenText Functional Testing in an enterprise business model across many computers in a network or company, ensure that you have administrator permissions on each computer.

OpenText Functional Testing also supports silent installations. For details, see Silent installation.

User Account Control (UAC)

You do not need to turn off the computer's User Account Control (UAC).

For users to connect to ALM from OpenText Functional Testing for the first time without turning off UAC, you must also install the ALM client MSI file on each machine.

Generate a custom MSI for all your users with the ALM Client MSI Generator. This tool enables you to configure the settings for your ALM servers before installing the client-side MSI.

Configure the settings for a custom MSI, as described in the user guide provided with each MSI Generator version.

Note:  When configuring the settings, select the Check Include Component Registration and Use Shared Deployment Mode options.

Back to top

Stingray or Terminal Emulator Add-ins

If your users are using either the Stingray or Terminal Emulator add-ins, there are additional configurations you or the user must perform after installing OpenText Functional Testing.

Both the Stingray and Terminal Emulator Add-ins

Run the Additional Installation Requirements, available in the Start menu, after the main installation on each computer.

In the Additional Installation Requirements, select the Run Stingray Wizard and/or Run Terminal Emulator Wizard options, and follow the configuration wizard steps to set up the add-ins.

Stingray Add-in

After installing OpenText Functional Testing, users must run the Stingray Support Configuration Wizard from inside OpenText Functional Testing: Tools > Options > GUI Testing tab > Stingray pane > Select Version.

This configuration requires no administrative permissions.

Terminal Emulator Add-in

After installing OpenText Functional Testing, users must run the Terminal Emulator configuration wizard from inside OpenText Functional Testing: Tools > Options > GUI Testing tab > Terminal Emulator pane > Open Wizard

Users must have administrator permissions to run this wizard.

You can also run the wizard once, and then save the settings to a registry file that can be deployed on all computers, as follows:

  1. In the final screen of the Terminal Emulator Wizard, select the Save terminal emulator settings to file option.

    Note: Ensure that you record the vendor name and emulator name assigned to the configuration, as well as the exact location of the .reg file.

  2. Copy the file to the <Installdir>\dat folder on your computer.

  3. Double-click the registry file to open the Registry Editor message box.

  4. Click Yes to add the information into the registry. A message opens confirming that the information has been copied into the registry.

  5. Click OK. The emulator name assigned to this configuration is added to the list of available terminal emulators for your OpenText Functional Testing installation.

Back to top