Monthly Archives: February 2012

OpenLM Maintenance Release Version 1.7.2.3

Posted on by

Version 1.7.2.3

Version 1.7.2.3 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.2.3:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.


What’s new in version 1.7.2.3 ?

OpenLM Server:

  1. Added estimated end time when license server is down.
  2. Fixed Oracle interface to deal with truncation of license output blobs bigger than 2000 characters. This is an important update for users of Oracle database.
  3. Replaced EasyAdmin cookies with local storage. Fixed repetitive appearance of “Enter time zone” in Internet Explorer.

OpenLM Software University Program

Posted on by

OpenLM is a worldwide operating software specialist for management and monitoring of network licenses (floating, concurrent user, token based) utilization. OpenLM’s Software provides a comprehensive management solution for license management software such as FLEXlm, FLEXnet, Sentinel RMS, Sentinel HASP, RLM, IBM LUM DSLS and LM-X.

Universities naturally hold an extensive profile of licensed software applications, a vast population of users set in various groups, and different levels of license usage permissions. Handling a database of this magnitude and complexity is a real challenge.

This is where OpenLM’s benefits show. OpenLM eases the management of diverse license databases, and introduces the option for cost allocation per usage for software licenses, thus reducing usage costs considerably, and minimizing the need for further license acquisition.

In order to improve OpenLM’s cooperation with universities, OpenLM has introduced its new university program. This program provides a professional solution for universities to manage and monitor the utilization of software products like CAD, CAE, Software Engineering and GIS. The program’s pricing scheme takes the universities’ financial considerations into account.

We are convinced that the apparent assets that the OpenLM software brings to license management would be highly appreciated by Universities, and that these benefits would be embraced by faculties such as Engineering (Electrical, Mechanical, Aerodynamics, etc), Physics, Informatics, Architecture and Geo-sciences. OpenLM has been known to improve the utilization of prominent licensed application such as  Autodesk Autocad, ESRI ArcGIS, MATLAB, PTC and CATIA by as much as 30%.

Universities and departments that are interested in this program should contact OpenLM through info@openlm.com.

 

OpenLM Maintenance Release Version 1.7.2.1

Posted on by

Version 1.7.2.1

Version 1.7.2.1 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.2.1:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.

What’s new in version 1.7.2.1 ?

OpenLM Server:

  1. Fix for logs uploader.
  2. Fix for DataExporter (timeout for http request).

OpenLM Agent (version 1.7.1.0)

  1. Fixed an issue that caused the software to close without showing a notification – in some cases.
  2. Fix localization issues for countries that use comma (,) as decimal point.
  3. Fix Portuguese configuration form (Bug #309).
  4. “License Usage Information” now shows available licenses.
  5. Improved “License Usage Information” & “Recently Closed Documents” windows loading time.

 

Flexera FLEXnet license management implementation in ESRI ArcGIS 10

Posted on by

Licensing ArcGIS version 10

It is a common misconception that migrating to ArcGIS version 10 replaces the licensing software. This is incorrect; ESRI has only upgraded the old FLEXlm version to a newer one. The FLEXlm licensing software has gone through many changes during the passed several years, and is now called FLEXera FLEXnet for publishers. For every practical term – it is still the same good old FLEXlm software.

The main changes

The main changes that have been implemented in the ESRI ArcGIS licensing scheme include:

  • The FLEXlm (Flexnet) license management tool was upgraded from version 7.* to version 11.6.
  • The license file was replaced with trusted storage, in order to enhance security.
  • The FLEXlm LMTOOLS UI is not provided with the ESRI ArcGIS 10 package. ESRI provides it’s own management tools.
  • Borrowing licenses is made possible in ESRI ArcGIS 10.

Problems

Some problems have appeared in FlexLM reporting alongside these changes:

  • Due to the use of FLEXera trusted storage some imporant FLEXlm management tools are malfunctioning, for example, lmutil.
  • The FlexLM ‘lmremove’ utility has been omitted from the pool of license management commands. This is a known ESRI ArcGIS version 10 issue.
  • ArcGIS 10 monitors Borrowed licenses on its proprietary interface. The license output file tends to be inaccurate when it comes to reporting Borrowed licenses. The Identity of the users who borrowed licenses is also concealed from the output file.

Effect of these issues on OpenLM

These issues have imposed several limitations on the capabilities of OpenLM when interfacing ESRI ArcGIS 10.

  • Instead of the old ‘linger’ license output-file line, Borrowed licenses are marked with the “ACTIVATED LICENSE” line. These lines’ syntax excludes the identity of the user who borrowed the licenses.
  • The output-file lmutil lmstat information regarding license borrowing is inaccurate; “ACTIVATED LICENSE” lines are multiplied, effectively increasing the number of licenses reported as borrowed.
  • The absence of the “lmremove” utility implies that the ArcGIS license can not be removed, thus application the use of the “Suspend and Resume” method is not possible in OpenLM. Also, for the same reason, the “License removal” button in the “Active products” window is not functional.

The OpenLM Advantage

The OpenLM Active Agent may still “Save and Close” the ArcGIS 10 extension enabled application. This is regardless of the omission of the “lmremove” command. The closure process employs the applications’ own closure APIs, sent by the Active Agent, and applied by the OpenLM extension. Closing ArcGIS 10 may also be done via the “Close Application” button on EasyAdmin’s “Active Products” window.

This makes OpenLM the only solution for remotely saving & closing ArcGIS 10.

OpenLM Performance Test

Posted on by

Scope

This document describes the performance tests done by OpenLM’s support team in order to help customers to choose the suitable configuration for their systems.

These tests evaluate the performance of the OpenLM system using 32 and 64 bit operating systems, different number of CPUs, different memory sizes and with external or internal databases.
The results of these tests promote a knowledge base that enables users to select the best database for their machine; A database that would maximize the performance of their OpenLM system.

Table of Contents:

OpenLM Performance Test


Scope:
Table of Contents:
Test environment
Test Data
The test stages:
Firebird DB (Embedded):
Operating System: Windows 7 32bit
Operating System: Windows 7 64bit
Microsoft SQL Server DB :
Operating System: Windows 7 32bit
Oracle:
Results:
Discussion and Recomendations

Test environment

The test was done using two computers with Intel I5 processor with 4 GB RAM. During the test the OpenLM Server was running on a virtual machine employing different amounts of memory and CPU.

When we tested the system using external databases, the external DB software (Oracle or MS SQL Server) ran on a different machine; not on the machine on which the OpenLM Server was run.

The queries were sent to the OpenLM Server virtual machine using a dedicated software developed for this purpose. This software was designed to send a set of queries to the OpenLM Server. It awaits acknowledgement, and calculates the elapsed time period.

The tests were conducted in the following environments:

  1. Windows 7 32 bit operating system:
    1 CPU, 1 GB base memory
    1 CPU, 2 GB base memory
    2 CPUs, 1 GB base memory
    2 CPUs, 2 GB base memory
    4 CPUs, 1 GB base memory
    4 CPUs, 2 GB base memory

  2. Windows 7 64 bit operating system:
    1 CPU, 1 GB base memory
    1 CPU, 2 GB base memory
    2 CPUs, 1 GB base memory
    2 CPUs, 2 GB base memory
    4 CPUs, 1 GB base memory
    4 CPUs, 2 GB base memory


Test Data

The test environment database is an actual customer’s database, that was selected as a test case. It contains information on more than 20 different license servers and vast number of stored license sessions. The magnitude of this database enables us to assess the performance of the OpenLM Server in big organizations.

The test benchmark data consists of 10 queries, submitted to the OpenLM Server. Each query fetches 100 records. The following set of queries was sent to the OpenLM server 3 times, sequentially:

  1. Alerts query.

  2. Denials query

  3. Denials query with a specific feature.

  4. License Activity report query

  5. License Activity report query- fetching the information of a specific feature

  6. License Activity report query- fetching the information of a specific server and vendor

  7. License usage report query.

  8. License usage report query – fetching the information of a specific vendor and feature.

  9. Server statistics query.

  10. Selected feature statistics query.

The test stages

The tests were conducted using various system configurations, evaluating the effect of different parameters on the system’s performance. The test variable parameters included:

  • The Number of CPUs on the OpenLM server machine: 1, 2, and 4 CPUs.

  • The Virtual Windows 7 operating system version: 32 bits Versus 64 bits.

  • Different external and internal Databases were examined:

    • Internal database (OpenLM’s default DB): Firebird embedded DB.

    • External databases: MS SQL server, Oracle.

The test results

Firebird DB (Embedded):
Operating System: Windows 7 32bit


Operating System: Windows 7 64bit
Microsoft SQL Server DB :
Operating System: Windows 7 32bit


Operating System: Windows 7 64bit


Oracle DB:

Operating System: Windows 7 32bit

Operating System: Windows 7 64bit

The test limitations

The test is limited by a few factors, due to our ability to build a test environment:

  1. Not a live system

We have used a big DB from a live system, but during the test OpenLM did not have to deal with routine tasks such as:

    • Receiving and processing broker information.

    • Query license server information and update DB tables.

    • Responding to Agent requests.

Please note that the OpenLM Server is a multi threaded system. Each of these tasks is processed in separate thread, so the effect of this factor is unknown.

  1. Limited RAM configurations

We were limited to a single machine with a total of 4 GB of RAM. This limited our OpenLM Server machine memory allocation to 2 GB. We have experienced slight differences in performance between 1 and 2 GB RAM when using Oracle and MS-SQL, in favor of the 2GB configurations. Firebird DB demonstrated a big difference between 1GB and 2GB of RAM in favor of 2GB.

  1. The limitation of the testing tool

The testing tool sequentially sends the same set of queries to the OpenLM Server. We have used 10 unique queries that were each sent 3 times to the server. This method may have created a diversion in favor of databases that have cache memories, such as Oracle and MS SQL Server.


Result Analysis

  1. The results show significant differences in performance between the embedded Firebird database systems and external database systems such as MS-SQL and Oracle, in favour of the external databases. In some cases the external database performed in excess of 10 times faster than the embedded one.

  2. The performance of MS-SQL was noticeably better than that of the other external database we have tested: the Oracle database.

  3. We have witnessed a positive linkage between the Server’s performance and the allocated memory size: The performance of 2GB was generally better than that of 1GB. This is especially evident when referring to the embedded Firebird database.

  4. On the embedded Firebird DB, we have seen improved performance when using the windows 64 bit OS, in comparison to 32Bit OS. This was not true in the case of external databases; Oracle and MS-SQL. The performance in the latter was better using a 32 bit OS.

  5. The results were inconclusive in regards to the added value of additional CPUs on the test performance. There was an inclination towards a positive linkage between the number of CPUs and the performance in regards to embedded Firebird databases, when using a 64bit  OS.

Discussion and Recommendations

The tests we have performed are informative but limited due to the limitations listed in the limitation section. We would like to recommend the following guidelines to customers designing their system architecture:

The use of an external DB significantly contributes to the performance of the system. External database also provides multiple user access, scalability and other benefits. The downside of having an external DB is higher costs and need for a professional workforce that is required for maintaining such databases. When considering the MS-SQL database vs Oracle’s database, we have found the prior to perform better.

We recommend using extensive RAM; 2GB has performed better that 1GB.

Based on these tests, we are not able to recommend a 64 bit system over a 32 bit system. We think that the benefits of a 64 bit system may become significant when more than 4 GB or RAM is available. Because of that we prefer 64 bit operating system when available.

OpenLM Newsletter 2012 #01

Posted on by


Dear valued OpenLM users,

On this first edition of the OpenLM 2012 Newsletter I would like to greet you all, and wish you a happy and successful new year. 2011 has been very good for us here at OpenLM, all thanks to your support. Our team has grown bigger, and is now able to provide better support to our improved product.

We are proud to introduce the OpenLM Mobile touch interface. This interface may run on any mobile device operating system; e.g.: IOs, Android, Blackberry, Windows Mobile etc. With the help of some of our faithful customers, we have managed to perform a successful Beta trial for this interface. The OpenLM Mobile Touch interface is available to all customers under a valid maintenance agreement with no additional cost.

Based upon requests from our customers, and following Dassault Systemes migration from IBM-LUM to their proprietary DSLS license manager, OpenLM has quickly adapted to provide support to DSLS. We look forward to receiving further customer requests, in order to meet our users’ needs.

We have recently launched a new and enhanced company website. This site is clearer, more informative, useful and generally – nicer than our old one. Among other things, It features a new introductory animated video on OpenLM. We hope that you will like it.

Best Regards,

Oren Gabay, CEO

OpenLM updates

OpenLM goes mobile !

 

The OpenLM EasyAdmin Mobile application enables system administrators to keep track of the license management systems, while being out of office. This document describes the essentials of the OpenLM EasyAdmin for mobile application; installing the application, and running it on a Mobile set.Read more…

 

OpenLM Live Webinars

OpenLM is now hosting a couple of Online Webex Webinars each week. This Webinars give an overview of the OpenLM system; its components and capabilities, and is intended for newbies as well as for experienced users. Please check out the date for the next webex Webinar on OpenLM’s site.

OpenLM resources

OpenLM introductory video

 

 

 

 

 

OpenLM Video tutorials: OpenLM server configuration – License server tab

 

 

 

 

 

 

OpenLM Video tutorials: Active Directory Synchronization

 

 

 

 

 

 

Monthly Articles

Get more out of your floating licenses

Being this our first edition of the OpenLM Newsletter for 2012, We found it adequate to give a brief summary of what the OpenLM utilizer actually is. This is good reading material for Newbees, and nice to remember for more experienced users. Read more…

OpenLM system structure

Another important article for first timers, this one elaborates all about the OpenLM system structure; Where should every module be installed, and what are the interconnections between them. Read more…

Products and Packaged licenses in OpenLMs EasyAdmin web application

This Article deals with two adjacent subjects: Renaming features as products, and gathering these features into licensed packages in the OpenLM EasyAdmin web application. Read more…

Configuring FLEXlm FLEXnet Option File Using OpenLM Easy Admin

FLEXlm (Flexera FLEXnet) option files grant license administrators close control over various operating parameters within the constraints of the license model. Licensed features can be dedicated, denied or reserved to users or groups of users, according to the option files setting.

The OpenLM solution incorporates synchronization of License administration tools with the organizations LDAP (Active Directory), keeping the FLEXlm option file up-to-date as users leave or join the organization, or move between groups. Read more…

 

Points of interest

IBM Rational – FlexNet Token based licensing:

The IBM Rational License Server uses FLEXnet for licensing IBM Rational products. This article presents the main characteristics of FlexNet Token based licensing, and the benefits of this method. Read more…

Autodesk cascade licensing and the PLIST

Cascade Licensing allows a product to obtain a license from a network license manager pool when that license manager is servicing more than one product. Cascading was implemented primarily to address mixed-product environments where both suite and base products co-exist.

Read more…

FlexNet Producer Suite Is Distinguished by the Frost & Sullivan 2011 Market Share Leadership Award for Software-Enforced License Management

The Frost & Sullivan Award for Market Share Leadership is presented to the company that has demonstrated excellence in capturing the highest market share within a segment of its industry. Read more…

OpenLM Maintenance Release Version 1.7.2.0

Posted on by

Version 1.7.2.0

Version 1.7.2.0 is a maintenance release to version 1.7. It contains some bug fixes to problems found in previous versions. We  recommend that users to whom these problems may be relevant to upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.2.0:

  1. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
  2. Stop the OpenLM Server service
  3. Make sure ALL windows are closed; especially the services window.
  4. Install the new version on top of the existing one.


What’s new in version 1.7.2.0 ?

OpenLM Server:

  1. Updated Firebird .Net Connector to the latest version. This component has caused unexpected crashes of the OpenLM Server for Firebird users.
  2. Fix denials chart by day sorting.
  3. Multiple sessions created because of cross-threading access (login problem).
  4. Fix “Server Error” when deleting package in “Products/Packages” window.
  5. Fix RLM license reading when RLM server is on a remote server.
  6. Add reservation when loading the touch App on FF or IE.
  7. Fix bug in license reading when license expiration date is missing.

 

 

OpenLM Broker (version 1.7.1.8):

Fixed installation bug: incorrect indication of preexisting Broker installation.

Trouble Shoot Form: EasyAdmin Item 001 (Unable to connect to EasyAdmin)

Posted on by

Title Unable to connect to EasyAdmin
Category EasyAdmin web application
Date Oct 11, 2011
Handled by -
Relevant Links
Applies to license managers FLEXlm, FLEXnet, IBM LUM, HASP, RLM, Sentinel RMS
Applies to license model Floating licenses, Network licenses, Concurrent licenses
Symptoms Customer could not connect to EasyAdmin.
Observed during investigation
Trouble shoot process Check web server service running,
Check OpenLM server service running.
Solution Found (Found/Pending/Known Issue)
Other steps for troubleshooting

Symptom

The customer complained that he “Couldn’t connect to the EasyAdmin”. Attempting to open the EasyAdmin web application resulted in the following message box appearing on his screen:

In a similar case, the customer got a different notification:

 Troubleshoot process

This kind of issues is related to services that have stopped and are not currently active. The 1st thing to try is restarting the respective process.

1. Navigate to the windows services: Click Start → Control Panel → System and Security → Administrative Tools → Services. The “Services” window appears.

2. In the first case (“Couldn’t connect to host” message box), it may be an issue of the OpenLM Server service.

2a. Select that OpenLM Server service in the “Services” window.

2b. Right click the OpenLM Server service, and set it to restart – see image below.

2c. Restart the EasyAdmin web application.

3. If the 2nd type message box (“Please Check your Internet connection”) appeared, it may be an issue of the web server service. Restart your web server service (e.g.: LightTPD).

Other steps for troubleshooting:

If restarting the services does not work – here are some other things you may try:

  • Run the EasyAdmin application from the same computer as the OpenLM Server.

  • Make sure that any security components (Firewall) are not blocking communication to the EasyAdmin web application.

  • Temporarily stop the OpenLM Server and OpenLM Broker services. Open the task manager’s processes window. Make sure the computer is not held-up by any other process.

  • Still in the task manager’s processes window, look for the LightTpd process. If there are multiple processes with that name – kill them, and restart the LightTpd service on the services window.

  • Make sure the default HTTP listener port (7019) is kept open. Try a different port (e.g. 7020) on the lighttpd-inc.conf configuration file(C:\Program Files\OpenLM\OpenLM Server\WebServer) . Then restart LightTPD service.

  • Try connecting the proxy to the test page; Select the test page from the ‘Start’ menu (see below). Click the ‘Check’ button. An indication similar to that of the 2nd image below should appear.

  • Try a different web browser.

  • Try erasing the Proxy server logs. These are found in the following positions:

Win 7: C:\ProgramData\OpenLM

XP, Win 2003: C:\Documents and Settings\All Users\Application\OpenLM