Tuning the PAS for OpenEdge client network connections involves controlling the HTTP client TCP/IP connections. Many of the network connection properties are defined as Java system properties in the instance-name/conf/catalina.properties file and have psc.as. name prefixes. These properties can be managed using the PASMAN command line utility. Each named psc.as… Java system property in the catalina.properties file is related to an XML element or attribute in an Apache Tomcat instance-name/conf/server.xml file. You can find that relationship using the command pasman.[bat|sh] help psc.as.xxxx.

Note:

Progress recommends that you do not edit the instance-name/conf/server.xml file unless an Apache Tomcat configuration attribute is needed that is not supplied by a psc.as configuration property. If a new Apache Tomcat configuration attribute is required, Progress recommends adding the attribute to the following locations:

  • The server.xml file using a psc.as. property
  • The catalina.properties file, which can be managed remotely using administration tools and automated scripts

PAS for OpenEdge client network connections are a server-level resource and exist for each open HTTP, HTTPS, and AJP13 port. You cannot control client network connections for each web application. Your primary goal is to ensure that PAS for OpenEdge has enough network connection capacity to handle the total client load for all deployed web applications including OpenEdge web applications and any additional external third-party web applications.

Tuning tips

  • Coordinate the maximum number of client connections to be equal to or larger than the size of the PAS for OpenEdge thread pool and the number of queued HTTP client requests.
  • Do not attempt to enable HTTP message compression for HTTP-connected OpenEdge clients by adding its mime-type to the psc.as.compress.types property because it will not work.
  • The HTTP-connected OpenEdge clients use HTTP POST messages with a maximum size of 8KB, so the maximum psc.as.msg.maxpostsize is not an issue. If you are using REST or SOAP clients with very large ProDataSet transfers, this property setting may become important.

The secondary goal is to modify the HTTP message-handling if the default settings do not allow very large message or response data exchange required by some web applications.

HTTP connection properties

Set these HTTP connection message-handling properties to increase network throughput:

HTTP Property Default Description
psc.as.HTTP.connectiontimeout 20000 The maximum time in milliseconds between a TCP connection and the appearance of a HTTP or HTTPS message.
psc.as.HTTP.maxconnections -1 Maximum client connections on the HTTP network port.
psc.as.HTTP.compress on Specifies whether HTTP compression support is enabled.

HTTPS connection properties

Set these HTTPS connection message-handling properties to increase network throughput:

Property Default Description
psc.as.HTTPs.maxconnections -1 Maximum client connections on the HTTPS network port.
psc.as.HTTPs.compress on Specifies whether HTTPS compression support is enabled.

HTTP message properties

Set these HTTP message connection properties to increase network throughput:

Property Default Description
psc.as.msg.timeout 10000 Timeout for async requests in milliseconds.
psc.as.msg.maxpostsize 2097152 The maximum size in bytes of a POST HTTP message.
psc.as.msg.socketbuffer 9000 The HTTP message buffer size in bytes.
psc.as.compress.min 2048 The minimum message size in bytes that enables compression for HTTP responses.
psc.as.compress.types

text/html

text/xml

text/javascript

text/css

application/json

 A comma-separated list of mime types that can be HTTP compressed.