Page tree
Skip to end of metadata
Go to start of metadata


  • NMIS9 installed on the same server that opEvents is being installed (NMIS9 version >=9.1.0)
  • The individual performing this installation has a small bit of Linux experience.
  • Root access is available.

  • Internet access is required for installing any missing but required software packages.
  • opEvents License (evaluation available here).
  • All licenses are added/updated at https://<hostname>/omk/opLicense .


  • For detailed information about Opmantek's interactive installer, including installation options (non-standard directory, non-interactive install, etc.)  please review the Opmantek Installer page.

  • If you do not yet have a working installation of NMIS in your server, please follow the procedure in the NMIS 9 Installation Guide.
  • While opEvents does not require any specific MongoDB setup, you will have to provide opEvents with the correct MongoDB server information, database name and user name/password (if you use authentication). opEvents works best with the default database name "nmis", and with MongoDB authentication enabled.

  • Download opEvents from the Opmantek website.


opEvents is distributed in a self-extracting download format that simplifies the installation process. More information on running the installer can be found on The Opmantek Installer page.

Transfer the opEvents installer file onto the server in question, either by direct download from the Opmantek website, or from your desktop with scp or sftp or a similar file transfer tool.

  • Start the interactive installer and follow its instructions:

    sudo sh ./
    opEvents (3.0.0) Installation script
    This installer will install opEvents into /usr/local/omk.
    To select a different installation location please rerun the 
    installer with the -t option.
  • The installer will interactively guide you through the steps of installing opEvents. Please make sure to read the on-screen prompts carefully.
  • When the installer finishes, opEvents is installed into /usr/local/omk, and the default configuration files are in /usr/local/omk/conf, ready for your initial config adjustments.
  • A detailed log of the installation process is saved as /usr/local/omk/install.log, and subsequent upgrades or installations of other Opmantek products will add to that logfile.

Initial Configuration

  • Authentication
    The installer will backup /usr/local/omk/conf/users.dat and then create a symlink to users.dat in your NMIS directory if it was found during installation.
    If the NMIS users.dat file could not be found during installation the existing users.dat file in /usr/local/omk/conf/ will be used.
    If /usr/local/omk/conf/users.dat is not found the default users.dat file will be copied to /usr/local/omk/conf/ from /usr/local/omk/install/.
    Default credentials can be found here.

Upgrade to version 3.2.0 and later

Starting from version 3.2.0,  we have made significant changes on our internal shared code for all our applications to work on Opmantek's latest and fastest platform, however, previously installed product are not compatible with this version. 

To find out more about this upgrade please read: 

Where to go from here

First you should test opEvents: open up a web browser, and point it to "http://<yourserverip>/omk/opEvents"; you will have to enter your license first, then you will see opEvents' main dashboard. See the authentication bullet point above for user/password info.

opEvents offers a rich and flexible set of configuration options to ensure it meets your requirements, but there are many more options than can be listed here. Please consult the opEvents documentation for details.

  • No labels