To make a Servoy Application Server work properly with the Apache HTTP Server and Load balancing, the following modifications to the configuration of the Servoy Application Server are required:

AJP 1.3 connector

• Open <servoy>/application_server/server/conf/server.xml and make the following adjustments:
  • Change line "<Engine name="Catalina" defaultHost="localhost">" into "<Engine jvmRoute="servoy1" name="Catalina" defaultHost="localhost">". The value of the jvmRoute atrribute needs to be differetn for each Servoy Application server and match with the list of workers registered with the Apache HTTP server (see Apache HTTP Server configuration)
  • Add the following connector before the already declared one in both installations:

    <Connector port="8009" enableLookups="false" maxThreads="500" connectionTimeout="60000" redirectPort="8443" useBodyEncodingForURI="true" protocol="AJP/1.3"/>

When you start the 2 Servoy Application Servers and the Apache HTTP server and you access the Apache HTTP server you will be automatically using one of the two Servoy Servers in a weighted round-robin load balancing with sticky sessions manner.

jnlpCodebaseOverride
Load-balancing of Smart Clients is done by serving the JNLP file from the different Servoy Application Servers when the Apache HTTP front-end is accessed. The Apache HTTP Server serves the JNLP file to the requesting client and using the JNLP, the requesting client will connect directly to the Servoy Application Server that supplied the JNLP.

This means that each Servoy Application Server needs to be accessible to connecting client. When clients do not have direct access to the Servoy Application Server, the external hostname/IP Address needs of the Servoy Application Server needs to be registered as jnlpCodebaseOverride value. For more information, see Network Settings#servoy.jnlpCodebaseOverride.