Open topic with navigation

TIBCO® BPM Enterprise 5.5.0

# 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.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO® BPM Enterprise

Copyright © 2015-2024. Cloud Software Group, Inc. All Rights Reserved.