Versions Compared

Old Version 8

changes.mady.by.user Alexander Zangerl

Saved on

compared with

New Version 9

changes.mady.by.user Alexander Zangerl

Saved on

Key

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

...

  • If you do not have a MongoDB installation yet, please either follow the instructions in the MongoDB Installation Guide or (with opEvents 1.2.6 and newer) tell the installer to install and configure MongoDB for you.
    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.

Installation (or Upgrade) Steps

Transfer the opEvents tarball onto the server in question, either by direct download from the Opmantek website, or from your desktop with scp or sftp or a similar file transfer tool.
Make a record of where you put the tarball (root's home directory or /tmp are good locations).

  • 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:. The installer now fully covers both initial installations as well as upgrades from earlier versions of opEVents.

    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.

...