Configuring High Availability Environment

After you plan for a high availability environment, you must set up and configure the environment. The following section contains tasks to complete when you are configuring a high availability environment:

Swagger based configurations

For a High availability environment, all the operating Control Center Director nodes must be synchronized. You must override the individual configurations set in application.properties of the Control Center Director nodes and set common properties for all the nodes. Refer Using RESTful APIs for Web Configurations to configure Control Center Director nodes for high availability environment.
Note: Following settings can be done from the Menu settings:
  • Email
  • External Authentication

Database Configuration

Database: Refer to Before you set up the database section for configuring your database.

Package Configuration

Package: Refer to Configuring Control Center Director for package configurations. A common package directory location can be configured for all the Control Center Director nodes using APIs, refer Using RESTful APIs for Web Configurations.

Load Balancer Configuration Sample : Nginx server

Following are the recommended configurations for Load Balancer Nginx server:
  • Add the servers of the connected Control Center Director nodes in the Load Balancer configuration file in the following format: 
    <IP_address/host>:<port>
  • While using a load balancer, the correct IP address of the end user is not shared with Control Center Director nodes, to avoid incorrect reporting information add the following configuration in Load Balancer configuration file:
    1. Set following proxy mandatory headers in Load Balancer configuration file.
      Example: 
      proxy_set_header X-SSL-CERT  $ssl_client_escaped_cert;      
proxy_set_header Host $http_host; 
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      Note: proxy_set_header X-Real-IP $remote_addr; can also be set as an optional header.
    2. Set the following mandatory parameter as explained in Using RESTful APIs for Web Configurations. 
      server.use-forwarded-for-with-proxy=true