Monokot Server 1.x
  • What is Monokot Server?
  • Quickstart
  • 🐸Basics
    • Supported OS and Hardware
    • Installation
    • Licensing
    • OPC UA
      • UA TCP Endpoint
      • UA Settings
      • Client Certificates
      • Aliases
      • Access to Object Settings
      • Troubleshooting
    • Security Certififcate
    • Users & Roles
    • Administrator GUI
      • Event Log
      • Users in Monokot Server Administrator
      • Roles in Monokot Server Administrator
    • Startup Parameters
  • 🦊Tags & Devices
    • Devices
      • Diagnostics
      • Devices in the Monokot Server Administrator
    • Tags
      • Parameters
      • Change Trigger
      • Tags in Monokot Server Administrator
        • Go Online
        • Group Action
        • Import & Export
    • Modbus Connectivity
      • Parameters
      • Addressing
      • Diagnostics
    • Siemens Connectivity
      • Parameters
      • Addressing
      • Access to DBs area in S7-1200/S7-1500
    • IEC 60870-5-104 Connectivity
      • Parameters
      • Addressing
      • Time Conversion
      • Diagnostics and Commands
    • OPC UA Connectivity
      • Parameters
      • Addressing
      • Diagnostics
      • How to: Importing OPC UA items
      • How to: Pulling Security Certificate
    • InfluxDB Connectivity (Connector)
      • Parameters
      • Addressing
      • Query Result and Data Mapping
      • Diagnostics
      • How to: Configure for InfluxDB 2.x
    • SNMP Connectivity
      • Parameters
      • Addressing
      • UDP Considerations
  • 🐺Time Series & Stores
    • Stores
      • Backlog
      • Diagnostics
      • Stores in Monokot Server Administrator
    • Time Series
      • Parameters
      • Deadband
      • Sampling
      • Last Sample Repeat
      • Time Series in Monokot Server Administrator
        • Group Action
        • Import & Export
    • InfluxDB Connectivity (Store)
      • Parameters
      • Addressing
      • Data Structure
      • About Metadata
      • Diagnostics
      • How to: Configure for InfluxDB 2.x
    • PostgreSQL Connectivity
      • Parameters
      • Addressing
      • Database Design
      • Data Compression
    • REST Connectivity
      • Parameters
      • Addressing
      • Message Script
      • RestRequestMessage
      • DataContext
      • TimeSeries
  • 🐻Scripts
    • Overview
    • Expression
      • Parameters
      • Import & Export
      • Go Online
    • Programming Examples
      • How to: Calculate Arithmetic Mean
      • How to: DoNothing
      • How to: Writing to Tag
      • How to: Inverting Bits
      • How to: Execute SQL
      • How to: Run Ping
      • How to: Do Simulation
      • How to: String Formatting
      • How to: OPC UA Method
      • How to: Initialize Device Settings from File
    • API
      • Bundle
      • BundlePair
      • Context
      • DataMap
      • DataMapPair
      • DataTriggerInfo
      • Expression
      • MosCrypto
      • MosDirectories
      • MosFiles
      • MosOdbc
      • MosOdbcReader
      • MosProcess
      • MosProcessExecuteResult
      • MosText
      • MosUtils
      • ValueState
Powered by GitBook
On this page
  • Installing a Hardware License
  • Installing a Software License via the Monokot Server Administrator
  1. Basics

Licensing

Server communication features such as Modbus Connectivity or InfluxDB Connectivity are licensed server components. Licensing is performed using software or hardware keys. Software license keys are perpetual and assigned to a specific device. Without a purchased license, server can operate in two modes:

  • with limited functionality

  • with full functionality for 3 hours

When connectivity switches to demo mode, the following warning will appear in the server event log: Demo timer for 'XXX Connectivity' started. Demo time expires in 180 minutes. Upon expiration of the demo period, the warning Demo period for 'XXX Connectivity' has expired will appear in the event log and all tags using this connectivity will go into the BadLicenseExpired status.

To reset the demo period timer, you have to restart the service/process/daemon or reinitialize the server. To reinitialize the server in Monokot Server Administrator, connect to the server and click the Reinitialize Server button on the General tab.

Components licensing and limitations (summary table)

Component

Licensing Method

Limitations

Modbus Connectivity

By number of tags used

Up to 16 tags / Up to 1 device

Siemens Connectivity

By number of tags used

Up to 16 tags / Up to 1 device

InfluxDB Connectivity

By total number of tags and time series used

Up to 16 tags (time series) / Up to 1 device (store); Immediately switches to demo mode when attempting a historical read (using OPC UA)

MongoDB Connectivity

By number of time series used

Up to 16 time series / Up to 1 store

REST Connectivity

By number of time series used

Up to 16 time series / Up to 1 store

PostgreSQL Connectivity

By number of time series used

Up to 16 time series / Up to 1 store; Immediately switches to demo mode when attempting a historical read (using OPC UA)

Oracle Database Connectivity

By number of time series used

Up to 16 time series / Up to 1 store; Immediately switches to demo mode when attempting a historical read (using OPC UA)

MS SQL Connectivity

By number of time series used

Up to 16 time series / Up to 1 store; Immediately switches to demo mode when attempting a historical read (using OPC UA)

MySQL Connectivity

By number of time series used

Up to 16 time series / Up to 1 store; Immediately switches to demo mode when attempting a historical read (using OPC UA)

SNMP Connectivity

By number of tags used

Up to 16 tags / Up to 1 device

IEC 60870-5-104 Connectivity

By number of tags used

Up to 16 tags / Up to 1 device

OPC UA Connectivity

By number of tags used

Up to 16 tags / Up to 1 device

Expressions (Scripts) Plugin

Only special features require licensing

The feature immediately switches to demo mode if extra functions are called (from MosUtils.setXXXProperty, MosOdbc, MosDirectories, MosFiles, MosProcess objects); Immediately switches to demo mode when trying to call the method (using OPC UA)

Installing a Hardware License

Please note that the current server version does not support hardware keys for ARM64

Installing a Software License via the Monokot Server Administrator

First, you need to obtain the Device ID for the server on which you want to install the license. To do this, connect to server and on the Server Explorer pane click on General. Go to the Licenses tab, click on Save Device ID As... button and specify the path and the file name; that way you will save the Device ID of the target server to your computer.

In the menu of the main window, select Tools → Activation Wizard, and the license activation wizard will open. Follow all of the steps listed by the activation wizard. Upon completion of the activation process, you will receive an email (within 10–15 minutes) with the license file. Save it to your computer.

On the Licenses tab, click on the Upload License(s)... button. A window for uploading the licenses to the server will open. Click on the Browse… button, select one or more license files, click on the Upload button and wait until the files are uploaded. To complete the licensing process, restart the server service/process/daemon.

PreviousInstallationNextOPC UA

Last updated 5 months ago

A license must be purchased for each physical device that hosts the server. It is linked to the device using the Device ID, which is generated using a special procedure. Licenses cannot be transferred from one device to another; if after activating the license the device malfunctions (or its components), please contact .

The hardware license key is a driverless device, so you just need to connect the USB-dongle to your computer and restart (or reinitialize) the server. If you need an extra feature after purchasing a hardware key, the key can be upgraded remotely. Thus, there is no need to purchase an additional hardware key. To upgrade your hardware key please contact .

🐸
support@monokot.io
support@monokot.io