Template:OX HE Tutorial Design - Revision history

Khgras: /* Middleware Details */

2017-07-05T09:39:31Z

Middleware Details

← Older revision		Revision as of 09:39, 5 July 2017
Line 26:		Line 26:
	== Middleware Details ==		== Middleware Details ==

	The middleware itself consists of many modules whose functionality is either exposed via the [~~HTTP_API\|~~https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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]]

Khgras: /* Middleware Details */

2017-07-05T09:39:09Z

Middleware Details

← Older revision		Revision as of 09:39, 5 July 2017
Line 26:		Line 26:
	== Middleware Details ==		== Middleware Details ==

	The middleware itself consists of many modules whose functionality is either exposed via the [HTTP_API \| https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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 [HTTP_API\|https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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]]

Khgras: /* Middleware Details */

2017-07-05T09:39:01Z

Middleware Details

← Older revision		Revision as of 09:39, 5 July 2017
Line 26:		Line 26:
	== Middleware Details ==		== Middleware Details ==

	The middleware itself consists of many modules whose functionality is either exposed via the [HTTP_API https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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 [HTTP_API \| https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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]]

Khgras: /* Middleware Details */

2017-07-05T09:38:24Z

Middleware Details

← Older revision		Revision as of 09:38, 5 July 2017
Line 26:		Line 26:
	== 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 [HTTP_API https://documentation.open-xchange.com/components/middleware/http/latest/index.html] 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]]

Marens at 13:52, 13 March 2015

2015-03-13T13:52:56Z

← Older revision		Revision as of 13:52, 13 March 2015
Line 60:		Line 60:
	<noinclude>		<noinclude>
	----		----
			===Dia files used to generate the images for this template===
	[[File:dia_files.zip]]		[[File:dia_files.zip]]
	</noinclude>		</noinclude>

Marens at 13:51, 13 March 2015

2015-03-13T13:51:00Z

← Older revision		Revision as of 13:51, 13 March 2015
Line 57:		Line 57:

	[[Image:AppSuite_Balancing.png\|frameless\|alt=AppSuite_Balancing\|800px]]		[[Image:AppSuite_Balancing.png\|frameless\|alt=AppSuite_Balancing\|800px]]

			<noinclude>
			----
			[[File:dia_files.zip]]
			</noinclude>

Marens at 13:43, 13 March 2015

2015-03-13T13:43:03Z

← Older revision		Revision as of 13:43, 13 March 2015
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 [[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.
Line 29:		Line 30:
	[[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'''

Marens at 11:05, 13 March 2015

2015-03-13T11:05:40Z

← Older revision		Revision as of 11:05, 13 March 2015
Line 1:		Line 1:
	= High Level System Design =		= High Level System Design =

	[[Image:AppSuite_High_Level.png\|frameless\|alt=AppSuite_High_Level\|~~1024px~~]]		[[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 the OX AppSuite consists of several components:
Line 25:		Line 25:
	= Middleware Details =		= Middleware Details =

	[[~~Image:Middleware_Subparts.png\|frameless\|alt=Middleware_Subparts\|896px~~]]		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 exposed via the~~ [[~~HTTP_API~~]]~~. We have identified three blocks that should be grouped together and considered as logical components when planning the hardware layout of your infrastructure.~~		[[Image:Middleware_Subparts.png\|frameless\|alt=Middleware_Subparts\|800px]]

	==Groupware==		==Groupware==
Line 59:		Line 59:
	: The members of this balancer container are responsible for handling only '''USM''', '''EAS''' and '''DAV''' synchronization requests		: The members of this balancer container are responsible for handling only '''USM''', '''EAS''' and '''DAV''' synchronization requests

	[[Image:AppSuite_Balancing.png\|frameless\|alt=AppSuite_Balancing\|~~1024px~~]]		[[Image:AppSuite_Balancing.png\|frameless\|alt=AppSuite_Balancing\|800px]]

Marens at 09:44, 13 March 2015

2015-03-13T09:44:04Z

← Older revision		Revision as of 09:44, 13 March 2015
Line 58:		Line 58:
	;<nowiki>Proxy balancer://oxcluster_sync</nowiki>		;<nowiki>Proxy balancer://oxcluster_sync</nowiki>
	: The members of this balancer container are responsible for handling only '''USM''', '''EAS''' and '''DAV''' synchronization requests		: The members of this balancer container are responsible for handling only '''USM''', '''EAS''' and '''DAV''' synchronization requests

			[[Image:AppSuite_Balancing.png\|frameless\|alt=AppSuite_Balancing\|1024px]]

Marens at 17:26, 12 March 2015

2015-03-12T17:26:35Z

← Older revision		Revision as of 17:26, 12 March 2015
Line 41:		Line 41:
	* CALDAV Add more text		* CALDAV Add more text
	* CARDDAV 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.

			;<nowiki>Proxy balancer://oxcluster</nowiki>
			: The members of this balancer container are responsible for handling general groupware requests

			;<nowiki>Proxy balancer://oxcluster_docs</nowiki>
			: The members of this balancer container are responsible for handling document conversion and thumbnailing requests

			;<nowiki>Proxy balancer://oxcluster_sync</nowiki>
			: The members of this balancer container are responsible for handling only '''USM''', '''EAS''' and '''DAV''' synchronization requests