Update PROPATH in a production instance with zero downtime
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
PAS for OpenEdge system administrators can dynamically update their applications by enabling live PROPATH updates in production instances.
- Deploy new application r-code to a running server instance.
- Change the PROPATH by using the OEPROP utility or by deploying an updated application to include the new r-code location.
PAS for OpenEdge ABL sessions that are not handling requests begin executing the new application code. PAS for OpenEdge ABL sessions running requests finish those requests before using the new application code.
When the PROPATH is updated, the ABL sessions execute sessionShutdownProc, restart, and then execute sessionStartupProc. Bound sessions are not updated with the new PROPATH
until the sessions finish executing the bound client requests.
- Run the Proenv utilty.
- Navigate to the target instance-name/bin directory.
- Use the OEPROP utility to set
allowRuntimeUpdatesto1in theopenedge.propertiesfile:oeprop.[sh|bat] AppServer.allowRuntimeUpdates=1This property turns on a process that checks the
openedge.propertiesfile for changes and interactively passes those changes to the PAS for OpenEdge multi-session agents. - Manually restart your PAS for OpenEdge instance to have this change take effect.