Versions Compared

Old Version 16

changes.mady.by.user Dan Carter (Unlicensed)

Saved on

compared with

New Version 17

changes.mady.by.user Josune Cordoba (Unlicensed)

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. If you do not yet have a working installation of NMIS in your server, please follow the procedure in the NMIS 8 Installation Guide and install NMIS before installing opEvents
  • You will need a license for opEvents (evaluation available HERE).
  • All licenses are added/updated at https://<hostname>/omk/opLicense .

...

Info
titleFor opEvents 1.2.3 Only

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

  • 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 /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 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_password' => 'op42flow42',
    'db_ping_timeout' => 2000,
    'db_port' => '27017',
    'db_query_timeout' => 5000,
    'db_server' => 'localhost',
    'db_use_v26_features' => 1,
    'db_username' => 'opUserRW',
    'db_write_concern' => 1
  },

...



  • For opEvents versions before 1.2.2 Only 
 Expand
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 (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

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