...

This  document explains the most essential installer features.

Installation of Opmantek Applications

Opmantek Applications Download Formats

...

Please feel free to submit your comment here or email us with your questions!

Uninstalling Opmantek Applications

Because Opmantek applications share code and modules wherever  possible, uninstalling a single application is not completely trivial.

Using the Uninstaller

As of September 2016, all application releases include an unistaller tool which performs a limited uninstallation of a particular application. It's easy to use, but primarily disables an application without removal of application data or files. The uninstaller offers a simulation mode, too. You simply start it up with the application module in question, e.g.

# -n invokes the simulation mode
/usr/local/omk/bin/uninstaller.exe -n opCharts
...
Would remove opCharts from load_applications list in opCommon.nmis.
Would restart service omkd.
Would stop service nmisd.
Would move init script nmisd to /root/uninstall-backup.

Manual Removal

If you desire a more permanent and complete application removal you will have to remove all Opmantek applications: it is infeasibly complicated to determine which files and code modules are removable and which have to remain behind to keep the remaining applications in working shape.

A checklist for complete removal would involve the following steps:

• Removal of all Opmantek daemon init scripts from /etc/init.d
  This may include init scripts for omkd,  nmisd, opeventsd, opconfigd, nfdump, opflowd.
  You should stop the daemons before removing the init scripts.
• Removal of cron schedules for the Opmantek applications
  This may include files in /etc/cron.d named oae, opaddress, opconfig, opevents,
  opflow, opreports, optrend.
• Removal of all of /usr/local/omk, /var/log/omk, /data/omk
  The latter two may not be present (but will be if your system started  as an Opmantek Virtual Appliance).
• Cleanup or removal of the Opmantek applications' MongoDB databases
  Unless you are actively using MongoDB you might simply stop the mongod daemon and remove the database files (typically under /var/lib/mongodb or /data/mongodb for the Opmantek VM).