User guide

Chapter 1 - Introduction and Overview
The License Request Process
18 FLEXnet Licensing End User Guide
The License Request Process
When you run a counted FLEXenabled application, the following occurs:
1. The license module in the FLEXenabled application finds the license file, which includes
the host name of the license server machine and TCP/IP port number of the license manager
daemon,
lmgrd.
2. The FLEXenabled application establishes a connection with the license manager daemon
(
lmgrd) and tells it what vendor daemon it needs to talk to.
3.
lmgrd determines which machine and TCP/IP port correspond to the master vendor
daemon and sends that information back to the FLEXenabled application.
4. The FLEXenabled application establishes a connection with the specified vendor daemon
and sends its request for a license.
5. The vendor daemon checks in its memory to see if any licenses are available and sends a
grant or denial back to the FLEXenabled application.
6. The license module in the application grants or denies use of the feature, as appropriate.
Uncounted features (where the license count is 0) do not require a license server, and the
FLEXnet Licensing client library routines in the application grant or deny usage based solely
upon the contents of the license file.
lmtools.exe Optional component. Graphical user interface for
FLEXnet Licensing utilities,
lmutil.exe. Also
available from www.macrovision.com.
lmgr10.dll
Required if the FLEXenabled application is
dynamically linked.This library provides the
standard FLEXnet Licensing client library routines.
flexid.exe or
flexidsilent.exe
Required if vendor supports FLEXid hostids.
flexid.exe is used to install FLEXid drivers for
use with FLEXid dongles. Alternatively, the vendor
may supply
flexidsilent.exe to silently install
the drivers as part of the software installation.
Table 1-1: FLEXnet Licensing Components for End-User Distribution
Component Description