Licensing

Legacy orchestrator obtains licenses for performance sessions from an instance of the Legacy License Server (the license server for your deployment) or from Internal License Server (activation key).

In the Admin ▶ Licensing page, administrators can do the following tasks related to the license server and licenses for performance sessions:

• Legacy orchestrator License Server - SDLS
• Configure the connection to the license server
• Check the state of the connection to the license server
• View statistics related to license use by Legacy orchestrator

• Internal License Server - Integrated Server
• Enables the Legacy orchestrator functionality for creating and managing performance sessions without using a license server (SDLS).

From release 23.04 and 23.04.1 (both Legacy orchestrator Virtual Machine and Docker), the Internal License Server key is preinstalled by default.

From release 23.12 and later (both Legacy orchestrator Virtual Machine and Docker), the Licensing tab is removed in Admin. The user can create, edit, and delete sessions without Licensing being required.

When performing a fresh install, all feature keys are preinstalled; admin configurations are not required in order to access features and remove SDLS.

When upgrading from a previous release, the previous customer configuration is preserved. The admin user can install the feature keys to enable all features and remove SDLS by using internal license-server key.

For more information about the Legacy orchestrator License Server, see its user guide or online help which is available from the license server web interface.

Configuring the Connection to the License Server

In order to configure the connection to the license server, you need to collect the following information:

• IP address of the Legacy orchestrator License Server for your deployment (your license server)
• Client ID for Legacy orchestrator

To configure Legacy orchestrator connection to the license server

1. Access the Admin page and open the Licensing section.

2. Choose SDLS in License server section.

3. If you want to clear all fields used to configure the connection to the license server, click the Clear field.

4. Complete the four fields in the SDLS configuration section. For more information about how to complete the fields, see the table below this procedure.

5. When you are satisfied with the values in the fields, click the Apply button to execute the changes to the configuration fields.

Admin ▶ Licensing (server configuration)

Configuring to use Internal License Server - Integrated Server

To configure Legacy orchestrator to use the Integrated Server

1. Access the Admin ▶ Licensing page

2. Choose Integrated Server in License server section.

3. Click the Apply button to execute the Integrated Server configuration.

Checking the Connection to the License Server

If you want to ensure that Legacy orchestrator is connected to the license server - SDLS and that licenses are being acquired, you can do so as explained here.

To view the state of the Legacy orchestrator connection to the license server

1. Access the Admin page and open the Licensing section.

2. Check the Server state fields. For help interpreting the fields, see the table after this procedure.

3. Check the License statistics fields to see if licenses are being acquired.

Admin ▶ Licensing ▶ Server state and License statistics

Server state Parameters

Connection:
The state of the connection between Legacy orchestrator and the license server (at the IP address in the Licensing Server IP field).

Possible values:

• Established
• Disconnected

Current client licensing ID:
The client ID is used to identify Legacy orchestrator on the license server. It will be visible in the license server's Usage Summary field.

The default port is 1443.

License statistics Parameters

Feature name:
Legacy orchestrator feature that requires a license. Currently the only feature that requires a license is:

• Probe-Session 1.0 - Required for performance sessions. For more information about this feature, see "Performance Sessions".

Expiry date:
The date that the global license (for your deployment) expires.

Possible values:

• A particular date
• Permanent - Global license cannot expire

Required:
Number of licenses currently requested by Legacy orchestrator.

Granted:
Number of licenses currently acquired from the license server.

For the feature to function correctly, Required must equal Granted.