When a licence is registered, the licence database and the platform used are linked (encrypted). The Q-DAS licence can be used as a fixed licence for a single device or as a floating licence that is shared across multiple devices (clients). This means that when a Q-DAS application is started on a device, the licence is blocked for further use until the Q-DAS application is closed.
The way in which Q-DAS applications are installed and a licence file is used depends on individual circumstances and the existing infrastructure. There are many different ways to provide Q-DAS applications and therefore how the licence can be used.
On purchase, Q-DAS sends a licence file (*.LIC) containing the products and options and the number of licences bought. The same licence file can be split so that the licences can be registered to more than one licence database on more than one platform. In other words, the splitting of a licence is required when more than one licence database is used instead of a single “global” licence database.
During registration, the Q-DAS Licensing System checks that the selected number of products and options are available for use. In principle, the Q-DAS Licensing System monitors the total number of licences purchased and in use (registered).
Start the "Q-DAS License" tool on the relevant platform.
The tool displays the currently registered products and options for the licence database connected to the "Q-DAS License" tool.
Select the licence file (*.LIC).
If already registered, check that the registered customer number matches the prefix of the purchased licence files sent by Q-DAS.
Select the products and options required to be available on this platform and click "Register".
Changing the number of licences is available for server provisioning, i.e. a concurrent network installation. For local (single) installation, only one licence per product or option can be registered. To change the number of licences, first activate the relevant product or option. Right-click on the activated item. A drop-down menu will appear on the left. Select the number of licences required.
To check that the licence has been registered, restart the "Q-DAS License" tool. It will display the selected products and options.
Examples of different installation variants with fixed and floating licences
Classic server-client provision with floating licences
All available licences in the licence file are registered for use on the server provision. The licence is linked to this platform. The clients connected to this platform can share the licences.
Floating licences in one global licence database
Multiple plants using one licence database is the case where one licence database is to be used from multiple cities/countries/regions around the world.
Each of the plants is its own server-client provision. They have installed their own Q-DAS programme files and data. But they share the same licence database. The platform linked to the licence database during registration is the provision of the Q-DAS licence database.
Floating licences in more than one licence database
This is a form of licence reservation (locking). While "Plant 1" provides the Q-DAS programme files and data on the same device, "Plant 2" uses a separate device to provide the databases. One part of a licence is linked to the "Plant 1" platform and the other part is linked to the platform that provides the Q-DAS databases for "Plant 2". The number of licences available per plant is limited. The type of installation used provides floating licences. Clients connected to a plant can share them. The use of separate licence databases also means that a client connected to “Plant 1” can no longer block licences from “Plant 2”. Or vice versa.
Fixed and floating licence
What if the connection to the global licence database is poor? And what if a client needs a licence that is always available (locked for use on a particular device)?
The storage of the Q-DAS programme files and the use of the licence is controlled by the Q-DAS Setup. There are local “single” installations for use with a fixed licence and “network” installation for use with floating licences.
The following is a description of a case where a licence file is split between three different licence databases. The Q-DAS applications and the licence database were made available using different installation variants.
“Client 1” uses programme data and files from the server-client provision but it has its own licence database. Part of the licence is registered for this platform. So the licence is blocked for use on “Client 1” only.
“Client 2” represents a device with a poor network connection. The single installation provides the Q-DAS programme files and data on this device. Part of the licence is registered for this platform. Such stand-alone installations require synchronisation of locally recorded data with a central location.
All other available licences are registered as floating licences for use on the server provision (shared network installation). Clients connected to this platform can share them.