Managing Licenses on the Edge – Flexera’s New product

The exploding growth of the Internet of Things (IoT) has brought massive change to license and security management. Even the smallest sensor has one or more software drivers, and there is growing recognition that the true value in the device or product lies in its use and the execution of the embedded software, rather than the device itself. New revenue models based on consumption rather than sale of capital-intensive assets are being adopted by industrial device and product manufacturers. Manufacturers of CT scanners recognise that small-scale hospitals and clinics cannot afford the capex for their hardware, so an alternative where the scanner is leased and the hospital is charged when scans are done is becoming popular. This has created a move to licenses embedded in the devices side-by-side with the software that drives the device. There are billions of “things” that are already connected via the Internet, and the volumes are increasing exponentially. This has created a new challenge, managing the data.

The Data Avalanche and How to Contain it

All the machines participating in the IoT have one purpose, to feed back data to a central source. This is creating huge volumes of data which are measured in petabytes and zettabytes. In principle, this data is streamed back via the cloud to data centers located in remote sites across the globe. In reality this model does not work:-

  • not all data gathered by a sensor is required real-time
  • Distance is not dead; the time taken to transmit a message to a data center and receive a reply may not meet requirements, especially because it is the cloud provider that directs the message, not the owner or vendor of the sensor
  • Some data is very time-critical, and needs low latency to get a response to the message, for instance, a pacemaker sensing a pending cardiac arrest needs an immediate reaction
  • Many devices are kept offline, due to security or connectivity constraints
  • Each connected device is a cyber risk which could allow hackers to infiltrate the main ecosystem

The answer to mitigate these risks is edge computing and edge computers.

What is Edge Computing and will it Destroy the Cloud?

Edge (or fog) computing takes processing close to the device (Fog computing is a descriptive synonym for edge computing, coined by Cisco, and while there are differences in how fog and edge network, the principles are basically the same, so we use edge here to cover both edge and fog).

Edge is both a halfway house to the cloud and a pre-processor that can return a response to the device in time-critical situations. There are those that believe that edge computers will displace cloud computing, while others believe that the two will always co-exist. Typical edge hardware is designed for high availability and very powerful, with GPUs to process data rapidly. Obviously, to perform as required, it needs its own software for various activities, including:-

  • polling sensors to send data,
  • evaluating and consolidating the data (rather like the ETL of a data warehouse)
  • application processing for time-critical responses (e.g. avoiding an accident for an autonomous vehicle)
  • and even AI and machine learning to provide business intelligence and to improve its own performance.

Where there is software, there must be a license, which must be managed, and Flexera have identified the need and devised a solution.

Flexera Edge – Managing Connected and Unconnected Devices

The development of a product to manage licenses on the edge makes good sense, when you consider this statement made by Gartner in 2017.

Currently, around 10% of enterprise-generated data is created and processed outside a traditional centralized data center or cloud. By 2022, Gartner predicts this figure will reach 50 percent.

They recently revised this statement (October 2018).

Currently, around 10% of enterprise-generated data is created and processed outside a traditional centralized data center or cloud. By 2022, Gartner predicts this figure will reach 75 percent.

IDC, in their predictions for IoT for 2018 stated

Prediction 7: By 2020, IT Spend on Edge Infrastructure Will Reach up to 18% of the Total Spend on IoT Infrastructure, Driven by Deployments of Converged IT/OT Systems That Reduce the Time to Value of Data Collected from Their Connected Devices

This, coupled with the concerns about Cyberthreats mentioned in the same report, makes it extermely good sense to be focusing on edge computing as the place where asset, entitlement and license management should be happening:-

Prediction 1: By 2020, the Potential Cybersecurity and Physical Safety Concerns Associated with IoT Devices Will Pressure CIOs at G2000 Companies to Increase IoT Security Spending by up to 25%, Temporarily Neutralizing Business Productivity Gains

Flexera have heeded the call and developed a product for managing devices at the edge.

The reasoning behind the product is simple:-

  • There already are billions of devices out there that need software enhancements and fixes updated. Some of these updates may be very occasional, but other devices may require updates daily or even more frequently.
  • The zettabytes of data reaching the edge should be aggregated and analysed and the distilled result should be relayed up to the cloud. This implies that edge computers will carry their own portfolio of software that enables them to perform AI and self-learn.
  • The customization of devices by applying rules in embedded software within the device as to what features the organization or even a single user signed up for, means that universal updates are no longer viable.
  • Entitlement management has to be applied in conjunction with the software update
  • Managing this from the cloud is impractical and unwieldy, because there are so many devices to which updates must be streamed.
  • Managing this manually is completely impossible.
  • Keeping software current is just not good enough; for some industries, it has to be proven that the latest release is the one being used. This is a requirement from the FDA, but may well be taken up by other authorities.
  • All the above applies to disconnected devices too.

An edge computer is the best platform for managing and controlling the software assets of devices that network to it. It can manage the updates for both connected and disconnected devices, without opening them up to cyberrisk, report on the current state of its IoT community, what software versions are out there, who is actually using them and which features and alert to any aberrations.

This means that the edge computer itself must be extremely secure and resistant to threats and attacks. From a physical perspective, and because many edge devices are situated in industrial locations, the computers themselves are ruggedized and housed in protective cages and lockers. Logically, there must be a resilient and resistant security infrastructure that will ward off cyber attacks within the edge computer logic. If the edge computer is secure, the devices it manages have a reduced risk of attack. If there is a direct attack on a device, the edge computer should be able to quarantine it and prevent the virus or infection from spreading.

Changing the Licensing Landscape

The traditional licensing landscape is still adapting to the changes imposed by factors such as cloud computing, BYOD and embedded software. The traditional setup of the on-site license server that controls perpetual and named licenses is inappropriate for the IoT, and will have to make way for new models that permit edge computers to oversee license and entitlement. While the emphasis is on monetizing the software that drive the IoT devices, the administration of who owns the licenses, what their entitlements are  and what software version they are using still need to be managed. A consolidated view of the feedback of all the edge computers for the organization is also a necessity. There will be many new licensing and asset management products reaching the market in the next few years as the demand for applications that can manage IoT licensing and entitlement grows, joining Flexera in this new niche.

Please follow and like us:

OpenLM monitoring of Aveva PDMS and Aveva Marine licenses.

Aveva PDMS and Aveva Marine environments

Aveva Marine is a comprehensive suite of software modules for offshore and shipping construction projects. It integrates several views and disciplines into a single project space for superior visualization and integrity between the project components.

Aveva PDMS provides similar capabilities for 3D plant designing. Users are able to select, place, assemble and check the integrity of complex 3D plant schemes.

Aveva licensing

  • Prior to the 12.1. series’ version, AVEVA Marine and AVEVA Plant (PDMS) employed the Flexera Flexnet manager (FlexLM) concurrent license manager to dispense and keep track of floating Aveva licenses. OpenLM fully supports FlexLM license monitoring.

  • In the 12.1 series, Aveva has drifted from the FlexLM solution to the Sentinel RMS license management tool to manage their floating licenses. They still kept the lmutil tools within their installation folders, but from our experience – running these lmutil lmstat commands produced empty results.

  • Instead, license usage information could be obtained by the Sentinel RMS command:  lsmon.exe (In fact – we needed to upgrade the lsmon.exe version to “Sentinel RMS Development Kit 8.5.3.0035 Application Monitor” in order to match our Aveva version). OpenLM fully supports Sentinel RMS license monitoring.

  • Another surprise Aveva 12.1 had stored for us was the license file, which was a type of hybrid between FlexLM and RMS. It was in XML format and contained the following headers:

<?xml version=”1.0″ encoding=”utf-8″?>

<CompositeLicenseFile xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema”>

<Hostname> … </Hostname>

<RMSlicenseFile> … </RMSlicenseFile>

<FlexLicenseFile> … </FlexLicenseFile>

<ProductFeatureMappingFile> … </ProductFeatureMappingFile>

<ARMS_ID> … </ARMS_ID>

<RevokeList> … </RevokeList>

</CompositeLicenseFile>

Please follow and like us:

Application Note 2011: Quick Installation guide for the OpenLM license management system v1.8

The OpenLM Floating license monitoring and Usage optimization tool interfaces an ever growing variety of license managers, such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, LM-X and Easycopy.

Step 1: Installation

The OpenLM System components are available for download on the OpenLM site. After filling in your name and email, you would be directed to the download section. Select the OpenLM Version 1.8 section:


And start by downloading the server:

When downloading is complete, double click the downloaded *.msi file and follow the standard installation instructions.

Step 2: Configuring License Servers

When the installation is complete, click:

Windows’ Start → All Programs → OpenLM → Server → OpenLM Server Configuration

The OpenLM Server configuration window opens.

1. Add in your license servers:

  • Click the ‘Add’ button,

  • Type in the License server’s host name or IP (e.g. lm10) and Port number (e.g. 27000)

  • Select the new License server’s type (e.g. FlexLM)

  • Type in an informative name (e.g. “lm10 – ArcGis server”)

  • Select the license server’s time zone (e.g. UTC+1)

The image below demonstrates this configuration:

 

2. Select a license server and click the check button in order to ensure that OpenLM can retrieve information from that license server. This information is the input received from the License manager.

3. Repeat steps 1 & 2 for all license servers.

4. Click ‘Apply’, and “Restart now”.

Step 3: The OpenLM EasyAdmin Interface

The EasyAdmin web application is the main OpenLM Administrative and user interface.

You can find it on:

Windows’ Start → All Programs → OpenLM → OpenLM EasyAdmin2.

The OpenLM EasyAdmin opens. Click the EasyAdmin start button to explore this application’s features.

The image above is an example of an EasyAdmin workspace. It features Administrative tools, License data, License usage data, Graphic usage representation, Roles and permissions’ assignment, and Active Agent capabilities.

For more information on the OpenLM EasyAdmin web interface, please refer to this document.

Congratulations!

You now have an up and running OpenLM system.

For further information regarding the installation and preliminary configuration of the OpenLM system components, please refer to the “Application Note 2010: OpenLM license management system Complete Installation guide v1.8” document.

Revision table

Revision

Author

Date

Remarks

0.1

Orik

Apr 23,  2013

Preliminary

Please follow and like us:

OpenLM Version 1.8 Screenshots

OpenLM floating license monitoring tool

The OpenLM Floating license monitoring and Usage optimization tool interfaces an ever growing variety of license managers, such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, EasyCopy, ProgeCAD and LM-X.

The OpenLM system consists of a number of modules. An overview of these modules’ function is found here. This document presents a screenshot appearance of the main OpenLM modules.

EasyAdmin

The EasyAdmin user interface is accessible from any standard internet browser, e.g.:

Mozilla FireFox, Microsoft Internet Explorer, Opera, Apple Safari & Google Chrome.

EasyAdmin Control Panel

The control panel allows users to get system status information in a single glance:

  • License server status.

  • OpenLM Broker status on each license server.

  • General statistics on license on daily and weekly license usage.

  • One-glance status of critical feature over multiple license servers.

  • Alerts system messages.

The control panel features a Windows-like interface that allows easy access and management of Windows on a standard browser interface.

EasyAdmin – Widgets – License Servers

License servers’ information includes the license manager status and the status of the OpenLM broker installed on the license server machine.

EasyAdmin – Widgets – Host availability

Host availability indication diagram provides the full information regarding the server’s activity over time.

OpenLM EasyAdmin – Widgets – Selected features statistics

OpenLM EasyAdmin – Widgets – Feature usage status

This window allows you to easily see the number of licenses used, the number of licenses borrowed, and the license-usage percentage. It’s easy to add features by using the filter.

EasyAdmin – Widgets – Alerts

The alerts window sends notifications if any problems occur with the OpenLM server.

OpenLM EasyAdmin – Management -Licenses window

The licenses window lists available licenses, and allows easy management of the organizational assets. A sophisticated sliding filter enables users to filter long lists easily.

OpenLM EasyAdmin supports advanced features like Flexnet packages (As used by Autodesk that produce Autocad). License Packages appear as boxed items.

OpenLM EasyAdmin – Management -License Procurement table

Shows comprehensive license information, as appears in the license file: Licensed packages and their member features, issuing and expiration dates, Asset info etc. (shown in the picture for Flexnet product)

OpenLM EasyAdmin – Management – Licenses not in use

Single out licenses that have not been used for a predefined period of time.

 

OpenLM EasyAdmin – Management – License utilization

This bar chart represents a histogram of license usage, i.e. each column ‘x’ answers the question: “what is the percentage of usage time that x licenses have been in use”. This form of presentation ignores momentary usage peaks, and provides a vivid realization of the true license consumption pattern. It clearly depicts the number of licenses that are actually required in the organization.

OpenLM EasyAdmin – Operational – Currently Consumed Licenses window

License managers may sometimes label licenses as occupied, when in fact they are idle and wasting your limited resources.

OpenLM EasyAdmin identifies these conditions, and resolves the problem of idle licenses.

The Active Products window lists all active users. It also serves as an interface for authorized system managers to retrieve a license from any user when necessary.

OpenLM EasyAdmin – Operational – Released Licenses window

The Released Licenses window reports license release (check-ins).

This functionality is only relevant for applications with supported extensions such as ESRI Desktop ArcGIS and Autodesk.

OpenLM EasyAdmin – Reports – License Activity

The License Activity window is a very powerful tool that enables system administrators and managers to produce sophisticated reports, and track license activity of individual users. This window facilitates license statistics report generation according to Workstations, Features, Users, Groups, and Projects.

OpenLM EasyAdmin – Reports – Denials window

OpenLM accumulates reports of license request denials. Thus it provides the comprehensive exact information, which is required for establishing a correct license purchasing policy.

OpenLM EasyAdmin – Recent features denials

This window provides preliminary statistic processing of license denials per feature: It presents the number of denied license requests in long term and short term period.

OpenLM EasyAdmin – Reports – License usage

The license usage reports allows system administrators to compare the actual license usage to the number of available licenses.

The smart Filter enables users to build a customized list of licenses and get the total usage on those licenses.

OpenLM EasyAdmin – Reports – Groups and Projects Usage

OpenLM enables organization to manage users according to groups and projects, and obtain the total usage time for these groups very easily.

This could be done either manually, or by synchronizing the OpenLM database with the organization’s Active directory. This functionality is often applied in order to implement license charge back policy (license usage billing).

Project Report

Project reporting enables project-oriented companies to get license usage time according to the active project, as reported by the end user.

Group Report

Group reporting allows managers and system administrators to obtain license usage statistics according to groups.

EasyAdmin – Administration

The configuration screens allows users to set their preferences. The choice of working hours effects the statistical information which is calculated shown to all system users.

EasyAdmin – User Settings

The configured preferences in the “User settings” window effect the format of information as it is presented to the User.

OpenLM EasyAdmin – Users and Permissions – Workstations window

The Workstations window provides all the information a system administrator needs in order to manage workstations that are accessing licenses.

This information includes:

  • Hostname

  • Agent version (if applicable)

  • Online (Workstation is online or offline)

  • Idle time (User idle time)

  • Controlled (for supported systems)

OpenLM Server

The OpenLM Server is the hub component of the OpenLM Utilizer system.

It collects license usage information from various sources and stores it in a relational database.

The OpenLM Server is a Windows service that can manage and monitor multiple license servers such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, and LM-X, located in different time zones and running on different operating systems (UNIX, Linux, or Windows).

For more information please refer to:

Application Note 2001a: Basic OpenLM Server configuration for FlexLM

OpenLM Server Configuration Form – License Servers Tab

This tab enables system administrators to effectively configure and manage license servers such as Flexera FlexLM (Flexnet publisher), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, MathLM, and LM-X via the OpenLM Server.

The OpenLM server supports world-wide license server monitoring; It is important to specify the timezone of each server.

After introducing new license servers, it is recommended to click the “Check” button to verify that the OpenLM server is able to connect to the license server.

Free text display names are attached to each server for better identification.

Fail safe server (Triad configuration) may also be configured on this tab.

OpenLM Server Configuration Form – Advanced Tab

Advanced OpenLM Server settings include:

  • Option file management

  • Translate workstation names to IPs

  • Enable the OpenLM Role based permissions system

  • Logging level etc.

OpenLM Server Configuration Form – Port settings Tab

The Openlm Server interfaces all other OpenLM peripheral modules via ports, which numbers are defined in this form.

OpenLM Server Configuration – Active Directory Tab

The OpenLM server can synchronize users and user groups with organizations’ LDAP Database (Microsoft Active Directory). OpenLM provides multiple policies for Group synchronizations.


OpenLM Server Configuration Form – Notifications Tab

These settings allow OpenLM to send error notifications, updates on new releases, and other important messages aimed at improving the license usage.

OpenLM Server Configuration Form – LM tools Tab

The LM tools tab holds the directories in which every license manager commands are located.

OpenLM Agent

The end user tool of OpenLM system improves license availability, empowers the user and provides advanced functionality.

OpenLM Agent functionality:

  1. Query  license manager status (and check who is using the license).

  2. Open documents that were closed by OpenLM.

  3. Allows the user to set the active project.

  4. Allows the user to set the license level.

  5. Provides license availability notifications.

OpenLM Agent is shown as an icon on the Windows system tray:

The blue and white icon indicates connectivity to OpenLM Server.

The grey icon indicates no connectivity to OpenLM Server.

OpenLM Agent – License Usage Information

The License Usage Information window is available to the end user.

The ability to query license availability from the end user workstation is a very important step towards improving license usability.

The license usage window displays the total number of used, borrowed, and available licenses.

Click on a row to get the complete list of active users who are currently drawing on that license.

The OpenLM Agent enables users to identify who is currently running a certain floating license on which station. This is an important and useful feature for any system that incorporates floating licenses such as: Autocad, Matlab, ESRI, AVEVA, Cadence, IntelliCAD, MathCAD, Pro-Engineer, Solidworks, and Synopsys.

A click on the any of the users displays the users details as stored in OpenLM Users table. These tables can be synchronized with an organization’s LDAP database: e.g.: Microsoft Active Directory.

OpenLM Agent – License available notification

When a user is denied a specific license, the OpenLM Server sends a notification to the user once the specific license becomes available again:

OpenLM Agent – Project selection

Projects can be introduced by end-users via the OpenLM Agent (once permission is set by the administrator in the EasyAdmin interface). Just click the “Create New Project” menu item in the OpenLM Agent interface:

The “Create new Project” window opens. Users can then create new projects and associate their working hours to these projects.

For more information please refer to this document:

Application Note 2030: OpenLM license usage monitoring according to projects – v1.8.

OpenLM Agent – Set ArcGIS license level

ArcGIS end users can set the licensing level before activating the software. If such a license is available, the software will start.

OpenLM Agent Configuration Form

The OpenLM Agent Configuration form sets and tests the connection to an OpenLM server.

Note – this is the OpenLM server, NOT a license (e.g.: Flexera FLEXnet) server.

The Agent’s logging level may also be set here.

A “Silent Install” option is available for automatic distribution of the OpenLM Agent to all workstations in the network.

OpenLM Active Agent

The OpenLM Active agent boosts organizations’ license usage by actively retrieving idle licenses.

The Active Agent supports many different software products from various vendors.These include: Autodesk software – Autocad, Revit, Electrical, Architecture, Mechanical, Map 3D, MEP, Navisworks and more…

ESRI –  ArcGIS  Desktop products: ArcView, ArcEditor, ArcInfo, Network Analyst, 3d Analyst, ArcGIS Data Interoperability, ArcGIS Data Reviewer, ArcGIS Spatial Analyst and more…

The Extension provides additional functions, such as:

  1. Closing idle sessions when licenses are no longer in use.

  2. One-click reopening of closed projects.

When OpenLM saves and closes an idle session of ArcGIS, it alerts the user with a notification message. Right clicking the Active Agent icon, and selecting “Recently Closed Documents” displays all recently closed documents:

Click on one of the recently closed documents to reopen it.

Please follow and like us:

Siemens PLM license analysis and license monitoring

OpenLM supports license monitoring of a wide, and ever growing variety of license managers. Among those are Flexera FlexLM (Flexnet publisher), IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, Reprise RLM, and LM-X.

This group of license management utilities encompass a great variety of licensed products. One group of such licensed products is the Siemens PLM (formerly UGS) 3D & 2D Product Lifecycle Management (PLM) group.

The OpenLM tool provides high level of application usage management and optimization for PLM licenses, providing clear and valuable usage information for Managers, License Administrators and End Users.

Siemens PLM Common Licensing

Siemens PLM employs the “Siemens PLM Software Common Licensing” tool in order to deliver a consistent licensing implementation to all PLM products. It is based on the Flexera FlexNet license management tool, and has incorporated some unique characteristics:

  • The PLM Common Licensing toolkit has adopted the Siemens PLM Software-wide licensing vendor daemon ugslmd. Consequently, all Siemens PLM products gain access to common licenses utilize this same daemon.
  • The PLM Common Licensing toolkit employs a unified license file for all PLM products.
  • The default port for the PLM ugslmd vendor daemon is 28000. That was decided in order to avoid conflicts with other applications, using the default FlexLM port 27000.
  • Composite ID (CID): This is a 12 digit hexadecimal unique machine identifier that is used as part of Siemens PLM Software licensing to lock a license file to a machine. The CID is distinguished from a FLEXnet hostid by the keyword “COMPOSITE=”.
  • NX bundles and Suite Packages: These are packages that Siemens PLM Software has predefined to meet the general needs of customers at a lower cost than purchasing individual floating licenses.

For more information on Siemens PLM Software Common Licensing, please refer to this PDF.

The OpenLM advantage

The OpenLM license monitoring tool incorporates many advantages in PLM software maintenance for members of all positions in an organization. In a nutshell:

  • Managers get a clear picture of their Software assets.
  • System Administrators are freed from managing licenses.
  • End users enjoy improved PLM license availability.

Additionally, OpenLM v 1.8 Automatically sorts NX suites, to clearly display Siemens PLM application usage measuring in its true context.

Please follow and like us:

Troubleshoot Form: OpenLM Server Item 003 (Unable to connect to FLEXlm license server error: -96,7:11004 “Comm. error”)

Title Unable to connect to FLEXlm license server
Category OpenLM Configuration Form
Date Oct 24, 2012
Handled by
Relevant Links
Applies to license managers FLEXlm, FLEXera FLEXnet,
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms No activity reported on EasyAdmin for a specific FlexLM license server
Observed during investigation Clicking the “Check” button for one of the FlexLM license servers on the OpenLM Configuration Form resulted in an error
Trouble shoot process Check License server connectivity configuration.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the FLEXlm license server”. Attempting to connect to the license server resulted in the following message box appearing on his screen:

lmgrd is not running: License server machine is down or not responding. (-96,7:11004 “Comm. error”)

Troubleshoot process

1. Make sure the license manager machine is up and that you could check out licenses from it.

2. Make sure that the hostname , Port number, License Manager type and timezone are configured correctly in the OpenLM server configuration tool. Also, please review this Troubleshoot guide.

3. Check the connectivity between the OpenLM server machine and the license server (using ping or telnet).

4.  Make sure that any security components (Firewall) are not blocking communication on both ends. The OpenLM server uses ports 7012, 7014, 7016, 7017 and 7019. The OpenLM server’s communication with the License server relies on port 7014.

Make sure that the port is open:

 

  • Try disabling the firewall temporarily.
  • Enter “Control Panel”→“System and Security”→“Windows Firewall”→ Advanced settings”.
  • If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:

5. The OpenLM Broker may bypass such communication issues. Install the OpenLM Broker on the license server machine. See this application note for more information: Application Note 1004: OpenLM Broker quick start guide

Please follow and like us:

Application Note 1001_b: Configuring OpenLM to interface the Sentinel RMS license manager

Scope:

OpenLM supports the monitoring of a wide variety of license managers such as Flexera FlexLM ( Flexnet ), Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This application note elaborates the steps required to configure OpenLM to interface the Sentinel RMS License Manager, and obtain reliable license reports and usage statistics.

Enabling the OpenLM server to work with RMS

In order to configure OpenLM to work with  Sentinel RMS, please follow this procedure:
1. Download lsmon.exe and lsapiw32.dll . These files aren’t included in the OpenLM installation package. For information on how to obtain these files, please contact OpenLM on support@openlm.com.
2. Copy these files to “C:\Program Files\OpenLM\OpenLM Server\LM”
3. Enter the OpenLM Server Configuration Form. Select the LM Tools tab → RMS.
4. Type in the full path of the executable file, i.e.:  “C:\Program Files\OpenLM\OpenLM Server\LM\lsmon.exe” in the “RMS executable file” text box.

See the following image for further clarification:

Introducing a new Sentinel RMS server

After configuring the OpenLM configuration tool to work with Sentinel RMS as elaborated above, the user may introduce an new  Sentinel RMS server under the License Servers tab:
1. Select the “License Servers” tab.
2. Select the RMS type from the “Type” dropdown list.
3. Type in a meaningful description in the “Description” text box.
4. Type in the appropriate “Hostname” and “Port” numbers. The Sentinel RMS default port is 5093.
5. Check the “Enabled” check box.
6. Click the “Apply” button. The  Sentinel RMS server is now ready to interface the OpenLM.

OpenLM Broker configuration for RMS

The OpenLM Broker is an optional though highly recommended component, that should be installed and configured on the RMS license manager machine. It provides accurate license statistics, and facilitates communication between the OpenLM Server and the License manager.

First, download and install the latest OpenLM Broker version. Follow the installation and configuration instructions on the OpenLM Broker configuration Application Note.

In the License server port dialog, select the RMS license manager type from the ‘Type’ dropdown list.
In the port’s Commands list make sure the ‘status’ command is
lsmon <License Server Name>

Document Revision Table

Version Author Date Changes
0.1 Orik May1, 2012 Preliminary
1.0 Orik Jun3, 2012 Revised.
1.1 Orik Jun6, 2012 Added Broker

 

Please follow and like us:

Setting FlexLM port numbers statically

Flexnet / FlexLM ports numbers may be set statically by declarations made in the FlexLM license file. When remain undeclared, these ports would be set randomly every time the license manager is started.

1. In order to set the port connecting the license manager with the installed applications:

On the server side, on the license file (<license>.lic), add a port number to the end of the SERVER line, e.g.:

SERVER <ServerName> <HostId> <PortNumber>

On the client side, on the <license>.dat file add the same number to the end of the SERVER line, e.g.:

SERVER <ServerName> ANY <PortNumber>

2. In order to set the license manager to interface the Vendor over a predefined static port number, add this number in the end of the VENDOR line, in the license file on the license server machine, e.g.:

VENDOR <VendorName> PORT=<VendorPortNumber>

In order for these changes to take affect, you would need to reread the license file. You may do that by clicking the “Reread License file” button, under the “Start/Stop/Reread” tab in Flexera’s LMTOOLS application.

The OpenLM license monitoring tool interfaces these ports in order to extract license statistics, and reliable license usage reports.

For any further information about license management, please visit the new OpenLM site, or address us directly on support@openlm.com.

Please follow and like us:

How do I know the FlexLM license manager port number ?

OpenLM employs the Flexnet / FlexLM reporting mechanism to monitor and optimize concurrent license usage, and obtain license statistics. The FlexLM license manager interfaces licensed applications via predefined ports. You can verify that a port number is set correctly by:

1. Using Flexera’s LMTOOL utility: Select the “Server Status” tab, and click the “Perform Status inquiry” button. the port number would appear on the line that begins with “License server status:” e.g.:

License server status: 27000@My_server

2. You can also find the server name and port number (If defined as static) directly in the license file, in the SERVER line e.g.:

SERVER <ServerName> <hostId> <PortNumber>

USE SERVER

The path and name of the license file is set in the LMTOOLS, under the “Config Services” tab.

Please follow and like us:

FlexNet vulnerability: lmgrd Remote Code Execution

Zero Day has reported that a security vulnerability has been discovered in FlexNet License Server Manager installations. This vulnerability enables attackers to execute arbitrary code on remote FlexNet License Server managers. Authentication is not required to exploit this vulnerability. The flaw was reported by Luigi Auriemma and Alexander Gavrun.

The specific flaw exists within lmgrd license server manager. lmgrd listens by default on TCP port 27000. A specially crafted packet sent to the server will cause a stack overflow allowing for remote code execution under the context of the server.

Flexera Software has issued an update to correct this vulnerability and also provided license administrators best practices for mitigating risk exposure.

More details can be found at:

http://www.flexerasoftware.com/pl/13057.htm

Please follow and like us: