Versions Compared

Key

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

Installation Prerequisites

  • The individual performing this installation has some Linux experience.
  • NMIS8 is installed on the same server where opHA will be installed
  • NMIS8 is installed in /usr/local/nmis8
  • opHA will be installed into /usr/local/nmis8
  • Root access is available (not always needed but much easier)
  • Perl 5.10 
  • RRDtool 1.4.7
  • NMIS 8.3.3G or later

Preparation for Installation

...

  • opHA will be installed onto the Master and each Slave NMIS server

Installation Steps

  • Copy the opHA tarball to the slave NMIS server (a tarball is a GZIP'd tar file, e.g. opHA-1.1.tar.gz)
    1. You may need to use SCP or FTP to get the file onto the server.
  • The file will now likely be in the users home directory.
  • If the installation directory does not already exist
  • Change into the directory where the tarball was copied
  • Untar the file

 

Code Block
themeEmacs
cd /usr/local~
tar xvf ~/opMaps64opHA-<version>.tar.gz
cd opmantekopHA/
cp install/MapsServers.nmis conf/
bin/opfixperms.pl
cp install/01opmantek.conf /etc/httpd/conf.d/
service httpd restart

 

 

Alternate Installation Directory

opMaps can be installed into another directory if required, e.g. /opt/opmantek, the same process applies, but a few files will need to be changed.

Edit Maps.nmis and change the <omk_base> to be the new, e.g.

'<omk_base>' => '/opt/opmantek',

Edit the Apache include file, which if already copied to /etc/httpd/conf.d will be /etc/httpd/conf.d/01opmantek.conf and change the following lines to the new installation location

Alias /opmantek/ "/usr/local/opmantek/htdocs/"

...

usr/local/nmis8/conf/
cp cgi-bin/connect.pl /usr/local/

...

nmis8/cgi-bin/

...

 

...


/usr/local/

...

nmis8/admin/fixperms.pl

opHA Slave Configuration

There are many configuration options in opReports, but the only one which must be updated to make everything work is the configuration for "report_server_prefix", this allows the emailed reports to point to the correct web server to load their configurations, this entry is in the opReports.nmis file and should be updated to be the public web prefix of the server, which the people receiving the emails would use to access the server (this might be the portal address).

'report_server_prefix' => 'http://nmis.domain.com',

Access opMaps Web Page

The default URL to access opMaps is http://nmis.domain.com/cgi-omk/opMaps

...