livenessProbe

TIBCO BPM Enterprise uses the Kubernetes livenessProbe to ensure that the container is healthy and responsive.

Kubernetes can perform an HTTPGet on the following REST endpoint to probe for liveness: 

path: /bpm/adapter/v1/liveness
port: <port_used_for_BPM_services>

TIBCO BPM Enterprise returns one of the following responses:

  • HTTP 200 - The TIBCO BPM Enterprise container is healthy and responsive.
  • HTTP 503 - The TIBCO BPM Enterprise container is not healthy. This same response is assumed if the container fails to repond.

The liveness REST endpoint has no required authentication.

The following parameters can be defined with the livenessProbe:

  • initialDelaySeconds - Number of seconds after the container has started before liveness checks are sent.
  • periodSeconds - How often, in seconds, to perform the probe.
  • timeoutSeconds - Number of seconds after which the probe times out if no response is received.
  • successThreshhold - Minimum consecutive successes for the probe to be considered successful after having failed.
  • failureThreshold - If a pod starts and the probe initially fails (HTTP 503 response), Kubernetes will re-try the probe this number of times before giving up.