How to configure an Apache load balancer - Revision history

Blucecio at 10:12, 27 June 2019

2019-06-27T10:12:55Z

← Older revision		Revision as of 10:12, 27 June 2019
Line 3:		Line 3:
	Sticky session will ensure that one visitor generally will be handled by the same server over the lifetime of a session. This is a requirement for the proper functioning of LogicalDOC in this mode.		Sticky session will ensure that one visitor generally will be handled by the same server over the lifetime of a session. This is a requirement for the proper functioning of LogicalDOC in this mode.

	Actually there are two configuration options for Apache: proxy via mod_proxy and proxy via mod_proxy_ajp.		Actually there are two configuration options for Apache: proxy via [https://httpd.apache.org/docs/2.4/mod/mod_proxy.html mod_proxy] and proxy via [https://httpd.apache.org/docs/2.4/mod/mod_proxy_ajp.html mod_proxy_ajp].
	The main difference is that mod_proxy sends http communications while with mod_proxy_ajp the messages exchanged between Apache and Tomcat take place in binary format.		The main difference is that mod_proxy sends http communications while with mod_proxy_ajp the messages exchanged between Apache and Tomcat take place in binary format.

Blucecio: /* Configuration Guides */

2019-06-27T10:11:24Z

Configuration Guides

← Older revision		Revision as of 10:11, 27 June 2019
Line 8:		Line 8:
	== Configuration Guides ==		== Configuration Guides ==
	Please choose one configuration. Trying to configure for both mod_proxy and mod_jk will only lead to confusion and tears.		Please choose one configuration. Trying to configure for both mod_proxy and mod_jk will only lead to confusion and tears.
	* Configure Apache load balancer with mod_proxy		* [[Configure Apache load balancer with mod_proxy]]
	* [[Configure Apache load balancer with mod_proxy_ajp]]		* [[Configure Apache load balancer with mod_proxy_ajp]]

Blucecio at 10:10, 27 June 2019

2019-06-27T10:10:54Z

@@ Line 3: / Line 3: @@
 Sticky session will ensure that one visitor generally will be handled by the same server over the lifetime of a session. This is a requirement for the proper functioning of LogicalDOC in this mode.
-== Server setup ==
+== Configuration Guides ==
+Please choose one configuration. Trying to configure for both mod_proxy and mod_jk will only lead to confusion and tears.
-The layout may look something like this (we will refer to these names through the rest of the guide).
+* Configure Apache load balancer with mod_proxy
+* [[Configure Apache load balancer with mod_proxy_ajp]]

Blucecio: /* Configure Tomcat Public1 / Public2 */

2019-06-27T09:44:26Z

Configure Tomcat Public1 / Public2

← Older revision		Revision as of 09:44, 27 June 2019
Line 90:		Line 90:
	</source>		</source>

	Note: on the ~~logicaldoc~~ node Tomcat config you should change publicXY with public1 or public2 depending on the node		Note: on the LogicalDOC node Tomcat's config you should change publicXY with public1 or public2 depending on the node

	== Done ==		== Done ==

Blucecio: /* Configure Tomcat Public1 / Public2 */

2019-06-27T09:43:57Z

Configure Tomcat Public1 / Public2

← Older revision		Revision as of 09:43, 27 June 2019
Line 89:		Line 89:
	<Engine name="Catalina" defaultHost="localhost" jvmRoute="publicXY">		<Engine name="Catalina" defaultHost="localhost" jvmRoute="publicXY">
	</source>		</source>

			Note: on the logicaldoc node Tomcat config you should change publicXY with public1 or public2 depending on the node

	== Done ==		== Done ==

Blucecio: /* Public1 / Public2 */

2019-06-27T09:42:52Z

Public1 / Public2

← Older revision		Revision as of 09:42, 27 June 2019
Line 72:		Line 72:
	</source>		</source>

	== Public1 / Public2 ==		== Configure Tomcat Public1 / Public2 ==

	Let's look at the relevant configuration here to set up the load-balancer. Most likely you will also have an Apache web-server installed on this machines, as for accessing the author instance if located on one of this servers with a nice URL. Here we suggest to use a single Tomcat application server for hosting one public instance. Make sure the AJP Port is set correctly to what you have defined in the virtual host configuration of the load-balancer (8009 as the default value used here).		Let's look at the relevant configuration here to set up the load-balancer. Most likely you will also have an Apache web-server installed on this machines, as for accessing the author instance if located on one of this servers with a nice URL. Here we suggest to use a single Tomcat application server for hosting one public instance. Make sure the AJP Port is set correctly to what you have defined in the virtual host configuration of the load-balancer (8009 as the default value used here).

Blucecio: /* Load-balancer */

2019-06-27T09:42:31Z

Load-balancer

← Older revision		Revision as of 09:42, 27 June 2019
Line 10:		Line 10:
	[[File:Apache-AJP-load-balancer.png\|options\|caption]]		[[File:Apache-AJP-load-balancer.png\|options\|caption]]

	== Load-balancer ==		== Define Apache Load-balancer ==

	This server will handle all HTTP requests from site visitors. As you might see, this means even though you run a load balanced system, using only a single load balancer means you still have a SPOF (single point of failure). It is also possible to configure an environment where yet another server will act as the fail-over load-balancer if the first one fails, but this is outside the scope of this guide.		This server will handle all HTTP requests from site visitors. As you might see, this means even though you run a load balanced system, using only a single load balancer means you still have a SPOF (single point of failure). It is also possible to configure an environment where yet another server will act as the fail-over load-balancer if the first one fails, but this is outside the scope of this guide.

Blucecio: /* Load-balancer */

2019-06-27T09:20:03Z

Load-balancer

← Older revision		Revision as of 09:20, 27 June 2019
Line 14:		Line 14:
	This server will handle all HTTP requests from site visitors. As you might see, this means even though you run a load balanced system, using only a single load balancer means you still have a SPOF (single point of failure). It is also possible to configure an environment where yet another server will act as the fail-over load-balancer if the first one fails, but this is outside the scope of this guide.		This server will handle all HTTP requests from site visitors. As you might see, this means even though you run a load balanced system, using only a single load balancer means you still have a SPOF (single point of failure). It is also possible to configure an environment where yet another server will act as the fail-over load-balancer if the first one fails, but this is outside the scope of this guide.

	To set up our load-balancer, we use the Apache web-server and its modules mod_proxy, mod_proxy_ajp and mod_proxy_balancer. These are part of most of the Apache web-server distributions.		To set up our load-balancer, we use the Apache web-server and its modules [https://httpd.apache.org/docs/2.4/mod/mod_proxy.html mod_proxy], [https://httpd.apache.org/docs/2.4/mod/mod_proxy_ajp.html mod_proxy_ajp] and [https://httpd.apache.org/docs/2.4/mod/mod_proxy_balancer.html mod_proxy_balancer]. These are part of most of the Apache web-server distributions.

	First, create a virtual host handling the requests for your domain: www.yourcompany.com		First, create a virtual host handling the requests for your domain: www.yourcompany.com

Blucecio: /* Load-balancer */

2019-06-27T09:05:48Z

Load-balancer

← Older revision		Revision as of 09:05, 27 June 2019
Line 21:		Line 21:
	<VirtualHost *:80>		<VirtualHost *:80>
	ServerName www.yourcompany.com		ServerName www.yourcompany.com
	ServerAlias yourcompany.com		ServerAlias yourcompany.com

	DocumentRoot /Library/WebServer/Documents		DocumentRoot /Library/WebServer/Documents

Blucecio: Blucecio moved page How to configure an apache load balancer to How to configure an Apache load balancer: apache is a name

2019-06-27T09:03:41Z

Blucecio moved page How to configure an apache load balancer to How to configure an Apache load balancer: apache is a name

← Older revision	Revision as of 09:03, 27 June 2019
(No difference)