Template:OX HE Tutorial Design

High Level System Design

The overview shows that the OX AppSuite consists of several components:

HTTP Balancer

Accepts user requests and decides which part of the OX Middleware should handle them

OX Middleware

The central logic layer

Control Panel

Used for creation and administration of users (not delivered by OX)

Mail Server

Used by the middleware to receive and send e-mails (not delivered by OX)

SQL Server

Used by the middleware to e.g. store pim objects

File Server

used by the middleware to store documents and files

Middleware Details

The middleware itself consists of many modules whose functionality is either exposed via the HTTP_API or used internally. We have identified three blocks that should be grouped together and considered as logical components when planning the hardware layout and sizing of your infrastructure.

Groupware

Add more text

Documentconversion

Add more text

Synchronization

• USM Add more text
• EAS Add more text
• CALDAV Add more text
• CARDDAV Add more text

Component mappings in HTTP Balancer

The logical components mentioned above can be found again in our default Apache configuration which is distributed as part of the open-xchange-core package and located at /usr/share/doc/open-xchange-core/exapmples/proxy_http.conf.gz

You can find the wikified version at AppSuite:Grizzly#Apache_configuration

For each of the components we set up a balancing Proxy container so you can scale each of those components according to the number and demands of your users.

Proxy balancer://oxcluster

The members of this balancer container are responsible for handling general groupware requests

Proxy balancer://oxcluster_docs

The members of this balancer container are responsible for handling document conversion and thumbnailing requests

Proxy balancer://oxcluster_sync

The members of this balancer container are responsible for handling only USM, EAS and DAV synchronization requests