Page Comparison

...

1. Create services in the Configurator for all of the installed components on every server
2. Disable CXO-Cockpit Agent Service on all the machines except one
3. Create and Configure Backplane database

4. 
   

   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

   
   

5. Configure load balancing across all the CXO-Cockpit web servers and enable sticky sessions on the load balancer

6. 
   

   Expand
   title Specify load balancer url as CXO-Cockpit Dashboard Url
   There should be specified a load-balanced url

   
   

Load Balancer configuration requirements

1. "Sticky sessions" scenario must be cofigured: all subsequent requests from a certain client must end up to the same CXO-Cockpit server as the first request from that client. The most typical implementation of this scenario is "Cookie-based Persistence"
2. The requests to the CXO-Cockpit server should include the following haders:
   1. "X-Forwarded-Host" should contain the original host name used in the end-user request. This host name can only equal to the host name used in the CXO-Cockpit Dashboard URL (as configured in the Configurator), otherwise it will be ignored.
   2. "X-Forwarded-Proto" should contain the original protocol used in the end-user request. Note, that this header is not required if the same protocol (HTTPS) is used on load balancer and on the individual CXO-Cockpit servers.