cd /usr/local tar xvf ~/opMaps64-<version>.tar.gz cd opmantek/ cp install/Maps.nmis conf/ bin/opfixperms.pl cp install/01opmantek.conf /etc/httpd/conf.d/ service httpd restart |
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">
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',
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.