View source for Seon Core parallel installation

== multiple separated configurations ==

Seon supports parallel installation on one machine with just one license key. The license key is machine dependant, so you can re-use it in every installation. 

If you plan to install more than one Seon instance on a machine you have to: 
*create a separate Seon configuration file for each installation ([[Seon Core installation#Main configuration|seon.conf]]) 
*use a different web interface directory for each installation 
*use a different [[Seon Core configuration#binary installation directory|binary installation directory]] for each installation (like in the above used examples, "<code>/opt/seon</code>" should be copied completely). This also affects the [[Seon Core configuration#data incoming directory|incoming]], [[Seon Core configuration#data outgoing directory|outgoing]], [[Seon Core configuration#temporary directory|temporary]], [[Seon Core configuration#database backup directory|backup]], [[Seon Core configuration#RRDB data path|RRD]] etc. directories (say: all directories which are configurable). 
*Use a different MySQL database. This is an absolute MUST!

You may want to share some parts of Seon between all instances, like the event scripts, backup directories or others (as you wish). This is done by configuring each instance to the appropriate values. 

If you define the Seon web interface to use "file" as a configuration source, all calls from the web interface will use this configured file as a parameter for all binary calls. If configured the web interface with the type „direct“, this functionality is not available, but all calls of Seon binaries are used using the configured binary installation directory. Some scripts may need special attention if a different configuration file is used.

== same configuration on multiple servers ==

Another solution is running Seon receive and send queue daemons with the parameter "<code>-i</code>", which defines the instance of this running installation. With this parameter, all send queue entries in the configured database with the used server ID are processed. This feature allows running multiple Seon instances on the same database with the same configuration.