This section explains the basics of floating (network) licensing, and gives a quick overview of the components of FLEX lm . It explains where system administrators have control and where end users have control. The section Getting Started Checklist describes how to start managing FLEX lm for both system administrators and end-users.
FLEX lm is a network license manager used by many software developers to control the use of their software products. FLEX lm allows software licenses to be available (float) anywhere on a network, instead of being tied to specific machines. Floating licensing benefits both users and system administrators. Users can make more efficient use of fewer licenses by sharing them on the network. System administrators can control who uses the licensed application, and the node(s) where the licenses will be available.
The license manager daemon (
lmgrd ) handles the initial contact with the client application programs, and passes the connection on to the vendor daemon. It also starts and restarts the vendor daemons. FLEX lm permits multiple redundant license manager daemons on different server nodes, allowing you to make your license available only if any two out of three server nodes is running. The lmgrd eliminates the necessity of splitting your licenses among multiple servers or of relying on any one machine.
In FLEX lm , licenses are handled by running processes. There is one process for each vendor who has a FLEX lm -licensed product on the network. This process is called the vendor daemon . The vendor daemon keeps track of how many licenses are checked out, and who has them. If the vendor daemon terminates for any reason, all users lose their licenses. Users normally regain their license when
lmgrd restarts the vendor daemon.
Client programs communicate with the vendor daemon through TCP/IP or UDP/IP sockets. The client (where the application runs) and the daemon processes (the license server) can run on separate nodes on your network. Also, the traffic between the client and the license manager daemon is machine-independent, allowing for heterogeneous networks. This simply means the license server and the workstation running an application can be either different hardware platforms or different operating systems.
Licensing data is stored in a text file called the license file. The license file is created by the system administrator. It contains information about the server nodes and vendor daemons, and at least one line of data (called a FEATURE line) for each licensed feature. Each FEATURE line contains an encryption code based on the data in that line, the hostids specified in the SERVER lines, and other vendor-specific data.
Users can override this location by setting the environment variable
LM_LICENSE_FILE to point elsewhere, or by following instructions supplied with the licensed application. If your site has software from multiple vendors with incompatible license files (due to different sets of servers), you can keep the data in separate files and set the
LM_LICENSE_FILE variable to reference multiple files. For details, refer to License File .
The application program using FLEX lm is linked with the program module (called the FLEX lm client library) that provides the communication with the license manager daemon. During execution, the application program communicates with the vendor daemon to request a license.
Additionally, the system administrator can reserve licenses for specific users, nodes, or groups, and control other license-related options. See section Options File for more detailed information about changing parameters.
Note: Refer to your vendor's documentation before attempting to change file names locations, or contents.
This section provides a quick overview of how to set up and use licensing for FLEX lm -licensed products. By scanning the list, the system administrator should be able to quickly find the areas of interest. Cross-references point to more details in other parts of this manual.
This section describes how to set up licensing on your system or network. If you are an end-user of the application, and you are not involved in the installation process, go to Notes for end users .
Note: The installation guide for your application software supersedes these instructions for installing and configuring FLEX lm .
Before running any FLEX lm -licensed program using floating licenses, you will need to set up your license server node (or nodes). You must select which node or nodes to run your license servers on, and provide the hostid of those machines to your software vendor. For pointers on selecting your server machine, see Selecting Server Nodes .
Obtain the hostid of the server machine by running FLEXlm's lmhostid utility on that machine. If you don't havelmhostid , you can obtain the hostid of your machine by using the appropriate command as described in Hostids for FLEXlm-Supported Machines .
· If you have multiple FLEX lm -licensed products, avoid licensing conflicts. For more detailed information, see Combining License Files .
· Unless your software vendor selected a default location for your license file, you can use any location you wish. For more detailed information, see License File .
· Some vendors provide special scripts to start up the license daemon. If not, you can run the
lmgrd program directly. To start
lmgrd automatically at boot time, you must modify your system files. For more detailed information, see Specifying Location of the License File .
Globetrotter Software supplies administration tools to your software vendor. The vendor usually includes them with their product. The recommended location for the tools is /usr/local/bin , but you can install them in a different location (or not at all). See User Commands for more information.
The options file controls various options such as reservations and timeouts of licenses. Most users run without an options file, but you may decide you want to use some options. For example, many administrators use an option to limit the quantity and content of logged messages. To set up an options file, see Options File .
For information about the standard way of specifying a license file for an application, see License File .
To find out who is using a license run lmstat , as described in User Commands .