Restarting OPE microservices after changing the configuration
Article ID: KB0073007
Updated On:
| Products | Versions |
|---|---|
| TIBCO Offer and Price Engine | 5.0.0 |
Description
According to the below OPE 5.0.0 documentation, there is no need to restart OPE microservers after updating the configuration in Consul UI:
===
Configuration
TIBCO OPE uses Consul as an external configuration management tool.
Any changes to the configuration are loaded without needing to restart the microservices. Additionally, applications running OPE Core Engine are notified of changes to the configuration information when the Model Loading Engine loaded the data models.
====
See: https://docs.tibco.com/pub/ope/5.0.0/doc/html/GUID-9C88690C-4964-4042-B40A-110B30D0563F.html
===
Configuration
TIBCO OPE uses Consul as an external configuration management tool.
Any changes to the configuration are loaded without needing to restart the microservices. Additionally, applications running OPE Core Engine are notified of changes to the configuration information when the Model Loading Engine loaded the data models.
====
See: https://docs.tibco.com/pub/ope/5.0.0/doc/html/GUID-9C88690C-4964-4042-B40A-110B30D0563F.html
Issue/Introduction
Restarting OPE services after changing the configuration.
Environment
ALL
Resolution
Actually, restarting the services (OPE, MLE ...) is required when changing the configuration. This is to have the new configuration taken into account.
The above documentation will be addressed in the future releases.
The above documentation will be addressed in the future releases.
Feedback
Yes
No
Powered by
