The classic AppServer keeps the properties for all defined instances in a single properties file located at $DLC/properties/ubroker.properties. With those properties, you define a set of property values that serve as the application's default configuration. An administrator installing an application typically defines a new classic AppServer instance and can change those property values to suit a site's specific requirements.

PAS for OpenEdge operates in the same general way, but is different with regards to the following:

  • Each PAS for OpenEdge instance embeds its openedge.properties file inside the instance-name/conf directory.
  • A PAS for OpenEdge instance supports named ABL applications that correspond to the installation directory architecture.
  • The properties for an ABL application in PAS for OpenEdge configure its web applications, transports, an ABL session manager, and ABL multi-session agents.

The following is a brief comparison of classic AppServer properties to PAS for OpenEdge properties:

  • Many of the properties used by a classic AppServer can be found in PAS for OpenEdge.
  • Some classic AppServer properties have no meaning and are not found in PAS for OpenEdge.
  • Some classic AppServer properties relate to functionality that is provided by the PAS for OpenEdge installation directory and are managed using core, server-level properties.
  • PAS for OpenEdge has new properties do not apply to the classic AppServer.

The following is an overview of how the properties found in the ubroker.properties file for a classic AppServer map to properties found in a PAS for OpenEdge instances openedge.properties file. The detailed information about individual properties can be found in the respective README files (ubroker.properties.README and openedge.properties.README).

There are certain rules for reading property names:

  • All classic AppServer property names do not supply a group (a [...] name as the properties can exist in any [Ubroker…] group).
  • All PAS for OpenEdge property names use a name-space declaration that tracks the group hierarchy found in the openedge.properties file. For example:
    • AppServer.Agent [AppServer.Agent]
    • AppServer.Agent [AppServer.Agent]
    • AppServer.Agent.oepas1 [AppServer.Agent.oepas1]
    • AppServer.Agent.wrkdir [AppServer.Agent] wrkdir
    • AppServer.Agent.oepas1.wrkdir [AppServer.Agent.oepas1] wrkdir
  • PAS for OpenEdge groups include:
    • [AppServer] — Properties that apply across the server instance
    • [AppServer.Agent] — Properties that apply across all multi-session agents in the server instance (inherits from nothing)
    • [AppServer.Agent.appname] — Multi-session agent properties that apply only to the ABL application named appname (inherits from [AppServer.Agent])
    • [AppServer.SessMgr] — Properties that apply across all ABL application session managers in the server instance (inherits from nothing )
    • [AppServer.SessMgr.appname] — ABL application session manager properties that apply only to the ABL application named appname (inherits from [AppServer.SessMgr])
    • [appname] — Properties that apply only to the ABL application’s web applications (inherits from nothing)
    • [appname.web-app-name] — Properties that apply only to the ABL application’s web application named web-app-name (inherits from [appname])
    • [appname.web-app-name.APSV] — Properties that apply only to the ABL application’s web application named web-app-name and to its APSV transport (inherits from [appname.web-app-name])
    • [appname.web-app-name.SOAP] — Properties that apply only to the ABL application’s web application named web-app-name and to its SOAP transport
    • [appname.web-app-name.REST] — Properties that apply only to the ABL application’s web application named web-app-name and to its REST transport
    • [appname.web-app-name.WEB] — Properties that apply only to the ABL application’s web application named web-app-name and to its WEB transport

The following table list the classic AppServer properties and how they correspond to a PAS for OpenEdge instance properties:

Table 1. Mapping AppServer to PAS for OpenEdge instance properties
Classic AppServer property PAS for OpenEdge property
4glSrcCompile N/A
allowRuntimeUpdates AppServer.allowRuntimeUpdates
appServerKeepaliveCapabilities N/A
appserviceNameList N/A
autoStart N/A
autoTrimTimeout N/A
brkrDebuggerEnabled N/A
brkrDebuggerKeyAlias N/A
brkrDebuggerKeyAliasPassword N/A
brkrDebuggerPassphrase N/A
brkrDebuggerPortNumber N/A
brkrDebuggerSSLEnable N/A
brkrDebuggerUseBrokerAlias N/A
brkrLogAppend N/A
brkrLogEntries N/A
brkrLogEntryTypes N/A
brkrLogThreshold N/A
brkrLoggingLevel N/A
brkrNumLogFiles N/A
brokerLogFile N/A
certStorePath N/A
classMain N/A
collectStatsData AppServer.Agent.collectStatsData
compressionEnable N/A
connectingTimeout See catalina.properties
controllingNameServer N/A
debuggerEnabled N/A
defaultService N/A
description N/A
environment N/A
flushStatsData AppServer.Agent.flushStatsData
groupName N/A
hostName N/A
infoVersion AppServer.Agent.infoVersion
initialSrvrInstance AppServer.SessMgr.numInitialAgents
ipver AppServer.SessMgr.ipver
keyAlias AppServer.Agent.keyAlias
keyAliasPasswd AppServer.Agent.keyAliasPasswd
keyStorePasswd AppServer.Agent.keyStorePasswd
keyStorePath AppServer.Agent.keyStorePath
maxClientInstance N/A
maxSrvrInstance AppServer.SessMgr.maxAgents
minSrvrInstance N/A
noSessionCache AppServer.Agent.noSessionCache
operatingMode N/A
password N/A
portNumber See catalina.properties
priorityWeight N/A
PROPATH AppServer.Agent.PROPATH
registerNameServer N/A
registrationMode N/A
registrationRetry N/A
requestTimeout AppServer.SessMgr.requestWaitTimeout
serverASKActivityTimeout N/A
serverASKResponseTimeout N/A
serverLifespan N/A
serverLifespanPadding N/A
sessionTimeout AppServer.Agent.sessionTimeout
srvrActivateProc AppServer.Agent.sessionActivateProc
srvrConnectProc AppServer.Agent.sessionConnectProc
srvrDeactivateProc AppServer.Agent.sessionDeactivateProc
srvrDisconnProc AppServer.Agent.sessionDisconnProc
srvrExecFile AppServer.SessMgr.agentExecFile
srvrExecutionTimeLimit N/A
srvrLogAppend N/A
srvrLogEntryTypes AppServer.SessMgr.agentLogEntryTypes
srvrLogFile AppServer.Agent.agentLogFile
srvrLogThreshold N/A
srvrLogWatchdogInterval N/A
srvrLoggingLevel AppServer.SessMgr.agentLoggingLevel
srvrMaxPort AppServer.Agent.agentMaxPort
srvrMinPort AppServer.Agent.agentMinPort
srvrNumLogFiles N/A
srvrSelectionScheme N/A
srvrShutdownProc AppServer.Agent.sessionShutdownProc
srvrStartupParam AppServer.Agent.sessionStartupParam
srvrStartupProc AppServer.Agent.sessionStartupProc
srvrStartupProcParam AppServer.Agent.sessionStartupProcParam
srvrStartupTimeout N/A
sslAlgorithms AppServer.Agent.sslAlgorithms
sslEnable AppServer.Agent.sslEnable
userName N/A
uuid AppServer.Agent.uuid
workDir N/A
N/A AppServer.statusEnabled
N/A AppServer.collectMetrics
N/A AppServer.applications
N/A AppServer.Agent.agentShutdownProc
N/A AppServer.Agent.agentStartupProc
N/A AppServer.Agent.agentStartupProcParam
N/A appname.webApps
N/A appname.SessionMgr
N/A appname.web-app-name.adapterEnabled
N/A appname.web-app-name.SOAP.adminEnabled
N/A appname.web-app-name.SOAP.adminSoapAction
N/A appname.web-app-name.SOAP.debugClients
N/A appname.web-app-name.SOAP.wsdlEnabled
N/A appname.web-app-name.SOAP.wsaUrl
N/A AppServer.SessMgr.publishDir
Note: AppServer KeepAlive (ASK) protocol is no longer supported in PAS for OpenEdge. The ASK protocol feature ensures that an idle AppServer session remains active and prevents it from timing out due to inactivity. This feature was useful in scenarios where a client intermittently communicates with the AppServer, avoiding unnecessary reconnections and overhead.

This feature is specific to Classic AppServer and it is not supported with PAS for OpenEdge, neither as ClientASK nor ServerASK. Hence, the related connection parameters like AppServer Keepalive and clientASKResponseTimeout are also not supported in PAS for OpedEdge.