How to update or add a server license

How to update or add a server license

How to update or add a server license

This article gives an overview about management of licenses including updating and adding new licenses.

First, copy the license file, that you have received from us by email, onto your computer.

Via lmadmin (all os, recommended)

  1. In the lmadmin web interface, go to AdministrationVendor Daemon Configuration, click on Import License
  2. Choose the new license file.
  3. Click Import License.
  4. Read the Import Information and click on OK.
  5. Back in the vendor daemon overview, click on the BIOSOLVE entry.
  6. Check, whether the new license file appears in the list General ConfigurationLicense File or Directory; now the file name should be a relative path beginning with licenses/BIOSOLVE/, see point 3 above.
  7. Restart the vendor daemon. In order to do so, click on Stop, then on Start. Only if you updated an existing license file, a click on Reread License Files is sufficient.
  8. Now the vendor daemon overview should appear with a green message “The license file was successfully reread”.
  9. You’re done!

Via lmtools (deprecated, only windows)

  1. Change license file name with the program lmtools, section Config Services.
    • If the new license file is just an update for the old license keys, remove the old license file. Always check, that you delete all license files with expired keys as those may lead to errors when a tool requests a license key.
    • If you want to use multiple license files including the new one, put all files into one directory, check that all license files have suffix .lic, enter the name of this directory into lmtools and check, that the directory entry in lmtools does not end with a \ (backslash).
  2. Don’t forget to Save Service.
  3. Switch to the Start/Stop/Reread section.
  4. Click Stop Server and Start Server.
  5. That’s all.

Via lmgrd (commandline)

  • Either run the license server with a license directory
    1. If you have started the license manager daemon with a license directory:
      % lmgrd -c <biosolveit-license-dir> -l BIOSOLVE.log

      you simply have to drop the new license file (with file name suffix “.lic”) into that directory.
      (Replace <biosolveit-license-dir> by the license directory name.)

    2. Reread all license files in that directory
      % lmutil lmreread -c <biosolveit-license-dir>

      (Replace <biosolveit-license-dir> by the license directory name.)

  • Or rename the new license file
    1. Rename the new license file to the file name of the old (current) license file. You may want to make a backup copy of your current license file first.
      Reread the license file:

      % lmutil lmreread -c <biosolveit-license.lic>
  • Or restart the license server
    1. Stop the current license server:
      % lmutil lmdown
    2. Start the license server manager daemon with the new license file:
      % lmgrd -c <new-biosolveit-license.lic> -l BIOSOLVE.log

      (Replace <new-biosolveit-license.lic> by the license key file name.)


Making the server license available to local software installations

When you have received a license extension, you only have to feed the license server with the updated file. The local installations don’t need the license again.
Otherwise, you have different options to make the license available to new or different local software installations:

  1. Installation directories
    • Just copy the license file into the directory of the software application, right beside the executable.
    • If you are using non-standard ports for the license server communication, you have to enter these ports into the license file.
  2. Environment variable
    • Set the environment variable BIOSOLVE_LICENSE_FILE to point to the server name prepended by “@”, e.g. BIOSOLVE_LICENSE_FILE=@my_server
    • If you are using non-standard ports, you have to specify the port number in front of “@”, e.g. BIOSOLVE_LICENSE_FILE=12345@my_server
  3. Other options
    Alternatively, you can use any other of the described options for the license installation of a machine-bound license.

Still stuck?