All Mistika licenses are "floating licenses". This means that you can use the license of one computer in any other computer on your network, as long as the network connection is available and the number of open Mistika sessions does not exceed the number of licenses.


When a computer is using a remote license, the license will be freed as soon as the Mistika application is closed. 


To configure a remote license server:


Configure the license server in the remote server:  In the license server you do not need to do anything special, just install Mistika as usual. Just make sure that it is visible to the client computers in the same network.


Configure the clients:  Use the SGOActivationTool->LicenseServer-Settings Wheel to indicate the ip address of the license server. 


That should be enough, now opening Mistika in a client system will get the license from the remote license server, and the license will be freed immediately after closing it.



ADVANCED USAGE (for linux experts)


Redirecting to a remote license server by using an Environment variable: This method is not normally required (as the easy method is to use the SGOActivationTool ). But advanced users may want to use it as a command line in text mode,  or within their own scripts, or for diagnostic purposes:  You can define the current license server with this environment variable: SGO_ELMHOST


Example (bash):  If the ip of the license server is 192.168.1.10 then you could execute this in the client:


export SGO_ELMHOST=192.168.1.10


And any mistika products launched in that context will get the license from the license server at 192.168.1.10



Configuring Mistika Ultima license servers on systems that are not installed with Mistika iso:   Mistika Ultima is a special Mistika product, as Mistika Ultima is a turnkey system that need to be installed with the Mistika installation iso (including the operating system). However, some clients may have an agreement with SGO to install the license server for Mistika Ultima in a separate server that can not be installed in this way (for example if they already have a license server for other 3rd party products and want to add Mistika Ultima licenses on it).  For this particular case you can do the following:


Note:  This method will work on linux systems based on CentOS 7.xxx or RedHat 7.xxx.  It should also work in other linux systems as long as they have compatible libraries, and support for daemons based on systemd (otherwise the client will need to implement the daemon on his own way ). 



1 - Install Mistika Ultima in the client systems as usual (Mistika installation iso and Mistika latest upgrade )


2 - Install the latest Mistika version in the license server system (in any linux user as you prefer, but it needs to be in graphics mode). 


Please note that you may need to repeat this every time that you install a new version in the clients (when the license server have changed in the new version).


Note:  The system may be automatically rebooted at the end of the upgrades.  This will happen on first installation, and in some cases at the end of some upgrades.  But if you do not want this to happen then you can install the related files manually by copying them from a client system. (see the reference files in next section)



3 - Get the LMData identifier of the license server (either with the SGOActivationTool or by executing the getlic command).   And send it to licenses@sgo.es indicating your company details.  Then you will receive a new license file for the new server. 


- If the license server has internet connection it will get the licenses automatically.  


- The license is also sent by email.  If the server does not  have internet connection, you can use the SGOActivationTool to install the license manually.  


 Alternatively (for example if you do not have access to the server in graphics mode), you can install the license file by putting it in this location: 


/var/flexlm/sgoLicenseV5.dat   


And then restart the license server as root user:


su

killall -9 sgoLicenseServer.bin

/var/flexlm/bin/sgoLicenseServer.bin &




5 - Once you have installed the new license file, redirect the clients to use the new license server as explained above. Either by using the SGOActivationTool->LicenseServer-Settings Wheel or by using the SGO_ELMHOST environment variable.




Mistika files related with the license server


For your reference, these are the important files related with the license server on linux. In principle you could configure a license server by installing all these files manually (getting those files from a Mistika Ultima system), but if you choose to do that you will need to install it and maintain it on your own:


/var/flexlm/sgoLicenseV5.dat (this file contains all the licenses for all Mistika products , one per line ).  The expiration dates and the hostid (mac address of the license server) are also indicated on each line, which can help on license diagnostics.


/var/flexlm/bin  (this folder contains the license server,  plus all the necessary libraries for it )


/etc/systemd/system/sgoLicenseServer.service  (this is the daemon that starts the license server at boot time. If you plan to launch it in other way then please note that the license server needs to be started after the network services )


/var/flexlm/bin/sgoLicenseServer.bin  (this is the license server itself, it is normally launched by the sgoLicenseServer.service daemon, although you can also launch it manually   )


/home/mistika/bin/getlic (this is used to get the system id (LMDATA code).  The output is always different (this is perfectly normal).  It can be used to get an LMDATA when you can not use the SGOActivationTool  (when not having access to the server in graphics mode). 


/home/mistika/MISTIKA-ENV/bin/SGOActivationTool  (Provides a GUI to manage licenses).