Prior to OpenEdge 10.2B:
- The ubroker.properties file is accessed once upon process initialization and is cached internally for the duration.
- The property file is never referenced again, which means that any subsequent changes made to the ubroker.properties file are not recognized by the AppServer or WebSpeed Transaction Server processes.
- The AppServer or WebSpeed Transaction Server processes must be restarted in order to recognize any modified property values.
Since OpenEdge 10.2B:
- The ability to have the AppServer and WebSpeed Transaction Server as well as other Servers will recognize changes made to the ubroker.properties configuration file without being restarted, if it is a property that can be changed at runtime.
- This is feature is enabled by configuring the allowRuntimeUpdates property, where a value of 1 means that runtime property changes will be allowed. This feature follows the same property hierarchical inheritance levels as other properties.
- When configuring UBrokers through the OpenEdge Management or OpenEdge Explorer Console, check: "Enable dynamic property updates". The default value for this property is 0 which means Runtime property changes are not allowed.
- References to properties that can be changed at runtime, review the properties listed as dynamic properties in the ubroker.properties.README file.
Starting with OpenEdge 11.5:Progress introduced the Pacific AppServer (PASOE) product. The PASOE properties are configured in the
openedge.properties file located under the server's instance configuration folder: {CATALINA_BASE}
/conf/openedge./conf/openedge.properties Prior to
OpenEdge 11.7.2 and in version 12.0, the PASOE instance will need to be restarted for property changes to the MSAgents configuration to take effect.
Since OpenEdge 11.7.2, 12.1, the MSAgent will detect dynamic property updates like a Classic AppServer. Session manager properties are updated when the
openedge.properties file changes.
a) A property file watchdog was implemented in the MSAgent Session Manager to monitor for online openedge.properties file changes:
- This feature is enabled by setting: allowRuntimeUpdates=1
- The PASOE instance must be restarted to take advantage of the allowRuntimeUpdates=1 (if it wasn't enabled before)
- PASOE MSAgent dynamic configuration properties are listed in the openedge.properties.README as: "This property can be dynamically updated" OCTA-17692 has been raised to get all dynamic properties listed:
agentStartupParam
agentMaxPort
agentMinPort
sessionStartupProcParam
PROPATH
Below properties can be picked up by existing MSagent.
agentLogEntryTypes
agentLoggingLevel
defrdLoggingLevel
defrdLogEntryTypes
defrdLogNumLines
PROPATH (Can be dynamically picked up since version 12.0)
b) The new admin API allows the
Session Manager to perform a dynamic property update on the Multi-Session Agent. For example, agent logging properties for agentLogEntryTypes can be dynamically upgraded and additional dynamic properties can be added as required. The new logging will be pushed to the currently running MSAgents. It won’t change until the current ABL Session completes a request and then notices the logging has changed however.
Example: After enabling
allowRuntimeUpdates=1 allows changes to :
- agentLogEntryTypes, agentLoggingLevel for ABL Sessions
- agentStartupParam agentMaxPort agentMinPort to be dynamically applied to new MSAgents when they start
0. Edit the
{CATALINA_BASE}/conf/openedge.properties of the sample
oepas1 instance as follows:
1. Start the PAS instance after enabling
allowRuntimeUpdates in "parent" [AppServer] Section:
[AppServer]
allowRuntimeUpdates=1
2. Once enabled, modifications to Session Manager dynamic properties will be updated:
[AppServer.SessMgr.oepas1]
agentLogEntryTypes=ASPlumbing,DB.Connects,DynObjects.*,4GLTrace,QryInfo
agentLoggingLevel=4
agentStartupParam=-T "${catalina.base}/temp" -s 256
There is a known issue preventing from dynamically updating the PASOE Multi-Session Agent (MSA) configuration in OpenEdge 11.7.5, 11.7.6, where additional MSA Session Manager configuration are needed. For further configuration detail instruction, refer to the workaround section in Article:
