Skip to main content

t80-installing-on-premise-licence-server

installing on-premise licence server​

In some production environments, you may want to install the licence server on-premise, instead of using the cloud-based licence server. This will be needed when using the product in a dockerized environment or in kubernetes.

The licence server is called lexfloatserver and need to be installed on a bare metal server.

The docker containers running the product will then connect to the lexfloatserver to get the licence information.

download the lexfloatserver​

  • Download LexFloatServer for Windows​
  • ​Download LexFloatServer for macOS
  • ​Download LexFloatServer for Linux​

Starting LexFloatServer in terminal​

lexfloatserver -s

Note: You need admin rights to run the LexFloatServer.

Online activation​

To activate use "-a" option along with the license key and product file path (if not set in the config.yml file):

lexfloatserver -a --license-key LICENSE_KEY

Offline activation​

To activate offline use "-g" option to generate the offline activation request:

lexfloatserver -g --license-key LICENSE_KEY --offline-request FILEPATH

After generating the offline response from the admin dashboard, pass it along with "-a" option to activate the server:

lexfloatserver -a --license-key=LICENSE_KEY --offline-response=FILEPATH

references:

Activating the licence server, when no internet connection is available​

This section explains the process for activating a licence for the @opcua/for-node-red module in environments without internet access, specifically when running Node-RED in Docker. It describes the requirement to install a Floating Licence Server within the local facility, which can operate offline as long as it is accessible to the Dockerized Node-RED instances. The Floating Licence Server manages licences for multiple Node-RED instances and requires a one-time activation using a fingerprint and offline activation cypher exchange. The licence is valid for 12 months and must be renewed annually through the same offline process.

If your system does not have internet access, you will need to activate the licence server offline.

In this scenario, since Node-RED is running in Docker, you must install a Floating Licence Server within your facility. The Floating Licence Server can operate in an environment without internet connectivity, provided it is accessible to the Dockerized Node-RED instances.

The Floating Licence Server enables up to Node-RED instances to use the @opcua/for-node-red module. By configuring the appropriate environment variable, each instance will direct its licence checks to the local Floating Licence Server instead of the global cloud-based server.

Only the Floating Licence Server requires activation. The activation process is as follows:

  1. Extract a fingerprint from the local Floating Licence Server (this is a simple copy/paste operation in the console; no internet connection is required).
  2. Send the fingerprint to us via email.
  3. We will provide you with an offline activation cipher.
  4. Apply the activation cipher to the local Floating Licence Server.
  5. The server will then be fully activated and able to manage licences for your Node-RED instances.

The licence is valid for 12 months and can be renewed annually with your support subscription. Each year, you will need to repeat the offline activation process to extend the licence.

enabling opcua/for-node-red to use the on-premise floating licence server​

To enable the @opcua/for-node-red module to use the on-premise Floating Licence Server, you need to set the environment variable CRYPTLEX_FLOATING_ON_PREMISE to point to your local Floating Licence Server.

For example, if your Floating Licence Server is running on 10.20.30.40 and port 27000, you would set the environment variable as follows:

export CRYPTLEX_FLOATING_ON_PREMISE=http://10.20.30.40:27000

In a docker compose file, you can set this environment variable for the Node-RED service:

services:
  nodered:
    image: nodered/node-red
    environment:
      - CRYPTLEX_FLOATING_ON_PREMISE=http://10.20.30.40:27000
    ports:
      - "1880:1880"
    volumes:
      - ./data:/data