To edit the properties of an ABL application deployed on a PAS for OpenEdge instance:

  1. In the OpenEdge Command Center console, click the ABL Applications tab.
    The ABL Applications page appears, listing all the ABL applications, web applications, and services deployed across multiple PAS for OpenEdge instances.
  2. On the ABL Applications page, click the name of the ABL application whose properties you want to modify. The Edit ABL Application page appears, displaying the properties of the corresponding ABL application. These properties are categorized into the following sections:
    • MS Agent Startup Configurations
    • MS Agent Session Procedures
    • MS Agent Procedures
    • MS Agent Logging Settings
    • Session Manager Performance Tuning and Limit Settings
    • Session Manager Timeouts
  3. In the MS Agent Startup Configurations section, you can edit values for the following properties:
    Field Description
    MS Agent Startup Directory Specifies the path to the agent startup working directory.
    MS Agent Startup Parameter Specifies the server and agent startup parameters that each process uses when the broker starts it. For example, you can specify the Database (-db) parameter to connect to the application database. You can update this property dynamically. Dynamic changes affect only new MS Agents that are started after the update.
    PROPATH Specifies the PROPATH, which is a Progress environment variable, that contains a list of directories that the ABL Virtual Machine (AVM) uses to search for files and procedures to run. In this field, you can add, edit, delete, or reorder the PROPATH entries.
  4. Click the MS Agent Session Procedures section to expand it, and then you can edit the values for the following properties:
    Field Description
    Activate Procedure Specifies the activate procedure for the session. This procedure must be a valid procedure on the PROPATH of the application service.
    Deactivate Procedure Specifies the deactivate procedure for the session. This procedure must be a valid procedure on the PROPATH of the application service.
    Connect Procedure Specifies the connect procedure for the session-managed sessions. This procedure must be a valid procedure on the PROPATH of the application service.
    Disconnect Procedure Specifies the disconnect procedure for session-managed sessions. This procedure must be a valid procedure on the PROPATH of the application service.
    Session Startup Procedure Specifies a startup procedure for the server. This procedure must be a valid procedure on the PROPATH of the application service.
    Session Startup Procedure Parameter Specifies the startup parameter that each session uses when the MS Agent starts it. You can update this property dynamically. Dynamic changes affect only new MS Agents that are started after the update.
    Session Shutdown Procedure Specifies the shutdown procedure for the server. This procedure must be a valid procedure on the PROPATH of the application service.
  5. Click the MS Agent Procedures section to expand it, and then you can edit the values for the following properties:
    Field Description
    MS Agent Startup Procedure Specifies a startup procedure used for a multi-session agent. This procedure must be a valid procedure on the PROPATH of the application service.
    MS Agent Startup Procedure Parameter Specifies a character parameter that is provided as an input into the agentStartupProc procedure.
    MS Agent Shutdown Procedure Specifies a shutdown procedure that is used for a multi-session agent. This procedure must be a valid procedure on the PROPATH of the application service.
  6. Click the MS Agent Logging Settings section to expand it, and then you can edit the values for the following properties:
    Field Description
    Log File Name Specifies the MS Agent log file that contains the location, name, and roll-over details of the MS Agent. If you want the MS Agent log file roll-over details at midnight, then add {yyy-MM-dd}. For example:<path-to>/<instance name>.agent.{yyyy-MM-dd}.log.
    Logging Level Specifies the logging level for messages written into the MS Agent log buffer. The acceptable value range is 1 to 4.
    Log Entry Types Specifies a single entry or comma-delimited list of logging entry types for the MS Agent log buffer. By default, this parameter is set to uBroker.basic.
  7. Click the Session Manager Performance Tuning and Limit Settings section to expand it, and then you can edit the values for the following properties:
    Field Description Minimum value
    Minimum Number of MS Agents Specifies the minimum number of MS Agents expected to be active at any given time. If the number of MS Agents drops below this threshold, a client request triggers the session manager to start additional MS Agents to match this number. 1
    Maximum Number of MS Agents Specifies the maximum number of concurrent MS Agent operating the system processes that an individual ABL application can start on the AppServer. 1
    Initial Number of MS Agents Specifies the number of MS Agents to be started when the AppServer starts. 1
    Maximum Connections per MS Agent Specifies the maximum number of concurrent TCP connections allowed between the session manager and the MS Agent. 1
    Maximum ABL Sessions per MS Agent Specifies the maximum number of sessions an MS Agent can run. 1
    Maximum Number of MS Agents to Start Specifies the maximum number of MS Agents that can be started simultaneously. If this value is set to zero or not defined, no limit is enforced. 0
  8. Click the Session Manager Timeouts section to expand it, and then you can edit the values for the following properties:
    Field Description Minimum value
    Request Wait Timeout Specifies the maximum amount of time in milliseconds, for which a request waits in the session manager for a connection to become available before the request is rejected. 0
    Connection Wait Timeout Specifies the maximum amount of time in milliseconds, for which the session manager waits for a connection to be freed before creating a new connection. 0
    Idle MS Agent Timeout Specifies the timeout value in milliseconds, for an idle MS Agent. If an MS Agent is idle for longer than the specified timeout value, the session is deleted when the idleResource cleanup is done. 0
    Idle Connection Timeout Specifies the timeout value in milliseconds, between an AppServer client and the session manager. If a connection is idle for longer than the specified timeout value, the session manager terminates the connection by automatically disconnecting it from the AppServer. 0
    Idle Resource Timeout Specifies the timeout value, in milliseconds, to determine the frequency with which the PAS for OpenEdge server checks for idle resources. Any resource (for example, connection, MS Agent, or client session) that is not accessed for longer than the specified timeout for that property, will be terminated. If this property is set to zero, idle resource checking is disabled. 0
    Idle Session Timeout Specifies the timeout value in milliseconds for an idle session in the session manager. When using HTTP sessions, the APSV transport uses this value to set the expiration time of the HTTP session, which defaults to 30 minutes and is the same value that other transports use. The expiration of HTTP sessions is controlled in web.xml and does not require idleResourceTimeout to be set because it is managed by Tomcat. 0
    MS Agent Listener Timeout Specifies the maximum amount of time in milliseconds for which the session manager waits for an MS Agent to start, when the connection is established. 0
  9. After editing the required properties, click Apply.
    The Confirm Changes dialog box appears, displaying the details of the edited properties. The buttons in the dialog box vary depending on the running status of the ABL application and type of the properties edited:
    • If the ABL application is running and you have edited:
      • Runtime updatable properties — the dialog box displays Save and Cancel buttons. Click Save to apply your changes.
      • Both types of properties or only the properties that require restart of the PAS for OpenEdge instance — the dialog box displays Save, Save and Restart, and Cancel buttons:
        • When you click Save, changes to the properties that do not require a restart of the PAS for OpenEdge instance are applied immediately, while changes to those properties requiring a restart will be applied after the PAS for OpenEdge instance restarts.
        • When you click Save and Restart. The Confirm Restart popup window appears. In the Type restart to confirm field, type restart and click Restart to restart the PAS for OpenEdge instance and apply changes to the properties. The ABL application will be unavailable during the restart.
    • If the ABL application is not running, the dialog box displays only Save and Cancel buttons, irrespective of the type of properties edited. Click Save to save your changes. The changes to the properties will be applied after the ABL application is in running state.