Health check for Order management Long Running 5 micro services
Article ID: KB0074623
Updated On:
| Products | Versions |
|---|---|
| TIBCO Order Management | 5 |
Description
User might like to check the statuses of the different OMLR 5 microservices using a URL endpoint. This article explains how to do this.
Issue/Introduction
This article explains how to perform health check for OMLR 5 microservices (configurator, omsui, omsServer ...)
Environment
ALL
Resolution
Health check services are implemented in the OMLR5 microservices (omsServer, omsui ...). These checks can be used to monitor activity if the system is still available. After starting the particular service, we can use the health check using the below Endpoint:
===
https://<host>:<port>/management/health
===
This is valid for all services. Hereafter a sample endpoint and output:
==
OMSServer health endpoint: http://127.0.0.1:9091/management/health
output:
{"status":"UP","OMS":{"status":"UP","name":"OMS","DB":"UP","JMS":"UP","status":"RUNNING"}}
==
PFA also healthCheck.png screenshot which is an example for OMSUI service.
===
https://<host>:<port>/management/health
===
This is valid for all services. Hereafter a sample endpoint and output:
==
OMSServer health endpoint: http://127.0.0.1:9091/management/health
output:
{"status":"UP","OMS":{"status":"UP","name":"OMS","DB":"UP","JMS":"UP","status":"RUNNING"}}
==
PFA also healthCheck.png screenshot which is an example for OMSUI service.
Attachments
Feedback
Yes
No
Powered by
