At a certain amount of traffic, or a certain need on availability, you might consider using multiple public instances. Most likely those instances are on different servers as well. This guide will illustrate how to setup a load-balanced system using three different servers, where one acts as the load-balancer (using apache for splitting the requests) and the two remaining servers host the Magnolia public instances.
Sticky session will ensure that one visitor generally will be handled by the same server over the lifetime of a session. If you want to access the public instances' adminCentral (or have public user registration or any other User Generated Content module installed) you want to use sticky sessions.
The layout may look something like this (we will refer to these names through the rest of the 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.
First, create a virtual host handling the requests for your domain: www.yourcompany.com
We exclude the path
balancer-manager from the proxy, since we can manage our balanced members with the balancer-manager tool. The balancer-manager is part of the mod_proxy_balancer module. To secure its path, create the folder and secure it. The setup may slightly differ on your server, so use the following as a starting guide.
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 application server (Tomcat or JBoss) 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).
If you want to change the AJP Port of your application server, this can be done here.
JBOSS_HOME/server/default/deploy/jbossweb-tomcat55.sar/server.xml (depending on your JBoss version)
Now in the same file as we configure the AJP Port
server.xml we need to configure the jvmRoute for sticky sessions working correctly. Use the name defined in the virtual host configuration on load-balancer, the route value here separately for the two servers.
That's basically it. Now you can set your DNS entry of www.yourcompany.com to your Load-Balancer's IP address and enjoy the comfort and security of a redundant Magnolia instalation. If one of the public Magnolia servers is failing, mod_proxy on your load-balancer will automatically detect this and stop serving requests to that server.
You can test this by stopping tomcat on one of the machines. Your load-balancer Apache webserver error_log will show something like
Also you could access the balancer-manager with http://www.yourcompany.com/balancer-manager to manually disable a worker. The balancer-manager also offers you an easy way to set different load factors for your servers.
Feedback? Use the comment features!