Use PAS for OpenEdge Server-Side Profiling to gather and monitor run-time performance data of ABL applications running on a PAS for OpenEdge instance. Performance data can be obtained for both development and production instances of PAS for OpenEdge. Instance shutdown is not required to configure an instance for profiling and enable the instance to gather data.

The following diagram illustrates a Server-Side ABL Performance Profiling workflow and architecture:

Figure 1. Server-Side ABL Performance Profiling architectural diagram
When Server-Side Profiling is enabled for a PAS for OpenEdge instance:
  1. One or more MS Agents gather performance data.
  2. The performance data is pushed to a diagnostic store.
  3. View the data using a Profiler Tool such as Progress Developer Studio.
Progress Software provides a default diagnostic store web application that you can deploy to an instance. The diagnostic store resides on a PAS for OpenEdge instance called Diagnostic Store, however, you can use your own implementation of a web server as a diagnostic store. You can then use a profiler tool such as Progress Developer Studio to view the profiler data.

The main steps for configuring Server-Side Profiling using JMX are:

  1. Configure the diagnostic store
  2. Configure Server-Side Profiling with PAS for OpenEdge

You can also configure and enable Server-Side Profiling using REST APIs. For information on how to configure and enable Server-Side Profiling using REST APIs, see Push profiler data and Get profiler settings.