What is FLEXlm? What is FlexNet? OpenLM support of FLEXlm
This document relates to the FlexLM / FlexNet Publisher license manager, and discusses OpenLM’s capabilities in supporting this license manager.
General
FLEXlm software is a prominent license management solution that enables software vendors to impose restrictions on the number of software seats available to their customers. FLEXlm supports different licensing policies such as Floating (aka Concurrent) and Node Locked licenses. This type of software system is also referred to as DRM (Digital Rights Management) Solutions . FLEXlm was originally a joint development of GLOBEtrotter Software and Highland Software in 1988. GLOBEtrotter was then acquired by Macrovision in 2000, which renamed the product FlexNet. In 2008 the company was sold to Acresso Software, and it’s name was changed to Flexera. The product was named Flexera FlexNet Publisher, but is still widely referred to as FlexLM. In 2011 the Canadian Teacher’s Private Capital fund acquired Flexera.
OpenLM monitoring and management of FlexLM / Flexnet Publisher
With FlexLM being as prominent as it is, it has implicitly set up a de-facto mod d’emploi standard in the field of license management. OpenLM has taken much care in supporting the different aspects of FlexLM monitoring and management, often exceeding Flexera’s proprietary tool in doing so.
Flexnet License Manager operation
The general structure of the Flexnet license manager is shown below:
LICENSE SERVER MANAGER
lmadmin or lmgrd FlexLM daemons are supplied either by the licensed FLEXenabled application publisher or by Flexera Software. Its job is to communicate with the application, and receive the license request from it. It then passes the request to the vendor daemon.
VENDOR DAEMON
Created by the publisher, and is unique to each FlexEnabled application installed on the network. It is the vendor daemon’s job to process the license request and to either grant it or deny it, depending on the number of available licenses, and predefined license usage constraints.
LICENSE FILE
Created by your software supplier, and holds detailed license information such as the quantity and time extent of the license
TRUSTED STORAGE
Some publishers provide trusted storage as an encrypted alternative to using license files.
DEBUG LOG AND REPORT LOG
FlexNet logs written by the license server manager (lmadmin or lmgrd), typically accounting the license check-outs and check-ins, and license denials.
OPTION FILES
Files created by license administrators to restrict license usage to specific users or user groups.
Why do you need software license management?
The need for effective software license management usually originates from one of the following business problems:
- High software expenses and a desire to reduce software spend
- Uncertainty about the the benefit of new licensing models
- Concerns about compliance with vendor licensing agreements
- Lack of knowledge about what software you have in your organization
OpenLM’s Software Licensing Tools
OpenLM is a software licensing tool that is meant for organizations that use engineering software, particularly engineering software that is licensed under a concurrent licensing model. Regarding license inventory, OpenLM does the accounting for you automatically and lets you know exactly what you have paid for – vendor, product and features – including the features you’ve bought but never used. OpenLM Software license management will give you the opportunity to cancel software license feature renewals that no-one needs. OpenLM empowers the user organization to implement software metering by which engineering application usage can be monitored, audited and reported. You can reach higher efficiency and maximize usage of your software licenses while reducing instances of denied licenses when your engineers cannot check out a license. See also software licensing tools.
License Managers and License Monitors
A common mistake made by people responsible for the administration of software licenses is in believing that the license manager software provided by the vendor ensures optimal use of the software. The main purpose of such software management software is to prevent concurrent use of the software beyond what the licensing agreement has defined. For more information about software license management and OpenLM’s license management tools, contact us.
Enquire More or ask for Demo
FAQ
FLEXlm (often pronounced “Flex-L-M”) is a widely used software license management system originally developed in 1988. Over time it was rebranded as FlexNet Publisher, and both names are still used interchangeably in the industry.
FlexLM / FlexNet runs a license server that tracks and controls software license usage. It works with a license server manager, vendor daemon, and license files to grant or deny license requests based on availability and usage rules.
FlexLM supports different licensing models such as floating (concurrent) and node-locked licenses, enabling efficient sharing or dedicated use of software across networks.
Because it has become an industry standard for engineering, CAD, simulation, and other high-value software, many major vendors embed FlexLM / FlexNet license controls in their applications.
Vendor daemons are application-specific processes that enforce licensing rules, while license files include the parameters like number of seats and expiration dates that define how the product can be used.
Yes — it logs check-outs, check-ins, and denials through debug and report logs, helping administrators understand how licenses are consumed.
FlexLM was developed by GLOBEtrotter Software and Highland Software. After acquisitions and rebranding, it became FlexNet Publisher under Flexera Software — though “FlexLM” remains a common industry term.
Yes — OpenLM fully supports monitoring and managing FlexLM / FlexNet Publisher, often providing deeper usage insight and optimisation features compared to vendor-provided tools.
By centrally managing licenses and tracking usage, FlexLM helps ensure compliance with vendor agreements and reduces costs through efficient utilisation of available licenses.
Not exactly — its primary purpose is to control license usage and prevent concurrent access beyond what the license terms allow, but it is not designed as an anti-piracy tool in the broader sense.