Versions Compared

Old Version 4

changes.mady.by.user Alexander Zangerl

Saved on

compared with

New Version 5

changes.mady.by.user Mark Dueck

Saved on

Key

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

...

  • 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 deployed toinstalled on.
  • opEvents requires a working MongoDB installation (but not necessarily on the same server)
  • You will need an a license for opEvents (evaluation available here) license for opEvents.

Preparation

  • If you do not have a MongoDB installation yet, please follow the instructions in the MongoDB Installation Guide.
    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.

...

  • 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.
  • For detailed information about the interactive installer please check the Opmantek Installer page.
  • When the  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.

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',
},

...