OpenLM All License Parser supports Seisware log interpretation.

What is Seisware

Seisware is a package of seismic interpretation tools, designed by seismic technology veterans for geoscientists. The first version of Seisware was launched by Zokero in 1997, gradually becoming a prevalent comprehensive solution in the field of geoscience. Zokero later merged with Blue Castle, thus becoming SeisWare International Inc.

The OpenLM “All License Parser” tool

OpenLM has received several requests to integrate this type of license server in its portfolio of monitored license servers. Seisware log files are now supported and interpreted in the OpenLM “All License Parser” online tool. In order obtain a clear image of your license manager’s activity, simply load (or drag) your Seisware log file (CSV format) onto the online parser tool, observe your license usage, and obtain license usage statistics. The “All license parser” tool is an evolving service; we are constantly updating it with new formats and capabilities, as these steam in from our customers.

1

Security note

OpenLM does not keep a copy of the files you upload into the “All License Parser” tool, and does not use the submitted information in any way.

OpenLM Maintenance Release: OpenLM Server version 3.0.0.18

OpenLM Server version 3.0.0.18

OpenLM Server version 3.0.0.18 is a maintenance release to OpenLM version 3.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.

What’s new in OpenLM Server 3.0.0.18 (April 16th, 2015)

Fixed Issues:

  • 3039:  Denials “Licensed number of users already reached.” are not stored in the DB
  • 3033:  Parallel sessions sometimes not logged properly
  • 1867: Denials – Chart is working in light version
  • 2990:  Could not import debug log file. Proxy log culprit ?
  • 3048: Opening EasyAdmin Dashboard causes OpenLM to crash
  • 2165:  Implementation of LS-DYNA into OpenLM Server .
  • 1361: report multliple projects on the same workstation
  • 3049: License Usage Report: Aggregate usage is not stored in Filter
  • 3044: Upgrade failed : 2.0.0.45 –> 3.0.0.14
  • 3028: Oracle database not upgrading from v1.8 to v2 or V3
  • 3031: EasyAdmin – License Activity – Date Range: When trying to set a month/year through “Choose a month” – not working
  • 3032: Procurements window – issuing date & expiration date – don’t show hour .
  • 3027: Feature Usage Status does not work with IE9 .

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)

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup the DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4. It is recommended to close all windows applications, including the services window.
  5. Install the new OpenLM Server 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 that file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

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

Upgrade will be automatically performed by the OpenLM Server installer. Make sure to stop the OpenLM Server Service and backup your Database before upgrading. For further information refer to https://www.openlm.com/?page_id=3507

License management on the cloud – Leaving the comfort zone

Past experience, Future progress

OpenLM has accumulated a great deal of experience in implementing on-premise license management solutions, monitoring application usage on our customers’ network. Now, as the world progresses towards cloud based solutions architecture, so do we. OpenLM now offers a SaaS (System as a Service) solution, enabling quick and effortless deployment of the OpenLM license management system.

Change – a scary word.

Even though there are numerous well established benefits for running OpenLM as a SaaS, we still find that many customers are generally reluctant to leave the comfort zone of monitoring their licenses from within the organization’s network. This sentiment presumably originates in distrust; Not having direct access to the OpenLM database, and submitting control over this data to the service provider requires a leap of faith. Or does it ?

 

In this article we would like to discuss the most common concerns, as raised from our discussions with users.

Security

Security is the main concern raised by customers on their way to implement a SaaS solution. OpenLM takes complete measures to keep your data secure:

1. Location:

The OpenLM cloud servers are physically kept by a leading online server provider. They are maintained in a secured facility, and treated with the highest levels of security standards, both in the aspect of physical access and network security.

2. Transmission:

All communication between the OpenLM Broker installed on the license server and the OpenLM SaaS Server is conducted over HTTPS protocol: encrypted communication via SSL using 2048-bit certificates (as used by banking systems).

3. Database isolation

Taking security as a major concern we have designed the system not to use one central database for all customers. The OpenLM SaaS is implemented so that each customer populates a dedicated database. Each user relates to a specific account and can access the data from that account only.

4. In application security

OpenLM is designed as an enterprise-level tool. This feature requires managing a set of permissions per each individual that has access to the system. The OpenLM advanced Role Based Security system enables administrators to determine which resources are made accessible per each group of users. Reports, charts, data items and  license servers employ viewing and management permissions up to a fine grain resolution.

Low risk level

Having said all that, please consider the low risk level of having license usage information leaking out; OpenLM data only includes session – based data, i.e. user names, and the time of day they had used specific applications. This is operational information that can’t cause any damage to the organization, even if leaked.

 

According to recent surveys, almost 90% of the companies are already using public cloud for critical applications such as email, ERP, CRM and document management. Considering the painful cost that might be related to a leak of customer data, license usage information can safely be defined as “low risk”.

What if we want to switch to on-premise in the future?

No problem. You can get your private database at any point in time, and use it with an on-premise installation of OpenLM. Our principle is that the data belongs to you, and you are entitled to get hold of it on demand.

What if the internet connectivity is disrupted ? Might I lose information?

No. OpenLM will be able to report all your license activity. No information will be lost even if your network connection goes down for a few days.

Is the SaaS implementation limited ?

The SaaS platform provides nearly all the capabilities of the on-premise OpenLM system. At this stage it does not include LDAP synchronization capabilities, and OpenLM Agent – related capabilities.

Benefits

Having reviewed all possible concerns related to the SaaS implementation, we can now observe the benefits:

  • Setting up the OpenLM SaaS is a breeze. A minimal installation of the OpenLM Broker is required on the organization’s license server, and OpenLM will take it from there
  • Maintenance and bug fixes are served automatically
  • Configuration is easily done using web interface
  • The OpenLM learning curve is brought to a minimum
  • No additional hardware is required to host the OpenLM Server
  • OpenLM provides a comprehensive solution: Hardware and Software
  • Full maintenance is done by OpenLM team
  • Small monthly cost

Get to know OpenLM SaaS

The structure is fairly simple. OpenLM will acquire license usage information from its brokers (Agents) on the organization’s license servers, and securely send it to the OpenLM Cloud Server. Please refer to this page for additional information.

Still doubtful ?

Please contact support at openlm.com to discuss the pros in implementing OpenLM SaaS for monitoring your licenses. We are confident in our ability to address any concern.

 

OpenLM License Parser version 1.13 – What is new?

We are very happy to announce version 1.13 of OpenLM License Parser. The main new functionality in this new version is:

– Better FlexLM Debug Log date handling.

– SeisWare CSV log file format supported

– LS-DYNA LSTC log and license file formats supported.

– Closed sessions are in a grid

– Added registration capability

– Fix for false detection of a tab separated data such as lmutil file format

Registration to the system now allows user to upload very big debug log file, removing the limitation of 10,000 rows. It also allows users to compare their performance to a benchmark data that we collect.


An example of benchmark data for the MATLAB feature from Matworks:

2015-04-14 16_59_46-Log Report

The image shows date that is based on about 21 samples. We invite users to upload their files so more statistical information will be collected. Note that your original files are automatically deleted after processing, only accumulated statistical information is preserved.

OpenLM Maintenance Release: OpenLM Broker version 3.0.0.11

OpenLM Broker version 3.0.0.11

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

Upgrade recommendation

  • We recommend that all users of previous OpenLM Broker 3.0 versions upgrade to this latest version.
  • The OpenLM Broker 3.0.0.9 requires an updated OpenLM Server version as well. Please upgrade the OpenLM Server to version 3.0.0.14 or higher to assure full functionality.

What’s new in OpenLM Broker 3.0.0.11 (April 13th, 2015) ?

  • 3029: Looking for License files where these not requested
  • Required changes for lmswitch
  • Update message timestamp after midnight

Upgrading the OpenLM Broker to version 3.0.0.11

Upgrading the OpenLM Broker is fairly straight forward:

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

 

 

OpenLM Maintenance Release: OpenLM Server version 3.0.0.17

General

OpenLM Server version 3.0.0.17 is a maintenance release to OpenLM version 3.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.

What’s new in OpenLM Server 3.0.0.17 (April 7th, 2015)

Fixed Issues:

  • 2722:  Alert the user regarding clocks sync
  • 3025:  Linux Broker 3.0 remains offline. indication is ‘red’, no info arriving from license server.
  • 3022: Idle time not reported on Dashboard
  • 3018: Denials report not working when grouping by day
  • 3009: Without Roles Based Security license you can’t assign any roles to users
  • 2796: After setting require login credentials on OpenLM server configuration can not be changed

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)

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup the DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db)
  4.  It is recommended to close all windows applications, including the services window.
  5. Install the new OpenLM Server 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 that file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

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

Upgrade will be automatically performed by the OpenLM Server installer. Make sure to stop the OpenLM Server Service and backup your Database before upgrading. For further information refer to https://www.openlm.com/?page_id=3507

 

OpenLM Maintenance Release: OpenLM Server version 3.0.0.15

General

OpenLM Server version 3.0.0.15 is a maintenance release to OpenLM version 3.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.

What’s new in OpenLM Server 3.0.0.15 (March 29th, 2015)

Fixed Issues:

  • 2979:  Error in crontab fixed
  • 1288:Can not write data in field in other language when a new host group is added
  • 1786: IBM LUM cluster terminology change
  • 2966: Adding a process in “process features” does not refresh the processes list

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)

  1. Download the OpenLM Server installation file from the ‘Downloads’ section in the OpenLM site.
  2. Stop the OpenLM Server service
  3. Backup the DB file (Typically located in: C:\Program Files (x86)\OpenLM\OpenLM Server\db) 4. It is recommended to close all windows applications, including the services window.
  4. Install the new OpenLM Server version on top of the existing one.
  5. 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 that file to the “C:\Program Files (x86)\OpenLM\OpenLM Server\License”  folder, and restart the OpenLM Server service.

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

Upgrade will be automatically performed by the OpenLM Server installer. Make sure to stop the OpenLM Server Service and backup your Database before upgrading. For further information refer to https://www.openlm.com/?page_id=3507

OpenLM Maintenance Release: OpenLM Server version 2.0.0.55

General

OpenLM Server version 2.0.0.55 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. You will need to update your Database

What’s new in OpenLM Server 2.0.0.55 (March 26th, 2015)

Fixed Issues:

  • 2704:  License usage chart – initial value incorrect.
  • 2894:  V2.0.0.50 License_activity_column_username no longer in openlm_users_role
  • 2986:  Unmanaged Process Add button greyed out
  • 2882: Logs Uploader: Can not upload big customer files to MySQL
  • 2985: Feature Usage Status screen does not show feature when some Servers names are selected
  • 1458:  Minor improvement in host availability presentation

Note

1. Before upgrading, please make sure your system is compliant with the OpenLM System requirements.

  1. 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.54 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.30

OpenLM Broker version 2.0.0.30

OpenLM Broker version 2.0.0.30 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.30 (March 26rth, 2015) ?

  • 2943: LUM commands: only first one is executed
  • 2880: Codemeter: When setting codemeter it puts cmu.exe into the command prompt. It should be cmu32.exe
  • 2481: Can’t find license file : License file path was split to two parts.
  • 2215: Denial command description in Broker configuration tool is taken from previous command

Note: The OpenLM Broker 2.0.0.30 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.30

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 3.0.0.9

OpenLM Broker version 3.0.0.9

OpenLM Broker version 3.0.0.9 is an official maintenance release of the OpenLM Broker version 3.0. It contains some enhancements and bug fixes to problems found in previous versions.

Upgrade recommendation

  • We recommend that all users of previous OpenLM Broker 3.0 versions upgrade to this latest version.
  • The OpenLM Broker 3.0.0.9 requires an updated OpenLM Server version as well. Please upgrade the OpenLM Server to version 3.0.0.14 or higher to assure full functionality.

What’s new in OpenLM Broker 3.0.0.9 (March 25th 2015) ?

  • 2955:  OpenLM Broker 2.0.0.29 for UNIX/LINUX configuration on AIX 7.1 does not work
  • 2962: Error message when trying to remove a license from CCL window
  • 2943: LUM commands: only first one is executed
  • 2165:  Implementation of LS-DYNA into OpenLM Server

Upgrading the OpenLM Broker to version 3.0.0.9

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.