User guide

Chapter 1 - Introduction and Overview
FLEXnet Licensing Components
FLEXnet Licensing End User Guide 15
Figure 1-2 shows this model. See “Component Overview” for a description of each
component.
Figure 1-2: FLEXnet Unserved License Component Model
The FLEXenabled application and license certificate reside on the same machine.
Component Overview
The License Manager Daemon (lmgrd)
The license manager daemon (lmgrd) handles the initial contact with the FLEXenabled
applications, passing the connection on to the appropriate vendor daemon. It also starts and
restarts the vendor daemons.
Chapter 6, “The License Manager Daemon,” contains information for configuring and starting
the license manager daemon in your environment.
The Vendor Daemon
In FLEXnet Licensing, counted (floating) licenses are granted by processes running on the
system. There is one process for each vendor who has a FLEXenabled 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.
FLEXenabled applications communicate with the vendor daemon, through TCP/IP network
communications. The FLEXenabled application and the daemon processes (the license server)
can run on separate machines on your network, across any size wide-area network. Also, the
format of the traffic between the FLEXenabled application and the vendor daemon is machine
independent, allowing for heterogeneous 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).
License
File(s)
FLEXenabled
Application
FLEXnet Licensing Client Library
Your
Application
Code