Load Balancing Feature

Pre-requisites

Using this feature, you will be able to manage a load balanced environment.

It means that the load of all your users will be distributed between your servers. The workload will be shared between all the servers of your farm.

Load Balancing enables to use an unlimited number of servers with load balancing. This very powerful and advanced capability is to be used when a large number of users/servers has to be deployed.

Screenshot 1

Usually we recommend using one server for 50 concurrent users. For standard commercial application written in VB, C, C++, Delphi or Uniface you can go up to 100 concurrent users especially if you decide to use XP 64 bits which, according to our experience, tops most operating systems delivered by Microsoft. XP or Windows 7 are much more stable operating systems. For W7, we recommend to use the 64 bits version.

Generated Clients and Web Access

There are two ways to connect to a Load Balanced cluster:

Please note that the Gateway Portal is only enabled in Terminal Service Plus Enterprise edition.

This page describes how to use the Load Balancing Manager with a Gateway Portal.

Gateway and Application Server Roles

The Load Balancing Manager tool must be used on the server having the Gateway role.
Using it on an other server of the load balanced cluster will have no effect on the load balancing.

Load Balancing Main Window

The main window displays a lot of data and allows you to configure your Gateway Portal Load Balancing.

Screenshot 2

It lists all the servers in your Load Balanced server farm, and allows you to add a new server (by clicking on the "Add a new Server" button) or displays an existing server (by clicking on it). It also allows you to enable, disable and configure the Load Balancing (more on this below).

Click on the buttons in the picture below to access the corresponding information:

Load Balancing

Enabling/Disabling Load Balancing

On top of the Gateway Portal Load Balancing window, you will see a big button:

Here is the button when the Load Balancing is Disabled. A click on it will activate it, and disable the Users/Servers Assignment.

Screenshot 3

Here is the button when the Load Balancing is Enabled. A click on it will deactivate it, and enable the Users/Servers Assignment.

Screenshot 4

How does Load Balancing choose a server?

When Load Balancing is enabled, the user will be sent to the less loaded server at the time of his connection.

Configuring the Computation of Servers' Loads

To determinate which is the less loaded server, the load of every server is computed using a weighted average between several performance indicators:

You can modify the weight (importance) of these indicators by using the following sliders:

Screenshot 5

Using these sliders, you will be able to fine-tune the Load Balancing, and to optimize it to your own needs. For instance if your users launch a business application with big memory requirements, it might be a good idea to increase the impact of the RAM in the load computation using the "Memory" slider.

You can also reset these values by clicking on the "Back to Default Settings" button.

How is Server's Load computed?

The load of each server is computed when needed in order to decide on which server the user must be sent.

For this computation, we use a weighted average between 4 hardware metrics.

The 4 sliders allow you to give more (or less) weight on each of these metrics, which are:

For example, if you put the "Memory" slider on its right side and all the other sliders on their left side, the load of each servers will be computed using almost only the percentage of used memory - and your users will be sent to the server having the most available memory.

Moreover, the load of a given server depends on the ratio [ used resources / total resources ] ; so if a server A is twice as powerful as a server B, twice more users should be sent to server A than to server B (all other things being equals).

Adding a new Server

To add a new server, simply click on the "Add a new Server" button. The following window will be displayed:

Screenshot 6

The "Display Name" is the title that will be shown to your users on the Web Access HTML page. It is supposed to be more user-friendly than a technical value (such as an IP), for instance "US Server" or "Blue Zone".

When using the Gateway Portal Load Balancing, the "RDP Port" will not be used. It is only used when connecting using a Generated Client. We advise you to keep the default setting ("Same as web").

Editing an existing Server

To modify an existing server, simply click on the "Edit" button of the server you want to update. The following window will be displayed:

Screenshot 7

The progress bar shows the current load of the server. It also confirms you that the server is well configured and can be contacted by the Gateway.

Load Balancing using a Connection Client

You are not using the Reverse Proxy role of the Gateway (default case)

This is the default case if you just installed Terminal Service Plus. In this case, if you want to generate a Connection Client to connect to a given Application server, then:

Screenshot 1

However, if you want to generate a Connection Client to connect to the less loaded server and use Load Balancing, then:

Screenshot 2

You are using the Reverse Proxy role of the Gateway ("/~~" in URL)

See this page.

Activating the Load Balancing for a Gateway Portal access

Activating Load Balancing is really easy. It only takes three steps:

Screenshot 1

Screenshot 2

Screenshot 3

Screenshot 4

Screenshot 5

Activating the sticky session feature

Regardless of your connection method, you will always be able to activate the sticky session feature by clicking on the right button of the Load balancing window:

Screenshot 6

It will allow you to reconnect to a disconnected session instead of opening a new session on a different server.



Discover all TSplus features »