Tuning the PAS for OpenEdge instance involves an iterative process of monitoring instance behavior for a given client and web application configuration, changing configuration values, and then returning to the monitoring phase to see if performance is improved. System administrators can control the following attributes from a PAS for OpenEdge configuration:

  • JVM stack, heap, and metaspace memory allocations
  • JVM garbage collection cycles and overhead
  • The number of HTTP client connections
  • The size of the thread pool used to execute HTTP client requests
  • Client connection timeout (elapsed time without an HTTP request)
  • The queue size for parking HTTP client requests until a thread is available from the pool
  • Socket buffer size
  • HTTP compression for SOAP and REST clients
  • Turning Tomcat optional features on or off
  • Determining the web applications that will be deployed to the PAS for OpenEdge instances

JVM configuration parameters exist in the instance-name/conf/jvm.properties file as Java system properties. You manually edit this file to make changes.

PAS for OpenEdge configuration parameters exist in the instance-name/conf/catalina.properties file as Java system properties, where they are easier to manage from local scripts and remote administration tools. Those Java system property values are used as variable values in the instance-name/conf/server.xml file. Normally you do not edit the server.xml file because it may cause the server to not start. You can use the pasman command line utility or a text editor to maintain the /conf/catalina.properties file.

Use the Java tools, commercial tools, or open source products to monitor PAS for OpenEdge resources and operations.