PAS for OpenEdge is scalable; it can be configured to optimize performance as the workload increases. Note the steps for how you scale PAS for OpenEdge in the following areas:

  • Add more maxConnectionsPerAgent—The first step in scaling an instance is to adjust the maxConnectionsPerAgent in order to maximize the response time of the instance under a given workload. You can set the maxConnectionsPerAgent using the OEPROP command-line utility. The methodology for tuning an instance is described in Tune PAS for OpenEdge instances and PAS for OpenEdge tuning recommendations.
  • Add and remove agents—The next step in scaling an instance is to adjust the number of agents if you cannot add more maxConnectionsPerAgent but still have CPU and memory available. You can adjust the number of agents running on an instance using the OEPROP command-line utility. The methodology for adding agents is described in Tune PAS for OpenEdge instances and PAS for OpenEdge tuning recommendations.
  • Load balancing—The last step in scaling is load balancing. Load balancing involves adding more instances of the server and configuring an environment where the workload is shared among those instances. Load balancing is achieved in PAS for OpenEdge through an Apache extension module or through third party applications, for example:

For information about machine sizing and to download a sample application that can be used for testing the tuning properties and size of the PAS for OpenEdge instance, see the PAS for OpenEdge ATM Benchmark Test and Machine Sizing Guide on the Progress Community.