OpenLM Brochure 2013

Posted on April 14, 2013 by orik

In addition to the newly released OpenLM version 1.8, here is an updated version of the

OpenLM Brochure 2013.

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

Posted on April 10, 2013 by orik

Changes in OpenLM 1.8

OpenLM version 1.8 has integrated profound improvements, enhancements and bug fixes to its predecessor – OpenLM 1.7. These changes are relevant to the OpenLM server and Database, as well as the OpenLM Broker and Agent. Please see this document for an overview of what’s new in version 1.8.

Gradual migration stages

In order to take advantage of these significant changes, we recommend a gradual migration of versions, from 1.7 to 1.8;

1. Sandbox installation

First Install OpenLM 1.8 alongside version 1.7 as a sandbox installation, to ensure complete compliance with your system’s configuration, and familiarize yourself with the changes made to the OpenLM tool. OpenLM server 1.8 should be installed on a different machine than the OpenLM Server 1.7. The OpenLM Broker 1.8 should be installed side by side with the OpenLM Broker 1.7, on the License server machine. Please read more about this here:

Application Note 1100: Dual OpenLM Installation: 1.8 beta version in conjunction with OpenLM 1.7

2. Perform a preliminary upgrade test.

The level of this preliminary test varies according to your needs. If 24/7 service level is required, then a comprehensive system installation and verification will be recommended. A short DB upgrade test will suffice for lesser customer requirements.

3. Upgrade the production environment from 1.7 to 1.8.

Two different procedures are outlined in this document. One is for installations that use the embedded Firebird database. The other is for installations that use an external database, i.e.: Oracle, MS-SQL or MySQL. (This type of installation requires additional licensing). The two procedures are further divided into a full and a preliminary check procedure.

OpenLM customers are welcomed to contact our support team and consult them about any upgrade issues.

Short preliminary check procedure for embedded database configuration

1. Backup the database !

Note that the backup stage is mandatory, since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file may compromise your data.

Stop the “OpenLM Server” Windows Service, navigate to the location of your OpenLM Server database file (typically “C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.FDB”), and backup the database file.

2. TEST THE DATABASE UPGRADE PROCESS (OPTIONAL)

Choose a test workstation (Any supported platform, e.g. Windows 7 or server OS) and take the following steps:

Install OpenLM Server version 1.8 on the test machine.
Stop the “OpenLM Server” windows service (on the workstation).
Copy your production database and replace the new installation’s db, typically located at “C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.FDB”.
Run Start → OpenLM → Server → Tools → Upgrade Database from Earlier Versions to upgrade your database and make sure that no errors are reported.

Now you can upgrade your production system.

Short preliminary check procedure for external databases

1. Backup the database !

Note that the backup stage is mandatory since the database upgrade process can be sensitive to hardware and software problems. Starting the upgrade process without backing up your database file may compromise your data.

Stop the “OpenLM Server” Windows Service, and back up the OpenLM Database.

2. Upgrade the database

Download the respective database upgrade script (For Oracle, MS-SQL or MySQL) from OpenLM Downloads area.
Stop OpenLM Server service and then Run the upgrade script in order to upgrade the database.
Make sure that no error messages are reported.

Now you can upgrade your production system.

Full Upgrade procedure with preliminary check for embedded database configuration

1. Backup the database !

2. Test the database upgrade process (optional)

Choose a test workstation (Not your current OpenLM Server) and take the following steps:

Install OpenLM Server version 1.7. (the exact version you currently use) on a workstation (Any supported platform, e.g. Windows 7 or server OS).
Stop the “OpenLM Server” windows service on both the test workstation, and the Production server.
Replace the database with a copy of your production database, typically located at “C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.FDB”
Start the “OpenLM Server” windows service on both the test workstation, and the Production server..
Upgrade the system by installing OpenLM Server 1.8 on-top of this installation and follow the instructions.

Test the new installation.

3. Make sure the Database backup is stored in a safe place and upgrade the production system.

This upgrade is simple – just install the new 1.8 package on your production server. It will update both the software and the database. The OpenLM service will not be available during the upgrade process.

4. Update the OpenLM Agent.

OpenLM Agent versions prior to 1.8 are not compatible with OpenLM Server 1.8. The OpenLM Agent must be upgraded on all workstations. OpenLM users can download and install the OpenLM Agent on every workstation using floating licenses.

OpenLM supports various distribution methods including start up scripts and network management systems. Check this blog post for more information about OpenLM Agent silent install.

5. Install the OpenLM Broker on any license server managed by OpenLM.

The OpenLM Broker is an optional component that highly enhances the capabilities of the OpenLM Software.

New installation: If the OpenLM Broker is not already installed, download the latest OpenLM Broker version from the OpenLM site’s downloads section, and install it on each license server machine. On Windows’ machines, the OpenLM Broker will automatically detect the license managers that exist on that machine, and will just need to be configured to interface the OpenLM server.

Recurring installation: If an older OpenLM Broker version 1.7 is already installed, a selection window will pop up during the OpenLM Broker 1.8 installation, prompting the user to select between two options:

Side by side: Will install both versions on the license server machine.
Upgrade: Will install OpenLM Broker 1.8 over the existing version of the software.

Full Upgrade procedure with preliminary check for sites that use an external database

The OpenLM Server can work with Oracle, Ms-SQL and MySQL external databases. This procedure is relevant to users who have chosen to work with any of these external databases.

1. Backup the database !

2. Upgrade the database

Download the appropriate database upgrade script from the OpenLM Downloads menu.

Stop OpenLM Server service and run the script in order to upgrade the database.

3. Upgrade the production system.

To Upgrade your production system, install the new package 1.8 over your production server. It will update the software while preserving all your settings. The OpenLM service will not be available during the upgrade process.

Test the system!

4. Update the OpenLM Agent.

OpenLM supports various distribution methods including start up scripts and network management systems. Check this blog post for more information about OpenLM Agent silent install.

5. Install the OpenLM Broker on any license server managed by OpenLM.

The OpenLM Broker is an optional component that highly enhances the capabilities of the OpenLM Software.

Side by side: Will install both versions on the license server machine.
Upgrade: Will install OpenLM Broker 1.8 over the existing version of the software.

OpenLM Contacts

If you encounter any issue during the upgrade process, or require technical assistance please refer to our support team, and we will be glad to help:

support@openlm.com

OpenLM contact form.

What is new in OpenLM version 1.8

Posted on April 9, 2013 by orik

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.

A smart spider came in to check the new version 1.8

Posted on April 8, 2013 by oren

We are not sure how happy he is with the new version but we are sure you will be, stay tuned.

Siemens PLM Connection 2013

Posted on March 14, 2013 by orik

SECOPTENA and OpenLM exhibit on Siemens PLM Connection 2013

23.04.2013 – 24.04.2013

Lufthansa Training & Conference Center Seeheim,

Lufthansaring 1, 64342 Seeheim-Jugenheim

This User Conference is the largest dedicated event for Siemens PLM users in Germany.

The complete Siemens PLM product portfolio like NX, Teamcenter and I-deas are covered in technical lectures, workshops and customer reviews.

Users, Decisions Makers and Product Specialists are gathered by an ambition to enhance the efficiency of their Siemens PLM products. In an intense exchange of experience they get to know the latest of PLM technologies and strategies.

Located in the exhibition space, SECOPTENA will demonstrate how to achieve this goal with proactive license management.

Monitoring – gain comprehensive overview of the most important parameters of your software licenses

Status of license server connections
Actual utilization of the most important licenses
Blocked licenses which are not actively used

Reporting – obtain fundamental usage information as grounds for decisions making

Cost allocation – ratio of license utilization per defined groups of users
Restrictions in productivity – shortages and denials of specific licenses
Compliance – to definitions of license agreements
Bundle check – optimal utilization of licenses and packages

Proactive license management – actively control license usage

Increase productivity by avoiding license shortage.
Secure Compliance through adaption of your license configuration.
Adjust your license packages to your real business needs.

Increase communication and reduce your efforts for license administration.

SECOPTENA will show you how,

Just stop by or fix an appointment now!

Email us: info@secoptena.com or

call us: 08151 77499-55

more information:

http://www.plm-benutzergruppe.de/

http://www.secoptena.com

Trouble Shoot Form: Agent Item 004 (Failure of automatic license release – save and close)

Posted on March 12, 2013 by orik

Title	Agent fails to Close idle session in “Save and Close” method
Category	Active Agent
Date	March 12, 2013
Handled by
Relevant Links
Applies to license managers	FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model	Floating licenses, Network licenses, Concurrent licenses
Symptoms	OpenLM Agent is set to release Idle licenses by “Save and Close”, but those stay checked out.
Observed during investigation
Trouble shoot process
Solution

Troubleshooting automatic license release issues – Save & Close

OpenLM supports two methods of shutting down idle licenses: Suspend & Resume and Save & Close. For more information on these configurations, please read the following Application note: Application Note 1005: Configuring OpenLM to close idle Licenses . This document covers the Save & Close method troubleshoot.

Suspend and Resume:

Suspends the session and releases the license on the server side. When the user resumes work, the license is retaken (if still available) and the application resumes from the same position it was suspended. This method’s troubleshoot is not covered in this document.

Save and Close:

Saves and closes the active session, releasing the license for other users. The OpenLM Active agent fully closes the licensed software. This document covers this method’s troubleshoot.

The Save and Close mode is only applicable if the OpenLM Agent extension was installed as part of the OpenLM Agent installation. Furthermore, the Save and Close method is only supported for ESRI ArcGIS , Autodesk software and Matlab applications.

Try closing the application manually

Applications may normally be closed manually by an administrator through the EasyAdmin tool:

Open the “OpenLM EasyAdmin” window.
Click “Active products” (see image below).
Find the current open session of the program on your machine.
Click the “Close Application” button.

If an application fails to close via the close application button, please try the following actions:

Make sure the extension was properly installed

ESRI ArcGIS Desktop ArcGIS: Click the “Customize” tab → Select “Extensions”. Confirm that “OpenLM Arcgis Extension” appears in the Extensions list.

Autodesk software: The Save and Close mode is supported for any Autodesk software application. In Autocad Map 3D, for example, type in the “OLM” command at the bottom of the AutoCAD window. If the OpenLM Agent extension was installed, you should get a message such as depicted below:

If the Extension is not installed, an Error message should appear, stating that the “OLM” command is not recognized.

The agent is not installed correctly / No extension installed:

Close the monitored Application
Remove the Agent using the “Program files” → “Add/Remove programs” application.
Download the latest version of the Active Agent (as opposed to the Utilizer Agent) from OpenLM’s downloads area, and review our agent installation guide.

OpenLM Server version not up-to-date:

Download the latest version of the OpenLM Server from OpenLM’s downloads area,
Stop the OpenLM server service, and Back up the OpenLM Database.
Install the latest version of the OpenLM Server on top of the existing one.

product_features xml file

Update the product_features xml file. See this post for clarification.

OpenLM Agent Configuration

On Workstations that have issues closing idle sessions, right click the Active Agent Icon and select “OpenLM Agent Configuration”. Verify that the OpenLM Server is configured correctly, and that the connectivity check is successful.

EasyAdmin web application configuration:

1. click ‘Start’ → Administration → Active Agent. Make sure “Enable License Release Functionality” is checked.
2. Try to alleviate the criteria for license closure. This is fine tuning: experiment here until you get results.

Try decreasing “start releasing …”. Perhaps you haven’t surpassed this threshold yet.
Minimum idle: Try doing that after 3 minutes as an experiment. Minimize the ArcGis application in order to make sure that it is indeed idle.
Increase the “%Processor time” (e.g. to 5).
Increase the “IO Data …” (e.g. to 5).
Increase the “%User usage ” (e.g. to 5).

OpenLM Support

If all this doesn’t help – please send us logs:

Set the OpenLM Server and Agent logging level to ‘ALL’,
Wait several minutes,
Invoke such a condition where you feel the Agen’t has failed to close an idle application,
Zip and send us the log file directories.
The OpenLM Server log file is normally located at: C:\Program Files\OpenLM\OpenLM Server\Log
You can find the Agent’s log by doing this: Click Windows Start → OpenLM → Agent → tools → OpenLM Agent Logs Folder.

Trouble Shoot Form: Agent Item 003 (Agent fails to connect to the OpenLM Server)

Posted on March 12, 2013 by orik

Title	Agent fails to connect to the OpenLM Server
Category	Permissions and Roles.
Date	March 12, 2013
Handled by
Relevant Links
Applies to license managers	FLEXlm, FLEXnet publisher, IBM LUM, HASP, RLM, Sentinel RMS, LM-X, DSLS
Applies to license model	Floating licenses, Network licenses, Concurrent licenses
Symptoms	Can not set a connection between OpenLM Server and OpenLM Agent.
Observed during investigation	No license usage presented in OpenLM Agent, “Check connectivity…” button yields an error, Other general Agent malfunctions
Trouble shoot process
Solution

Connectivity issues

OpenLM Agent connectivity issues can manifest in many ways, but are summarized as general Agent malfunction. Such connectivity issues may be caused by the following reasons:
1. Incorrect server name or address
2. Firewall blocks the OpenLM Server or the Agent port.
3. A proxy server blocks the Agent requests.
4. .NET Framework not installed on the OpenLM Agent machine

Troubleshooting

If you encounter connectivity issues, Please act according to the following checklist:
1. Make sure that .NET Framework not installed on the OpenLM Agent machine
2. Make sure that the server name and address are correct.
3. Make sure that the port is open:
3a. Try disabling the firewall temporarily.
3b. Enter “Control Panel” → “System and Security” → “Windows Firewall” → “Advanced settings”.
3c. If the port isn’t defined under the “‘Inbound Rules” open the port by adding a New Rule using the “New Rule” button located on the lower right side of the screen as depicted below:

If connectivity issues persist, and a Proxy Server is configured on your machine, ensure that it is not blocking the OpenLM server; Open the OpenLM Agent Configuration window and uncheck the “Use local computer’s proxy settings” box as depicted below:

OpenLM Maintenance Release Version 1.7.4.1

Posted on March 12, 2013 by orik

Version 1.7.4.1

Version 1.7.4.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 upgrade their system to this version.

Upgrading

In order to upgrade to version 1.7.4.1:
1. Stop the OpenLM Server service
2. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
3. Make sure ALL windows are closed; especially the services window.
4. Install the new version on top of the existing one.
5. Update the products XML from the OpenLM site. In order to do so:
5a. Open the OpenLM Server configuration tool in the ‘Advanced’ tab,
5b. Click the “Update products…” button. The “Update product features” window opens.
5c. Select online updating, and click the ‘Update’ button.
5d. Click the ‘Apply’ button, and “Restart Now” when prompted.
See image below for clarification.

What was fixed in OpenLM server version 1.7.4.1 (and its close predecessors)?

1. Project UI not showing when license manager reports fqdn workstation name.
2. Ignore duplicate immediate denials (Bug #481).
3. RMS license quantity and usage reported ’0′ (Bug #600).

OpenLM beta version 1.8 is publicised

Posted on March 7, 2013 by orik

General

In the past couple of years, OpenLM v1.7 has been the selected tool for application usage metering and license usage optimization for an expanding circle of customers. OpenLM has steadily widened the variety of supported network license managers, and enhanced its monitoring capabilities per each license management tool.

OpenLM beta Version 1.8 incorporates many bug fixes, performance improvements and new features that were required by our cooperative and trusted customers. These changes have increased OpenLM’s robustness and made it less prone to errors.

This version also integrates some fundamental architectural changes that have expanded OpenLM’s ability to further develop license usage control and monitoring. Here are some of the main highlights of this new version.

Important note:

As of today the released version is still a beta, and as such it is not yet error free.
DO NOT upgrade production installations of OpenLM 1.7 to 1.8 beta.
The use of version 1.8 beta is recommended for:

New evaluating customers, who wish to explore the 1.8 beta version functionality, or

Active OpenLM 1.7 users, installing version 1.8 beta separately and parallel to the 1.7 production installation.

Please read this document prior to installing OpenLM 1.8 beta parallel to production 1.7 installations.

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.
Also on 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, Offline Licenses indications, and support for HAL (High Availability Licensing) configuration support.
DSLS has been fully integrated into the OpenLM 1.8 system. License borrowing is reported.
RMS: License versions’ reporting was added

EasyAdmin

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

Personalization:

License usage status windows’ configuration can now be saved between workstations and browsers.

New reports

Some of the new reports are:

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

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
The “License Usage” graphic presentation was improved.

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.

License Servers

Reported license servers’ information has been enhanced to include:

License server timezone indication
Host availability indication
License not in use indication.

Active Directory

In version 1.8, LDAP 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.

Projects

The Project license usage recording capability is available for OpenLM from version 1.6 onward. 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), and
Can be introduced by end-users via the OpenLM Agent module.

OpenLM Broker

The OpenLM Broker has overgone important changes, enhancing its robustness and compatibility with a wide array of license managers. One of these changes is the implementation of buffers for Broker messages, providing the ability to overcome network connectivity failure.

Finally

we would like to thank our loyal customers for collaborating as beta sites for this new version. Your ever welcomed feedback has enabled us to publicize this product, and is constantly driving us toward improving our releases.

OpenLM Maintenance Release Version 1.7.3.9

Posted on March 3, 2013 by orik

Version 1.7.3.9

Version 1.7.3.9 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.3.9:
1. Stop the OpenLM Server service
2. Backup your DB file (Typically located in: C:\Program Files\OpenLM\OpenLM Server\db)
3. Make sure ALL windows are closed; especially the services window.
4. Install the new version on top of the existing one.

What was fixed in OpenLM server version 1.7.3.9 (and its close predecessors)?

1. nhibernate upgrade related issue with sql server (1.7.3.6, Bug #563).
2. Groups list error due to nhibernate upgrade (1.7.3.7).
3. Duplicated FlexLM sessions reported in OpenLM License Activity (1.7.3.8, Bug #580)
4. Active directory memory leaks issue (1.7.3.9).
5. EasyAdmin touch problem: Connection error message (1.7.3.9, Bug #633)