OpenLM Maintenance Release: OpenLM Server version 2.0.0.47

General

OpenLM Server version 2.0.0.47 is a maintenance release to OpenLM version 2.0. It contains enhancements and bug fixes to problems found in previous versions. Users for whom these fixes are relevant should upgrade  to this latest version.

Note that this version does not update the OpenLM database, only the OpenLM Server software. If your current OpenLM Server version is 2.0.0.28 or later no database upgrade will be necesary.

What’s new in OpenLM Server 2.0.0.47 (January 28th, 2015)

Fixed Issues:  FB upgrade 45-46 was not running properly

Note:

  1. Before upgrading, please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process.

In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.
  7. Run the installation file. An OpenLM Server Service restart may be required after installation.

Upgrading the OpenLM Server (External MS-SQL, Oracle, MySQL Database)

If your current version is 2.0.0.43 or earlier please contact OpenLM support at:

support@openlm.com

For later versions: just run the upgrade process as elaborated in the “Upgrading the OpenLM Server (Internal Firebird Database)” above.

 

OpenLM Maintenance Release: OpenLM Broker 2.0.0.24

OpenLM Broker version 2.0.0.24

OpenLM Broker version 2.0.0.24 is an official maintenance release to OpenLM version 2.0.  We recommend to install this version when asked so by support of OpenLM

What’s new in OpenLM Broker 2.0.0.24 (January 27th, 2015) ?

  • 2622: Process is suspended several times

Note: The OpenLM Broker 2.0.0.24 requires an updated OpenLM Server version 2.0.0.41 or higher. Please upgrade the OpenLM Server to version 2.0.0.41 or higher to assure full functionality.

Upgrading the OpenLM Broker to version 2.0.0.24

Upgrading the OpenLM Broker is fairly straight forward:

  1. Download the Broker installation file from the ‘Downloads’ section in the OpenLM website.
  2. Make sure ALL windows are closed; especially the services window.
  3. Install the new version on top of the existing one.

OpenLM Maintenance Release: OpenLM Broker 2.0.0.23

OpenLM Broker version 2.0.0.23

OpenLM Broker version 2.0.0.23 is an official maintenance release to OpenLM version 2.0.  We recommend to install this version when asked so by support of OpenLM

What’s new in OpenLM Broker 2.0.0.23 (January 26th, 2015) ?

  • Multiple Remove Issues fixed

Note: The OpenLM Broker 2.0.0.22 requires an updated OpenLM Server version as well. Please upgrade the OpenLM Server to version 2.0.0.41 or higher to assure full functionality.

Upgrading the OpenLM Broker to version 2.0.0.23

Upgrading the OpenLM Broker is fairly straight forward:

  1. Download the Broker installation file from the ‘Downloads’ section in the OpenLM website.
  2. Make sure ALL windows are closed; especially the services window.
  3. Install the new version on top of the existing one.

OpenLM Maintenance Release: OpenLM Server version 2.0.0.46

OpenLM Server version 2.0.0.46

OpenLM Server version 2.0.0.46 is a maintenance release to OpenLM version 2.0. It contains some bug fixes to problems found in previous versions and enhancements. Users for whom these fixes are relevant should upgrade  to this latest version.

Note that this version contains an update for the OpenLM database. This is particularly important for users of external databases.

What’s new in OpenLM Server 2.0.0.46 (Jan. 26, 2015)

Fixed Issues:

  • 2759: Version 2.0.0.45, Product name not changeable from the Product packages screen
  • 2574: Downloaded files are not in CSV Format
  • 2766: Make sure all users are members of OpenLM_Everyone group

Notes:

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process. In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.46:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External Databases)

Customers who employ external databases (MS-SQL Server, Oracle, MySQL) will need to run database upgrade scripts. For more information, please contact support@openlm.com

Monitoring and management of the LS-DYNA license manager

General

OpenLM is a license management and monitoring system for a wide variety of Network license types, such as FLEXlm, IBM LUM, DSLS etc. As part of the new milestone version 3.0, OpenLM now supports the LS-DYNA license manager as well.

LS-DYNA

LS-DYNA is a finite element simulation tool produced by LSTC: Livermore Software Technology Corporation. LS-DYNA accommodates a series of peripheral tools such as LS-OPT, LS_PREPOST, LS_TASC and THUMS. Together they comprise a wide variety of applicable physics simulation subjects, from fluid dynamics to car safety. LS-DYNA’s proprietary license manager controls the deployment of network licenses for the different LS-DYNA features.

The OpenLM benefit

OpenLM provides a clear method of viewing the current utilization of LS-DYNA licenses, as well as accumulating license usage statistics and patterns, and manage idle licenses.

OpenLM Maintenance Release: OpenLM Server version 2.0.0.45

OpenLM Server version 2.0.0.45

Oops…

Version 2.0.0.44 had a small bug in it; New OpenLM Server installations would not have an up-to-date Database structure.

So, if you’re installing a fresh Firebird database – please do it with this latest version (2.0.0.45), not with the previous one (2.0.0.44).

This version update is not required for OpenLM Server upgrades.

 

What are token-based licenses

Token licenses are in fact a form of Network Floating licenses, only that instead of having a pool of licenses – they have a pool of tokens. When a feature is checked-out, a certain amount of tokens are consumed. The number of consumed tokens is specific to each feature, and is apparent in the feature/Increment line in the license file. When the application is closed, the tokens are returned to the pool for other end users to use.

Advantages of Token licenses

Having the ability to apply the acquired licenses to multiple products is an appealing concept:

  • Customers are not always aware of the full array of features they may acquire. having a token based license scheme ensures customer satisfaction from the license acquisition.

  • As development stages progress, customer needs change. They may require different licensed features, and eliminate the charge of unused software.

  • The entire license purchasing method is simplified. Customers can add or try new software applications during the project, without a need for new POs or an evaluation process

What are Network Floating Licenses ?

Network floating licensing is a method of deploying licensed software applications over an organization’s internal network. Through this method, multiple users can share single licenses, thus increasing the license utilization in accordance to momentary license demand.

Network licensing is implemented by means of dedicated license managers; Services that centralize clients’ requests for licenses. When an end-user starts a licensed application, a request is sent to the license manager. The license manager handles each license request according to the temporary license availability, and according to predefined constraints. It will consequently either grant the license or deny license usage.

License managers follow predefined rules, that accommodate the software purchase agreement. These rules may be stored in license files or in trusted storage, and they elaborate the terms and conditions for license compliance.

The OpenLM benefit

OpenLM provides means to monitor and manage Network licenses, and has multiple benefits for all position holders in the organization. Please refer to this post for more information.

OpenLM Maintenance Release: OpenLM Server version 2.0.0.44

OpenLM Server version 2.0.0.44

OpenLM Server version 2.0.0.44 is a maintenance release to OpenLM version 2.0. It contains some important bug fixes to problems found in previous versions. We recommend that all customers would upgrade their OpenLM Server to this version.

Note that this version contains an update for the OpenLM database. This is particularly important for users of external databases.

What’s new in OpenLM Server 2.0.0.44 (Jan. 19, 2015)

Fixed Issues:

  • 2724: [OpenLM Server] Server Error when running “Update Features\Packages”
  • 2341: [OpenLM Server] Missing License Availability notification OpenLM Agent
  • 2736: [EasyAdmin] Can’t remove broker from license servers’ window
  • 2726: [EasyAdmin] Bad error message when server configuration tool is configured to read options files
  • 2725: [EasyAdmin] EasyAdmin – Product Packages Download malfunction

Notes:

  1. Before upgrading please make sure your system is compliant with the OpenLM System requirements.
  2. If the OpenLM server (of any version) has been already installed on the machine for a period longer than the Evaluation period, A license file will be required . Please make sure you have one before proceeding with the upgrade process. In order to obtain a valid OpenLM license file, please contact OpenLM support, and provide your MAC address and Hostname (case sensitive).

Upgrading the OpenLM Server (Internal Firebird Database)

In order to upgrade to version 2.0.0.44:

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup your DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. Make sure ALL windows are closed; especially the services window.
  5. For OpenLM versions 1.8, Install the new version on top of the existing one.
  6. If prompted to do so, contact OpenLM to obtain an up-to-date license file. Please provide your MAC address and Hostname (case sensitive) for that. Copy this file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

Upgrading the OpenLM Server (External Databases)

Customers who employ external databases (MS-SQL Server, Oracle, MySQL) will need to run database upgrade scripts. For more information, please contact support@openlm.com

License usage statistics and patterns

In order to make intelligent decisions regarding license procurement and maintenance, IT and management personnel obviously need concrete and reliable data. License management systems provide basic information such as usage level, and notify users when license usage is at its maximum capacity. But this is not enough

It is not only the top watermark numbers that show how many licenses are needed in an organization, but also the usage patterns. For example:

OpenLM clearly presents license usage charts, clarifying usage patterns. Here are a few examples:

OpenLM EasyAdmin – Widgets –  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.

4

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.

Doors_AllVersions_December

OpenLM EasyAdmin – Management – License utilization

This 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.

6