Child pages
  • opEvents Installation Guide
Skip to end of metadata
Go to start of metadata

Prerequisites

  • 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.
  • NMIS must be installed on the same server that opEvents is being installed on.
  • opEvents requires a working MongoDB installation (but not necessarily on the same server)
  • You will need a license for opEvents (evaluation available here).

Preparation

  • If you do not have a MongoDB installation yet, either follow the instructions in the MongoDB Installation Guide or (with opEvents 1.2.6 and newer) tell the installer to install and configure MongoDB for you.
    opEvents does not require any specific MongoDB setup, but 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.

  • If you do not yet have a working installation of NMIS in your server, please follow the procedure in the NMIS 8 Installation Guide.
  • Download opEvents from the Opmantek website.

Installation (or Upgrade) Steps

Transfer the opEvents tarball 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.
Make a record of where you put the tarball (root's home directory or /tmp are good locations).

  • Become root and unpack the tarball:

  • Start the interactive installer and follow its instructions. The installer now fully covers both initial installations as well as upgrades from earlier versions of opEVents.

  • 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.
  • For detailed information about the interactive installer please check the Opmantek Installer page.
  • a small warning: the installer for opEvents 1.2.3 may warn about two "incorrect checksum detected" for two files, if you install this version on top of the Opmantek Virtual Appliance version 8.5.6G or after other Opmantek applications that were released since opEvents 1.2.3. These warnings are benign and you can safely confirm that the installer is allowed to 'overwrite' those files.

Initial Configuration

  • You will need to adjust the MongoDB-related settings:
    open conf/opCommon.nmis in an editor, go to the database section and change the server, username and password to reflect your MongoDB installation.
    The result should look similar to the following (but there might be extra settings related to other products):

  • For opEvents versions before 1.2.2 you'll need to initialize your MongoDB with suitable indices. opEvents version 1.2.2 and later take care of  that step for you automatically.
    To perform this operation, run the following command as root:

  • After completing your configuration changes you'll need to restart both the opEvents daemon as well as the Opmantek daemon.
    Simply run the following commands as root:

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.

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