Versions Compared

Old Version 6

changes.mady.by.user Mark Dueck

Saved on

compared with

New Version 7

changes.mady.by.user Mark Dueck

Saved on

Key

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

...

  • 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 files 
  • Code Block
    cd /usr/local
tar xvf ~/opExport-x86_64-1.0.0.tar.gz
chown -R nmis:nmis opExport 
cd opExport
cp ./install/opCommon.nmis ./conf/opCommon.nmis 
cp install/opexport.init.d /etc/init.d/opexport
chkconfig --add opexport 
chown -R nmis:nmis opExport
  • Set the key that the daemons will use to verify each other, opexport_connection_key, in opCommon.nmis (. The default key is opexport_connection_key)=key123.

Additional Steps for

...

the MySQL Database server

  • copy the schema files to the conf directory directory, this should ONLY be done on the MySQL server, not on the NMIS servers

  • Code Block
    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 all of the servers, e.g. the MySQL Database server as well as all the NMIS servers that will be exporting data

 

Code Block
cd /usr/local/opExport/scripts ./opmantek.pl preforkservice opexport start
Check that the all the daemons are running and that you can access them with the connection key that you configured (do this for all daemons you have configured), at this point you will need to enter your license key and accept the EULA:

 

Code Block
http://your.server.names.or.ip:3000/opExport/?opexport_connection_key=key123

 

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.  

Each NMIS server that will export it's data must be able to access the MySQL server with a simple host name (no dots), so you may need to edit /etc/hosts and add entries to allow this.

Additionally, the MySQL server requires the same for all the NMIS servers that will push to it, so again you may need to add them to it's /etc/hosts file.

NextFirst, check that the MySQL server has a schema configured.  In a web browser load:

Code Block
http://your.MySQL.server.name.or.ip:3000/opExport/schemas

 

?opexport_connection_key=key123

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

Code Block
http://your.MySQL.server.name.or.ip:3000/opExport/schemas/push/NMIS_Server_Name1?opexport_connection_key=key123
http://your.MySQL.server.name.or.ip:3000/opExport/schemas/push/NMIS_Server_NameName2?opexport_connection_key=key123
http://your.MySQL.server.name.or.ip:3000/opExport/schemas/push/NMIS_Server_Name3?opexport_connection_key=key123

 

You can now verify that each of the NMIS servers have the schema:

Code Block
http://your.NMIS.server.namename1.or.ip:3000/opExport/schemas?opexport_connection_key=key123

 

Transferring Data

There are two ways to transfer, the MySQL server can "pull" the data, or the NMIS server can "push" the data.

To pull:

Code Block
http://your.MySQL.server.name.or.ip:3000/opExport/schemas/pull/NMIS_server_name?opexport_connection_key=key123

To push:

Code Block
http://your.NMIS.server.name.or.ip:3000/opExport/schemas/push/MySQL_server_name?opexport_connection_key=key123

 

Error checking

The daemon should be writing to /usr/local/opExportopexport/log, currently that functionality is not working so it will dump everything to STDOUT.  That is where you will want to look.