Summary

Normally upgrading Opmantek applications is very straight forward but lately, the team has been busy with new generations of our products including a new faster build system to support all of our products.

This page is to assist you to determine what you need to do to upgrade your current applications to your target applications.

Considerations and Guidelines for Upgrading

Check compatibility with other OMK apps

Has a dependency changed

  • Review the application release notes for specific requirements, deprecated dependencies or new dependencies. For example: Newer MongoDB version

Test in a non production system

  • Prior to upgrade, it is recommended to test the upgrade in a test environment that matches you current setup on production.
  • Create a test environment

Have you got custom modifications or template changes

  • Review any custom modification applied to you applications and consider that they may not work after upgrade and they may need adjustments.

Have you got a test plan and steps to perform a rollback in your production environment

  • It is recommended to have a plan of action in case the upgrade process doesn't work as expected.

Recommendation

As always, we strongly recommend to keep a backup of the current installation. This is a recommended practice and it's an important step on any software installation or upgrade.

Verify a successful upgrade

  • Load the applications and verify the basic operations firsts as login, load process and data displayed. 
  • Review the specific application log for errors (opEvents.log, opCharts.log, etc)

  • The installer saves a log of all actions taken, files copied etc. in the installation directory as install.log, ie. normally it'll be in /usr/local/omk/install.log. Subsequent upgrades or installations of other Opmantek products will add to that logfile, so you may very well want to remove or clear the install.log file before upgrading or adding extra software.

If you have a problem with the upgrade see the section below "Restoring from Backup"

Upgrade Decision Support

This document will highlight some key aspects of the upgrade process of the current Opmantek Applications.



SECTION A: Upgrading NMIS 8 compatible applications

A.1 Upgrading from Older NMIS 8 Compatible applications

You are currently running NMIS 8 and the related Opmantek applications and you want to upgrade from the versions below to the newer versions.

When you install the newer version of the first commercial application, e.g. opConfig, it will move aside all the existing commercial applications and you will also need to install those.  You can download the applications from the Opmantek.com website.

Once you have downloaded all the applications you need, if you have not already, please review the section above "Considerations and Guidelines for Upgrading".

ApplicationVersion
NMIS 88.7.1G or earlier version
opCharts 33.4.0 or earlier version
opConfig 3 3.4.0 or earlier version
opEvents 22.5.0 or earlier version
opHA 22.1.6 or earlier version
opReports 3 3.3.0 or earlier version
opFlow 3

3.0.16 or earlier version

opFlowSP 11.0.10 or earlier version

A.2 Upgrading from Current NMIS 8 Compatible applications

If you are running the versions below or greater then the upgrade is very straight forward, download the product you need and upgrade the individual product, just like you would an installation, see "Starting the Upgrade/Installation".

ApplicationVersion
opCharts 33.5.0 or later version
opConfig 3 3.5.0 or later version
opEvents 22.6.0 or later version
opHA 22.2 or later version
opReports 3 3.4.0 or later version
opFlow 3

3.1 or later version

opFlowSP 12.0.0 or later version

Starting the Upgrade/Installation

When you are ready proceed with the upgrade as you normally would an installation, details on:

SECTION B: Upgrading NMIS 9 compatible applications

You are currently running NMIS 9 and the related Opmantek applications and you want to upgrade from the versions below to the newer versions.

When you install the newer version of the first commercial application, e.g. opConfig, it will move aside all the existing commercial applications and you will also need to install those.  You can download the applications from the Opmantek.com website.

Once you have downloaded all the applications you need, if you have not already, please review the section above "Considerations and Guidelines for Upgrading".

B.1 Upgrading from Older NMIS 9 Compatible applications

ApplicationVersion
opCharts 44.1.3 or earlier version
opConfig 4 4.1.1 or earlier version
opEvents 33.1.0 or earlier version
opHA 33.1.2 or earlier version
opReports 4 4.1.1 or earlier version

B.2 Upgrading from Current NMIS 9 Compatible applications

If you are running the versions below or greater then the upgrade is very straight forward, download the product you need and upgrade the individual product, just like you would an installation, see "Starting the Upgrade/Installation".

ApplicationVersion
opCharts 44.2 or later version
opConfig 4 4.2 or later version
opEvents 33.2 or later version
opHA 33.2 or later version
opReports 4 4.2 or later version

Starting the Upgrade/Installation

When you are ready proceed with the upgrade as you normally would an installation.

SECTION C: Upgrading from NMIS8 compatible applications to NMIS9 compatible applications

SECTION D: Migration documentation under development

Migrations mean when moving an existing system to run on another server, usually done when changing something significant in the infrastructure like the Operating System version.

For further details, please contact Support

In case of failed upgrade

If something goes wrong during the upgrade process follow these steps to roll back to your previous state.

  1. Restore Backup after Install


  • No labels