Page History

• copy the schema files to the conf directory 

• 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 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.  

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.  

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

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

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

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

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

http://your.NMIS.server.name.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:

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

To push:

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/opExport/log, currently that functionality is not working so it will dump everything to STDOUT.  That is where you will want to look.