AppSuite:OX Tutorial 1M - Revision history

Khgras: /* Install and configure OX on both servers */

2026-05-07T12:38:45Z

Install and configure OX on both servers

← Older revision		Revision as of 12:38, 7 May 2026
Line 78:		Line 78:

	[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]		[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]

	~~Let your users connect to their data from other services like Twitter or LinkedIn (removed since 7.10.0) by configuring the "SocialOX"~~

	~~[[SocialOX\|SocialOX-Configuration]]~~

	= Installation Steps depending on your environment - Instructions & Recommendations =		= Installation Steps depending on your environment - Instructions & Recommendations =

Ioannis.chouklis: /* Install and configure OX on both servers */

2018-02-08T08:33:26Z

Install and configure OX on both servers

← Older revision		Revision as of 08:33, 8 February 2018
Line 79:		Line 79:
	[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]		[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]

	Let your users connect to their data from other services like Twitter or LinkedIn by configuring the "SocialOX"		Let your users connect to their data from other services like Twitter or LinkedIn (removed since 7.10.0) by configuring the "SocialOX"

	[[SocialOX\|SocialOX-Configuration]]		[[SocialOX\|SocialOX-Configuration]]

Khgras at 10:19, 22 May 2017

2017-05-22T10:19:28Z

← Older revision		Revision as of 10:19, 22 May 2017
Line 45:		Line 45:
	# Upsell Plugin (see [[AppSuite:Upsell\|here]] and [[AppSuite:Upsell_tools\|here]])		# Upsell Plugin (see [[AppSuite:Upsell\|here]] and [[AppSuite:Upsell_tools\|here]])
	# Automatic FailOver		# Automatic FailOver
	# Theming (see [~~[AppSuite~~:~~Theming\|~~here]])		# Theming (see [https://documentation.open-xchange.com/latest/ui/theming.html here])

	= Mandatory Installation Steps - Instructions & Recommendations =		= Mandatory Installation Steps - Instructions & Recommendations =

Martin.schneider: US 97798972, remove everything related to facebook

2015-07-07T13:10:43Z

US 97798972, remove everything related to facebook

← Older revision		Revision as of 13:10, 7 July 2015
Line 79:		Line 79:
	[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]		[[OXtender_for_Business_Mobility\| exchange active sync configuration for Open-Xchange]]

	Let your users connect to their data from other services like ~~Facebook,~~ Twitter or LinkedIn by configuring the "SocialOX"		Let your users connect to their data from other services like Twitter or LinkedIn by configuring the "SocialOX"

	[[SocialOX\|SocialOX-Configuration]]		[[SocialOX\|SocialOX-Configuration]]

Dennis Sieben: /* Recommended Optional Next Steps */

2014-01-30T15:37:29Z

Recommended Optional Next Steps

← Older revision		Revision as of 15:37, 30 January 2014
Line 42:		Line 42:

	== Recommended Optional Next Steps ==		== Recommended Optional Next Steps ==
	# Automated Frontend Tests		# Automated Frontend Tests (see [[Automated_GUI_Tests\|here]])
	# Upsell Plugin (see [[AppSuite:Upsell]] and [[AppSuite:Upsell_tools]])		# Upsell Plugin (see [[AppSuite:Upsell\|here]] and [[AppSuite:Upsell_tools\|here]])
	~~# Mobile Autoconfiguration~~
	# Automatic FailOver		# Automatic FailOver
	# ~~Branding~~		# Theming (see [[AppSuite:Theming\|here]])

	= Mandatory Installation Steps - Instructions & Recommendations =		= Mandatory Installation Steps - Instructions & Recommendations =

Dennis Sieben: /* Recommended Optional Next Steps */

2014-01-30T15:24:17Z

Recommended Optional Next Steps

← Older revision		Revision as of 15:24, 30 January 2014
Line 43:		Line 43:
	== Recommended Optional Next Steps ==		== Recommended Optional Next Steps ==
	# Automated Frontend Tests		# Automated Frontend Tests
	# Upsell Plugin		# Upsell Plugin (see [[AppSuite:Upsell]] and [[AppSuite:Upsell_tools]])
	# Mobile Autoconfiguration		# Mobile Autoconfiguration
	# Automatic FailOver		# Automatic FailOver
	# Branding		# Branding


	= Mandatory Installation Steps - Instructions & Recommendations =		= Mandatory Installation Steps - Instructions & Recommendations =

Dennis Sieben: /* Core Components for OX App Suite */

2014-01-30T15:17:06Z

Core Components for OX App Suite

← Older revision		Revision as of 15:17, 30 January 2014
Line 15:		Line 15:
	The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.		The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.

	== ~~Core Components for OX App Suite~~ ==		== General recommendations ==

	* ~~Minimum two (~~recommended ~~three) OX AppSuite servers (HW recommendation: 32GB RAM / 8 cores each)~~		* A virtualisation enviroment is recommended
	* ~~Minimum one MySQL cluster~~ with ~~two servers in Master-Master configuration~~ (~~HW recommendation: 32GB RAM / 8 cores each~~)		* Many machines with less memory (16 GB) are preferred to fewer machines with big memory
	* NFS Server to ~~store documents and files~~		* The picture above shows a valid setup for a webmail only system. Further features like the Business Mobility Connector or OX Documentes require more ressources.
	* ~~Recommended~~ for more ~~than 500~~.~~000 mailboxes: one OX App Suite server dedicated for user provisioning (HW recommendation: 16GB RAM / 4 cores each)~~

	== Infrastructure Components not delivered by OX ==		== Infrastructure Components not delivered by OX ==

Dennis Sieben: /* System Design */

2014-01-28T12:33:10Z

System Design

← Older revision		Revision as of 12:33, 28 January 2014
Line 11:		Line 11:
	= System Design =		= System Design =

	[[Image:~~SaaS~~-1M.~~jpg~~]]		[[Image:AppSuite-1M.png\|1000px]]

	The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.		The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.

Dennis Sieben at 10:49, 12 November 2013

2013-11-12T10:49:12Z

← Older revision		Revision as of 10:49, 12 November 2013
Line 66:		Line 66:
	OX will be installed on minimum two servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database in one cluster. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed MySQL server will be taken over to the working server, the system stays operable.		OX will be installed on minimum two servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database in one cluster. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed MySQL server will be taken over to the working server, the system stays operable.

	[[OXLoadBalancingClustering_OXConfiguration\|Open-Xchange setup and configuration for clustered environments]]		[[AppSuite:OXLoadBalancingClustering_OXConfiguration\|Open-Xchange setup and configuration for clustered environments]]

	The NFS server will be mounted on all machines and registered as filestore.		The NFS server will be mounted on all machines and registered as filestore.

Dennis Sieben: Created page with "= Tutorial: High Available OX App Suite Setup for up to 1 Milion users = '''This article describes what you need for a typical OX App Suite Setup for up to 1.000.000 Users, w..."

2013-11-11T15:57:36Z

Created page with "= Tutorial: High Available OX App Suite Setup for up to 1 Milion users = '''This article describes what you need for a typical OX App Suite Setup for up to 1.000.000 Users, w..."

New page

= Tutorial: High Available OX App Suite Setup for up to 1 Milion users =

'''This article describes what you need for a typical OX App Suite Setup for up to 1.000.000 Users, which is fully clustered, high available and scaling very flexible.'''

It contains everything you need to:
* Understand the design of the OX App Suite setup including additional services
* Install the whole system based on the relevant articles
* Find pointers to the next steps of integration

= System Design =

[[Image:SaaS-1M.jpg]]

The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one OX server fail, this is transparently handled by the load balancer. If one MySQL server fails, it is sufficient to take over the IP address on the other MySQL server in the cluster to stay fully in operation.

== Core Components for OX App Suite ==

* Minimum two (recommended three) OX AppSuite servers (HW recommendation: 32GB RAM / 8 cores each)
* Minimum one MySQL cluster with two servers in Master-Master configuration (HW recommendation: 32GB RAM / 8 cores each)
* NFS Server to store documents and files
* Recommended for more than 500.000 mailboxes: one OX App Suite server dedicated for user provisioning (HW recommendation: 16GB RAM / 4 cores each)

== Infrastructure Components not delivered by OX ==

* An email system providing IMAP and SMTP
* A control panel for creation and administration of users
* A Load Balancer in front of the OX servers (optional, recommended)

= Overview Installation Steps =

'''To deploy the described OX setup, the following steps need to be done. '''

== Mandatory Steps ==
# Initialize and configure MySQL database servers
# Install and configure OX on all servers

== Steps depending on your environment ==
# Implement Load Balancer
# Connect Control Panel
# Connect Email System

== Recommended Optional Next Steps ==
# Automated Frontend Tests
# Upsell Plugin
# Mobile Autoconfiguration
# Automatic FailOver
# Branding

= Mandatory Installation Steps - Instructions & Recommendations =

'''The following steps need to be done in every case to get OX up and running:'''

== Initialize and configure MySQL database on both servers ==

MySQL will be configured as Master-Master configuration to ensure data consistency on both servers.
If one machine fails, the other machine will take over all functionality.

[[OXLoadBalancingClustering_Database|Database setup for clustered environments]]

== Install and configure OX on both servers ==

OX will be installed on minimum two servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database in one cluster. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed MySQL server will be taken over to the working server, the system stays operable.

[[OXLoadBalancingClustering_OXConfiguration|Open-Xchange setup and configuration for clustered environments]]

The NFS server will be mounted on all machines and registered as filestore.

[[OXLoadBalancingClustering_Filestore|Filestore setup for clustered environments]]

When multiple Open-Xchange Servers are configured within a cluster Session and Loadbalancing needs to be set up.

[[OXLoadBalancingClustering_SessionLoadbalancing|Session and Loadbalancing for clustered environments]]

[[OXLoadBalancingClustering_NetworkConfiguration|Network configuration for clustered environments]]

You also should install and configure the OXtender for Business Mobility:

[[OXtender_for_Business_Mobility| exchange active sync configuration for Open-Xchange]]

Let your users connect to their data from other services like Facebook, Twitter or LinkedIn by configuring the "SocialOX"

[[SocialOX|SocialOX-Configuration]]

= Installation Steps depending on your environment - Instructions & Recommendations =

'''The following components need to be implemented in your environment.'''

== Implement Load Balancer ==

A load balancer in front of the OX servers is necessary for this deployment size. It needs to handle the requests if one OX server fails.

If you already have a hardware load balancing solution in place, this can be used. OX is known to work with the standard load balancing solutions from BigIP, Barracuda, Foundry, ...

If you do not have a load balancing solution already in place, we recommend to use [http://www.keepalived.org/ Keepalived] as reliable and cost effective solution.

Read more about configuring [[Keepalived | Keepalived for Open-Xchange]]

{{OX_HE_Tutorial_CP}}

{{OX_HE_Tutorial_HGP}}

{{OX_HE_Tutorial_POA}}

{{OX_HE_Tutorial_Auth}}

== Connect Email System ==

Every email system providing IMAP and SMTP can be used as backend to OX. Best experiences are made with the widespread Linux based IMAP servers [http://dovecot.org/ Dovecot], [http://www.cyrusimap.org/ Cyrus] or [http://www.courier-mta.org/imap/ Courier].

Other IMAP servers need to be tested thoroughly before going into production.

There are several possibilities to implement the Email system:

# You already have an email system available: Nothing needs to be done, it just needs to be configured
# You use Parallels Automation (POA): Nothing special needs to be done, everything you need is contained in the APS package
# You want to setup a new Email system: It is recommended to use Dovecot, as this is very stable, fast, feature rich and easy to scale

{{OX_HE_Tutorial_Dovecot}}

{{AppSuite:OX_Tutorial_Next}}