Configure license behavior

This topic describes how to configure your OpenText Functional Testing license behavior.

If you are installing OpenText Functional Testing for Developers on Linux or Mac, or OpenText Functional Testing for Developers standalone, see the OpenText Functional Testing for Developers Help Center instead.

Note: Some folder paths intentionally include previous company branding, due to backward compatibility considerations.

General license settings

General licensing behavior is managed in the AutoPass license configuration file, located on your OpenText Functional Testing or OpenText Functional Testing for Developers machine. This file includes details about supported options and values.

The file is located at: C:\ProgramData\OpenText\UFT\License\autopass.txt

Caution: Configure this file with caution. Incorrect configuration may prevent the products consuming the licenses from starting, or cause them to behave unexpectedly.

Additional configurations include:

Back to top

Configure the licensing fallback mechanism

Define whether your system uses the licensing fallback mechanism for OpenText Functional Testing and OpenText Functional Testing for Developers as follows:

  1. On your AutoPass License Server machine, browse to the C:\ProgramData\autopass\apls\licenseserver\data\conf\UFT.xml file.

    Note: This file is available with AutoPass versions 9.3 or higher.

  2. Edit and add keys and values to set the following values to true, as needed:

    Product License type Key
    OpenText Functional Testing Any

    license.fallback.uft.rte

    Runtime Engine Any

    license.fallback.rte.rte

    OpenText Functional Testing for Developers UFT Developer

    license.fallback.leanft.leanft

    OpenText Functional Testing for Developers Runtime Engine

    license.fallback.leanft.rte

    Make sure that you add key entries within the <properties> element and after the <comment> element.

    Edit and add keys and values in the following format:

    <entry key="{Key}">{Value}</entry>

Example: To enable the fallback mechanism when you want to use OpenText Functional Testing and you have any of the license types configured, set the relevant key value to true, as follows:

<entry key="license.fallback.uft.rte">true</entry>

Finding a Runtime Engine license

If the fallback mechanism is enabled, and an available Runtime Engine license is found, you will only be able to run your tests, with no creation or editing abilities.

Ensure that you can always access the OpenText Functional Testing IDE or the OpenText Functional Testing for Developers IDE plug-ins by doing one of the following:

  • Deactivate the fallback mechanism by setting the key values to false (this is the default).

  • Contact your License Server administrator to ensure that any OpenText Functional Testing Runtime Engine licenses are blocked or are in use.

For more details, see Licensing fallback mechanism.

Back to top

Configure licensing timeouts

Define the number of minutes, with no keyboard or mouse input, after which OpenText Functional Testing or OpenText Functional Testing for Developers releases the currently used concurrent license.

Configure a timeout for OpenText Functional Testing or OpenText Functional Testing for Developers

  1. On your OpenText Functional Testing or OpenText Functional Testing for Developers machine, open the LicenseSettings.xml file for editing.

    The file is located in the C:\ProgramData\OpenText\UFT\License folder.

  2. Update the following parameters with the number of minutes you want to define for your timeout:

    LicenseAutoReleaseInterval

    The number of minutes after which a confirmation message appears, warning the user that the license is about to time-out.

    ConfirmLicenseReleaseTimeout The number of minutes after which the confirmation message closes, and the license is released.

Configure a timeout for your AutoPass concurrent license server

On your AutoPass License Server machine, browse to the UFT.xml file at C:\ProgramData\autopass\apls\licenseserver\data\conf\UFT.xml.

Open the file for editing, and add the following line of code:

<entry key="autorelease.interval"><#></entry>

where # is the number of minutes of inactivity.

Example: The following syntax defines that your license is released after 10 minutes of inactivity.

<entry key="autorelease.interval">10</entry>

Back to top

See also: