Versions Compared

Old Version 9

changes.mady.by.user Alexander Zangerl

Saved on

compared with

New Version 10

changes.mady.by.user Mark Henry

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel2
minLevel2

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).

...

  • 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.

...

Installing (or

...

Upgrading)

...

opEvents

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).

...

  • 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):

    Code Block
    'database' => { 
	'db_server' => 'localhost', 
	'db_port' => '27017',
	'db_name' => 'nmis',
	'db_username' => 'opUserRW',
	'db_password' => 'op42flow42',
},

  • 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  of that step for you automatically.
    To perform this operation, run the following command as root:

    Code Block
    /usr/local/omk/bin/opeventsd.pl act=setup
# you can also get an overview of opeventsd's capabilities by running opeventsd.pl --help

...

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.