Internal load balancer is used to balance and distribute the requests sent by Adeptia Connect GUI Portal on all the nodes of a cluster. You need to configure the following:
- IP address of all the nodes of a cluster beneath the load balancer.
- Sticky session: For internal load balancer, enable cookie stickiness and use application generated cookie 'JSESSIONID'.
- Deploy SSL: Steps to configure SSL varies from load balancer to load balancer.
- Set connection idle timeout to 180 seconds.
Verifying Internal Load Balancer Configuration
After the load balancer is configured, you need to verify whether load balancer is configured successfully or not. To verify:
Login to Connect Server using load balancer IP Address in the URL format:
<protocol_name>://<IP_address>:<port_number>...
- .
...
Configuring Internal Load Balancer for Health Checkup
...
- Login to Amazon Web Services.
- Under the 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 /adeptia/healthcheck/kernel in the Ping Path text box.
Info The Ping Protocol must be HTTP or HTTPS.
After you have configured Internal Load Balancer on Connect Server, you need to configure HTTP/HTTPS URL in the app.adeptia.host.url property:
- Go to .../ConnectPortalInstallFolder>/resources_config.
- Open application.properties file in the Text Editor.
- Set the IP address or domain name of Internal Load Balancer using http/https protocol to access Connect Server in the app.adeptia.host.url.
- Save the file.
- Restart Connect Portal.
Verifying Internal Load Balancer Configuration
After the load balancer is configured, you need to verify whether load balancer is configured successfully or not. To verify:
Login to Connect Server using load balancer IP Address in the URL format:
<protocol_name>://<IP_address>:<port_number>For example, http://192.168.1.1:80