Versions Compared

Key

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

...

######################################################
# Opmantek Config
######################################################
# Run opReports Batch 
0 0 * * * /usr/local/opmantek/bin/opReports-daily.sh
0 0 * * Sun /usr/local/opmantek/bin/opReports-weekly.sh

 

Alternate Installation Directory

...

<Directory "/usr/local/opmantek/cgi-bin"> 

Edit the crontab and use the locations of the two shell scripts, e.g.

0 0 * * * /opt/opmantek/bin/opReports-daily.sh
0 0 * * Sun /opt/opmantek/bin/opReports-weekly.sh

Edit each of the opReports shell scripts and update the following line

OMK=/opt/opmantek

Basic opReports 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',

Patching opReports

Often patches will be released for opReports, the following are commands to install a patch, unless other instructions are specifically provided.

...