Page History

...

Initial Configuration

• You If the interactive installer installed MongoDB it will also configure opEvents to connect to it. However, if you did not instruct the installer to install mongoDB, or if yoy want to point opEvents to use mongoDB on another server, you will need to adjust the MongoDB-related settings:open 

  • Open /usr/local/omk/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

  • example below is from a default installation with a local MongoDB installed by the opEvents installer. Your entries should look similar to the following (but there might be extra settings related to other products):

    Code Block
    'database' => { 'db_admin_port' => '28017', 'db_connection_timeout' => 20000, 'db_name'

  • => 'nmis', 'db_

  server

  • password' => '

  localhost

  • op42flow42',

  • 'db_ping_timeout' => 2000, 'db_port' => '27017'

  ,

  • , 'db_query_timeout' => 5000, 'db_

  name

  • server' => '

  nmis

  • localhost',

  • 'db_use_v26_features' => 1, 'db_username' => 'opUserRW',

  • 'db_

  password

  • write_concern' =>

  'op42flow42',

  • 1 },

• For opEvents versions before 1.2.2 Only 

...

• After completing your configuration changes you'll need to restart both the opEvents daemon (opeventsd) as well as the Opmantek daemon (omkd).
  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

...