Import the driver's license
The driver checks its license itself, without a network and without activation. The license is a file with
the extension .lic that you receive when you buy the driver at wvds.it. It applies to the driver, not to a
single data source: in one of the places below, it covers every data source and application of the user or
of the machine.
Without a valid license, the driver still works fully. The first 30 days from the first connection are an evaluation period; after that, only a notice remains. No connection fails and no query waits because of the license.
Solution overview
The driver reads every *.lic file in these places, in this order, and adds the licenses up:
| Place | Applies to | Suited for |
|---|---|---|
File or folder in the environment variable WKL_LICENSE_PATH | whoever the variable reaches | deployment by IT, special locations |
%APPDATA%\WKL\Licenses\ | the signed-in Windows user | single workstations; “Import license” copies here |
%PROGRAMDATA%\WKL\Licenses\ | all users of the machine | software distribution, Group Policy |
An application that ships the driver can also bring the license and put it in these places when it starts; the driver then finds it like an imported one.
Import the license on a workstation
Prerequisite: the driver is installed, and a data source with the driver Wkl OData is set up or is being set up.
- Open ODBC Data Sources in the bitness of your application, for example from the Start menu (“ODBC Data Sources (64-bit)”).
- On the User DSN tab, select a data source with the driver Wkl OData and choose Configure…. If there is none yet, choose Add… and Wkl OData.
- At the bottom of the dialog, choose License….
- Choose Import license… and open the
.licfile.
Result: Below the list, the dialog says which license with which revision was imported and where it is
(%APPDATA%\WKL\Licenses\<license>-r<revision>.lic). The list shows the new result, for example
“Licensed (LICENSED)”. A notice in the data source dialog disappears at once; the application doesn't have to
restart.
The “License” dialog with a valid license for 20 workstations (development build, test license from the shop with a key of the test environment).
A file that isn't a valid license isn't copied. The line below the list then names the file and a code, for
example E10_SIGNATURE_INVALID for a changed file; include this code when you contact the manufacturer.
Store the license for all users of a machine
- As an administrator, create the folder
%PROGRAMDATA%\WKL\Licenses\if it doesn't exist. - Copy the
.licfile into it, for example through software distribution or Group Policy.
Result: Every user of the machine is licensed from the next connection on; the License dialog shows the license for every user.
Alternatively, set the environment variable WKL_LICENSE_PATH to the file or to a folder with licenses, for
example a share that only IT can write to.
What the driver shows
| Result | The driver |
|---|---|
| Licensed | works without a notice |
| Evaluation (no license for the driver, first 30 days) | shows the days left |
| No valid license (after the evaluation) | shows a lasting notice |
| Maintenance ended | shows that this build was released after maintenance ended; builds released up to the end of maintenance stay licensed |
| Term ended (license with a term) | shows the end of the term |
The notice appears in the data source dialog, in the Connect dialog and in the sign-in form whenever one of them opens anyway, and in the trace. It names the reason and the way out: import a license or buy one at wvds.it. It never stops anything.
Notes
- No binding to the machine. The license contains no hardware characteristics. Moving to a new machine or reinstalling needs only the file.
- The quantity is shown, not counted. How many workstations a license covers is stated in the license and the contract; the driver doesn't count.
- Maintenance. A license states up to when released builds are covered (“Updates until”). A build released before that date stays licensed for good, even after maintenance ends.
- Evaluation per user. Its start is kept in
%APPDATA%\WKL\Evaluation\odata-odbc.json. - Copy for support requests. The list in the License dialog can be selected and copied, for example for a request to the manufacturer. It contains no prices and no email addresses.