FLEXlm End User Manual: Chapter 1 Introduction and Overview

FLEXlm End User Guide — August 2004 11 Chapter 1 Introduction and Overview This chapter explains the basics of floating (network) licensing and gives a quick overview of the components of FLEXlm. It explains where license administrators have control and where end users have control. Many translated example sentences containing 'flexlm end user manual' – German-English dictionary and search engine for German translations. Look up in Linguee; Suggest as a translation of 'flexlm end user manual'. Look up words and phrases in comprehensive, reliable bilingual dictionaries and search through billions of online.

Full pathname of the end-user specified options file for this daemon. (See Chapter 5, `The Options File' on page 31.) FLEXlm does not require an options file. The keyword `options=' requires a v5+ vendor daemon. If the vendor daemon is FLEXlm v6 or later, the options file need not be.
The products currently on your network is licensed by FLEXlm. About This Manual This manual explains FLEX lm for administrators and end users and describes how to use the tools which are part of the standard FLEXlm distribution kit. Macrovision Corporation also provides the SAMsuite and SAMreport asset.

Personal tools

Table of Contents * Index * Next Chapter

This chapter explains the basics of floating (network) licensing, and gives a quick overview of the components of FLEXlm. It explains where license administrators have control and where end-users have control. A section called `Getting Started Checklist' on page 4 tells both license administrators and end-users how to start managing FLEXlm.

1.1 Introduction to FLEXlm

FLEXlm is the most popular license manager used in the software industry. FLEXlm is best known for its ability to allow software licenses to be available (or float) anywhere on a network, instead of being tied to specific machines. Floating licensing benefits both users and license administrators. Users can make more efficient use of fewer licenses by sharing them on the network. License administrators can control who uses the licensed application, and the node(s) where the licenses will be available. See Section 2.4, `Types of License Files,' on page 19 for details about the different licensing models supported by FLEXlm.

Flexlm End User Manual

1.1.1 FLEXlm Components

The four main components of FLEXlm are:

license manager daemon
vendor daemon
license file
application program

The License Manager Daemon (lmgrd)

The license manager daemon (lmgrd) handles the initial contact with the client application programs, passing the connection on to the appropriate vendor daemon. It also starts and restarts the vendor daemons. FLEXlm permits multiple redundant license manager daemons on three server nodes, allowing you to make your license available if any two out of the three server nodes is running. Redundancy can be achieved with 3-server redundant servers, or by using a license file list with any number of servers.

Flexlm End User Manual 11.13 Free

lmgrd is not present on VMS or Netware systems.

The Vendor Daemon

In FLEXlm, licenses are granted by running processes (unless they're node locked, uncounted, in which case they need only read the license file to run). There is one process for each vendor who has a FLEXlm-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 (though this does not mean the applications suddenly stop running). Users normally regain their license automatically when lmgrd restarts the vendor daemon, though they may exit if the vendor daemon remains unavailable.

Client programs communicate with the vendor daemon, usually through TCP/IP network communications. The client application and the daemon processes (the license server) can run on separate nodes on your network, across any size wide-area network. Also, the format of the traffic between the client and the vendor daemon is machine-independent, allowing for heterogenous networks. This means the license server and the computer running an application can be either different hardware platforms or even different operating systems (Windows and Unix, for example).

The License File

Licensing data is stored in a text file called the license file. The license file is created by the software vendor, and edited and installed by the license administrator. It contains information about the server nodes and vendor daemons, and at least one line of data (called FEATURE or INCREMENT lines) for each licensed product. Each FEATURE line contains a license key based on the data in that line, the hostids specified in the SERVER lines, and other vendor-specific data.

So, if the noise level is under a threshold, the microprocessor U in the radio detects the DC level and un-mutes the radio.Operational Cautions Antennas Do not use any portable radio that has a damaged antenna. A repair constitutes something done internally to the unit that would bring it back to its original condition.This manual also for: Exposure awareness can be facilitated by the use of a product label directing users to specific user awareness information. Motorola mag one a9 user manual software.

In some environments, the licensing information for several vendors may be combined into a single license file. The default location is:

End-users can usually 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.

The default location should be used with caution: setting LM_LICENSE_FILE may actually cause applications to fail if their license is located in the default location, but that location is not included in LM_LICENSE_FILE. This is because setting LM_LICENSE_FILE removes the default location from the license file list.

It's strongly recommended that you keep a copy or link (on Unix) of the license file in the vendor's `default' location, so that users will not need to set LM_LICENSE_FILE to run their applications. For details, see Chapter 2, `The License File' on page 7.

The Application Program

The application program using FLEXlm is linked with the program module (called the FLEXlm client library) that provides the communication with the license server. On Windows, this module is called LMGRxxx.DLL, where xxx indicates the FLEXlm version. During execution, the application program communicates with the vendor daemon to request a license.

1.1.2 The License Request Process

Flexlm End User Manual Pdf

When you run a `counted' FLEXlm-licensed application the following occurs:

The license module in the client application finds the license file, which includes the host name of the license server node and port number of the license manager daemon, lmgrd.
The client establishes a connection with the license manager daemon (lmgrd) and tells it what vendor daemon it needs to talk to.
lmgrd determines which machine and port correspond to the master vendor daemon and sends that information back to the client.
The client establishes a connection with the specified vendor daemon and sends its request for a license.
The vendor daemon checks in its memory to see if any licenses are available and sends a grant or denial back to the client.
The license module in the application grants or denies use of the feature, as appropriate.

`Uncounted' features (where the number of licenses is 0) do not require a server, and the FLEXlm client library routines in the application grant or deny usage based solely upon the license contents.

Flexlm License Manager

1.1.3 Configuring FLEXlm

Most of the parameters of FLEXlm are configurable by the license administrator. The license administrator can set:

the location of the license file (though it's recommended that a copy or link of the license remains at the location where the application expects it)
the location of all executables
the location of all log files
the TCP/IP port number used by the license manager process, lmgrd.

In additi