Page History
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 clients
...
- and
- Automatic distribution of connecting clients over the available Servoy Application Servers, using Load Balancing functionality.
| Note | ||
|---|---|---|
| ||
When multiple Servoy Application |
...
Servers are used to host the same set of solutions to the same group of users, sharing the same set of databases, Servoy Cluster can be put to use. Using Servoy Cluster all clustered |
...
Servoy Application |
...
Servers become one virtual Servoy Application Server. For more information see Clustering Servers |
| Tip |
|---|
There are multiple ways to setup Load Balancing and the single point of entry, for example:
- Custom Balancing inside Tomcat
- Using HTTP servers
...
- that support (or have modules for) AJP1.3
...
- , like Apache HTTP Server or IIS
This chapter describes the process of setting up and using Apache HTTP Server
...
. This manual doesn't replace the documentation of the Apache HTTP Server itself, as it details the bare minimum to install Apache HTTP Server and do the required configuration to make
...
it work with the Servoy Application Server instances.
| Note | 1 | http://httpd.apache.org/]?|||||
|---|---|---|---|---|---|---|
| [
| Read through the section when not planning to use
| ||||
This chapter also contains useful information when setting up Load Balancing using different tools than Apache HTTP Server, as it shows configuration changes needed for Servoy Application Servers to run in a similar setup. It is important that the chosen load balancer is configured to use sticky sessions. |
After setting up Apache HTTP Server to act as single point of entry for connecting clients and as Load Balancer, all starting connecting 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 continue to service the connectionclient.
Servoy Smart clients Clients will connect directly to the individual Servoy Application Servers Server 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):servoy.jnlpCodebaseOverride=http://thisServersHostnameAsSeenByClients:port
What you should also take into consideration when setting up a load-balanced cluster, is allowing smart-clients to connect directly to individual servers in the cluster. This means that all Servoy Application Servers should be accessible from the client side - and you might want to isolate the cluster so that connections to ports used by Terracotta (see tc-config.xml) are only allowed from within the cluster, even if connections from client machines on Servoy ports should be allowed to all Servoy Application Serversto which they have been directed by the HTTP Server.
Servoy Web Clients connections to run through the HTTP Server to the Servoy Application Server instance that services the client.
Overview
Content Tools
Activity