In this article
Octopus has the ability to take your servers in and out of the load balanced pool during the installation of features that will drop user sessions.
There are no configuration options for this Load Balancing management functionality and it must be implemented exactly as described below.
The load balancing management functionality has been implemented for the following features:
- Reportal
- Authoring
- Web Services
Configuring Automated Load Balancing
This functionality can only be configured in one specific manner.
Your load balancer will need to be configured to examine an isalive.htm file in the default Webroot of the Forsta Plus application on the server.
During the configuration / installation of the three features listed, the Octopus will:
- Look up the IIS webroot on that server.
- Rename isalive.htm file - your load balancer will see that this file doesn't exist, hence taking it out of the load balanced pool.
- Install the feature.
- Rename the isalive.htm file back to the correct name - your load balancer will see this file exists and will add it back to the load balanced pool.