Summary
As of October 15th, the installer for an ABI4 application does not allow to upgrade from ABI1 products. However, there are some ways to get around this, here is one.
Upgrading process
In short
After installing NMIS9, move aside the omk directory and install the new ABI4 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 ABI4 application previously installed and restart the omk daemon.
In detail
- Install NMIS9, should install without any issues
- Rename the omk directory
mv /usr/local/omk /usr/local/omk-old
- Run the installer for the ABI4 application
- Rename the new omk/conf directory
mv /usr/local/omk/conf /usr/local/omk/conf-original
- Copy the omk-old/conf directory into the new omk/
cp -r /usr/local/omk-old/conf /usr/local/omk
- Convert the .nmis files in omk/conf/ directory into .json using the opcommon-cli tool
/usr/local/omk/bin/opcommon-cli.exe act=convert_json_dir dir="/usr/local/omk/conf/"
- Change any "nmis_dir" and "nmis8" entires to "nmis9_dir" and "nmis9" in the omk/conf/opCommon.json file. You can do this manually or by using the following Perl regex
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
- Change the "load_applications" entry in the opCommon.json file to only show the ABI4 application recently installed.
- Restart omkd
systemctl restart omkd.service