QLM Enterprise provides support for floating licenses using two different approaches: (a) for simple installations with 100 or less concurrent users, we recommend that you use the network share model where the concurrent license information is stored on a network share at the customer site and (b) for larger installations, we recommend that you use the QLM Web service model where you install the web service along with a database at the customer site.
You can as well support floating licenses with QLM Pro if your application is guaranteed internet access when it is launched and when it exits. Note that this limitation does not exist with QLM Enterprise.
The steps to implement floating licenses with QLM Pro are:
1. Create an Activation Key and set the "Number of Activations per Key" to the required number of floating licenses.
2. When your application starts up, call ActivateLicense to activate the license key
3. When your application exits, call DeleteKeysEx (false, true, false, false, out errorMessage) then call ReleaseLicense.
This will work if at the time the application starts and exists, the computer has internet connection.
Say a user with a laptop starts the application before leaving the office while he has an internet connection. A license is checked-out and acquired by his laptop. He then closes his laptop without closing the application and leaves the office. The checked-out license remains checked-out by his laptop. He then travels and uses the application as expected. If he closes the application and reopens it while no internet connection is available, the license remains checked-out by his laptop and he can use the application at will. Upon his return to the office, when he closes the application, his license is checked-in and is returned to the pool of licenses available to other users.
You can find a sample that demonstrates this capability here:
C:\Users\Public\Documents\Quick License Manager\Samples\qlmpro\Windows\DotNet\C#\QlmProFloatingLicense
If you implement floating licenses using QLM Pro, it is recommended to set the historyTableLogRelease and historyTableLogUpgrade Server Properties to false. To do so: