Ports

The communication between the VS License Manager and the 3DViewStation clients uses the TCP network protocol. The TCP_PORT setting defines the port used:

The License Monitor, the web interface of the VS License Manager, can be accessed via a web browser: <License Server Address>:<HTTP_PORT>. The HTTP_PORT setting determines the HTTP port used:

Note:

▪The specified local ports must be opened in the server's firewall for the VS License Manager to function properly. The required protocol is TCP for both ports.

▪If you are using ports other than the default, please let us know so we can keep your license up to date. To do so, send an email to orders-viewer@kisters.de with your server name, the TCP port you are using, and the serial number of your license.

Passwords

To access the Admin view of the License Monitor (including logs, configuration overview, and checkout history), a password must be configured:

Note: The password is sent in base64 encoding only, so please choose a unique password that will be used only for the VS License Manager.

Optionally, it is possible to configure a main password. With this setting enabled, even the basic License Monitor will prompt for a password before displaying any information:

Logging

The location of the VS License Manager log files can be changed using the LOG_PATH parameter. The path can be absolute or relative with a leading "./":

The log format can be specified with the eponymous parameter:

The alternative log format to NORMAL is RESTRICTED, which suppresses writing usernames, host names and IP addresses to the log file and displaying them in the License Monitor. For support cases, it is possible to convert recent log files from normal to restricted format using a button in the License Monitor.

It is possible to configure the number of days before old log files are removed:

The default is 90 files, which is equivalent to 90 days or 3 months. If you never want log files to be removed, set the value to zero.

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:

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:

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:

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: