Server Health
You can configure the TIBCO Enterprise Message Service server to service HTTP GET requests for the current health of the server on a dedicated port.
This feature can be used to support the health check probes in Kubernetes. For more information refer to the Kubernetes documentation.
Configure the Health Check Listen
The health_check_listen configuration property in tibemsd.conf controls the interface and port the server will service HTTP health check requests on. If this property is not set, the server will not attempt to service these type of requests. This property cannot be set dynamically.
You can use only one health_check_listen and this listen should not conflict with other server listens.
These same restrictions apply to secondary_health_check_listen which is used by a server designated as secondary in a fault tolerant pair.
Health Check Response
A requestor can check whether the server is live or ready. An OK response to a liveness request means the server is up and running. An OK response on a readiness request means the server is in the active state while a BAD response means the server is not.
Liveness requests to the server should be HTTP GET requests for the path /isLive. Readiness requests to the server should be HTTP GET requests for the path /isReady.
For example: http://machine:7220/isLive and http://machine:7220/isReady.