In versions
prior to OpenEdge 10.0A01, 10.0B04, 10.1B, the AdminServer only handled manual edits/changes to the
ubroker.properties file. Manual changes to the
conmgr.properties file requires the AdminServer to be restarted.
Since
OpenEdge 10.0A01, 10.0B04, 10.1B the AdminServer's
Property File Monitoring capability was enhanced by adding the ability to also detect manual property file changes in
conmgr.properties and
<db>.repl.properties like the ubroker.properties in prior versions.
If the
conmgr.properties file itself is
overwritten by another copy while the AdminServer is running, configurations of the file being coped will not be recognized until the AdminServer is restarted.
It is only when the current DLC/properties file is manually edited or the mergeprop utility is used when the AdminServer is online that new instances are updated within the current file are recognized.
In the OpenEdge Console UI, .properties changes need to be polled successfully twice before they are listed in the Console UI. The default polling time is 5 minutes. Polling information can be seen in the upper right hand corner of the right most view. To see changes without having to wait on the polling cycle, make use of the Refresh button.
When changes are made to existing resources, these 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 added for ubrokers but not for databases, where some configuration changes are applied while the resource is online. For further detail, refer to Article:
