We are using three Portal servers (EP 7.0) and load is distributed between these servers by a load balancer.
Load balancer does a basic check - Portal server is listening on TCP port.
If one of the servers is really down (eg. after a stopsap) the load balancer does not send any request to that server. That was the intention.
During startup of a server, it starts listening on the port and load balancer sends requests to it. As 20 minutes startup phase is not completed, users get a message 503- unavailable. This means we do not really have redundancy.
The load balancer can also check for URL, but expects to get a 200 ok response.
We tried that with page http://<server>:<port>/index.html. This was no improvement, as this page is also displayed in a very early phase of the startup.
If we use http://<server>:<port>/irj/portal load balancer gets authentication requests and no 200 ok and does not send any request to servers, even if they are up and running.
Question :
What URL can be used, which works like index.html (send 200 ok), but only after startup is complete ?