Child pages
  • opMaps Installation Guide
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Installation Prerequisites

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

Installation Steps

  • Copy the opMaps tarball to the server (a tarball is a GZIP'd tar file, e.g. opMaps-Linux-x86_64-1.3.tar.gz for 64bit Linux or opMaps-Linux-i686-1.3.tar.gz for 32bit Linux)
    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
cd /usr/local
tar xvf ~/opMaps-Linux-x86_64-<version>.tar.gz
cd opmantek/
cp install/Maps.nmis conf/
cp install/opCommon.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/"
ScriptAlias /cgi-omk/ "/usr/local/opmantek/cgi-bin/"
<Directory "/usr/local/opmantek/cgi-bin"> 

Basic opMaps 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

Any authentication challenges will be the same as to login to your NMIS8 system.

 

 
  • No labels