Altair’s New Licensing for solidThinking is a Win for SMEs

A major barrier to innovation for startups and small and medium enterprises (SMEs) is the cost of simulation software. Combining this cost with the learning curve required to apply the principles embedded in computer-aided engineering (CAE) has resulted in many great ideas not getting to market. It is widely recognised that SMEs are the powerhouse of economic growth globally, and that every effort should be made to facilitate their rocky path to create a sustainable business. Altair’s contribution to SME growth is to make CAE more accessible, firstly by changing their licensing model for solidThinking.

Eight years ago, when they released Hyperworks 11.0, Altair changed their license manager from Flexera to LM-X from X-Formation. The objective of this change was to provide greater flexibility in the licensing options offered to customers, especially for their Hyperworks suite. The licensing model is units-based and the customer buys and uses the Hyperworks units (HWUs) according to the business need, selecting the specific software they require from the suite, rather than buying licenses for each product. Users of solidThinking software were still required to buy each of the products they wanted, based on the license model that was in force when Altair acquired solidThinking.

Although Altair had purchased solidThinking in 2008, they did not change the license management software from the original Flexera FlexLM and the purchase-per-product approach until recently, in August 2018. solidThinking units (sTUs) are now available for all products in the solidThinking suite. The units are stored in a pool, and the user books out the software he needs by checking out the number of units required for that application, for instance, Altair Inspire 2018. On finishing with the application, the sTUs are returned to the pool for the next user.

A Single Licensing Model for On-Site and the Cloud

To simplify the license model even more, the software can either be used on-site or in the cloud. This is useful for SMEs who have limited computing power and want to avail themselves of cloud services, such as Altair’s own cloud-hosting service, Altair 365. The number of units required for the organization is also flexible; units can be added or removed to fit current circumstances.

Existing customers can convert to the new model with the minimum of fuss:-

  • Perpetual license holders with maintenance agreements will have their licenses converted to full sTU licenses for the same cost as the existing annual maintenance agreement.
  • Where the perpetual license holder had let their maintenance agreement lapse, there was an offer made  to upgrade the existing licenses during an incentive period, which lapsed at the end of December 2018.
  • Where the licenses were being leased, the customer is upgraded to sTU licensing at no additional cost.

For all existing license holders, the conversion gives them access to the entire solidThinking suite of applications, and the ability to run the programs on-site or in the cloud.

More Intuitive Software

Altair recognizes that many SMEs will not have the necessary skills on-board to handle the complexities of CAE. To this end, they have focused on making the simulation products easy to use and intuitive, both for engineers who are familiar with simulation software and other resources who are not from a engineering background but need to run simulations. The combination of easy-to-use software and an affordable pricing model make solidThinking an attractive option for SMEs. Through purchasing sTUs, they have access to 9 applications, ranging from conceptual designs using Evolve through to extrusion and cast metal moulding using the Inspire applications for this. There is even Compose, a programming language for mathematical modelling, similar to Matlab.

The flexibility of the solution, combined with its scaleability, allows an SME to develop and grow at their own pace. Cost constraints imposed by the need to invest in costly high-performance computing can be avoided by using the cloud, either Altair’s own service or another cloud provider. By removing the barriers to using simulation software, Altair has levelled the playing field for small businesses to compete against large organizations. Using simulation software instead of prototyping both reduces costs of product development and accelerates time to market.

Small Startups get a Boost

While Altair has come up with this licensing model to boost innovation by small businesses, it recognises that the cost may still be beyond the means of early-stage startups. For this reason they have developed a startup program for startups and entrepreneurs who meet certain criteria, including:-

  • an annual revenue of less than $10 million
  • a privately held concern, and
  • less than 4 years old.

Apart from providing software at deep discounts of up to 80%, Altair also offers free consultancy and training to such startups. They are also prepared to assist SMEs who do not meet the criteria with discounts, based on the current state of their business.

Like other vendors providing simulation software, Altair facilitates academic institutions by providing discounted software to the institutions and teachers, and free software to students who need to perform simulations as part of their studies.

How Altair benefits from the New License Model

While the units-based license model brings in less revenue from a user who previously had to buy each of the solidThinking applications separately, Altair have opened up their market to a new customer base of SMEs and startups. This means more sales and the ability to partner with small businesses as they grow. Their larger customers, such as Airbus and Samsung, can also benefit from the new business model, which is easy to administer and tailor according to demand.

Customers who start the relationship with solidThinking products can move on to other Altair products as the need arises, such as their high-performance platform or Internet of Things and digital twins platforms. In this respect, the new license model is a win-win for both Altair and their customers.

Please follow and like us:

FLEXlm Timeout Settings

What is FLEXlm?

FLEXlm is a license manager that manages software used by multiple end users on different computers. Notably, it allows companies to take advantage of floating licenses. A system employing floating licenses has a license pool on a host server from which end users check out licenses. When a user finishes using a software license, it is checked back into the pool, now available for another user to check out.

Further information on FLEXlm

What is FLEXlm license timeout?

FLEXlm license timeout is a feature that releases inactive licenses back to the license pool. Licensed software is determined to be inactive when a machine is completely idle, meaning no mouse clicks, keystrokes, modal dialog boxes are occurring. Its timeout settings determines how long such a period continues before licenses are freed up.

How to set FLEXlm timeout

License timeout settings can be configured for some or all the features, and are configured in the FLEXlm option file.

Further information on option files

Individual license key timeout is set by entering the variable “timeout” followed by the timeout period (in seconds).

Example: Setting AutoCAD to be timed out in 108000 seconds (3 hours)

 timeout AutoCAD 108000

License timeout for all license keys in the system is set by the variable “timeoutall,” followed by the timeout period.

Example: Setting all licenses to be timed out after 30 minutes of inactivity

timeoutall 1800

Limitations on license timeout settings

It is important to note that software vendors often impose limitations on the timeout period for their products; specifically, the minimum amount of time of inactivity after which licenses can be freed up. For example, whereas Autodesk licenses can be released after 15 minutes of inactivity, MathWorks licenses can only be released after 4 hours.

Autodesk 900 sec (15 minutes)

MathWorks 14,400 seconds (4 hours)

IBM 7200 seconds (2 hours)

Application

Customizing FLEXlm timeout settings is simple way to improve the efficiency of your company’s licenses, ensuring that end users aren’t slowed down by waiting for inactive, locked-up licenses.

 

Please follow and like us:

FLEXnet Option Files Examples

What is FLEXnet publisher?

FLEXnet publisher (formerly known as FLEXlm) is a software license manager utilized by companies to manage software shared by different people on different workstations. With what are termed “floating licenses,” FLEXnet enables end users to draw and return software licenses from a license pool on a host server.

What is a FLEXnet option file?

An option file defines various operating parameters of the license manager.

Creating/Editing an option file

In order to create an option file, save a text document in the same folder as the license file. Next, the document the according to the name of the vendor, followed by the extension “.opt”

For example, an option file for Matlab will be named “mlm.opt”. Accordingly, option files for Autodesk and ESRI ArcGIS would be named “adskflex.opt” and “ARCGIS.opt,” respectively.

Allocating licenses to a specific user group

First, define a group with the keyword “GROUP,” followed by the name of the group, followed by the members of that group. Names are all case sensitive.

Example: A group called “Matlab_Users,” consisting of Billy, Jim, and Kim

GROUP Matlab_Users billy jim kim

Next, to select which licenses to allocate to that group, type the keyword “INCLUDE,” followed by the feature name, followed by the group name.

 Example: Allocating feature “Optimization Toolbox” to the group “Matlab_Users”

 INCLUDE MATLAB GROUP Matlab_Users

These two steps are combined:

GROUP Matlab_Users billy jim kim

INCLUDE MATLAB GROUP Matlab_Users

Limiting individuals or groups of users to a maximum number of licenses

In order to limit the usage of a feature by a group, first allocate the license to that group or individual as demonstrated above. Then, set a usage limit with the keyword “MAX,” followed by the name of the feature, followed by the group name.

Example: Limiting the max number of Autocad 2002 licenses used by group “Autocad_Users,” consisting of users Ronald and Lisa, to 7. (41100ACD_2002_OF is the name of the Autocad 2002 feature)

GROUP Autocad_Users ronald lisa

INCLUDE 41100ACD_2002_0F GROUP Autocad_Users

MAX 7 41100ACD_2002_0F GROUP Autocad_Users

Excluding access to specific features

Enter the keyword “EXCLUDE,” followed by the feature name, followed by group or individual being excluding.

Example: Excluding user Franklin from feature “Geosteering plug-in for Petrel 2013”

EXCLUDE OCEAN_SLB_SIM_GEOSTEERING franklin

Controlling license borrowing

To allow someone to borrow a feature, use keyword “BORROW,” followed by the name of the borrowed feature, followed by the user or group of users.

Example: Including users Bill and Sam in the list to borrow the feature Ansys Fluent

BORROW fluent bill sam

Alternately, to exclude someone from borrowing a feature, simply replace “BORROW” with “EXCLUDE_BORROW”

Example: Excluding users Bill and Sam from the list to borrow the feature Ansys Fluent

EXCLUDE_BORROW fluent bill sam

A “borrow lowwater” determines the number of licenses that must remain unused at any given time. Enter the keyword “BORROW_LOWWATER,” followed by the feature name, followed by the number of licenses that can’t be borrowed.

 Example: Setting a borrow lowwater for the feature autocad at 5

BORROW_LOWWATER autocad 5

To adjust how long a license feature can be borrowed, enter “MAX_BORROW_HOURS,” followed by the feature name, followed by the number of hours

Example: Maxing the number of hours a solidworks feature license can be borrowed for at 15 hours

MAX_BORROW_HOURS sldworks 15

Setting license timeout

FLEXlm license timeout is a feature that releases inactive licenses back to the license pool. Enter the keyword “TIMEOUT,” followed by name of the feature, followed by the time (in seconds) after which inactive licenses are released. To set a timeout for all features, simply enter “TIMEOUTALL,” followed by the time.

Example: Setting timeout for Matlab Database Toolbox for 14400 seconds (4 hours)

TIMEOUT Database_Toolbox 14400

Example: Setting a timeout for all licenses for 108000 (3 hours)

TIMEOUT  108000

The OpenLM Difference

OpenLM allows users to harness the full capability of option files using a unique graphical user interface. This interface dramatically simplifies the process of managing license parameters by allowing companies to use active directory groups to automatically generate option files.

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 2008a: OpenLM database migration, from Firebird to MS-SQL

General

OpenLM is a license management tool that provides application usage monitoring for a variety of Concurrent license servers. These include FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy.

Scope

OpenLM provides an embedded Firebird database  as part of the software installation. It also supports different types of external databases, such as MS-SQL, Oracle and MySQL. This document is intended for system administrators who wish to perform an OpenLM database migration from the default Firebird to MS-SQL. It elaborates the process and tools required for such a migration. This document is closely related to the “Guide to OpenLM Data Migration Tool”, “OpenLM Database Configuration Form”  and “Backing Up Your OpenLM DB” documents, which are recommended for further reading.

Backup the current OpenLM database

It is good practice to begin with backing up the OpenLM database prior to migrating its content. In order to do so:

1. Navigate to the windows services (you can do that by searching for services.msc in the start menu’s search line).

2. Select the “OpenLM Server” service, and Click the Stop icon.

3. Backup the OpenLM database. Please refer to the “Backing Up Your OpenLM DB” document for a more detailed explanation.

Important note: Planning the workflow: Firebird 1.7 to MS-SQL 1.8

There are two routes for migrating Firebird 1.7 to MS-SQL 1.8:

Workflow 1: Migrate Firebird 1.7 to MS-SQL 1.7, and then upgrade MS-SQL 1.7 to MS-SQL 1.8

Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8, and then migrate Firebird 1.8 to MS-SQL 1.8.

We will relate to these two routes throughout this document.

At the time of writing this revision (Rev 1.0), only Workflow 1 is supported, but both are described in this document. Please follow through the steps required according to your selected workflow.

Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8

Upgrading of the Firebird database OpenLM Server version 1.7 to Firebird database OpenLM Server version 1.8 is done by simply installing the later OpenLM Server version over the old one. It is important to keep a copy of the database prior to this upgrade. For more information, please refer to this document:

Application Note 1101: Upgrade guide of OpenLM Version 1.7 to Version 1.8

Workflows 1 & 2: Creating a new MS-SQL Database (Building the tables)

Create a new empty database with OpenLM tables in MS-SQL. In order to do so, OpenLM supplies dedicated DDL scripts (*.SQL files) to be applied in the MS-SQL Database control application.

1. For Workflow 1: The DDL scripts for MS-SQL 1.7 databases are available for download here. The Downloaded file contains two files for MS-SQL servers.

For Workflow 2: The DDL scripts for MS-SQL 1.8 databases 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 choose the DDL scripts. The Downloaded file contains two files for MS-SQL servers.

2. Open the Microsoft SQL Server Management Studio

(Start → All Programs →  Microsoft SQL Server → SQL Server Management Studio).

3. Create a new DB: Right click the  “Databases” icon. select  “New Database” from the pop-up menu, as shown below.

4. Enter a new name for the database (e.g.: db_name) and click OK.

5. For workflow 1: Drag the “OpenLM_SQLServer.SQL” file from the downloaded directory over to the Microsoft SQL Management Studio window. The Contents of “OpenLM_SQLServer.SQL” is displayed. (The file can also be opened by clicking “File → Open → File…” and selecting “OpenLM_SQLServer.SQL” from the unzipped folder).

For workflow 2: Drag the “OpenLM_SQLServer_1.8.0.SQL” file from the downloaded directory over to the Microsoft SQL Management Studio window. The Contents of “OpenLM_SQLServer_1.8.0.SQL” is displayed. (The file can also be opened by clicking “File → Open → File…” and selecting “OpenLM_SQLServer_1.8.0.SQL” from the unzipped folder).

6. Enter the new database name after the word “use” as shown below (e.g.: db_name) and click “Execute”

7. Wait until you see the message  “Query executed successfully” as shown below:

Workflows 1 & 2: Data Migration

Now we get to the actual migration of data from Firebird to MS-SQL:

1. Make sure that the original Firebird DB is backed up, according to this document.

2. Open the “OpenLM Data Migration” tool.

For workflow 1: Data migration is done from Firebird 1.7 → MS-SQL 1.7. Use the data migration 1.7 version.

For workflow 2: Data migration is done from Firebird 1.8 → MS-SQL 1.8. Use the data migration 1.8 version.

3. On the Source frame:

3a. Select “Firebird”. The “Database Credentials” window appears:

3b. Enter the Firebird database path in the appropriate text box.

3c. Select your database(*.FDB) and enter the username and password. By default, the username is set to ‘sysdba’ and the password is ‘masterkey’

4. Target frame actions:

4a. Type in the MS-SQL Server name.

4b. Select the ‘MS-SQL’ radio button. The “Database Credentials” window appears.

4c. In the “MS-SQL Service” text box type in the MS-SQL instance name.

4d. The MS-SQL default port is set to 1521

4e. Set the Username and Password, and click OK.

5. After configuring the Source and Target databases, click the ‘Transfer’ button to begin the migration process. At the end of the migration, a notifier window appears.

Please refer to the “Guide to OpenLM Data Migration Tool” document for further information.

Workflow 1: Upgrade MS-SQL 1.7 to MS-SQL 1.8

Upgrading the MS-SQL 1.7 database to 1.8 is done by applying the 2nd SQL script (‘OpenLM_SQLServer_1.8.0_Upgrade.sql’) downloaded as part of the “Workflows 1 & 2: Creating a new MS-SQL Database (Building the tables)” section above. Drag it over to the Microsoft SQL Management Studio, and run it. The OpenLM MS-SQL schema is upgraded to version 1.8.

Configuring Openlm to work with the SQL server

Now the OpenLM server must be made to reference the new SQL Server.

1. Open the “OpenLM Database Configuration” tool:

(Start → All Programs → OpenLM → Server → OpenLM Database configuration)

.

2. Click the DB provider drop-down menu. Choose one of the options: “SQL Server Authentication” or “Windows Authentication mode”. The “OpenLM Database Configuration” window changes accordingly:

3. Fill in the information in the blank text boxes.

4. Click “Check” to check the OpenLM server’s connection to SQL Server.

5. Click “Apply” to finish the configuration.

Please refer to “OpenLM Database Configuration Form” for further information.

Revision

Rev 1.0, May 30 2013.

 

Please follow and like us:

Application Note 2008b: OpenLM database migration, from Firebird 1.7 to Oracle 1.8

General

OpenLM is a license management tool that provides application usage monitoring for a variety of Concurrent license servers. These include FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy.

Scope

OpenLM provides an embedded Firebird database  as part of the software installation. It also supports different types of external databases, such as MS-SQL, Oracle and MySQL. This document is intended for system administrators who wish to perform an OpenLM database migration from the default Firebird to Oracle. It elaborates the process and tools required for such a migration. This document is closely related to the “Guide to OpenLM Data Migration Tool”, “OpenLM Database Configuration Form”  and “Backing Up Your OpenLM DB” documents, which are recommended for further reading.

Backup the current OpenLM database

It is good practice to begin with backing up the OpenLM database prior to migrating its content. In order to do so:

1. Navigate to the windows services (you can do that by searching for services.msc in the start menu’s search line).

2. Select the “OpenLM Server” service, and Click the Stop icon.

3. Backup the OpenLM database. Please refer to the “Backing Up Your OpenLM DB” document for a more detailed explanation.

Prerequisites

1. Download “ODAC 11.2 Release 5 (11.2.0.3.20) with Xcopy Deployment” for 64 or 32 bit from oracle.com.

32b: http://www.oracle.com/technetwork/database/windows/downloads/index-101290.html

64b: http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html)

2. Unzip the file downloaded in Step 1. The ODAC1120320Xcopy_x64\32 folder is created.

3. Copy the following Dll’s to two locations:

3a. The Openlm server installation folder \bin directory

(usually located in: “C:\Program Files (x86)\OpenLM\OpenLM Server\bin”), and

3b. The data migration folder:

(usually located in: “C:\Program Files (x86)\OpenLM\OpenLM Data Migration”).

  • ODAC1120320Xcopy_x64\instantclient_11_2\oci.dll

  • ODAC1120320Xcopy_x64\instantclient_11_2\ociw32.dll

  • ODAC1120320Xcopy_x64\instantclient_11_2\orannzsbb11.dll

  • ODAC1120320Xcopy_x64\instantclient_11_2\oraocci11.dll

  • ODAC1120320Xcopy_x64\instantclient_11_2\oraociei11.dll

  • ODAC1120320Xcopy_x64\instantclient_11_2\orasql11.dll

  • ODAC1120320Xcopy_x64\odp.net4\bin\OraOps11w.dll

Important note: Planning the workflow: Firebird 1.7 to Oracle 1.8

There are two routes for migrating Firebird 1.7 to Oracle 1.8:

Workflow 1: Migrate Firebird 1.7 to Oracle 1.7, and then upgrade Oracle 1.7 to Oracle 1.8

Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8, and then migrate Firebird 1.8 to Oracle 1.8.

We will relate to these two routes throughout this document.

Workflow 2: Upgrade Firebird 1.7 to Firebird 1.8

Upgrading of the Firebird database OpenLM Server version 1.7 to Firebird database OpenLM Server version 1.8 is done by simply installing the later OpenLM Server version over the old one. It is important to keep a copy of the database prior to this upgrade. For more information, please refer to this document:

Application Note 1101: Upgrade guide of OpenLM Version 1.7 to Version 1.8

Workflows 1 & 2: Creating a new Oracle Database (Building the tables)

Create a new empty database with OpenLM tables in Oracle. In order to do so, OpenLM supplies dedicated DDL scripts (*.SQL files) to be applied in the Oracle Database control application.

1. For Workflow 1: The DDL scripts for Oracle 1.7 databases are available for download here. The Downloaded file contains two files for Oracle servers.

For Workflow 2: The DDL scripts for Oracle 1.8 databases 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 choose the DDL scripts. The Downloaded file contains two files for Oracle servers.

2. Open the Oracle Database control application from the Windows start button. Use only Microsoft’s Internet Explorer.

3. Create a new OpenLM Schema in the Oracle database

3a. Create a new User:

3b. Select the Server tab, and click the “Users” link (see below).

3c. Create a new user. Add the following Roles and System Privileges to the user:

  • Roles: CONNECT

  • RESOURCE

  • System Privileges: add all System Privileges.

4. Open the Oracle SQL developer, and create a new connection. Log in to that connection with the previously defined Username and Password.

For workflow 1: Drag the “OpenLM_Oracle.sql” file from the downloaded directory over onto the Oracle SQL developer window. The Contents of “OpenLM_Oracle.sql” is displayed.

Run the SQL script. The OpenLM 1.7 schema is created in Oracle.

For workflow 2: Drag the “OpenLM_Oracle_1.8.0.sql” file from the downloaded directory over to the Oracle SQL developer window. The Contents of “OpenLM_Oracle_1.8.0.sql” is displayed. Run the SQL script. The OpenLM 1.8 schema is created in Oracle.

Workflows 1 & 2: Data Migration

Now we get to the actual migration of data from Firebird to Oracle:

1. Make sure that the original Firebird DB is backed up, according to this document.

2. Open the “OpenLM Data Migration” tool.

For workflow 1: Data migration is done from Firebird 1.7 → Oracle 1.7. Use the data migration 1.7 version.

For workflow 2: Data migration is done from Firebird 1.8 → Oracle 1.8. Use the data migration 1.8 version.

3. On the Source frame:

3a. Select “Firebird”. The “Database Credentials” window appears:

3b. Enter the Firebird database path in the appropriate text box.

3c. Select your database(*.FDB) and enter the username and password. By default, the username is set to ‘sysdba’ and the password is ‘masterkey’

4. Target frame actions:

4a. Type in the Oracle Server name.

4b. Select the ‘Oracle’ radio button. The “Database Credentials” window appears.

4c. In the “Oracle Service” text box type in the Oracle instance name.

4d. The Oracle default port is set to 1521

4e. Set the Username and Password, and click OK.

5. After configuring the Source and Target databases, click the ‘Transfer’ button to begin the migration process. At the end of the migration, a notifier window appears.

Please refer to the “Guide to OpenLM Data Migration Tool” document for further information.

Workflow 1: Upgrade Oracle 1.7 to Oracle 1.8

Upgrading the Oracle 1.7 database to 1.8 is done by applying the 2nd SQL script (‘OpenLM_Oracle_1.8.0_Upgrade.sql’) downloaded as part of the “Workflows 1 & 2: Creating a new Oracle Database (Building the tables)” section above. Drag it to the Oracle SQL developer window, and run it. The OpenLM Oracle schema is upgraded to version 1.8.

Configuring Openlm to work with the Oracle database

Now the OpenLM server must be made to refer to the new Oracle database.

1. Open the “OpenLM Database Configuration” tool:

(Start → All Programs → OpenLM → Server → OpenLM Database configuration).

2. Click the DB provider drop-down menu, and select ‘Oracle’.

3. Fill in the information in the blank text boxes. See example below.

4. Click “Check” to check the OpenLM server’s connection to the Oracle DB

5. Click “Apply” to finish the configuration.

Please refer to “OpenLM Database Configuration Form” for further information.

Revision

Rev 1.1, September 11 2013.

Please follow and like us:

Application Note 2005a: Monitoring Idle Application time, and Closing Licenses manually via the “Currently Consumed Licenses”

License managers may sometimes label licenses as occupied, when in fact they are idle and wasting limited company resources. System administrators can utilize the OpenLM EasyAdmin web interface to identify such conditions and retrieve idle licenses either manually or automatically.

This document describes how to monitor application idle time and harvest idle licenses manually. For information on retrieving licenses automatically – please refer to this document:

Application Note 2005: Configuring OpenLM to close idle Licenses, OpenLM v1.8

User Idle

If the user has not been actively using the license, the idle time period would be shown in the “User Idle” column. This information is sampled by the OpenLM Agent module on each client workstation, and sent to the OpenLM server. The sample period is set by the Agent policy’s “Agent report” period, as in the example below (set to 60 sec).

The “Currently Consumed Licenses” Window:

Open the OpenLM Easyadmin tool and press ‘Start’ → ‘Operational’ → “Currently Consumed Licenses”. The “Currently Consumed Licenses” window opens:

This window lists all currently active sessions. With this window, administrators can monitor individual workstations that run licensed applications. They can detect idle applications, and shut them down with a mouse click. In order to do so, an OpenLM Agent module must be installed on each client workstation.

OpenLM Extension

Some functionality of the “Currently Consumed Licenses” window is “Extension dedicated”, i.e.: only available for applications and installations that incorporate the OpenLM extension. At the time of writing this revision (Rev 1.0) these applications include Autodesk, ArcGIS and Matlab. For more information on this – please refer to the Automatic license retrieval document:

Application Note 2005: Configuring OpenLM to close idle Licenses, OpenLM v1.8

Workstation Idle Time:

The end user’s workstation’s idle time is recorded and presented in the “Workstation Idle time” column. This report requires an active agent to be installed on the workstation.

Recent APP. Idle Period:

Records the recent idle time of a specific application. This activity requires an Agent installation on the end user’s workstation, and is “Extension Dedicated”.

View Idle Times:

Click the crescent moon icon   for a graphic view of idle and active time as well as a list of idle periods. This report requires an active agent and is “Extension Dedicated” .

 

Removing licenses

Administrators have the option to manually remove a license from a specified workstation. This is done by highlighting the user row on the Active Products window and clicking the “Remove License” icon    . There are several constraints that are specific to this feature:

  • The end user must have been inactive for a minimum period of time in order for this license to be retrieved. This value is set by default to 5 minutes in compliance with FLEXlm license manager’s limitations.

  • If the license is not really associated with any real product activity on the specified workstation (as happens when a license gets artificially “frozen” on a computer), then the license will be freed and will be returned to the pool of available licenses.

  • If the worker is actually using the product, then re-obtaining a license would be automatically attempted. If this happens the license for that product and workstation will reappear on the active products screen, with a new handle number.

Closing applications

In order to manually close an application on the workstation,  an administrator should highlight the relevant row, and click the Close Application icon .

This operation will retrieve the license back to the license pool, save the open project,  and the application itself will be shut down.

There are some constraints that are specific to this feature:

  • It requires a proper installation of the OpenLM Agent module.

  • It works only on extension enabled applications. At the time of writing this revision (Rev 1.0), these include Matlab, ArcGIS and AutoCAD.

Common Constraints

There are several constraints that are common to both the License Removal and Application Closure features.These are as follows:

  • At the time of writing this revision (Rev 1.0), These features are only applicable to the FLEXlm license manager.

  • An OpenLM Agent module must be properly installed on each Client workstation.

  • Borrowed licenses (AKA “Linger licenses”) can not be retrieved via the EasyAdmin application.

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:

What is new in OpenLM version 1.8

OpenLM 1.8 is out !

The release of this milestone version is a big deal for us here in OpenLM, and we are sure you will feel the same when you start working with it.

Note for OpenLM veterans:

At this stage we recommend not to upgrade OpenLM 1.7 production systems to 1.8, but rather to install it at a sandbox, side by side with the 1.7 production server. This is in order to ensure that full functionality has been maintained in your environment, and to familiarize yourself with the new version.

This document goes over the main features that have been added or enhanced in this version, and the list is quite long:

  • OpenLM Server engine
  • EasyAdmin: Personalization, New reports, Enhanced report windows,
    Moving configuration options to EasyAdmin
  • Support of License management tools
  • Active Directory
  • Named Users support
  • Packages
  • Projects
  • Permissions
  • License Usage
  • License Procurement table
  • License Usage Efficiency report window
  • Licenses not in use report window
  • Recent Feature Denials report window
  • License Servers
  • Session Idle time measurement
  • Database manipulation
  • ArcGIS Borrowed Licenses issue
  • OpenLM Broker
  • OpenLM Agent
  • ArcGIS Set Licensing level tool
  • Installation Process
  • Logs uploader

OpenLM Server engine

The OpenLM server integrates information from various sources in order to create accurate and coherent license usage information. All processing algorithms were reviewed and rewritten as needed in order to improve accuracy and processing speed.

EasyAdmin

The EasyAdmin web application has undergone facelift surgery, is more user friendly, and generally looks nicer. Some graphic presentation windows have been added, and others have been improved in both clarity and robustness.

Personalization:

EasyAdmin windows’ configuration and user settings are now maintained by the OpenLM database, not on the browser’s cache memory (as was in version 1.7). This provides the ability to personalize the EasyAdmin appearance, and get the same user’s view on different computers.

New reports

The new reports are hereby listed. Elaboration on each of these windows is provided below:

  • The License denial widget.
  • Procurement table: Shows licenses’ procurement path, providing detailed expiration information.
  • License usage efficiency report: Histogram per single feature, showing how much of the time have N licenses been used.

Enhanced report windows

Report windows have also been enhanced. It is now possible to:

  • Export chart images or PDF documents and
  • Set report window refresh period


Moving more configuration options to EasyAdmin

Several configuration options were moved from the OpenLM server configuration tool to the EasyAdmin web application, making them accessible from anywhere. One such option is the usage logging according to projects, as depicted below:

Support of License management tools

The addition of license management tools to the expanding portfolio of OpenLM’s supported license managers is an on-going task. Version 1.8 now supports the following concurrent license servers: FlexLM / Flexnet, Sentinel RMS (Aspentech SLM), DSLS, IBM LUM, Sentinel HASP, LM-X (Altair), Reprise RLM, Beta-LM, Mathematica LM (MathLM), and Easycopy. In addition to that, support of some license management tools was enhanced. Here are some of these enhancements:

  • FlexLM: Asset Info information, which is unique per license pool is now monitored. Hence, it is now possible to follow user and group license check out per license pool.
  • FlexLM: Software packages are automatically recognized, and populated by the respective software products. Single features can be associated with different software packages.
  • IBM_LUM license manager monitoring has been added expiration date.
  • IBM_LUM Offline Licenses indications.
  • IBM_LUM HAL (High Availability Licensing) configuration support.
  • DSLS has been fully integrated into the OpenLM 1.8 system.
  • DSLS License borrowing is reported.
  • BetaLM has been introduced in the 1.8 version.
  • BetaLM Cluster configuration is supported.
  • RMS: License versions’ reporting was added.
  • Easycopy LM has been fully integrated into the OpenLM 1.8 system.
  • Matematica (MathLM) has been fully integrated into the OpenLM 1.8 system.

Active Directory

The OpenLM Server is capable of synchronizing users and groups with an organization’s LDAP (Active Directory) to combine license management with other company information. LDAP synchronization provides automatic maintenance of Users’ and Groups’ data.

In version 1.8, Active Directory synchronization has been profoundly improved, to support versatile and complex Active Directory environments. As a bonus, a preview of the impending synchronization scheme is now available. For more information please refer to these documents:

Application Note 2029_a: LDAP (Active Directory) Synchronization. Basic guide v1.8

Application Note 2029_b: LDAP (Active Directory) Synchronization. Comprehensive guide v1.8

Version 1.8 now allows system managers to easily synchronize very complex structures of LDAP. In EasyAdmin the user can now control the execution of the synchronization, exclude groups and users from synchronizing and understand why each synchronized entity was generated.

EasyAdmin incorporates new administrative tools for LDAP synchronization. These provide a better view of the synchronization definitions and the relations between synchronized entities. Group and Users entities are interconnected by hyperlinks, to facilitate the browsing through LDAP synchronized data.

Named licenses support

FlexLM gets its licensing information from the license file, option file and other resources.

The License file contains the asset info information which is unique for every license pool.

The License file also contains asset info associated with groups. OpenLM Version 1.8 can be configured to read Flexnet publisher license files, and hence can report which user takes licenses from which pool.

License Suites and packages

OpenLM 1.8 is capable of integrating more information from FlexLM license files. One of the benefits of that is the capability of arranging licensed features within their respective license packages. The user does no longer need to configure packages’ members manually.

In addition to that, OpenLM 1.8 supports licensing schemes in which single features are associated with two different packages.

Projects

The Project license usage recording capability is available for OpenLM from version 1.6 onwards. In the 1.8 version, some major modifications have been made:

  • The configuration of Project monitoring was shifted from the OpenLM Server configuration tool to the EasyAdmin web application.
  • Administrative capabilities have been added, such as Enabling / Disabling a project, assigning it a priority and expected duration, and marking the project’s completeness percentage.
  • Projects can now be assigned to user groups (not just to individual users).
  • Projects can also be introduced by end-users via the OpenLM Agent module. Please see the ‘Agent’ section below for more information on that.

For more information on monitoring licenses according to projects in OpenLM 1.8 please refer to this document:

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

Permissions

New users are automatically associated to the “Everyone” group. After being synchronized (or associated manually) to a different group – the new group becomes the default group.

License Usage

The central “License Usage” window’s graphic presentation was improved, and now employs a cleaner GUI, with a zoom-in option.

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.

License Efficiency report

A new window that provides a histogram of usage for a single feature, showing how much of the time have N licenses been used. The image below clearly demonstrates ineffective usage of the pool of licenses:

Licenses not in use report

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

Recent Feature Denials report

A graphic presentation to show a comparative chart of the number of license denials over predefined periods of time: recent and long term.

License Servers

Reported license servers’ information has been enhanced to include:

  • License server timezone
  • Status of the OpenLM broker installed on the license server machine
  • Host availability indication


Session Idle time measurement

Graphical waveform presentation of the Active / Idle ratio for currently and historical sessions.

Database manipulation

Version 1.8 enhances the administrator’s capabilities to manipulate the OpenLM database. It is now possible to

  • Archive or delete old data.
  • Extract irrelevant users and
  • Delete unnecessary groups.

ArcGIS Borrowed Licenses issue

We previously reported an issue pertaining to the upgrade of ArcGIS to the newer FlexLM version. This issue manifested in erroneous reporting of license borrowing. OpenLM 1.8 bypasses this issue and shows the actual borrowing user.

OpenLM Broker

The OpenLM Broker has undergone important changes. These include:

  • Enhanced robustness
  • Enhanced compatibility with a wide array of license managers
  • Ability to read FlexLM license files and Audit logs, in addition to Option files.
  • Implementation of buffers for Broker messages, providing the ability to overcome limited network connectivity failure and continues usage reported even if the OpenLM Server machine crashes for long period of times.

OpenLM Agent

The OpenLM Agent has changed skin and looks much nicer now.

It also integrated the improvements for the following features:

  • Restoring of closed sessions
  • Searching and sorting of the license usage list
  • Selectively hiding or showing specific features
  • ArcGIS licensing level determination (see below).
  • As mentioned above, projects can be introduced by end-users via the OpenLM Agent. 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.

ArcGIS Set Licensing level tool

ESRI implementation is unique in the sense that you can activate the ArcMap software in three different licensing levels:

  • Basic (Previously called viewer or ArcView)
  • Standard (Previously called ‘ArcEditor’)
  • Advanced (Previously called ‘ArcInfo’)

ArcGIS end users can set the licensing level before activating the software. If such a license is available, the software will start. OpenLM has provided this capability since version 1.6 of the software. In version 1.8 we have highly enhanced it:

  • It is now possible to set the licensing level according to available licenses, and
  • The user can choose whether to save the ArcGIS licensing level to the Registry, to do it on a user level, or on a system level (for all users – requires administrative permissions).

Installation Process

The OpenLM installation process has been standardized, and is more coherent on OpenLM version 1.8.

Logs uploader

The Logs uploader has been rewritten, and its robustness has been improved.

Please follow and like us: