readinessProbe

TIBCO BPM Enterprise uses the Kubernetes readinessProbe to determine a container's readiness to accept work.

Kubernetes can perform an HTTPGetAction on the following REST endpoint to probe for readiness: 

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

TIBCO BPM Enterprise returns one of the following responses:

  • HTTP 200 - The TIBCO BPM Enterprise container is ready to accept requests.
  • HTTP 503 - The TIBCO BPM Enterprise container is not ready to accept requests.

The readiness REST endpoint has no required authentication.

The following parameters can be defined with the readinessProbe:

  • initialDelaySeconds - Number of seconds after the container has started before readiness 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.