Seon master-slave database usage
If your environment enforces a parallel database installation, where Seon should use the slave database (i.e. in a DMZ or multi-application firewalled environment), Seon webinterface is able to change both the main defined database, but also another (slave) database for various updates. These entities are the following:
- basic configuration
- CAPI configuration
- partner specific CAPI configuration
- cipher suite definition
- automatic software update settings
- position of a self-signed certificate
- OFTP partner configuration
- send queue entries (status, priority etc.)
- receive queue
- poll queue
The behaviour can be enabled with the configuration switch "Update other partner database too?". The remote partner database parameter can be inserted if the switch is enabled. The defined database has to be the same schema as the local one, since the SQL statements are executed on both databases.
The configured database user must have INSERT, UPDATE and DELETE permissions on the configured database. It's highly recommended to configure the "slave" Seon web interface to use a database user which has no writing permissions in the database, but data SELECT permissions only.
When changing information in the "master" environment, the data will be transfered to the second database server, executed there. If there is any error during this transfer, there will appear an error message in the web interface. The error should then be fixed and the command restarted in order to have a consistent databse.
Before starting in such an environment, you should clone the complete database from the master to the slave, so they have the same ky information, like auto-increment values etc.!
