Monthly Archives: April 2012

Application Note 1027_a: OpenLM Agent Installation and Configuration

Posted on by

OpenLM Utilizer Agent

The OpenLM Utilizer Agent is the end user tool of the OpenLM system. It completes the OpenLM license monitoring tool from the End user’s point of view. It provides end users the following capabilities:

  • Query license availability.
  • Check which users are holding required licenses.
  • View a user’s full set of details as they appear on the LDAP, and communicate with users regarding license availability.
  • Receive license availability notifications as soon as requested licenses become available.
  • Report the session’s active project (mainly for billing purposes).

OpenLM Active Agent

The Active Agent incorporates all the characteristics of the Utilizer Agent. On top of that, it supports an extension that enables system administrators to shut down open applications either manually, or by defining a timeout policy. In this manner, system administrators can suspend or save and close idle applications, in order to make more efficient use of licenses. The Active Agent features a user-friendly interface that enables users to quickly reopen closed applications, or resume suspended ones.

Installation

Download and save the Openlm Utilizer or Active Agent MSI installation file from the Download section of OpenLM’s site. Double-click it, and follow the instructions of the installation wizard.

When installing the Active Agent, the Extensions “OpenLM Extensions” dialog window appears.

The user may either:

  • Select to install the appropriate software extensions, thus ruling an idle application to be treated in the “Save and Close” method, or
  • Select NOT to install the appropriate software extensions, thus ruling an idle application to be treated in the “Suspend and Resume” method, even though it is an “Extension Supported” application.

For more information on Extension-Enabled applications, please refer to “Application Note 1005: Configuring OpenLM to close idle Licenses”.

At the end of the installation process, in the “Agent Configuration” dialog window, type in the OpenLM server with which the Agent is required to connect, and click the “Apply” button. The Installation is now complete, can be changed at any time (see below).

After installing:

The OpenLM Agent icon appears on the “system tray”.
OpenLM Agent in a connected state:
OpenLM Agent in a disconnected state:

Agent Configuration

  • Right click on the agent icon and select ‘OpenLM Agent Configuration’. The Agent configuration window opens.
  • Select the Agent’s language.
  • Type in the OpenLM server name or IP.
  • Type in the OpenLM server port. This is by default 7012.
  • Click the “Check connectivity to OpenLM server” button.

Advanced settings:

  • Logger Configuration File: Type in the location of the Agent Log File.
  • Logging Level: Adjust the Agent’s logging level.
  • Skip Double Instances Alert: This option either enables or blocks alerts when trying to open two agent sessions simultaneously. This option is set active by default.
  • Use Local Computer’s Proxy Settings: This setting may solve issues that originate using a proxy server. This option is set inactive by default.
  • Shut Agent when products Are inactive… : These parameters are relevant for VM servers. When OpoenLM closes a licensed application, the VM (e.g: Citrix) is kept in use by the workstation, unnecessarily consuming a license. This configuration shuts down the OpenLM Agent after INACTIVITY_TIME, thus releasing the VM license.

The OpenLM Java Agent window

The OpenLM Agent window shows the Feature usage status, per License Server, Vendor and User name. Individual user data is also available through the Agent; Just click a chart line to get more information on the user who is currently occupying the license.

Revision 0.1, Apr29 2012.

OpenLM Hotfix: Broker version 1.7.2.0 for IBM-LUM and LM-X license managers

Posted on by

The OpenLM Broker version 1.7.20 is a Hotfix version, dedicated for the solution of an issue that was raised by a customer.

Issue description:

The IBM LUM license manager was not configured correctly on the Broker configuration interface, when Java JRE 1.7 was installed on the PC. It was configured correctly for JRE 1.6.

OpenLM recommends to download and install version 1.7.20 of the OpenLM Broker on IBM LUM and LM-X license servers that run JRE 1.7.

The OpenLM Forum returns !

Posted on by

After the previous OpenLM Forum has fallen victim to spam, we have decided to clean up the stables and start fresh.

The new Forum would be accessible for everyone to read, but posting priviledges would be manually granted to confirmed customers only.

We hope it would rise as a knowledge-base and a source for cooperation between OpenLM customers.


AutoDesk FlexNet feature codes, March 2012

Posted on by

Feature codes

FlexNet (FlexLM) uses a predefined set of codes in order to manage multiple licensed Features. Each of these features is given a unique code, by which FlexNet grants license requests, and keeps track of the license pool.

OpenLM Also makes use of these feature codes during FlexLM reporting in order to monitor and optimize Autodesk license usage. As versions progress and features are added, the code tables need constant updating. The following is a complete list of AutoDesk codes, updated to March 2012. It was taken from Autodesk’s official site.

Autodesk code table

AutoCAD 2013 85871ACD_2013_0F
AutoCAD Architecture 2013 85883ARCHDESK_2013_0F
AutoCAD Civil 3D 2013 85976CIV3D_2013_0F
AutoCAD Design Suite Premium 2013 85969DSPRM_2013_0F
AutoCAD Design Suite Standard 2013 85970DSSTD_2013_0F
AutoCAD Design Suite Ultimate 2013 85971DSADV_2013_0F
AutoCAD ecscad 2013 85889ECSCAD_2013_0F
AutoCAD Electrical 2013 85890ACAD_E_2013_0F
AutoCAD for Mac 2013 85989ACDMAC_2013_0F
AutoCAD Inventor LT Suite 2013 85958INVLTS_2013_0F
AutoCAD LT 2013 85872ACDLT_2013_0F
AutoCAD LT Civil Suite 2013 85991ACDLTC_2013_0F
AutoCAD LT for Mac 2013  86021ACDLTM_2013_0F
AutoCAD Map 3D 2013 85981MAP_2013_0F
AutoCAD Map 3D Enterprise 2013 85982MAP3DE_2013_0F
AutoCAD Mechanical 2013 85885AMECH_PP_2013_0F
AutoCAD MEP 2013 85887BLDSYS_2013_0F
AutoCAD P&ID 2013 85977PNID_2013_0F
AutoCAD Plant 3D 2013 85978PLNT3D_2013_0F
AutoCAD Raster Design 2013 85952ARDES_2013_0F
AutoCAD Revit Architecture Suite 2013 85954REVITS_2013_0F
AutoCAD Revit MEP Suite 2013 85955REVSYP_2013_0F
AutoCAD Revit Structure Suite 2013 85957REVSU_2013_0F
AutoCAD Structural Detailing 2013 85943STRDET_2013_0F
AutoCAD Utility Design 2013 86027UTLDESN_2013_0F
Autodesk 360 Vault Collaboration 2013 85983VLTC_2013_0F
Autodesk 360 Vault Collaboration AEC 2013 85984VTCAEC_2013_0F
Autodesk 360 Vault Office 2013 85986PCOFFI_2013_0F
Autodesk 360 Vault Professional 2013 85987VLTM_2013_0F
Autodesk 360 Vault Workgroup 2013 85988VLTWG_2013_0F
Autodesk 3ds Max 2013 858923DSMAX_2013_0F
Autodesk 3ds Max Design 2013 85893MAXDES_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Premium 2013 85918MXECSP_2013_0F
Autodesk 3ds Max Entertainment Creation Suite Standard 2013 85920MXECS_2013_0F
Autodesk Alias Automotive 2013 85881AUTOST_2013_0F
Autodesk Alias Design 2013 85896DESNST_2013_0F
Autodesk Alias Surface 2013 85895SURFST_2013_0F
Autodesk Animation Academy 2013 85922AAA_2013_0F
Autodesk Building Design Suite Premium 2013 85946BDSPRM_2013_0F
Autodesk Building Design Suite Standard 2013 85947BDSS_2013_0F
Autodesk Building Design Suite Ultimate 2013 85948BDSADV_2013_0F
Autodesk Entertainment Creation Suite Premium 2013 Exclusives 86043ECSPE_2013_0F
Autodesk Entertainment Creation Suite Standard 2013 Exclusives 86044ECSSE_2013_0F
Autodesk Entertainment Creation Suite Ultimate 2013 85926ENCSU_2013_0F
Autodesk Factory Design Suite Premium 2013 85965FDSPRM_2013_0F
Autodesk Factory Design Suite Standard 2013 85966FDSS_2013_0F
Autodesk Factory Design Suite Ultimate 2013 85967FDSADV_2013_0F
Autodesk Infrastructure Design Suite for Education 2013 85974ESCSE_2013_0F
Autodesk Infrastructure Design Suite Premium 2013 85992IDSP_2013_0F
Autodesk Infrastructure Design Suite Standard 2013 85993IDSS_2013_0F
Autodesk Infrastructure Design Suite Ultimate 2013 85994IDSU_2013_0F
Autodesk Infrastructure Map Server 2013 86014IMS_2013_0F
Autodesk Infrastructure Modeler 2013 86013INFMDR_2013_0F
Autodesk Inventor 2013 85998INVNTOR_2013_0F
Autodesk Inventor Factory Premium 2013 85999INVFPR_2013_0F
Autodesk Inventor Factory Ultimate 2013 86000INVFAD_2013_0F
Autodesk Inventor LT 2013 86004INVLT_2013_0F
Autodesk Inventor OEM 2013 86002INVOEM_2013_0F
Autodesk Inventor Professional 2013 86001INVPROSA_2013_0F
Autodesk Inventor Publisher 2013 85979INVPUB_2013_0F
Autodesk Maya 2013 85857MAYA_2013_0F
Autodesk Maya Entertainment Creation Suite Premium 2013 85928MYECSP_2013_0F
Autodesk Maya Entertainment Creation Suite Standard 2013 85930MYECS_2013_0F
Autodesk MotionBuilder 2013 85936MOBPRO_2013_0F
Autodesk Mudbox 2013 85869MBXPRO_2013_0F
Autodesk Navisworks Manage 2013 86022NAVMAN_2013_0F
Autodesk Navisworks Simulate 2013 86023NAVSIM_2013_0F
Autodesk Plant Design Suite Premium 2013 85995PDSPRM_2013_0F
Autodesk Plant Design Suite Standard 2013 85996PLTDSS_2013_0F
Autodesk Plant Design Suite Ultimate 2013 85997PDSADV_2013_0F
Autodesk Product Design Suite for Education 2013 85961ESME_2013_0F
Autodesk Product Design Suite Premium 2013 85962PDSP_2013_0F
Autodesk Product Design Suite Standard 2013 85964PDSS_2013_0F
Autodesk Product Design Suite Ultimate 2013 85963PDSU_2013_0F
Autodesk Quantity Takeoff 2013 86024AQTO_2013_0F
Autodesk Revit 2013 85950RVT_2013_0F
Autodesk Revit Architecture 2013 85862REVIT_2013_0F
Autodesk Revit Structure 2013 85866REVITST_2013_0F
Autodesk Robot Structural Analysis 2013 86005RSA_2013_0F
Autodesk Robot Structural Analysis Professional 2013 85975RSAPRO_2013_0F
Autodesk Showcase 2013 85956SHOWCASE_2013_0F
Autodesk Showcase Professional 2013 85949SHOWPRO_2013_0F
Autodesk Simulation CFD 2013 86025SCFD_2013_0F
Autodesk Simulation CFD 2013 Advanced 86028SCFDA_2013_0F
Autodesk Simulation CFD 2013 Connection for ACIS 86045SCACIS_2013_0F
Autodesk Simulation CFD 2013 Connection for NX 86030SCFDNX_2013_0F
Autodesk Simulation CFD 2013 Connection for Parasolid 86047SCFDP_2013_0F
Autodesk Simulation CFD 2013 Connection for Pro/E 86032SCPROE_2013_0F
Autodesk Simulation CFD 2013 Design Study Environment 86034SCDSE_2013_0F
Autodesk Simulation CFD 2013 Motion 86036SCFDM_2013_0F
Autodesk Simulation DFM 2013 86056SIMDFM_2013_0F
Autodesk Simulation Mechanical 2013 85940ASMES_2013_0F
Autodesk Simulation Moldflow Adviser Premium 2013 86006MFAM_2013_0F
Autodesk Simulation Moldflow Adviser Standard 2013 86008MFAD_2013_0F
Autodesk Simulation Moldflow Adviser Ultimate 2013 86007MFAA_2013_0F
Autodesk Simulation Moldflow CAD Doctor 2013 86009MFCD_2013_0F
Autodesk Simulation Moldflow Design Link 2013 86010MFDL_2013_0F
Autodesk Simulation Moldflow Insight Premium 2013 86038MFIP_2013_0F
Autodesk Simulation Moldflow Insight Standard 2013 86042MFIB_2013_0F
Autodesk Simulation Moldflow Insight Ultimate 2013 86040MFIA_2013_0F
Autodesk Simulation Moldflow Synergy 2013 86012MFS_2013_0F
Autodesk Simulation Multiphysics 2013 85942ASPRO_2013_0F
Autodesk SketchBook Designer 2013 85990ALSK_2013_0F
Autodesk Softimage 2013 85934SFTIM_2013_0F
Autodesk Softimage Entertainment Creation Suite Standard 2013 85932SIECS_2013_0F
mental ray Standalone 2013 86019MRSTND_2013_0F

Application Note 1027: OpenLM Java Agent Installation and Configuration

Posted on by

General

The OpenLM Java Agent is an end-user tool that enables OpenLM to interact with the end user in order to promote license availability. System administrators are granted full control over any functions available to the end user.
The OpenLM Java Agent is a “lightweight” software component. It is apparent on screen as an icon, located on the end users “System tray bar”. The Java Agent facilitates the following abilities:

  • Query license availability, license users and full users details.
  • Receive license availability notifications.
  • Report any active projects.

This article elaborates the installation process of the Java Agent.
The OpenLM Java Agent can run on any Java supported system. It is primarily intended for UNIX or Linux OS. OpenLM provides a native Windows agent recommended for a Windows environment.

Prerequisite

It is necessary to have the Java Runtime Environment (JRE) version 1.6 (or newer) installed.

Installation

1. Unzip the Openlm Java Agent zip file and copy all files from the Agent directory to a folder.
Ensure that the target folder does not have “read only” permissions.

2. Run the software using a terminal on the Unix \ Linux workstation:
cd to the target folder, and run the command:
java -jar openlm_agent.jar &

If the following message appears, make sure that the Java software is in the system path or uses full path.

After installing:

The OpenLM Agent icon appears on the “system tray”.
OpenLM Agent in a connected state:      
OpenLM Agent in a disconnected state:

The OpenLM Agent may be set to start with your system; this setting is available in all UNIX/Linux systems.

Agent Configuration

  • Right click on the agent icon and select ‘OpenLM Agent Configuration’. The Agent configuration window opens.
  • Select the Agent’s language.
  • Type in the OpenLM server name or IP.
  • Type in the OpenLM server port. This is by default 7012.
  • Click the “Check connectivity to OpenLM server” button.

Advanced settings:

  • Logger Configuration File: Type in the location of the Agent Log File.
  • Logging Level: Adjust the Agent’s logging level.
  • Skip Double Instances Alert: This option either enables or blocks alerts when trying to open two agent sessions simultaneously. This option is set active by default.
  • Use Local Computer’s Proxy Settings: This setting may solve issues that originate using a proxy server. This option is set inactive by default.
  • Shut Agent when products Are inactive… : These parameters are relevant for VM servers. When OpenLM closes a licensed application, the VM (e.g: Citrix) is kept in use by the workstation, unnecessarily consuming a license. This configuration shuts down the OpenLM Agent after INACTIVITY_TIME, thus releasing the VM license.

The OpenLM Java Agent window

The OpenLM Java Agent window shows the Feature usage status, per Server, Vendor and User name. Individual user data is also available through the Agent; Mark a chart line and click the “Show Users” button to get more information on the user who is currently using the license. (See license usage information below)

Revision 1.1, Apr29 2012.

Application Note 1026: Basic OpenLM Server configuration for FlexLM

Posted on by

General

OpenLM supports the monitoring of a wide, and ever growing variety of license servers. Among those are Flexera FlexLM (Flexnet) , Beta LM, IBM LUM, DSLS, Sentinel HASP, Sentinel RMS, RLM, and LM-X. This is an description of the basic procedure for configuring the Openlm server to interface a FlexLM license manager, to monitor Flexnet reporting.

Procedure

Please first refer to this Application Note. It gives a general description of the OpenLM system; what should be installed where, and who needs to communicate with whom.

Install the latest version of the OpenLM server. It is found on the OpenLM site.

  1. Configure the OpenLM server so that it would communicate with the License server:
  • Open the “OpenLM server configuration window, On the “License Servers” tab (see image below).

  • Click the ‘Add’ button, and type in the license server parameters (Type, Host name (or IP), port & time zone). In order to find the Server name and port, please refer to this post.
  • You can type in a descriptive name to make recognizing the sever easier
  • In the image above, these parameters are: FLEXlm, olm-lm-arcgis10, 27000, UTC+08, “ArcGIS 10 Head Office”.
  • Click the ‘Apply’ button. Select ‘Restart now’. That’s it: the OpenLM server is
  1. Check the connection of the OpenLM server to the license server; click the ‘Check’ button. A text would follow. This text is a query of the License server. It indicates whether a connection to that server is established.
  1. Now open the EasyAdmin web application. Click start -> Management -> License servers. The “License servers” window appears. Verify that the configured license managers appear on the list. Circle nodes indicate a connection to a license server. Square nodes indicate a connection to a Broker which is installed on the License server machine.


Setting FlexLM port numbers statically

Posted on by

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.

How do I know the FlexLM license manager port number ?

Posted on by

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.

OpenLM and the trend of increase in license auditing

Posted on by

Background

As the economic condition continues to falter, the rate of software compliance auditing rises. This is caused by rising pressure in companies to use unlicensed software on one end, and equivalent pressure on the side of software vendors to keep their revenue. According to BSA (Business Software Alliance) officials,  the current economic climate “could have an impact on companies cutting corners and using unlicensed software to save perceived-costs”. This in turn leads the BSA step up license compliance enforcement and litigation against violators.

As a tool dedicated for the monitoring of licensed applications, OpenLM perfectly fits in the capacity of keeping BSA officials content, and CEOs of software using companies relaxed.

Ensuring license agreement compliance.

Software vendors use several methods in order to ensure license compliance.

  • Inside information: Violation reports are routinely submitted to the BSA by insiders. These are individuals with inside information, that report violation of license usage for various reasons. The BSA’s response to such referrals would normally be a letter to the suspected violator, indicating that an investigation is taking place and offering to give up litigation action if a compliance audit is conducted. If the compliance audit is conducted, the company must provide a list of all the software in question, as well as the purchase dates of the software licenses.

  • Piracy business intelligence may be collected by the software and gathered by the vendors in order to pinpoint license violations.

  • End-User License Agreements: Large vendors may have the ability to conduct software audits for their software for license compliance purposes according to their End User License Agreements.

Pressure builds up

When the time comes for an unexpected external audit, or when the expiration of a license is closing in, companies tend to rush IT personnel to take manual inventory of existing software. This process is inefficient for several reasons:

  • It is an error prone process, mainly in large companies that run hundreds of licensed applications. Moreover: employees don‘t necessarily act in compliance with license agreements.

  • It is also inefficient. It consumes system administrators’ time and concentration, and may raise tension within the organization.

Continuous monitoring is needed

In order to ensure full compliance and peace of mind, organization executives should enforce formal, ongoing software license management policies. This is where OpenLM comes in into the picture:

  • Having an organized license usage report reduces the risk of an external audit, and serves as an insurance policy against the consequences of liability actions by the BSA.

  • Organized reports may also improve a company’s position, and have benefits when negotiating with a vendor for license renewal.

  • En-route the organization of software inventory, license activity is made apparent, and software costs are reduced.

  • IT personnel are taken off the mundane, but error prone procedure of manual inventory taking, and their productivity is increased.

Further reading

Software License Audits: What Does It Mean to Be Non-Compliant?

OpenLM fits in the US Federal “Shared First” policy.

Posted on by

US Federal Budget cuts have produced a new policy of software procurement within government agencies. This strategy is nicknamed the “Shared First” policy, and is at the base of some major changes in Federal software license procurement and maintenance.

The “Shared First” policy requires agencies to share IT systems, acquisition and expertise. US Government agencies are required to consider using existing software, both inside their agencies and across government before turning to further purchase of software. This policy has manifested in enormous cuts in IT expenditure.

Increased sharing of software assets is one of the central pillars of this policy. Federal agencies have reported saving many millions of Dollars by using enterprise-wide (“floating”) license agreements over the passed two years. Being a software that specializes in the monitoring of floating licenses, OpenLM fits in this capacity perfectly. It is ideal for monitoring enterprise-wide licenses over WAN or LAN networks, and over different time zones.

Moreover, Following President Obama’s executive order from last November to take inventory of Federal agencies’ software assets, there has been a growing need for monitoring license usage and pointing out weak spots in software license utilization. These weak spots are non-compliance with license agreements and under-utilization of  existing software licenses. Again: circling out such weak spots is what OpenLM is for. OpenLM may be configured to alert for such conditions, and actively improve license utilization.

Further reading …