Internal load balancer is used to balance and distribute the requests sent by Connect 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 load balancer generated cookie. Set the cookie expiration period to 0 second.
Deploy SSL: Steps to configure SSL varies from load balancer to load balancer.
Set connection idle timeout to 180 seconds.

Configuring Internal Load Balancer for Health Checkup

Consider a clustering environment working with two nodes where the Load Balancer sends request(s) to the WebRunner(s). In case, Kernel of any of the two nodes goes down, the Load Balancer keeps on sending the request to the WebRunner. This happens because Load Balancer does not interact with the Kernel resulting in the request failure from the node where Kernel is down.

One way to check the status of the Kernel and WebRunner in all the nodes is to set up the Health Check URL on the Load Balancer. The Load Balancer will check the URL at a particular interval of time and when any of the Kernel or WebRunner is down, it stops sending a request to that particular node.

To set up the health checkup, you need to configure the Load Balancer.

Configuring Load Balancer

You need to configure Load Balancer for all nodes to process the request. To do so, type the URL in the below format:

<protocol_name>://<ip_address>:<port_number>/adeptia/healthcheck/kernel

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.1:8443/adeptia/healthcheck/kernel

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 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.

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

Next Step

Configuring External Load Balancer

You may be interested in...

What's new

Best practices

Training guides

Frequently asked questions

Adeptia Connect APIs

Adeptia security report

Browser not supported