...
- Move the tar archive opReports-3.4.1-standalone.tar.gz, provided by Opmantek for this purpose, to /opt/ directory on server to be deployed to
Uncompress the file, then set permissions on /opt/omk/ directory structure appropriately:
Code Block title /opt/ cd /opt/ sudo tar -xzvf opReports-3.4.1-standalone.tar.gz sudo chown -R root:nmis /opt/omk/ # verify cd omk/ ls -lah total 52K drwxr-xr-x. 9 root nmis 4.0K Mar 30 00:36 . drwxr-xr-x. 4 root root 4.0K Mar 30 20:06 .. drwxrwsr-x. 3 root nmis 4.0K Mar 29 02:21 bin drwxr-xr-x. 3 root nmis 4.0K Mar 30 00:06 conf drwxr-xr-x. 4 root nmis 4.0K Mar 30 16:57 install -rw-r--r--. 1 root nmis 16K Mar 29 22:09 LICENSE drwxr-xr-x. 2 root nmis 4.0K Mar 30 00:40 log drwxr-xr-x. 3 root nmis 4.0K Mar 29 22:09 public drwxr-xr-x. 8 root nmis 4.0K Mar 29 22:42 templates drwxr-xr-x. 3 root nmis 4.0K Mar 30 00:40 var # verify bin directory ls -lah bin/ total 136M drwxrwsr-x. 3 root nmis 4.0K Mar 29 02:21 . drwxr-xr-x. 9 root nmis 4.0K Mar 30 00:36 .. drwxr-sr-x. 2 root nmis 4.0K Mar 29 02:21 install lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 oplicense-cli-standalone.exe -> opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 oplicense-cli-standalone.pl -> opmantek-standalone.exe -rwxr-xr-x. 1 root nmis 136M Mar 26 01:53 opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 opmantek-standalone.pl -> opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 opreports-cli-standalone.exe -> opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 opreports-cli-standalone.pl -> opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 opreports-scheduler-standalone.exe -> opmantek-standalone.exe lrwxrwxrwx. 1 root nmis 23 Mar 30 20:06 opreports-scheduler-standalone.pl -> opmantek-standalone.exe # clean sudo rm opReports-3.4.1-standalone.tar.gz # set up init.d service (opReports-3.4.1-standalone.tar.gz was built on a VM with systemd # - hence the '.bak' in filename at this stage: install/omkd-standalone.init.d.bak) # - we copy to /etc/init.d and rename file to omkd-standalone sudo cp install/omkd-standalone.init.d.bak /etc/init.d/omkd-standalone # on Debian or Ubuntu we would now: # sudo update-rc.d omkd-standalone defaults # but we are on Centos, so: sudo chkconfig --add omkd-standalone sudo chkconfig omkd-standalone on # copy our proxy config into position: # on Debian or Ubuntu we would now: # sudo cp -f install/05omk-standalone-proxy.conf /etc/apache2/conf.d/ # # # newer apache: different location, and use a2enmod # [ -d "/etc/apache2/conf-available" ] && sudo cp -f /etc/apache2/conf.d/05omk-standalone-proxy.conf /etc/apache2/conf-available/ # [ -d "/etc/apache2/conf-available" ] && sudo a2enmod proxy # [ -d "/etc/apache2/conf-available" ] && sudo a2enmod proxy_http # [ -d "/etc/apache2/conf-available" ] && sudo a2enmod headers # [ -d "/etc/apache2/conf-available" ] && sudo a2enconf 05omk-standalone-proxy.conf # # sudo service apache2 restart # # but we are on Centos, so: sudo cp -f install/05omk-standalone-proxy.conf /etc/httpd/conf.d/ sudo service httpd restart # set up the opReports 3.4.1 cron-jobs
...