|Table of Contents|
This document will highlight some key aspects of the upgrade process of the current Opmantek Applications.
Requirements to upgrade
Upgrading NMIS 9 compatible applications
In order to be able to upgrade you need to have please ensure the following version product versions are installed on your system.
|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 our products release notes
- opReports 4 release notes
- opHA 3 release notes
- NMIS 9 Release Notes
- opEvents 3 Release Notes
- opConfig 4 release notes
- opCharts Release Notes
Check compatibility with other OMK apps
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.
Unless this is the very first installation of an Opmantek product on this system, the installer will offer taking a backup of all affected files before the installation commences. This backup will be saved in the
rootuser's home directory as omk-backup-YYYY-MM-DD.tgz. The backup includes:
- all the directories that the installer will later copy files to,
- the old software manifest,
- and the old install.log.
Restoring from backup
How to restore from a failed upgrade
This is the process to use if you need to roll back from the installer using this backup:
A couple things to remember -