Difference between revisions of "Template:OX HE Tutorial Design"

(Middleware Details)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= High Level System Design =
+
=System Design=
 +
==High Level System Design==
  
 
[[Image:AppSuite_High_Level.png|frameless|alt=AppSuite_High_Level|800px]]
 
[[Image:AppSuite_High_Level.png|frameless|alt=AppSuite_High_Level|800px]]
  
The overview shows that the OX AppSuite consists of several components:
+
The overview shows that our OX AppSuite system will consist of several components:
  
 
; HTTP Balancer
 
; HTTP Balancer
Line 9: Line 10:
  
 
; OX Middleware
 
; OX Middleware
: The central logic layer
+
: The central logic layer that handles the incoming requests
  
 
; Control Panel
 
; Control Panel
Line 23: Line 24:
 
: used by the middleware to store documents and files
 
: used by the middleware to store documents and files
  
= Middleware Details =
+
== 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.
+
The middleware itself consists of many modules whose functionality is either exposed via the [https://documentation.open-xchange.com/components/middleware/http/latest/index.html 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.
  
 
[[Image:Middleware_Subparts.png|frameless|alt=Middleware_Subparts|800px]]
 
[[Image:Middleware_Subparts.png|frameless|alt=Middleware_Subparts|800px]]
  
==Groupware==
+
;Groupware
Add more text
+
:definiton
  
==Documentconversion==
+
;Documentconversion
Add more text
+
:definition
  
==Synchronization==
+
;Synchronization
 +
:definition
  
* USM Add more text
+
== Component mappings in HTTP Balancer ==
* 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'''
 
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'''
Line 60: Line 57:
  
 
[[Image:AppSuite_Balancing.png|frameless|alt=AppSuite_Balancing|800px]]
 
[[Image:AppSuite_Balancing.png|frameless|alt=AppSuite_Balancing|800px]]
 +
 +
<noinclude>
 +
----
 +
===Dia files used to generate the images for this template===
 +
[[File:dia_files.zip]]
 +
</noinclude>

Latest revision as of 09:39, 5 July 2017

System Design

High Level System Design

AppSuite_High_Level

The overview shows that our OX AppSuite system will consist 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 that handles the incoming requests
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.

Middleware_Subparts

Groupware
definiton
Documentconversion
definition
Synchronization
definition

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

AppSuite_Balancing



Dia files used to generate the images for this template

File:Dia files.zip