OpenLM Version 1.6.0.2 – Maintenance release

Version 1.6.0.2 is a small maintenance release fixing small problems found by our customers that upgraded to version 1.6. We recommend all users of version 1.6.0 to upgrade their system to this version simply by installing it on-top of their existing version.
What is included in version 1.6.0.2?

  1. Broker LED – Fix bug that caused the led to show as red even when information is sent from OpenLM Broker.
  2. DB – Fix SQL Server script error running on SQL Server 2005.
  3. DB – Fix upgrade scripts when updating admin user as existing user.
  4. Fix SQLServer script – remove identity form OLM_CONFIG_AD_DOMAINS.

Upgrade guide of OpenLM Version 1.5 to Version 1.6

OpenLM version 1.6 includes significant changes at the database structure and other aspects and because of that we recommend our customers to perform a preliminary upgrade test before actually performing the upgrade on the production environment.

The level of the preliminary check depends on the organization’s requirements. If the requirement is to provide a 24/7 service then a full check is recommended that includes an installation of a test system and a fully upgrading and testing of the test system. If down time is acceptable then a short DB upgrade test may be sufficient. OpenLM customers are welcomed to contact our support team and consult with us about upgrade issues.

Considering the upgrade process, the changes relevant to the installation included in this version are:
  • DB structure change.
  • The Agent software is also highly upgraded, its performance is better and it visually provides a better interface. Older versions of the agent are not compatible with the new server version so the upgrade of the agent is a must.
  • OpenLM Server configuration settings moved into the DB (older versions stored it in an XML file).
  • OpenLM Users Management software is obsolete now. All its functionality was moved to OpenLM EasyAdmin interface. The new interface is better, easier to use and faster. Group management is still a part of the Groups & Projects extension and requires additional licensing.
  • OpenLM Broker was significantly upgraded to support the advanced functionality of OpenLM version 1.6. We highly recommend to also upgrade OpenLM Broker but this can be done on a second stage, after upgrading the server.

Two different procedures are outlined in this document. One for installations that use the embedded Firebird database and another one for installations that use external database (Oracle, MS SQL Server or Firebird Server – requires additional licensing). These two procedures are also divided to two, a full and a preliminary check procedure.

Short preliminary check procedure for embedded database configuration

First stage: Backup your database file!

Navigate to the location of your OpenLM Server database file, typically: C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB and backup the database file.

Note that 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 is risking your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation  (XP, Vista, Windows 7) and take the following steps:

  • Install OpenLM Server version 1.6 on a workstation.
  • Stop “OpenLM Server” windows service (on the workstation).
  • Copy of your production database C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB to the test workstation.
  • Navigate to C:\Program Files\OpenLM\OpenLM Server\bin and execute DBUpgrade.exe.
  • 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

First stage: Backup your database!

Note that 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 is risking your data.

Second stage: Upgrade your database

  • Download the appropriate database upgrade script from OpenLM Downloads area.
  • Stop OpenLM Server service and then Run the appropriate 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

First stage: Backup your database file!

Navigate to the location of your OpenLM Server database file, typically: C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB and backup the database file.

Note that 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 is risking your data.

Second stage: Test the database upgrade process (optional)

Choose a test workstation  (XP, Vista or Windows 7) and take the following steps:

  • Install OpenLM Server version 1.5.6 (the exact version you currently use) on a workstation (XP, Vista or Windows 7).
  • Stop “OpenLM Server” windows service (on the workstation).
  • Replace the database with a copy of your production database C:\Program Files\OpenLM\OpenLMServer\db\OPENLM_DB.GDB.
  • Start “OpenLM Server” windows service.
  • Upgrade the system by installing OpenLM Server 1.6 on the workstation.
Test the new installation.

Third stage: Make sure your database backup is in safe place and upgrade your production system.

Upgrade is simple – install the new 1.6 package on your production server. It will update the software and upgrade your database. OpenLM service will not be available during the upgrade process.

Forth stage: Update OpenLM Agents.

Older OpenLM Utilizer Agent versions are not compatible with OpenLM Server 1.6. You must upgrade OpenLM Agent software on all workstations.
OpenLM Utilizer users are licensed to download and install OpenLM Utilizer on every workstation using floating licenses.
OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are licensed to download and install OpenLM Active Agent.
OpenLM supports different distribution methods: Start up scripts, Network management systems like CA Unicenter, Microsoft SMS or others. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on the any FLEXlm server managed by OpenLM.

If OpenLM Broker is not already installed yet then download OpenLM Broker and install it on each license server. Using OpenLM Broker highly enhance the capabilities of OpenLM Software.
We also recommend to upgrade existing OpenLM Broker installations.

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

This procedure is relevant to users that configured an external database with OpenLM Server. OpenLM Server supports Oracle, Ms SQL Server or Firebird server.

First stage: Backup your database!

Note that 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 is risking your data.

Second stage: Upgrade your database

Download the appropriate database upgrade script from OpenLM Downloads area.
Stop OpenLM Server service and then Run the script in order to upgrade the database.

Third stage: upgrade your production system.

Upgrade is simple, install the new package 1.6 on your production server. It will update the software while preserving all your settings. OpenLM service will not be available during the upgrade process.

Test the system!

Forth stage: Update OpenLM Agents.

Older OpenLM Utilizer Agent versions are not compatible with OpenLM Server 1.6. You must upgrade OpenLM Agent software on all workstations.
OpenLM Utilizer users are licensed to download and install OpenLM Utilizer on every workstation using floating licenses.
OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are licensed to download and install OpenLM Active Agent.
OpenLM supports different distribution methods: Start up scripts, Network management systems like CA Unicenter, Microsoft SMS or others. Check this blog post for more information about OpenLM Agent silent install.

Fifth Stage: Install OpenLM Broker on the any FLEXlm server you may have.

If OpenLM Broker is not already installed yet then download OpenLM Broker and install it on each license server. Using OpenLM Broker highly enhance the capabilities of OpenLM Software.
We also recommend to upgrade existing OpenLM Broker installations.

Please report problems to OpenLM Team!
Email: support@openlm.com
OpenLM Site contact form.