Upgrade guide of OpenLM Version 1.6 to Version 1.7

To take advantage of the significant changes made to the database structure and other important aspects in OpenLM version 1.7, we recommend performing a preliminary upgrade test before actually upgrading the production environment.

The level of this preliminary check varies depending on the customer’s needs. If 24/7 service level is needed, then a full check that includes an installation of a test system and a full upgrading and testing of the test system is recommended. A short DB upgrade test may sufficiently satisfy less comprehensive customer requirements. OpenLM customers are welcome to contact our support team and consult with them about any upgrade issues.

The changes to the upgrade process relevant to the installation included in this version are:

  • DB structure change
  • Agent software, featuring an improved performance and streamlined interface. As OpenLM Agents prior to version 1.6 are not compatible with the new server version, this upgrade is a must. Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version.
  • FDB has replaced GDB as the standard extension for the Firebird DB file.
  • OpenLM now supports the use of a virtual license server, which can be a group of Triad servers (with FLEXlm). This will change your existing license server configuration.
  • OpenLM Broker is significantly upgraded to support the advanced new functions of OpenLM version 1.7. We highly recommend to also upgrade OpenLM Broker, but this can be done separately after upgrading the server. The current installation of Broker 1.7 will not be able to preserver your current broker settings (link).
  • The server and agent software requires .NET Framework 4.0.

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

Short preliminary check procedure for embedded database configuration

First stage: Backup your database file!

Stop “OpenLM Server” Windows Service, navigate to the location of your OpenLM Server database file, typically “C:\Program Files\OpenLM\OpenLM Server\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 risks your data.

Second stage: Test the database upgrade process (optional)

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

  • Install OpenLM Server version 1.7 on the test machine.
  • Stop “OpenLM Server” windows service (on the workstation).
  • Copy of your production database and paste it to C:\Program Files\OpenLM\OpenLM Server\db\OPENLM_DB.GDB to the test workstation. Rename it to OPENLM_DB.FDB and delete the DB provided with the software. Run Start→OpenLM→Server→Upgrade Database from Earlier Versions.
  • 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 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 risks 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!

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

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 risks your data.

Second stage: 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.6. (the exact version you currently use) on a workstation (XP, Vista or Windows 7).
  • Stop “OpenLM Server” windows service (on the test 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.7 on-top of this installation and follow the instructions.

Test the new installation.

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

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

Fourth stage: Update OpenLM Agents.

OpenLM Utilizer Agent versions that prior to version 1.6 are not compatible with OpenLM Server 1.7. You must upgrade OpenLM Agent software on all workstations.

Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version (like the Active Agent new features).

OpenLM Utilizer users can download and install OpenLM Utilizer Agent on every workstation using floating licenses.

OpenLM for ESRI ArcGIS and OpenLM for Autodesk users can download and install OpenLM Active Agent.

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

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

If OpenLM Broker is not already installed, download OpenLM Broker and install it on each license server. OpenLM Broker highly enhances the capabilities of OpenLM Software.

We also recommend upgrading existing OpenLM Broker installations by installing OpenLM Broker 1.7 over the existing version of the software. Since now the upgrade program will not preserve your existing settings,  please backup the settings by taking screenshots or by backing up the broker configuration file named: broker.xml. The file is located in the broker installation folder. On Windows it typically located in C:\Program Files\OpenLM\OpenLM Broker (Link) .

On a Windows workstation the broker typically recognizes most of the settings automatically.

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

This procedure is relevant to users who 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 risks your data.

Second stage: Upgrade your database

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

Third stage: upgrade your production system.

To Upgrade your production system, install the new package 1.7 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!

Fourth stage: Update OpenLM Agents.

OpenLM Utilizer Agent versions prior to version 1.6 are not compatible with OpenLM Server 1.7. You must upgrade OpenLM Agent software on all workstations.

Agent versions 1.6 and above are compatible with the new version, so a graduate upgrade is recommended to enjoy the full capabilities of the new version (like the Active Agent new features).

OpenLM Utilizer users are able to download and install OpenLM Utilizer on every workstation using floating licenses.

OpenLM for ESRI ArcGIS and OpenLM for Autodesk users are able to download and install OpenLM Active Agent.

OpenLM supports various distribution methods including start up scripts and network management systems like CA Unicenter, Microsoft SMS and others. Check this blog post for more information about OpenLM Agent silent install.

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

If OpenLM Broker is not already installed then download OpenLM Broker and install it on each license server. OpenLM Broker highly enhances 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 contact form.

OpenLM Broker Upgrade Guide from version 1.6 to 1.7

OpenLM Broker is a tool on the license server. This optional but highly recommended program significantly enhances OpenLM System capabilities.

Although the upgrade process of OpenLM components is usually fully automatic, the transition from OpenLM Broker version 1.6 to version 1.7 is more complex. Thus, some manual steps are required in order to preserve your settings.

In order to preserve your current configuration, you must follow these steps:

  1. Save your broker configuration. To do this, copy the ‘broker.xml’ file from the broker installation folder, whose default location is “C:\Program Files\OpenLM\OpenLM Broker,” to a temporary folder.
  2. Download  the OpenLM Broker 1.7 installer from our download area.
  3. Run the installation package. Removing the previous installation is uneccessary, as it is a standard ‘Next-Next’ installation.
  4. At the end of the installation process, the “OpenLM Broker Configuration Tool” will pop up.
If your configuration was saved:
  1. Click ‘Servers’ on “OpenLM Broker Configuration Tool,” and select “Add.”
    Complete the fields as illustrated in  in the following image:
  2. Apply your changes.
  3. Exit the configuration tool.
If your configuration was not saved:

Please close the “OpenLM Broker Configuration Tool.”

  1. Open the “Openlm Broker” Folder and replace the new ‘broker.xml’ file with the copy you made earlier.
  2. Open “Openlm Broker Configuration’” from the start menu and then click “Servers.” Choose “Add,” and fill in the fields as shown in the following image:
  3. Apply your changes and click “Restart Broker” to restart the broker service.
  4. Exit the configuration tool.

OpenLM Version 1.6.1.4 – Maintenance release

Version 1.6.1.4 is a maintenance release to version 1.6. It contains minor bug fixes to problems found in previous versions. We  recommend users that these problems may be relevant to them to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.1.4?

OpenLM Server:

  1. Hide Active Directory password also while editing in “Configuration Form”.
  2. Fix roles management functions for Oracle users..
  3. Fix License Activity TAB sometimes shows negative working hours when “Consider only working hours” is checked.
  4. Fix message box shadow in “Change Password” form in IE8 with compatibility view.

OpenLM Active Agent version 1.6.0.4 was also published. Please check a separate message regarding this.

OpenLM Version 1.6.1.2 – Maintenance release

Version 1.6.1.2 is a maintenance release to version 1.6. It contains bug fixes to problems found in previous versions. We recommend all users of version 1.6. to upgrade their system to this version simply by installing it on-top of their existing version.

What is included in version 1.6.1.2?

OpenLM Server – Fixed problem with reading messages from OpenLM Broker.
OpenLM Server – Fixed a problem with RLM license server.
OpenLM Server – Fixed an issue with workstations listing in Workstations tab.
OpenLM Server – Fixed an issue related to many agents.
Easyadmin – Solved problem with dragging and dropping groups in Groups window..
Easyadmin – Solved a problem with Minutes-resolution charts.
Easyadmin – Fix an issue related to  message-box shadow in IE in compatibility mode.
EasyAdmin – Set default group automatically when a user is assigned to one group.
OpenLM Alerts – Fixed problem with listing user without groups.

OpenLM Version 1.6.0.5 – Maintenance release

Version 1.6.0.5 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. 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.5?

OpenLM EasyAdmin – IP Address was added to Active Products & License Activity tabs.
OpenLM Easyadmin – Fixed problem of loosing task bar on re-size.
OpenLM Easyadmin – Added v-scroll for Groups/Projects in user form.
OpenLM Easyadmin – Allowing multi-selection in projects form (when used in search mode).
OpenLM Easyadmin – users search is also searching on first/last name.
Install Process – Setup process made simple by removing external DB configuration from install.
OpenLM Server Configuration Form – Allow users to activate authentication and set admin password.
OpenLM Server Configuration Form – Make server monitoring stop/start icons clearer.
OpenLM Server – Update lmutil to version 11.9.1.
OpenLM Agent – Fix ‘Run As’ message for pre-vista users (Windows Server 2003, Windows XP).

OpenLM Broker – 1.6.0.5

Two version of OpenLM Broker are now available for download:
– OpenLM Broker for Windows
– OpenLM Broker for Unix/Linux

  • The updated version 1.6.0.5 contains the following improvements:
  • Add status and data_inquery command for IBM LUM.
  • Add FLEXlm lmutil.exe and IBM LUM i4blt to setup.
  • Set data_inquiry to be periodic.
  • Changing logging level does not require restart.
  • Adding restart to UI.

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.