If manual changes are edited directly into the current ubroker.properties file, then under normal conditions, the AdminServer does not have to be restarted.
The AdminServer regularly checks the corresponding ubroker.properties files for changes. If a change is detected it automatically reloads the new settings from the modified *.properties file into memory
by performing partial warm start up without the need to restart the AdminServer and saves the previous file as
*.properties-sav. When this occurs a
WarmStartFinished alert is triggered.
However, c
hanges to the ubroker.properties file will not be taken into effect automatically (warm start will not be performed), if the file is overwritten using cp/mv command as opposed to being edited. Instead, the mergeprop utility should be used to this end. When manually editing the ubroker.properties while the AdminServer is running, caution should be exercised as when invalid values or entries are added to a ubroker.properties section, it can cause the AdminServer to become unstable and may require a restart of the Adminserver to correct the instability. The
ubconfig utility should be used to verify changes in a copy first.
For example, a new 'asbroker2' is added to the ubroker.properties file while the AdminServer is running:
[AdminServer] Start doing partial warm start...
[Fathom] * Alert! Alert Name: WarmStartBegan, Resource Name: hostname, Severity: 4, Message: AdminServer started partial warm start. (11234)
[AdminServer] Partial warm start has completed.
[Fathom] Binding resource to surrogate. AdminServer name: hostname. Resource name: asbroker2 (17219)
[Monitor] hostname:asbroker2: online
[Fathom] Alert Cleared! Alert Name: WarmStartBegan, Resource Name: hostname, Comment: "" (9627)
[Fathom] * Alert! Alert Name: WarmStartFinished, Resource Name: hostname, Severity: 4, Message: AdminServer finished partial warm start. (11235)
...
[Monitor] hostname:asbroker1: online
[Monitor] hostname:asbroker2: online
If changes are made to
existing resources, the changes may take a few minutes to load, however once the reload is complete, the resource will need to be restarted in order it will pick up the changes. Since OpenEdge 10.2B, the "
Dynamic Property Update" feature was introduced where some of these properties are allowed to be dynamically updated when the
allowRuntimeUpdates property is set to 1, thereby negating the need to restart. Refer to Article: P145705,
Can an AppServer Server process detect changes to the ubroker.properties file when the AppServer Server process is running? Changed properties can be verified by running the "
-listallprops":
Example:
$ asbman -name asbroker2 -listallprops
An enhancement request has been submitted as an Idea on the Progress Community. To promote the Idea, click on this link:
https://community.progress.com/community_groups/products_enhancements/i/openedge_installation__deployment/add_clonecopy_option_to_openedge_managementexplorer_servers
For detailed information on how to submit an Idea, please refer to Article P11255, How to submit an idea for a Progress product enhancement (embedded video)
