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.
Upgrade Decision Support
This document will highlight some key aspects of the upgrade process of the current Opmantek Applications.
In order to be able to upgrade please ensure the following product versions are installed on your system.
SECTION A: Upgrading 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.
|NMIS 8||8.7.1G or earlier version|
|opCharts 3||3.4.0 or earlier version|
|opConfig 3||3.4.0 or earlier version|
|opEvents 2||2.5.0 or earlier version|
|opHA 2||2.1.6 or earlier version|
|opReports 3||3.3.0 or earlier version|
3.0.16 or earlier version
|opFlowSP 1||1.0.10 or earlier version|
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.
|NMIS 9||9.1.0G or earlier version|
|opCharts 4||4.1.3 or earlier version|
|opConfig 4||4.1.1 or earlier version|
|opEvents 3||3.1.0 or earlier version|
|opHA 3||3.1.2 or earlier version|
|opReports 4||4.1.1 or earlier version|
Check compatibility with other OMK apps
- Please check our Product Compatibility Page (Product Compatibility)
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.
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.
SECTION D: Migration documentation under development
For further details, please contact Support
Restoring from backup
How to restore from a failed upgrade
All opModule installers create a backup of /usr/local/omk prior to the installer running PROVIDED you answered the following question early in the installation procedure in the affirmative:
- Do you want to perform a backup of your installation directory?
- Default answer for automated install is 'Yes'.
This is the process to use if you need to roll back from the installer using this backup:
You also need to run the installer for each previously application that was installed (reinstall) in order to downgrade properly and have the initd and systemd services restored too.
A couple things to remember -
- Each run of an opModule installer creates a new backup file. However, since they all use the same name only the most recent will be maintained. If you are installing several packages you should rename each backup before running the next.
- This process overlays the backup into the /usr/local/omk directory and DOES NOT replace it.
There is no need to request a license update, as the licenses are continuing to be valid with this upgrade.