License descriptions
The usage of base product and test extensions are enabled by floating licenses, whereas schedule runs can be enabled by floating. With floating licenses, multiple users can use the product; however, the total number of concurrent users cannot exceed the number of floating licenses you purchase.
When a software order is placed and acknowledged, a software entitlement is created for the user. a license server deployment in My HCLSoftware (MHS) and map the licenses to the deployment through the MHS. Every Deployment is associated with a server ID or deployment ID. This server ID or deployment ID is applied in the product. Multiple software entitlements can be created based on the requirements.
You can use any of these licenses according to your requirements:
- Floating license to use the product:
To use the product, you need a Test Performance floating license or you can also use a Test Workbench floating license. A floating license is checked out when you use the product and is returned to MHS when the license is not used for 15 minutes.
- Floating licenses for test extensions:
For Test Performance, in addition to the license for product usage, if you use SOA, SAP, and Citrix test extensions, you need separate software entitlements. You can map all the entitlements to one server ID. With Test Workbench license, you can use the above test extensions without the need for separate entitlements. A license is checked out from the time the product is opened by the user. The license remains checked out until the user closes the product. When the user closes the product, after 15 minutes, the license is returned to the MHS.
- HCL DevOps Test Workbench - Virtual Users:
These are floating licenses that are purchased in blocks of 100 virtual users each. After the run, the licenses are checked back in to the server. For example, if you have 200 DevOps Test Workbench - Virtual Users available, you can run schedule A with 100 virtual users and schedule B with 20 virtual users, leaving 80 virtual users for other team members to use for schedule execution using the same license server. After the schedule run completes, the all the virtual users are returned to the server for others to use.
You can add more virtual users or change the rate of execution during the test or schedule run only if there are sufficient number of Virtual User licenses or if a sufficient number of VU-Hours are on balance in the customer's account.