Setting up licenses on Windows
After you have set up the licenses, you might want to change the location of the system cache that stores the license information temporarily or if you want to add the logging details for the licensing issues that you can use to troubleshoot such issues. See Troubleshooting licensing issues.
Setting up licenses by using the Cloud License Server
Before you begin
- Purchased the licenses.
- Configured the URL of a FlexNet Cloud License Server with the appropriate
entitlements. The URL of the FlexNet Cloud License Server is in this form:
https://hclsoftware.compliance.flexnetoperations.com
- Been issued the Server ID of the FlexNet Cloud License Server.
Procedure
- Press Windows + Break to open the System Properties window.
- Select the Advanced tab, and then click Environment variables.
-
Click New under System variables and add the
following environment variables:
Environment variable Value HCL_LICENSING_URL https://hclsoftware.compliance.flexnetoperations.com HCL_LICENSING_ID The value specifies the ID of the licensing server. The ID provided is a 12-digit alphanumeric code. For example, 1234567890AB. Note: If you have set up the environment variables for previous versions of the products, you can continue to use those variables too.
Results
What to do next
- Learn how to troubleshoot licensing issues, see Troubleshooting licensing issues.
- Configure HCL DevOps Test Integrations and APIs (Test Integrations and APIs). See Configuration of DevOps Test Integrations and APIs.
Setting up licenses by using a Local License Server
When you install the product on computers which cannot access the internet and are behind a firewall, you must set up a Local License Server. You must install the Local License Server on a physical computer and not on a Virtual Machine.
Before you begin
- Purchased the licenses.
- Installed the Local License Server.
- Configured the Local License Server with the appropriate entitlements. For more information about installing and configuring the Local License Server, see the documentation for the Local License Server on the HCL® License & Delivery portal.
- Created a self-signed certificate, if you want to use the HTTPS method to check out the licenses from the Local License Server.
Procedure
- Perform any of the following actions:
-
Perform the following steps if you are using the HTTP method:
-
Perform the following steps if you are using the HTTPS method:
Results
What to do next
- Learn how to troubleshoot licensing issues, see Troubleshooting licensing issues.
- Configure HCL DevOps Test Integrations and APIs (Test Integrations and APIs). See Configuration of DevOps Test Integrations and APIs.
Setting up licenses by using a proxy License Server
When you do not want to use the Cloud License Server or a Local License Server, you can use a proxy license server that mimics either the Cloud License Server or a Local License Server.
Before you begin
- Purchased the licenses.
Procedure
- Press Windows + Break to open the System Properties window.
- Select the Advanced tab, and then click Environment variables.
-
Click New under System variables and add the
following environment variables:
Environment variable Value Description HCL_LICENSING_PROXY_URL http://<ProxyServer Host name The value points to the hostname of the proxy license server that you want to use. HCL_LICENSING_PROXY_PORT ProxyServer Port number The value points to the port number of the proxy license server that you want to use. HCL_LICENSING_PROXY_USER ProxyServer user name The value points to the user configured to use the proxy license server. HCL_LICENSING_PROXY_PASS ProxyServer password The value points to the password for the user configured to use the proxy license server. Note: If you have set up the environment variables for previous versions of the products, you can continue to use those variables too.
Results
What to do next
- Learn how to troubleshoot licensing issues, see Troubleshooting licensing issues.
- Configure HCL DevOps Test Integrations and APIs (Test Integrations and APIs). See Configuration of DevOps Test Integrations and APIs.