...
Load balancing for the CXO Software Web Application
CXO Software web application can be installed on several servers. There should be a load balancer provided by the destination infrastructure that passes the HTTP(s) requests from the clients through to one of the available CXO Software servers. The only requirement to the load balancer is that it must implement "sticky sessions" scenario: all subsequent requests from a certain client must end up to the same CXO Software server as the first request from that client. The most typical implementation of this scenario is "Cookie-based Persistence". In this scenario the load balancer appends a cookie to the first client's request that cookie is used later on to identify the server all the subsequent requests should be forwarded to.
...
- Create services in the Configurator for all of the installed components on every server
- Disable CXO Software Agent Service on all the machines except one
- Create and Configure Backplane database
Expand title Configure a network path for the export files location 
There should be specified a network path that is accessible from all the CXO-Cockpit servers. All the service accounts that CXO-Cockpit components are running under mush be authorized to change files at the specified location
Configure load balancing across all the CXO Software web servers and enable sticky sessions on the load balancer
Expand title Specify load balancer url as CXO-Cockpit Dashboard Url 
There should be specified a load-balanced url
...