Child pages
  • Load Balancing Servers
Skip to end of metadata
Go to start of metadata

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.

Clustering of Servoy Application Servers using [Servoy Cluster]

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

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.

Not using Apache HTTP Server?

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 HTTP Server to act as single point of entry for connecting clients and as Load Balancer, all connecting clients will connect to the HTTP Server's url. The HTTP Server will dispatch the request to one of the Servoy Application Servers which will then continue to service the client.

Servoy Smart Clients will connect directly to the individual Servoy Application Server in the cluster to 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.

  • No labels