# License type and use

MonolixSuite2016R1 licenses can be of the following types:

• Individual license – named user. The named user can install and run MonolixSuite2016R1 on a computer.
• Server license – concurrent access. MonolixSuite2016R1 run on an application server and a predetermined number of users can use it at the same time.
• Floating license – concurrent access. The license is hosted by a license server, and MonolixSuite2016R1 can either run on a server or individual workstations.

In any case, a license key number or file is generated. Notice that the license request is only done when no license is available on the user’s computer or when the license expires.
Two folders are key {MonolixSuite2016R1}/config/system/access and {MonolixSuite2016R1}/bin/Monolix_mcr/runtime/config/system/access, where  {MonolixSuite2016R1} corresponds to the directory where MonolixSuite 2016R1 is installed. In the following, these folders will be refereed as KeyFolder1 and KeyFolder2 respectively.

The activation key (provided by Lixoft) must be entered in the dialog box titled “Lixoft license activation” (“With activation key” tab).

In that case, the license is copied into {UserName}/lixoft/license. The dialog box only appears when no license is available on the user’s computer or when the license expires. Our software is available with independent licenses for Mlxplore, Monolix and Simulx if you just need a particular product. We also propose a license for the Monolix Suite for you to take full advantage of the integrated visualisation, modelling and simulation features.

When do I need an individual license ?

Two main cases

• when the user accesses to MonolixSuite with its own computer
• when the user accesses to MonolixSuite through a remote access and wants its own dedicated license.

In that case, MonolixSuite runs on an application server. The activation key (provided by Lixoft) must be copied into the following folders of the server: KeyFolder1and KeyFolder2.
With that, each time a user starts an application of MonolixSuite, it takes a token from the license for the application under consideration. If all tokens are used (too many users use the software), a popup titled “Lixoft activate” appears and the user is supposed to add its own license or buy other licenses to increase the number of tokens for the server license.

When do I need a server license ?

Two main cases

• when the user accesses to MonolixSuite through a remote access. In that case, all the license management is defined by the IT.
• when the user accesses to MonolixSuite through a shared directory (via CIFS, Network drive, NFS, …). In that case, if the IT provides Lixoft with all the MAC address of the users, Lixoft can provide a dedicated license key to the IT in order the user not to have to provide a license key when running.

The use of a floating license requires to set up a license server. Two utilisations are possible:

• when the user accesses to MonolixSuite with its own computer and just need a license that points toward the license server. In that case, the IT provides the user a license key (using the license server management system)  to copy it into {UserName}/lixoft/license folder,
• when the user accesses through a remote access or a shared directory. Then, the license key is provided by the IT (using the license server management system) and should be copied into KeyFolder1and KeyFolder2.

The setup and configuration of the license server is described here.

RLM has the ability to allow a floating license to roam to a system which will subsequently be disconnected from the network for a short period of time. The resulting license can be used for the number of days specified when the license was set to roam, and is checked back in automatically at the end of this. In addition the user can return the roamed license back to license pool early if this is desired. See License activate tools (which can be launched from the Monolix interface, in tools menu)

This feature is enabled on demand. An extra activation key will be provided by Lixoft and the procedure to get the roaming license feature is identical to the installation of a floating license. To enable this feature, the file system.xmlx (stored in both KeyFolder1 and KeyFolder2 directories) must be modified by setting to “on” the roaming option:

<?xml version="1.0" encoding="utf-8"?>
<monolix>
<preference>
<session>
<userPath windows="%USERPROFILE%" linux="\$HOME"/>
</monolix>