The

...

entire load balancing chapter is stuff under construction

When multiple Servoy Application Servers are used to host the same set of solutions to the same group of users, a HTTP Server can be added to the infrastructure to:

• provide clients with a single point of entry, hiding the separate Servoy Application Servers from view for Clientsclients.
• Using a Load Balancer in front of the cluster, allows allow for the automatic distribution of connecting Clients clients over the available Servoy Application Servers, using Load Balancing functionality.

There are multiple ways to setup Load Balancing and the single point of entry, for example:

...

In this manual the process of setting up and using Apache HTTP Server is described. This manual doesn't replace the documentation of the Apache HTTP Server itself, as it gives details the bare minimum to install Apache HTTP Server and do the required configuration to make the Apache HTTP Server work with the Servoy Application Server Instancesinstances.Using Apache HTTP server as a front-end to load-balance a cluster of Servoy Application Servers is optional. You should be able to do this in other ways, including custom balancing inside a Tomcat instance application or using other HTTP servers such as IIS that support (or have modules for) AJP1.3. Read through the section even if you do not plan

...

After setting up Apache HTTP Server to act as single point of entry for connecting clients and as Load Balancer, all starting clients will connect to the Apache HTTP Server's url. The Apache HTTP Server will dispatch the request to one of the Servoy Application Servers which will then handle the connection.

Smart clients will connect directly to the individual Servoy Application Servers in the cluster. The load-balancing is done by serving the JNLP file from different servers when the Apache HTTP front-end is accessed. Add to each of the Servoy Application Server's "servoy.properties" files the following line (needed for Smart Client load balancing):

...