Page History

...

After installing NMIS9, move aside the omk directory and install the new NMIS9 compatible application. Once the installation has finished rename the new omk/conf folder and copy over the old omk/conf folder. Convert the .nmis files in omk/conf/ directory into .json using the opcommon-cli tool. Edit the new omk/conf/opCommon.json file replacing any "nmis_dir" and "nmis8" entries for "nmis9_dir" and "nmis9". Lastly ensure the "load_applications" entry in this file shows only the new NMIS9 application previously installed and restart the omk daemon. We recommend starting this upgrade process with either opCharts or opConfig.

In detail

1. Install NMIS9, should install without any issues
2. Rename the omk directory

   
   

   Code Block
   mv /usr/local/omk /usr/local/omk-old

   
   

3. Run the installer for the new NMIS9 application
4. Rename the new omk/conf directory

   
   

   Code Block
   mv /usr/local/omk/conf /usr/local/omk/conf-original

   
   

5. Copy the omk-old/conf directory into the new omk/

   
   

   Code Block
   cp -r /usr/local/omk-old/conf /usr/local/omk

   
   

6. Convert the .nmis files in omk/conf/ directory into .json using the opcommon-cli tool

   
   

   Code Block
   /usr/local/omk/bin/opcommon-cli.exe act=convert_json_dir dir="/usr/local/omk/conf/"

   
   

7. Change any "nmis_dir" and "nmis8" entries to "nmis9_dir" and "nmis9" in the omk/conf/opCommon.json file. You can do this manually or by using the following Perl regex

   
   

   Code Block
   perl -p -i -e 's/nmis_dir/nmis9_dir/g' /usr/local/omk/conf/opCommon.json perl -p -i -e 's/nmis8/nmis9/g' /usr/local/omk/conf/opCommon.json perl -p -i -e 's/nmis_logs/nmis9_logs/g' /usr/local/omk/conf/opCommon.json

   
   

8. Change the "load_applications" entry in the opCommon.json file to only show the NMIS9 application recently installed. You can do this manually or by running the required patch_config commands to delete each application from the "load_applications" entry, except for the one that was recently installed.

   
   

   Code Block

   # E.g.: Previously installed applications: opConfig, opCharts, opEvents, opHA, opReports and Open-AudIT # Recently installed application: opConfig /usr/local/omk/bin/patch_config.pl -b /usr/local/omk/conf/opCommon.json /omkd/load_applications-=opCharts # -b = Creates backup (opCommon.json.prepatch) /usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /omkd/load_applications-=opEvents /usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /omkd/load_applications-=opHA /usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /omkd/load_applications-=opReports /usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /omkd/load_applications-=Open-AudIT # If the recently installed application (eg.: opConfig) is deleted by mistake, you can add it back by running the follow patch_config command /usr/local/omk/bin/patch_config.pl /usr/local/omk/conf/opCommon.json /omkd/load_applications+=opConfig

   
   

9. Restart omkd

   
   

   Code Block
   systemctl restart omkd.service

   
   

...

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

1. Rename the opevents_db_name from 'opevents' to 'nmis in the opCommon.json file. You can do this manually or by using the the following patch_config command

   
   

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

   
   

2. Drop or rename the state collection in the NMIS database. This can be done through the mongo shell

   
   

   
   2.1 - Open Mongo shell

   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