About VirtServer Licensing

The way you activate, use, and manage licenses depends on the license type.

VirtServer license types

VirtServer, from version 3.16 onwards, uses two types of license:

  • SmartBear ID-based - These licenses are part of SmartBear's proprietary SmartBear License Management solution. To request and install a license on the product, a user needs to specify their access credentials based on the location of the SmartBear License Server.

    • Where the customer plans to use SmartBear-hosted license, customer will need to assign a license to the VirtServer administrator, use the administrator’s access key when requesting a license and ensure the machine VirtServer is installed on can access the SmartBear license servers. This is the current default support option for SmartBear ID-based licenses in VirtServer.

    • Where customers plan to host the license server for on-premise deployment, customer will need to export the SmartBear ID-based license for on-premise use and point to that location when requesting a license.

    • To view and manage the account settings, use the new SmartBear License Management Portal.

  • File-based - This is the licensing model that you are most familiar with. These licenses involve using a SmartBear license file. You apply that file on your computer to activate the license, or consume the license from the license server running in your network and is licensed with this file.

ID-based licenses for existing users

The following table helps you understand the difference between ID-based and file-based licenses:

Feature

ID-based

File-based

Activation procedure

License is purchased, assigned in manage.smartbear.com.

Where the customer plans to use SmartBear-hosted license, customer will need to assign a license to the VirtServer administrator in manage.smartbear.com, use the administrator’s access key when requesting a license and ensure the machine VirtServer is installed on can access the SmartBear license servers. This is the current default support option for SmartBear ID-based licenses in VirtServer.

Where customers plan to host the license server for on-premise deployment, customer will need to export the SmartBear ID-based license for on-premise use and point to that location when requesting a license.

The user gets a license file from SmartBear and uses this file to activate the license on their machine.

Binding to computer

The license is bound to a user, not to a computer.

Users can easily switch between the machines and instances through installing and uninstalling as required. The license can only be used on a single instance once unless you have agreed otherwise with SmartBear.

The license is bound to one workstation or server.

Activation on another machine means deactivation of the current one.

License subtypes

ID-based licenses can be online or offline.

File-based licenses can be Fixed User and Floating.

Using on multiple machines

License can be easily switched between user machines: to use the product on another computer, one just needs to uninstall it on the current machine and install on the other machine.

An easy switch is possible for Floating licenses only.

Fixed User licenses must be deactivated first.

Control of use

Usage is managed through SmartBear-hosted license servers by default. For offline use, the license needs to be converted so it can be hosted and used on your network.

Fixed User: by the licensing subsystem of your ReadyAPI instance.

Floating: by the standalone License Manager running in the local network.

Work in private networks

Support for offline licenses is included in VirtServer 3.16 release. License activation requires licensing administrator connection to the SmartBear Licensing Portal and converting for on-premise use.

Supported. License activation may require a connection to the SmartBear License Servers.

Managing users

In the SmartBear Licensing Portal or in the On-Premise License Server installed in your network.

In the standalone License Server.

Further reading

Flie-Based Licenses

SmartBear ID-Based Licenses

Publication date: