Root access is available.
If you do not have a MongoDB installation yet, 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.
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:
# 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.
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. ... |
/usr/local/omk, and the default configuration files are in /usr/local/omk/conf, ready for your initial config adjustments./usr/local/omk/install.log, and subsequent upgrades or installations of other Opmantek products will add to that logfile.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):
'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:
/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 as well as the Opmantek daemon.
Simply run the following commands as root:
# 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 |
First you should test opEvents: open up a web browser, and point it to "http://<yourserverip>/omk/opEvents"; you will have to enter your license first, then you will see opEvents' main dashboard.
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.