Versions Compared

Old Version 7

changes.mady.by.user Alexander Zangerl

Saved on

compared with

New Version 8

changes.mady.by.user Alexander Zangerl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added checksum warning

...

  • Become root and unpack the tarball:

    Code Block
    # become root
sudo sh
# if the tarball was saved in a different location, adjust the following command 
cd
tar xzf opEvents-x86_64-1.2.0.tar.gz

  • Start the interactive installer and follow its instructions:

    Code Block
    sudo sh
cd opEvents-1.2.0
./installer

++++++++++++++++++++++++++++++++++++++++++++++++++++++
opEvents (1.2.0) Installation script
++++++++++++++++++++++++++++++++++++++++++++++++++++++

This installer will install opEvents into /usr/local/omk.
To select a different installation location please rerun the 
installer with the -t option.
...
  • 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):

    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

...