License Server stores and distributes license tokens to Parasoft products deployed to your network. Parasoft provides you with license passwords that you can add to and manage in License Server (administrator access required). Parasoft tools on your network can be configured to connect to License Server to retrieve a license.
Included in this section:
An upgrade license extends the access rights of the base license by providing authorized access to the newer version of a licensed tool. Its limit is determined by the number of tokens available within the base license of the specific tool. Linking licenses allows you to use base license tokens or upgrade tokens interchangeably.
For example, if you purchase five licenses (tokens) but eventually upgrade to a new version of your product, you can link the old and new product versions and use the original five licenses across both versions. You could use three license tokens for the new version and two for the old version. You could also use all five for another other distribution.
Another reason why the upgrade license should be linked to its base license is because an upgrade license can only be reserved within the base license. By reserving base license tokens, you can use either main or upgrade tokens, based on your needs. See Reserving Licenses for instructions about how to do this. Any available upgrade licenses are displayed on the Manage Licenses page.
| Tool | Parasoft tool, e.g., dotTEST, C++test, SOAtest, etc. |
|---|---|
| Version | You can access the version number from the tool's About panel. |
| Architecture | The correct architecture for which the license is assigned must be selected (for example LINUX2; this is the first part of the machine ID). |
| Expiration date | You can enter the expiration date code given to you by your Parasoft representative, the date that the license server expires, or the time for which the license is valid. Use the format: mm/dd/yyyy or mm/dd/yy. |
| Password | The password code for the license. |
Information about the added license is accessible on the Installed Tool Licenses List page. An entry about this license will be added to the .psrc.xml file (the file that records license information); this file is located in the License Server installation directory.
Click Manage Licenses to view a list of all licenses currently installed. You can also view license information on the License Server home page (see License Server Usage).
You can perform the following tasks:
Click the supported tool name link in the Installed Tool Licenses List to view the following details (also see License Server Usage):
The all status refers to the total number of installed (purchased) license tokens
You can use the filter mechanism to manage access to the available license tokens. See Filtering License Access for details.
You can manually reserve a license token and allocate it to a specific user on a specific host. Use the format specified by the tools when specifying the host. Tools on different platforms use different formats, for example, the same machine can be defined in three different ways: 10.9.1.50, gina, gina.parasoft.com.pl. You can verify the user/host format by checking the Tokens Usage Details or Licenses Usage Details report.
The user name appears in the License Reserved section. You can remove one or all selected reservations if necessary.
Machine-locked licenses bind the license token to a machine ID for 30 days. During the 30-day reservation period, no other machine can request the token.
There are two ways that machine-locked license is allocated:
You can prevent specific users or user groups from automatically reserving tokens upon request. See Filtering License Access for details.
Specify a machine ID.
Parasoft products include a utility for accessing the machine ID. Refer to your tool's documentation for instructions. |
After the 30-day reservation period, a [Remove] link will appear in the license details page. Click the link to remove the reservation and make the token available for other machines.
User-locked licenses bind a license token to a user in the order in which they are requested until they are exhausted, after which new users will not be able to obtain license tokens. Users request user-locked license tokens directly; there is no need for admins to assign them.
License tokens remain bound to the user until they are released. The user can utilize the license token on any host, though only one host at a time. License Server admins can prevent specific users or user groups from reserving tokens. See Filtering License Access for details.
License Server admins can release user-bound license tokens manually, putting them back in the available pool where they can be requested by other users.
Information about the removed license is displayed. You can also remove licenses from the License Server home screen. See License Server Usage for details.