Hot Update of Application Module Properties
This feature is to update the application module properties without a restart of the application.
Hot Update feature can only be used by configuring application with Configuration Management Service. For more information, see Using Configurations from Configuration Management Services.
Affected areas where the updated properties come in effect at runtime:
Behavioral changes during runtime after update call of application properties:
In an application, a number of jobs (process instances) are running in an Appnode. After the update call of application module properties, the already running process instances will continue to run with the old set of the module properties, and the new process instances created after the update will run with the new set of module properties.
Behavioral changes for subprocesses after update call of application properties:
- Direct subprocesses:
- Service-based subprocess: In the service-based subprocess, the parent process waits for a reply from the subprocess, so the same set of properties as the parent is used for the subprocess.
- To configure Hot Update, change the properties of the application at the configured Configuration Management Service.
- Hit a public rest API /bwm/monitor.json/refresh of the container at port 8090.
- The updated properties from the Configured Management Services will be used to update the application module properties inside the application.