Filter
Top Products
Licensing in Prolifics
58 2-Tier Installation
` lmstat — Monitors the status of all licensing activity.
` lmswitchr — Switches the log file for the specified feature.
` lmver — Reports the FLEXlm version of a library or binary.
Licensing in Prolifics
Prolifics components use local or remote licensing schemes and are defined as
follows:
` Local licensing is when the license file for the application resides on the same
machine as the Prolifics component being used.
` Remote licensing is when the license file for the application resides on a
different machine from the Prolifics component being used.
The setup program recommends a default licensing scheme for each Prolifics
component. If you accept the default, the setup program guides you through the
appropriate steps to obtain a permanent license file. You can choose a different
scheme if your license administrator recommends it. In this case, the setup program
requests contact information, and the Prolifics License Desk will contact you or
your license administrator to arrange for licensing. Default license schemes are:
Component name Platforms Licensing scheme
Prolifics client UNIX Local
Prolifics web application server UNIX
Windows NT
Local
Local
License Daemons and License Types
The license daemons are programs that manage the license types that allow limited
access to users. License daemons are only required for node-locked counted and
floating licenses. Thus, only the Prolifics development client requires daemons,
and the license daemons always run on the license host machine.
The license type and number used at your site was determined when Prolifics was
purchased.
The two types of daemons are:
` License daemon (lmgrd) — Manages the license file and starts the vendor
daemon prold. Only one license daemon can be active for a given license
Types of
Daemons