OS4X Core parallel installation - Revision history

Admin at 17:27, 7 May 2007

2007-05-07T17:27:01Z

Admin at 10:10, 2 May 2007

2007-05-02T10:10:44Z

Admin at 10:10, 2 May 2007

2007-05-02T10:10:35Z

Admin at 20:48, 10 April 2007

2007-04-10T20:48:43Z

Admin: New page: OS4X 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 mor...

2007-04-10T20:47:56Z

New page: OS4X 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 mor...

New page

OS4X 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 OS4X instance on a machine you have to:
*create a separate OS4X configuration file for each installation ([[OS4X Core installation# Main configuration|os4x.conf]])
*use a different web interface directory for each installation
*use a different [[OS4X Core configuration#binary installation directory|binary installation directory]] for each installation (like in the above used examples, "<code>/opt/os4x</code>" should be copied completely). This also affects the [[OS4X Core configuration#data incoming directory|incoming]], [[OS4X Core configuration#data outgoing directory|outgoing]], [[OS4X Core configuration#temporary directory|temporary]], [[OS4X Core configuration#database backup directory|backup]], [[OS4X 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 OS4X 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 OS4X 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 OS4X binaries are used using the configured binary installation directory. Some scripts may need special attention if a different configuration file is used.

@@ Line 1: / Line 1: @@
 OS4X 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.
@@ Line 11: / Line 13: @@
 If you define the OS4X 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 OS4X 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 OS4X 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 OS4X instances on the same database with the same configuration.

@@ Line 10: / Line 10: @@
 If you define the OS4X 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 OS4X binaries are used using the configured binary installation directory. Some scripts may need special attention if a different configuration file is used.
 ----
 Another solution is running OS4X 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 OS4X instances on the same database with the same configuration.

← Older revision		Revision as of 10:10, 2 May 2007
Line 10:		Line 10:

	If you define the OS4X 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 OS4X binaries are used using the configured binary installation directory. Some scripts may need special attention if a different configuration file is used.		If you define the OS4X 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 OS4X binaries are used using the configured binary installation directory. Some scripts may need special attention if a different configuration file is used.
		+
		+
		+	----
		+
		+	Another solution is running OS4X 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 OS4X instances on the same database with the same configuration.

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