AppSuite:Grizzly - Revision history

Khgras: /* RedHat Enterprise Linux 7 */

2024-09-12T13:21:04Z

RedHat Enterprise Linux 7

@@ Line 170: / Line 170: @@
   $ yum update
   $ yum install open-xchange-grizzly
 <!-- === CentOS 6 ===

Khgras: /* Installation on OX App Suite */

2024-09-12T13:20:11Z

Installation on OX App Suite

@@ Line 107: / Line 107: @@
   $ yum update
   $ yum install open-xchange-grizzly -->
 === RedHat Enterprise Linux 7 ===

Khgras: /* Installation on OX App Suite */

2024-09-12T13:18:52Z

Installation on OX App Suite

← Older revision		Revision as of 13:18, 12 September 2024
Line 16:		Line 16:
	== Installation on OX App Suite ==		== Installation on OX App Suite ==

	=== Debian GNU/Linux 7.0 (valid until v7.8.2) ===		<!-- === Debian GNU/Linux 7.0 (valid until v7.8.2) ===

	Add the following entry to /etc/apt/sources.list.d/open-xchange.list if not already present:		Add the following entry to /etc/apt/sources.list.d/open-xchange.list if not already present:
Line 106:		Line 106:

	$ yum update		$ yum update
	$ yum install open-xchange-grizzly		$ yum install open-xchange-grizzly -->

	=== RedHat Enterprise Linux 7 ===		=== RedHat Enterprise Linux 7 ===
Line 138:		Line 138:
	$ yum install open-xchange-grizzly		$ yum install open-xchange-grizzly

	=== CentOS 6 ===		<!-- === CentOS 6 ===

	Start a console and create a software repository file if not already present:		Start a console and create a software repository file if not already present:
Line 166:		Line 166:

	$ yum update		$ yum update
	$ yum install open-xchange-grizzly		$ yum install open-xchange-grizzly -->

	=== CentOS 7 ===		=== CentOS 7 ===

Khgras at 06:05, 18 September 2019

2019-09-18T06:05:22Z

← Older revision		Revision as of 06:05, 18 September 2019
Line 218:		Line 218:
	{{Template:ApacheAppSuiteConf\|connector=http\|connectorConf=/etc/apache2/conf.d/proxy_http.conf\|apacheconf=/etc/apache2/sites-enabled/000-default\|docroot=/var/www/\|loadmodule=\|easProxyName=eas_oxcluster\|syncProxyName=oxcluster_sync}}		{{Template:ApacheAppSuiteConf\|connector=http\|connectorConf=/etc/apache2/conf.d/proxy_http.conf\|apacheconf=/etc/apache2/sites-enabled/000-default\|docroot=/var/www/\|loadmodule=\|easProxyName=eas_oxcluster\|syncProxyName=oxcluster_sync}}

	====~~Apache HTTPS termination setup~~====		====X-FORWARDED-PROTO Header====

	[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.		[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.

Khgras at 06:03, 18 September 2019

2019-09-18T06:03:17Z

← Older revision		Revision as of 06:03, 18 September 2019
Line 218:		Line 218:
	{{Template:ApacheAppSuiteConf\|connector=http\|connectorConf=/etc/apache2/conf.d/proxy_http.conf\|apacheconf=/etc/apache2/sites-enabled/000-default\|docroot=/var/www/\|loadmodule=\|easProxyName=eas_oxcluster\|syncProxyName=oxcluster_sync}}		{{Template:ApacheAppSuiteConf\|connector=http\|connectorConf=/etc/apache2/conf.d/proxy_http.conf\|apacheconf=/etc/apache2/sites-enabled/000-default\|docroot=/var/www/\|loadmodule=\|easProxyName=eas_oxcluster\|syncProxyName=oxcluster_sync}}

	====~~X-FORWARDED-PROTO Header~~====		====Apache HTTPS termination setup====

	[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.		[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.

Khgras: /* Installation on OX App Suite */

2016-11-29T12:09:32Z

Installation on OX App Suite

Show changes

Khgras at 12:05, 29 November 2016

2016-11-29T12:05:39Z

Show changes

Felix.Marx: /* Apache configuration */

2015-12-09T08:58:46Z

Apache configuration

← Older revision		Revision as of 08:58, 9 December 2015
Line 28:		Line 28:
	{{Template:ApacheOXModsDebian\|connector=http}}		{{Template:ApacheOXModsDebian\|connector=http}}

			If you are using Apache 2.4, you will also need to enable the mod_lbmethod_byrequests

			$ a2enmod lbmethod_byrequests

	If you used AJP before, you have to delete /etc/apache2/conf.d/proxy_ajp.conf.		If you used AJP before, you have to delete /etc/apache2/conf.d/proxy_ajp.conf.

Martin.schneider: /* US 68424070: Remove AJP because of discontinued support */

2014-11-18T08:08:31Z

US 68424070: Remove AJP because of discontinued support

← Older revision		Revision as of 08:08, 18 November 2014
Line 214:		Line 214:

	The remote IP is detected in the following way: All configured known proxies are removed from the list of IPs listed in the X-FORWARDED-FOR header, beginning frome the right side of the list. The rightmost leftover IP is then seen as our new remote address as it represents the first IP not known to us.		The remote IP is detected in the following way: All configured known proxies are removed from the list of IPs listed in the X-FORWARDED-FOR header, beginning frome the right side of the list. The rightmost leftover IP is then seen as our new remote address as it represents the first IP not known to us.

	~~==Make Grizzly speak AJP instead of HTTP==~~
	Grizzly normally acts as an HTTP server and demands that the balancing proxy in front of it communicates via HTTP. This behaviour can be changed to Grizzly accepting the Apache JServ Protocol by simply adjusting the Grizzly and Apache configurations and restarting both servers.

	~~===Grizzly.properties===~~

	~~Change this parameter from the value seen in [[#Grizzly configuration\|Grizzly configuration]] to:~~

	~~### Protocol~~
	~~################################################################################~~

	~~# Grizzly is able to communicate via AJP besides its default prototcol HTTP.~~
	~~# Do you want to use AJP instead of HTTP?~~
	~~# Default value: false~~
	~~com.openexchange.http.grizzly.hasAJPEnabled='''true'''~~

	~~===Apache configuration===~~

	~~Change the HTTP related parameters from the values seen in [[#Apache configuration\|Apache configuration]] to AJP. This involves the IfModule directive and the BalancerMember declarations.~~

	~~To make Apach communicate via AJP instead of HTTP you have to replace the proxy_http with the proxy_ajp module.~~

	~~<IfModule mod_proxy_'''ajp'''.c>~~
	~~ProxyRequests Off~~
	~~# When enabled, this option will pass the Host: line from the incoming request to the proxied host.~~
	~~ProxyPreserveHost On~~
	~~<Proxy balancer://oxcluster>~~
	~~Order deny,allow~~
	~~Allow from all~~
	~~# multiple server setups need to have the hostname inserted instead localhost~~
	~~BalancerMember '''ajp'''://localhost:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1~~
	~~# Enable and maybe add additional hosts running OX here~~
	~~# BalancerMember '''ajp'''://oxhost2:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2~~
	~~ProxySet stickysession=JSESSIONID\|jsessionid scolonpathdelim=On~~
	~~</Proxy>~~
	~~# Microsoft recommends a minimum timeout value of 15 minutes for eas connections~~
	~~<Proxy balancer://eas_oxcluster>~~
	~~Order deny,allow~~
	~~Allow from all~~
	~~# multiple server setups need to have the hostname inserted instead localhost~~
	~~BalancerMember '''ajp'''://localhost:8009 timeout=1800 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1~~
	~~# Enable and maybe add additional hosts running OX here~~
	~~# BalancerMember '''ajp'''://oxhost2:8009 timeout=1800 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2~~
	~~ProxySet stickysession=JSESSIONID\|jsessionid scolonpathdelim=On~~
	~~</Proxy>~~

	~~$ a2dismod proxy_http && a2enmod proxy_ajp~~

	~~===Restart the servers===~~

	~~$ /etc/init.d/open-xchange restart~~
	~~$ /etc/init.d/apache2 restart~~

	=Servlet Filters=		=Servlet Filters=

Martin.schneider: /* US 68424070: Remove AJP because of discontinued support */

2014-11-18T08:07:54Z

US 68424070: Remove AJP because of discontinued support

← Older revision		Revision as of 08:07, 18 November 2014
Line 18:		Line 18:
	=Cluster setup=		=Cluster setup=
	[[File:GrizzlOXClusterSetup.png\|left\|alt=The default cluster setup.]]		[[File:GrizzlOXClusterSetup.png\|left\|alt=The default cluster setup.]]
	This picture shows our default cluster setup. It consists of a proxying balancer (in our case Apache) and a cluster of multiple OX App Suite backends. The balancer receives HTTP and/or HTTPS requests. It then decides which requests should be handled by itself and which should be forwarded, so they can be handled by one of the OX App Suite backends. That's where the ~~AJP or~~ HTTP connector is used.		This picture shows our default cluster setup. It consists of a proxying balancer (in our case Apache) and a cluster of multiple OX App Suite backends. The balancer receives HTTP and/or HTTPS requests. It then decides which requests should be handled by itself and which should be forwarded, so they can be handled by one of the OX App Suite backends. That's where the HTTP connector is used.
	<div style="clear: both"></div>		<div style="clear: both"></div>

Line 54:		Line 54:

	====/opt/open-xchange/etc/server.properties====		====/opt/open-xchange/etc/server.properties====
	This extract of the server.properties shows the properties that can be applied to the grizzly ~~and ajp~~ backend.		This extract of the server.properties shows the properties that can be applied to the grizzly backend.
	<pre>		<pre>
	...		...
Line 61:		Line 61:
	DefaultEncoding=UTF-8		DefaultEncoding=UTF-8
	...		...
	# The host for the connector's ~~(ajp,~~ http) network listener. Set to "*" if you		# The host for the connector's http network listener. Set to "*" if you
	# want to listen on all available interfaces.		# want to listen on all available interfaces.
	#Default value: 127.0.0.1, bind to localhost only.		#Default value: 127.0.0.1, bind to localhost only.
	com.openexchange.connector.networkListenerHost=*		com.openexchange.connector.networkListenerHost=*

	# The default port for the connector's ~~(ajp,~~ http) network listener.		# The default port for the connector's http network listener.
	# Default value: 8009.		# Default value: 8009.
	com.openexchange.connector.networkListenerPort=8009		com.openexchange.connector.networkListenerPort=8009

	# Specify the max. number of allowed request parameters for the connector ~~(ajp,~~ http)		# Specify the max. number of allowed request parameters for the connector http
	# Default value: 30		# Default value: 30
	com.openexchange.connector.maxRequestParameters: 30		com.openexchange.connector.maxRequestParameters: 30
Line 104:		Line 104:

	====/opt/open-xchange/etc/grizzly.properties====		====/opt/open-xchange/etc/grizzly.properties====
	Next we'll look at the parts of the grizzly.properties that ~~configure only~~ the grizzly ~~backend but not the ajp~~ backend.		Next we'll look at the parts of the grizzly.properties that configures the grizzly backend.
	<pre>		<pre>
	# Grizzly.properties		# Grizzly.properties
Line 136:		Line 136:
	# Do you want to enable grizzly monitoring via JMX? Default value: true.		# Do you want to enable grizzly monitoring via JMX? Default value: true.
	com.openexchange.http.grizzly.hasJMXEnabled=true		com.openexchange.http.grizzly.hasJMXEnabled=true


	~~### Protocol~~
	~~################################################################################~~

	~~# Grizzly is able to communicate via AJP besides its default prototcol HTTP.~~
	~~# Do you want to use AJP instead of HTTP?~~
	~~# Default value: false~~
	~~com.openexchange.http.grizzly.hasAJPEnabled=false~~
	</pre>		</pre>

	====/opt/open-xchange/etc/requestwatcher.properties====		====/opt/open-xchange/etc/requestwatcher.properties====
	And finally the properties to configure the requestwatchers of the http ~~and ajp backends~~		And finally the properties to configure the requestwatchers of the http backend
	<pre>		<pre>
	# Requestwatcher.properties		# Requestwatcher.properties
Line 171:		Line 162:
	# Default value: 60000.		# Default value: 60000.
	com.openexchange.requestwatcher.maxRequestAge: 60000		com.openexchange.requestwatcher.maxRequestAge: 60000

	~~# Permission to stop & re-init system (works only for the ajp connector)~~
	~~com.openexchange.requestwatcher.restartPermission: false~~
	</pre>		</pre>