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 FilesOpenLMOpenLM ServerdbOPENLM_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 FilesOpenLMOpenLM ServerdbOPENLM_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 FilesOpenLMOpenLM ServerdbOPENLM_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 FilesOpenLMOpenLMServerdbOPENLM_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.
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 FilesOpenLMOpenLM 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.
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.
