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

Compare with Current View Page History

« Previous Version 2 Next »

Prerequisites

A working copy of NMIS that opExport can read and export the data from

Installation Steps

Common Steps

  • copy the tarball to the server, into your users home directory

  • untar the file into a location of your choice, the default location is /usr/local/opExport 

  • copy the config file 
  • cd /usr/local
tar xvf ~/opExport-x86_64-1.0.0.tar.gz
cd opExport
cp ./install/opCommon.nmis ./conf/opCommon.nmis
  • Set the key that the daemons will use to verify each other in opCommon.nmis (opexport_connection_key)

Additional Steps for server holding the MySQL Database

  • copy the schema files to the conf directory 
  • cd /usr/local/opExport
cp ./install/schema_set.json ./config/
cp ./install/export-* ./config/

Start the server

This will need to be done on the server holding the MySQL Database as well as all the NMIS servers that will be exporting data

cd /usr/local/opExport/scripts
./opmantek.pl prefork

Configure the daemons that will export data

The server that holds the MySQL Database holds the master copy of the schema, in order for an NMIS server to export it's daemon requires a schema to be pushed to it.  

First we will check that the server has a schema configured.  In a web browser load:

http://your.mysql.server.name.or.ip:3000/opExport/

 

For each server you wish to have export you need to push the schema, in a web browser load:

http://your.server.name.or.ip:3000/opExport/schemas/push/NMIS_Server_Name?opexport_connection_key=key123
  • No labels