About the MVTec License Serverđź”—
The MVTec License Server enables network licensing for MVTec products.
The core functionality is a HTTP(S) server that can be contacted by HALCON applications to request a license session.
It is a command line application, which can be run by a user or as a service.
Note that in contrast to standard licenses, each floating license can only be used by a single instance of an application.
For example, you can only run a single HDevelop with one license.
The MVTec License Server is available in two variants, solely depending on the used licenses. The License Server On-Premises uses an USB dongle, whereas the License Server Cloud-Ready uses an internet connection to a cloud backend as anchor of trust.
Compatibilityđź”—
The MVTec License Server is available for HALCON Progress edition starting with version 22.05 and for HALCON Steady edition starting with version 22.11.
Since version 24.01, the MVTec License Server can be used as “Cloud-Ready” variant for HALCON 23.11 and newer, which is intended for running it in environments like public clouds, where no physical access (to plug in the dongle) to the server is possible.
Version 24.11 of the MVTec License Server is required for HALCON starting with version 24.11.
Under Windows, floating licenses must be returned actively by the licensed application when it is stopped to avoid a time-out (default: 240 s) before reusing the license is possible. See the chapter “Returning Floating Licenses on Windows” in the HALCON Programmer’s Guide (available since HALCON 23.11).
System requirementsđź”—
| Linux | Windows | Note | |
|---|---|---|---|
| CPU | x64-sse4@1 GHz | x64-sse3@1 GHz | |
| Memory | 1 GB | 1 GB | |
| Disk space | 300 MB | 300 MB | |
| OS version | Kernel 3.x, glibc 2.17 (including Docker container) | 10, 11, Server 2016 to Server 2022 | |
| Wibu CodeMeter version | 8.20 | 8.20 | See the Wibu documentation . |
| HALCON version | ≥ HALCON 22.05 Progress ≥ HALCON 22.11 Steady |
≥ HALCON 22.05 Progress ≥ HALCON 22.11 Steady |
This is the first version supporting HALCON 24.11.
Additional requirementsđź”—
| License Server On-Premises (with dongle) |
License Server Cloud-Ready (no dongle, cloud backend is used instead) |
|
|---|---|---|
| Installation of CodeMeter Runtime | required | required |
| Access to physical dongle | required | not required |
| Internet access to cloud backend | not required | required |
Connection to the internet is only required by the License Server itself and the communication direction is only from inside to the cloud side. No licensing details are exposed to the cloud side. Clients connect only to the License Server.
This configuration has been tested serving 500 licenses.
Note
Setting up the MVTec License Server in a particular cloud environment requires specific knowledge on the part of the person performing the task. Generally, MVTec cannot support this free of charge.