How To Implement a Keep-Alive Heartbeat with LoadBalancer to an ODI Agent (Doc ID 2273184.1)

Last updated on DECEMBER 19, 2023

Applies to:

Goal

The purpose of the Keep-Alive setting (as it is in Microsoft IIS) is to keep the client/server connection open for multiple requests to boost performance. In order to send traffic in a round robin fashion, a load balancer continues to make a request to a resource (for example, http://[hostname]:[port]/keepalive.html) every second. If the response is received, the load balancer would know the HTTP instance is running and would keep diverting the traffic to it. However, if a request to the server failed with a time-out or 404 error, the load balancer would stop diverting any traffic to that particular URL and will send the requests to the next server. When the requests to the Keep-Alive file on the failed server become successful again, the load balancer would automatically start sending the traffic again.

Without a HTTP Web Host, can a hardware load balancer be configured with the cluster Oracle Data Integrator J2EE Agent to replicate the Keep-Alive behavior in this fashion?

Solution