Child pages
  • Upgrading from NMIS8 compatible applications to NMIS9 compatible applications

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As of October 15th, the installer for an NMIS9 compatible application does not allow to upgrade when an NMIS8 product is installed. However, there are some ways to get around this, here is one.

As of November 13th the opEvents-3.2.1 installer handles upgrading from NMIS8 computable applications to NMIS9. Therefore, if opEvents is one of the applications you wish to upgrade, please start from that one and you'll be able to upgrade the remaining products without any issues. Otherwise, please follow the upgrade process below.

Upgrading process

In short

...

Code Block
cp -rf /usr/local/omk-old/var/opreports/known_reports_cache /usr/local/omk/var/opreports
cp /usr/local/omk-old/var/opreports/selftest.json /usr/local/omk/var/opreports

About opEvents

In order to get the new opEvents to show the old events two steps are required post installation:

...

Code Block
/usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /opevents/opevents_db_name=nmis

...

Code Block
mongo

2.2 - Switch to the nmis database

Code Block
> use nmis

2.3 - Rename the sate collection

Code Block
> db.state.renameCollection('state-old')

2.4 - Exit

Code Block
> exit

2.5 - Restart omkd

Code Block
systemctl restart omkd.service