Versions Compared

Old Version 6

changes.mady.by.user Mark Dueck

Saved on

compared with

New Version 7

changes.mady.by.user Alexander Zangerl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated install guide with db indexing step

...

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

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

    Code Block
    # don't forget to become root, using sudo sh or su
service opeventsd restart
service omkd restart
# to verify the status of the daemons:
service opeventsd status
service omkd status

...