This section is applicable if you are deploying Adeptia Connect UI on multiples nodes (clustering mode).
To distribute the load and manage incoming users' requests, you must use an external load balancer for Tomcat. For this, you need to configure the IP address of all the instances of Tomcat beneath the load balancer.
You need to configure the following:
- IP address of all the instances of Tomcat beneath the load balancer.
- Sticky session: For load balancer, enable Load Balancer generated cookies stickiness.
- Deploy SSL: Steps to configure SSL varies from load balancer to load balancer.
- Set connection idle timeout to 180 seconds.
Configuring External Load Balancer for Health Checkup
Consider a clustering environment working with two nodes where the Load Balancer sends request(s) to the Adeptia Connect UI.
To setup the health checkup, you need to configure the Load Balancer for all nodes to process the request. To do so, configure your Load Balancer Health Checkup and type the URL in the below format:
<protocol_name>://<ip_address>:<port_number>/index.html
where,
<protocol_name> is the name of the protocol you are using. It could be HTTP or HTTPS.
<ip_address> is the IP address of the WebRunner.
<port_number> is the port number at which WebRunner is running. By default, it is 8080 for HTTP and 8443 for HTTPS.
For example, https://192.168.1.14:8443/index.html
The configuration settings of Load Balancer may vary depending upon the Load Balancer you are using.
Following are the steps to configure Load Balancer on Amazon Web Services:
- Login to Amazon Web Services.
- Under Compute group, click EC2.
- Under Resources, click Load Balancers.
- Select the load balancer to configure the health check.
- Under Health Check tab, click Edit Health Check.
Type /index.html in the Ping Path text box.
The Ping Protocol must be HTTP or HTTPS.
See also