Configuration and maintenance

Setup and operation of the library and the servers

These pages go into technical details about how you configure

  1. QuidLM software library to use in you application

  2. QuidLM license server, should you choose to operate it

  3. QuidLM license definition and delivery server, also known as QuidLM mint

Getting started

The software is packaged into QuidLM.zip archive, and the first step is to unpack it. The main components are

Name Description
build_all.sh The setup script
test_floating_server.sh The testing script that verifies that QuidLM has been configured correctly
setup/ The directory containing setup and administration utilities
client/ The library for communication with the servers, to embed (link) into your software; code samples that demonstrate the library usage in C, C++, C#, and Java
server/ The floating license server
mint/ The license definition and delivery server

The build_all.sh script sets up the software libraries that empower your application with QuidLM technology. The script requires you to specify your company name on the command line - the name will distinguish licenses for your software from licenses of other software vendors. The script produces several things:

  1. Public and private key pair - this pair will allow you to cryptographically sign and verify your licenses, as well as to communicate with license servers securely. The files will have your company name and .pk and .sk extensions. The .sk files must be kept secret, as the file content allows you to create new license files, and you want to be the sole owner of that power.

  2. Example applications that use your company name and the above cryptographic keys to demonstrate the QuidLM functionality. That is done by compiling the code samples in C, C++, C#, and Java. For this step to succeed, you need the C compiler to be available (which means that it needs to be in one of the directories listed in the PATH environment variable). If you make C++, C#, and Java compilers available on your computer, then each of those programming languages will also produce an example application that demonstrates QuildLM usage in that language.

  3. Example licenses for the floating license server and example products for the order fulfillment server.

The build_all.sh script takes less than a minute to accomplish all those tasks. It describes its progress and finishes by running the test_floating_server.sh script, which starts the floating license server and uses each of the sample applications built in the previous step to procure a floating license and to hold it for 2 seconds. If all goes well, it gives you a command line to start the license server and invites you to visit the control panel of the license server in a browser.