Server software licensing information

You can find information about the licensing on HCL OneTest™ Server.

To use the features offered by HCL OneTest™ Server, you must purchase the following licenses:

  • Named user

  • Concurrent Virtual Service

Named user licenses

As a Team Space Owner, you can configure the License Server and add users to the Named Users list for the team spaces.

The Named user licenses are automatically self-acquired on a first-come-first-serve basis. The licenses are always available for the users who are added to the Named Users list. Also, those users can perform the project tasks in their team space even though the Disable automatic self-acquisition of named user licenses checkbox is cleared in the Team Space License Configuration page. However, the other users receive an error notification about the unavailability of the license when they try to perform the project tasks.

Remember: A single Named user license is used from the total number of Named user licenses when you perform most of the operations in HCL OneTest™ Server.
Important: You can perform only the following operations in team space without using a license:

  • Configure the License Server

  • Modify the user roles in a team space

  • Delete the team space

Remember: The Named user license is returned to the license pool only under any of the following conditions:

  • When the Named user is no longer a member of any team space.

  • When the Named user is removed as a user of HCL OneTest™ Server.
    Important: The Named user license can take a few minutes to return to the license pool.

Concurrent Virtual Service licenses

HCL OneTest™ Server requires an additional license to use the service virtualization feature. You must have sufficient Concurrent Virtual Service licenses to run instances of virtual services that are contained in API Suites on HCL OneTest™ Server.

A single Concurrent Virtual Service is used from the total number of Concurrent Virtual Service licenses when any of the following events occur:

  • An instance of a virtual service is started by running a virtual service resource. A license is consumed for every running instance of the virtual service.

  • An API suite is run that has a scenario that references a local virtual service and the scenario begins

The Concurrent Virtual Service license is returned to the license pool when the virtual service instance stops.

For example, consider you decided to have three team spaces including the initial team space, then you must configure the licenses required for each team space on the License Server based on your requirement. You must then use the URL and ID of those License Servers to configure the licenses for the team spaces.