This glossary lists terms that are specific to LM-X License Manager.
| Term | Description |
|---|---|
| Client application | An application program that requests or receives a license. |
| Contact | A customer's contact person. |
| Customer | A company that orders licenses from a Vendor. |
| End user | A machine defined by a set of HostIDs, for example a personal computer, server, virtual machine, or any other equipment running licensed software. |
| Feature | Any functionality that needs to be licensed. The definition of feature is developer-dependent, according to the application and to the developer's requirements. For example, a feature can consist of:
|
Floating license | A license that can authorize usage of an application for users on a network. A license server is required to manage a floating license. With this type of license, the number of concurrent users is counted with the licensed application usable by only a specified number of users at any time. A variation of this scheme is a license that can be locked to work both with specific client computers and with a specified server computer. A floating license is sometimes referred to as network licensing. |
| Heartbeat | A message sent from the client application and acknowledged by the license server to ensure that both the license server and the client are still up and running. This action is triggered periodically. |
| HostID | A unique machine value that can be used to lock a license file to a specific host. |
| License | A text file shipped to an end user, which provides one or more features. Features contain information about specific modules in your program that are licensed. Each feature in a license has its own key, where all security information is encrypted. |
| lmx-serv | A process that serves licenses for clients over a network. Sometimes referred to as a license server. |
| Log file | One or more ASCII text files written by a license server. A log file contains status information useful for debugging purposes. |
| Node-locked license | A license that can authorize use of an application running on a single specific machine, as opposed to being on a network. Node-locked licenses do not require a license server because they are uncounted. A node-locked license is sometimes referred to as local licensing. |
| Security configuration file | LM-X security configuration file. A file, specific to the vendor, which holds cryptographic keys and is used for generating licenses and for generating specific files required for compiling the client application. Created by the developer tool lmxdev. |
| Terminal Server Client | A Terminal Server Client, also known as a Remote Desktop, is a Windows feature that lets you administrate Windows on a remote host. From a licensing point of view, this may be prone to abuse if a few people are running the application simultaneously. |
| Vendor name | The name of the vendor that is used in license files. |
| Unix system | Refers to Linux, Solaris, HP-UX, AIX and FreeBSD platforms. (See PLATFORMS for more platform-specific information). |
| Windows system | Refers to Win32 or Win64 platform. |