Setting up licenses for DevOps Test Integrations and APIs

Before you can start using HCL DevOps Test Integrations and APIs (Test Integrations and APIs), you must set up and apply the licenses.

When you use Test Integrations and APIs or the non-GUI applications such as RunTests or IntegrationTesterCmd, a Test Integrations and APIs floating seat license is consumed. This is a portable license that is consumed on-demand, enabling several users and applications to time-share a license. With this license, you can open a project, view, edit, and run resources on the computer on which you have installed Test Integrations and APIs. When you close the application, this seat is released within 15 minutes.
Note: If the license is not used for 15 minutes, the license is returned to the License server for others to consume it. If the product loses connectivity to the HCL® License & Delivery portal, you can use the product for two hours only if the server ID that you entered last time is correct.
You must add the License Server as an environment variable on the computer on which you want to run the Test Integrations and APIs assets. You might want to run the assets on any of the following computers:
  • On which you have installed Test Integrations and APIs.
  • On which you have installed Docker.
  • On which you have installed Test Integrations and APIs Agent, if the computer is different from the one on which you installed Test Integrations and APIs.
Configure the environment variables as described in the following table:
Environment variable Description Value
HCL_LICENSING_URL The value specifies the URL of the licensing server. The value depends on the method you used to configure the license server.

For example, if you used the Cloud License Server, the value can be as follows: https://hclsoftware.compliance.flexnetoperations.com

HCL_LICENSING_ID The value specifies the ID of the licensing server. The ID is a 12-character alphanumeric identifier provided by HCL for the product licenses you purchased.
Note: If you have set up the environment variables for previous versions of the products, you can continue to use those variables too.