View source for AppSuite:OX Tutorial 100K

= Tutorial: High Available OX AppSuite Setup for up to 100.000 users =

'''This article describes what you need for a typical OX AppSuite Setup for up to 100.000 Users, which is fully clustered and high available.'''

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


= System Design =

[[Image:AppSuite-100k.png|800px]]

The system is designed to provide maximum functionality and availability with a minimum of necessary hardware. If the services on one server fail, it is enough to take over the IP address to the other machine and service will stay up and running.

== Core Components for OX AppSuite ==

* Two OX AppSuite servers (HW recommendation: 16GB RAM / 4 cores each)
* MySQL installed directly on these server 
* NFS Server to store documents and files

== 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 on both servers
# Install and configure OX on both servers

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

== Recommended Optional Next Steps ==
# Automated Frontend Tests (see [[Automated_GUI_Tests|here]])
# Upsell Plugin (see [[AppSuite:Upsell|here]] and [[AppSuite:Upsell_tools|here]])
# Automatic FailOver
# Theming (see [https://documentation.open-xchange.com/latest/ui/theming.html here])

= 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 run 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 both servers. It will be configured to '''write''' to the '''first''' MySQL database and to '''read''' from the '''second''' MySQL database. This will distribute the load during normal operation as smooth as possible. During FailOver the IP address of the failed server will be taken over to the working server, the system stays operable.

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

The NFS server will be mounted on both 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_Installation_Guide|Installation of the OXtender for Business Mobility]]

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 =

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


== Implement Load Balancer ==

A load balancer in front of the OX servers is recommended, but optional in this deployment size. (In small environments, DNS Round Robin may be sufficient).

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}}


{{OX_HE_Tutorial_FailOver}}