FlexNet Import Parser Setup and
FlexLM Usage Monitoring Overview
The FlexNet Parser feature of LAMUM is a FlexNet Manager alternative that enables existing FlexNet Manager customers to safely migrate their data to LAMUM without losing the history of data that has already been collected. This FlexNet Manager one time parser is a special tool which allows you to import your existing FlexNet License Utilization Report to LAMUM. The import utility will only work with FlexNet Manager Data in a .log or .txt format. This is only for the Flexlm license types and should be done only for features which customers wish to continue monitoring.
LAMUM needs the Raw FlexNet Data log file to parse. To generate that, follow the FlexNet Manager Setup instructions below;
FlexNet Manager Setup
To generate, start with the sample FlexNet Manager raw report;
specify the time period for the report and select the vendor daemon.
Specify the event types of Used and Denied and set the denial filtering period to 30 seconds.
Specify a Text output type.
Specify the report fields of Event, User, User Host Name, User Display Name, Count, Start Time of Event, and Duration.
NOTE: These are fixed width fields that can have the width changed, the field removed, or fields added.
Run the report and make the log file accessible to LAMUM or put it on the LAMUM server.
FlexNet Input Parser Basic Setup
Start by adding a new line item under the “Licenses” Tab, select “Flexlm” from the “License Type” menu just like you would add a new Flexlm tool.
Click on Usage tab, do a “Monitor Update”.
Navigate to Parsers à FlexNet Manager Parser.
Select the tag name from the “Select Tag Name” drop down.
Choose the “FlexNet Manager Raw Report” that has been generated in the FlexNet Manager Setup Instructions section previously and click on the “Import” button. The information should now be successfully imported.
FlexLM Usage Monitoring Overview
For FlexLM Licensing, Usage, and Monitoring in LAMUM
FlexLM is the most commonly used license checkout control daemon for shared, concurrent-use, or network-based applications in the engineering industry. When administrators share licenses there are several benefits that include;
Shared licenses are easier to administrate
The cost is lower to share licensing rather than purchasing a multitude of node-locked or user-locked licenses
Shared licenses are typically LAN (Local Area Network) or WAN (Wide Area Network).
WAN licenses are usually more expensive but cover a wider number of users than LAN licenses. WAN can be US, another specific country, or Global. LAN is typically a “site”, and is less expensive than WAN but more expensive than node-locked.
The Vendor of a shared software application contracts with Flexera to use the FlexLM license-control daemon to control access to their applications, a customer purchases from the Vendor a specific number of concurrent-use seats (licenses), and the FlexLM daemon is then mounted on a specific license server (port@host). The daemon name, port@host, authorized license count, and expiration date is specified in the Vendor license file. The Vendor creates the license file and sends it to their customer. After receiving the license file the customer installs it on their license server and the users are now able to access the application licenses up to the limit purchased.
The license file sets up and starts the daemon.
The daemon monitors checkouts (User ID, checkout time, check in time,….) up the limit purchased, through a library of books.
Once all the “books” are all checked out, a “Denial” occurs, and the user will have to wait until a license is available.
The FlexLM daemon keeps real-time status of Users, checkouts and check ins. The command “LMstat” recalls the current status of licenses at a given port@host, at that moment. Denials are captured in the Flex Debug Logs, a separate file that records all information about the specific daemon and its license checkout activity including what is in the LMstat.
LAMUM runs the LMstat command every 10 minutes (user configurable) and enables the Current Reports in LAMUM and the Debug Logs provide the data for the Denial Reports.
For additional information on Methods for Entering Licenses into LAMUM please refer to this document.