License installation and management

To work with the lab, you require a valid license. The license installation and management process depends on your environment.

In this topic:

Overview

OpenText Functional Testing Lab comes with a 45-day trial license, activated on the date that you install the software. After the trial period, you need to install a valid license to continue working.

The following table summarizes where to install your license if applicable, and how to manage license quota.

License	Shared spaces enabled	Install license	Manage quotas
OpenText Functional Testing Lab: Express, Pro License	No	Administration menu	No
OpenText Functional Testing Lab: Enterprise, Ultimate,Trial License	No	Administration menu	Allocate quota to workspaces
OpenText Functional Testing Lab: Enterprise, Ultimate,Trial License	Yes	Operator console	Allocate quota to shared spaces Allocate quota to workspaces
OpenText Core Functional Testing Lab	Not applicable	No	Allocate quota to workspaces
OpenText Core Software Delivery Platform	Not applicable	No	Allocate quota to workspaces
Managed Service Provider (MSP)	Yes	Operator console	Allocate quota to shared spaces
MSP customer	Not applicable	No	Allocate quota to workspaces

For more details about shared spaces, see Shared spaces.

Back to top

License types

OpenText Functional Testing Lab has two types of licenses:

• Concurrent license
• Hours license

Concurrent license

This license is based on concurrency. The following table summarizes how the license works.

License	Details
OpenText Functional Testing Lab	This license type is based on concurrent device use. You can connect as many devices as you want to the lab. However, the number of lab devices that can be used simultaneously (regardless of the type of activity on the devices) is determined by the license capacity. This license is installed in the OpenText Functional Testing Lab License Management screen.
OpenText Core Functional Testing Lab	This license type is based on concurrent device use. You can connect as many devices as you want to the lab. However, the number of lab devices that can be used simultaneously (regardless of the type of activity on the devices) is determined by the license capacity.
OpenText Core Software Delivery Platform	This license type is based on concurrent use of devices or OpenText Functional Testing Lab cloud browsers. You can connect as many devices or browsers as you want to the lab. However, the number of lab devices or browsers that can be used simultaneously (regardless of the type of activity) is determined by the license capacity.

Hours license

This license type is based on usage time. The following table summarizes the various time-based licenses.

License	Details
Public device and cloud browser hours	The total usage time of public devices/cloud browsers is limited by the number of usage hours purchased. Note: A concurrent license must also be installed. However, when using a public device, license capacity is consumed from the public device and cloud browser hours license and not from the concurrent license. This section does not apply to OpenText Core SDP.
Public device hours	The total usage time of public devices is limited by the number of usage hours purchased. Note: A concurrent license must also be installed. However, when using a public device, license capacity is consumed from the public device hours license and not from the concurrent license. Applies to OpenText Core SDP only.
MSP device hours	The total usage time of devices is limited by the number of usage hours purchased. This device hours license is available only for Managed Service Providers.
ADM Consumption token license	This is a single license that can be used for multiple Application Delivery Management products. Note: The ADM consumption token license is not supported for shared spaces.

Back to top

License modes

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

There are two license modes: Standard mode and MSP mode. The following table describes when the modes are used.

License mode	Use
Standard	Use this mode when using: Concurrent license Public device and cloud browser hours license
MSP	Use this mode when using: MSP Device hours license ADM consumption token license

To switch between license modes:

You can switch between the two license modes, if you have a valid license. To switch the mode, on the License Management screen, select the required license mode and click Activate. You can only use one license mode at a time.

Back to top

Get your license key

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

Customers with a valid order number access their entitlements to software activations and downloads in the Software Licenses and Downloads (SLD) portal. For assistance, refer to the videos and quick start guide available on the portal, or contact a regional licensing support center or your sales representative.

For the different license editions available, and the functionality included with each, see Licenses.

Back to top

Install your license

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

After you obtain your license key, you need to install it.

To install a concurrent devices license:

1. Open License Management.
   Go to the Lab console at http/s://<OpenText Functional Testing Lab server IP address>:<server port> and log in with your credentials:
   
   

   Console	How to access License Management
   Lab Console - Administration menu	Click Administration > Licenses. In the left pane, select License Management. Accessing the menu requires an admin role.
   Operator console	Open the Operator console and select Licenses. In the left pane, select License Management. Accessing the console requires an operator role.

2. In the License Management screen, click +, and add the license in one of the following ways:
• Click Upload file to select the .dat file containing the license.
• Paste the license string into the text box. Click Upload text to send the new license to the server.

If you upload two licenses of the same type, their capacity is combined. The expiration date displayed in the Active section is that of the license that expires first.

To install a device and cloud browser hours license:

1. Refer to Support matrix for the required version of AutoPass License server. Download the installation from the ITOM Marketplace (may require login).
2. Install the AutoPass License Server and upload your OpenText Functional Testing Lab license to it. For more details, such as managing licenses, see the AutoPass License server documentation.
3. Complete the AutoPass details in the OpenText Functional Testing Lab Administration > Settings > AutoPass License server configuration. For details, see Administration settings or Global settings (if shared spaces are enabled). After you do this, you can view the license details in Licenses > License Management.

Back to top

License management

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

In License Management you can view information relating to your licenses, such as the number of active licenses, their expiration dates, capacity, and the type of license.

Console	How to access License Management
Lab console - Administration menu	Click Administration >Licenses. In the Management pane, select License Management.
Operator console	Open the Operator console and select Licenses. In the Management pane, select License Management. Note: An operator role is required to access to the Operator console.

When a license is about to expire, a notification is displayed in the masthead.

Back to top

License quotas overview

Allocate license quota to ensure shared spaces and workspaces have adequate license capacity. For example, allocate more capacity to a shared space during peak testing or limit usage to prevent excessive consumption.

The following table details how license capacity quotas can be allocated.

License	Shared spaces enabled?	Quota allocations
OpenText Functional Testing Lab License capacity is based on concurrent devices. If MSP mode is enabled, capacity is based on MSP device hours.	Yes	Allocate quota to shared spaces Allocate quota to workspaces
OpenText Functional Testing Lab License capacity is based on concurrent devices. If MSP mode is enabled, capacity is based on MSP device hours.	No	Allocate quota to workspaces
OpenText Core Functional Testing Lab License capacity is based on concurrent devices	Not applicable	Allocate quota to workspaces
OpenText Core Software Delivery Platform License capacity is based on concurrent use of devices or OpenText Functional Testing Lab cloud browsers.	Not applicable	Allocate quota to workspaces

Back to top

Allocate quota to shared spaces

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

When shared spaces are enabled, you must allocate license quota across shared spaces first. The operator allocates quota to specific shared spaces, which administrators can then further allocate to workspaces within each space. For details, see Allocate quota to workspaces. The operator can allocate all, or part, of the available quantity. However, capacity that is not allocated cannot be consumed.

To allocate license quotas to shared spaces:

To set, view, and adjust the license quota allocation per shared space, select Quota Allocation in the left pane of the Licences menu of the Operator console. The grid provides an overview of license capacity. You can view the total capacity, the quota allocated to each shared space, and the consumption status for all shared spaces.

Ultimate License: Capacity is unlimited. However, you can restrict usage for a shared space by setting a fixed quota for consumption. When you create a new shared space with an Ultimate license, allocate license capacity by entering a fixed capacity for consumption, or turn on unlimited capacity.

To change the license quota allocation:

The operator can change the allocation at any stage, however, shared space quota cannot be reduced to less than the amount already consumed. To change the quota allocated to a shared space, select Quota Allocation in the left pane of the Licenses menu of the Operator console, and adjust the quota allocated.

Keep in mind the following considerations:

License	Considerations
Concurrent license	Running tests are allowed to complete before the allocation change takes effect.
MSP device hours	Within a shared space, the amount is deducted from the general bucket. If the number of device hours in the general bucket is not sufficient, capacity needs to be deallocated from workspaces before this change can take effect. Workspaces/shared spaces that consumed MSP devices hours and were then deleted are not listed in the license quota table. However, the device hours allocated and consumed by these deleted workspaces/shared spaces are included in the totals in the license quota table.

Back to top

Allocate quota to workspaces

The total license capacity for allocation across workspaces is added to the General bucket. An admin user must allocate quota to a workspace before users can access devices.

OpenText Functional Testing Lab: When shared spaces are enabled, the total capacity available to a specific shared space is determined by the quota allocation at the operator level. For details, see Allocate quota to shared spaces.

General bucket

The general bucket is a shared pool of unallocated license capacity that acts as a buffer during peak testing times. It allows a workspace to continue testing without interruption, even after the allocated quota has been reached.

To enable the general bucket for a workspace, turn on the general bucket switch to Allowed. This lets the workspace access additional capacity from the unallocated pool when needed.

Important: If you do not allocate any quota to a specific workspace and restrict it from accessing the general bucket, users assigned to that workspace cannot use any devices.

To allocate license quotas to workspaces:

Select Quota Allocation in the left pane Administration > Licenses, and set or adjust the allocation for the workspaces in your shared space.

The grid provides an overview of license consumption. View the quota allocated to each workspace, as well as how many licenses are being consumed from a workspace and from the general bucket at any point in time.

Note: If the only active license is the ADM Consumption Token license, the Quota Allocation tab is disabled.

License consumption when using quotas

When connecting to the lab, you connect to a specific workspace. You can only select devices and apps from this specific workspace, or from the Shared assets. When you connect within the context of a specific workspace, the license is consumed from the quota of that workspace (even if the device selected is a shared device). If no devices or apps were assigned to your workspace, you can access those in the Shared assets.

Back to top

Clock tampering

This section does not apply to OpenText Core SDP and OpenText Core Functional Testing Lab.

A clock is said to be tampered with when the system detects that the server's time has been moved backward. This can occur due to accidental system time adjustments, daylight saving time misconfiguration, or manual clock changes. The license system tracks the last access time (the previous time the license was used) and compares it to the current access time (the current system time). If the current time is earlier, it indicates tampering.

When OpenText Functional Testing Lab detects clock tampering, you cannot log in and any new licenses you upload will not work.

To allow your license to be usable after clock tampering:

1. Stop the server.
2. Return the clock to the original date before the change.
3. Start the server.

Back to top

See also:

• Admin
• Lab and workspace management
• Administration settings