You can configure tuning parameters and process limits of your OpenEdge ABL application using the Application configuration for <ABL application name> page.

To set tuning parameters and process limits:

  1. Click Resources > Go to Resources in the OpenEdge Management console menu.
    All resources managed by your console appear in the grid frame.
  2. Filter or search for, and select the required PAS for OpenEdge instance.

    For example, type the default PAS for OpenEdge instance name, oepas1, in the Filter field or select Progress Application Server as the selection in the Type drop-down menu and select the PAS instance.

    The Progress Application Server: <instance name> page appears.

  3. Click an ABL application in ABL Applications section.
    The ABL Application: <ABL application name> page appears.
    Note: The OpenEdge manager web application, oemanager, must be installed on PAS for OpenEdge for you to manage OpenEdge ABL applications and transport services while the PAS for OpenEdge instance is running.
  4. Click Configuration.
    The Application configuration for <ABL application name> page appears.
  5. Select the Performance Tuning and Limits tab to set the following performance tuning and process limits:
    Table 1. Tuning and process limits parameters
    Parameter Default value Description
    Minimum number of agents 0 Specifies the minimum number of agents expected at any time. If the number of agents drops below this number, a client request will cause the session manager to start enough agents to equal this number.
    Maximum number of agents 10 Specifies the maximum number of concurrent multi-session agents that can run on the AppServer.
    Initial number of agents 1 Specifies the number of multi-session agents to start when AppServer is started.
    Initial number of sessions 0 Specifies the number of sessions associated with a PAS for OpenEdge instance when it starts.
    Maximum connections per agent 16 Specifies the maximum number of TCP connections between session manager and multi-session agent.
    Maximum ABL sessions per agent 200 Specifies the maximum number of concurrent sessions a multi-session agent can run concurrently.
    Maximum number of agents to start 0

    Determines the maximum number of agents that may be started at the same time.

    If this value is zero or not defined, then no limit is enforced.
    Request wait timeout 15000 Specifies the maximum amount of time, in milliseconds, a request will wait in the session manager for a connection to be available before rejecting the request.
    Connection wait timeout 3000 Specifies the maximum amount of time, in milliseconds, that the session manager will wait for a connection to be freed up before creating a new connection.
    Idle agent timeout 300000

    Timeout value in milliseconds for an idle agent. If an agent is idle for more than the specified timeout value, then the session will be deleted when idleResource cleanup is done.
    Idle connection timeout 300000

    Timeout value in milliseconds applicable for socket connections between the Session Manager and MS Agent. If a socket connection is idle for more than the specified timeout value, then it will cleaned when idleResource cleanup is done.
    Idle resource timeout 0

    Timeout value in milliseconds to determine the frequency with which the PASOE server checks for idle resources. Any resource (e.g. connection, agent, or client session) that has not been accessed more recently than the specified timeout for that property will be terminated. If this property is set to zero, then idle resource checking is disabled.
    Idle session timeout 300000 Specifies the timeout value in milliseconds for an idle SessionManager session.

    If a SessionManager session is idle for more than the specified timeout value, then the session will be deleted when idleResource cleanup is done.
    Agent listener timeout 10000 When the session manager starts a multi-session Agent, it creates a listening socket, and passes the port number of the listening socket to the agent as a startup argument. After startup, the agent process completes the network initialization based on the timeout value specified for this property.
  6. Click:
    • Save to save the changes.
    • Reset to apply the last-saved settings.
    • Cancel to reject the recent changes.