• Skip to main content
  • Skip to header right navigation
  • Skip to site footer
CDP Studio logo

CDP Studio

The no-code and full-code software development tool for distributed control systems and HMI

  • Doc
  • Why CDP
    • Software developers
    • Automation engineers
    • Managers
  • Products
    • Automation Designer
    • HMI Designer
    • CDP Linux
  • Services
  • Use cases
  • Pricing
  • Try CDP

CDP Studio Documentation

  • Framework - License Server
  • License Server Manual
  • 5.1.1

Framework - License Server

License Server Manual

Overview

Use RuntimeLicenseServer in the application that should act as a runtime license source. Applications that do not have local feature license files can then run by accepting licenses from a reachable license source on the same network.

Typical Use

  1. Add the LicenseServer library to the application that should serve licenses.
  2. Add a RuntimeLicenseServer component to that application.
  3. Install a valid local license_server feature license on that application.
  4. Install local feature licenses on that application for each feature it should serve to others.
  5. Start the source application and the consumer applications on the same controller network.

Consumer applications do not need a RuntimeLicenseServer component. They only need access to a reachable and properly licensed source application.

Behavior

  • Local licenses always take precedence over runtime-served licenses.
  • One good license source is enough. If multiple sources are present, a synchronized valid source is sufficient.
  • Applications can receive runtime licenses even when the source application uses a different application domain.
  • After an application has become licensed from a runtime license source, it continues running for the current start even if that source later disappears. The next start still requires either a local license or a reachable license source.

Controller Clock Synchronization

Runtime license sharing depends on controller clocks being kept closely synchronized.

  • When the controller time difference is less than 3 seconds, the consumer application clears its license alarm.
  • When the controller time difference is 3 seconds to 1 minute, the consumer application keeps running but shows a warning that controller time is not synchronized and the next start may fail.
  • When the controller time difference is greater than 1 minute, the remote license is not accepted and the application remains unlicensed unless it has a local license.

Use NTP or PTP to keep controllers synchronized. For normal operation, target a time difference well below 3 seconds.

Requirements

  • Only applications with a valid local license_server license can act as a license source.
  • A source can only serve features for which it also has valid local licenses.
  • Adding RuntimeLicenseServer alone does not enable license serving. The required local licenses must also be present.

Framework - License Server

The content of this document is confidential information not to be published without the consent of CDP Technologies AS.

CDP Technologies AS, www.cdpstudio.com

Get started with CDP Studio today

Let us help you take your great ideas and turn them into the products your customer will love.

Try CDP Studio for free
Why CDP Studio?

CDP Technologies AS
Hundsværgata 8,
P.O. Box 144
6001 Ålesund, Norway

Tel: +47 990 80 900
E-mail: info@cdptech.com

Company

About CDP

Contact us

Services

Partners

Blog

Developers

Get started

User manuals

Support

Document download

Release notes

My account

Follow CDP

  • LinkedIn
  • YouTube
  • GitHub

© Copyright 2026 CDP Technologies. Privacy and cookie policy.

Return to top