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 server
manager,
lmgrd.
2. The FLEXenabled application establishes a connection with the license server manager
(
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.
FLEXidInstaller.exe Required if vendor supports FLEXid hostids on
Windows platforms
aksusbd-redhat-1.5-1.i386.rpm Required if vendor supports FLEXid hostids on Red
Hat Linux version 8 and 9 platforms.
aksusbd-suse-1.7-2.i386.rpm Required if vendor supports FLEXid hostids on
SuSE Linux platforms.
HDD_Linux.tar.gz Required if vendor supports FLEXid hostids on Red
Hat Linux 7 platforms.
HDD_Unified_Installer_sit.hqx Required if vendor supports FLEXid hostids on Mac
OS X platforms.
Additional Windows Components
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.
Table 1-1: FLEXnet Licensing Components for End-User Distribution
Component Description