High Availability Licensing (HAL)
To ensure fail-safe licensing (e.g. server failure or updates), it is possible to set up redundant servers that can all serve the same licenses and features. The server addresses are defined like the value LicenseServerAddress in the client license 3DVS.lic:
"HAL_SERVERS": "6200@server01;6200@server02;6200@server03",
|
The order of the servers defines the priority of availability, so the first server should be the main server with the highest availability. If one server goes down, the next server in the list will take over as long as the other server is unavailable. The Borrow functionality is only available on the main server and will be unavailable during the downtime of the main server. Our HAL configuration supports two or more servers, the default is three.
Note:
▪The list must be the same for all server configurations and client licenses. Otherwise, undefined behavior occurs. ▪Please inform us about changes in your HAL configuration to keep your license up to date. To do this, send an email to orders-viewer@kisters.de with your server names, selected ports, the serial number of your license. Internet Protocol Version
The VS License Manager supports both versions of the Internet Protocol (IPv4 or IPv6). Which one is preferred can be defined here:
History Settings
The history data (maximum usage and denials) is updated frequently, but only every eight hours by default to reduce server load. This can be changed in the preferences:
"HISTORY_UPDATE_HOURS": 8,
|
Similar to the log file archive cleanup, it is possible to automatically remove old history data. This includes only real-time data, which occupies most of the history data space. This setting is disabled by default:
"HISTORY_ARCHIVE_COUNT": 0,
|
Heartbeats and Timeout
To ensure continued use of checked-out features, the VS License Manager uses heartbeats.
▪Use HEARTBEAT_SECONDS to configure how often heartbeats are sent from clients. The default is 2 minutes and 20 seconds. ▪TIMEOUT_SECONDS allows you to configure when a client should timeout after the last heartbeat has been successfully received. The default is 5 minutes. ▪Use HEARTBEAT_CONTROL_SECONDS to configure how often the server checks for client heartbeats. The default is 3 seconds. If you have a large number of clients, this value can be increased slightly to reduce server load. In the configuration file, these values will look like the following:
"HEARTBEAT_SECONDS": 140,
"TIMEOUT_SECONDS": 300,
"HEARTBEAT_CONTROL_SECONDS": 3,
|
|