5.1 System JD Edwards EnterpriseOne Performance Monitoring

This section contains an overview of monitoring system performance and lists the forms that are used to monitor system performance.

5.1.1 Monitoring System Performance

The activities that are related to monitoring system performance are primarily for viewing and analyzing the most recent performance data that is received from agents in a monitored system.

Note:

The information that is presented in the System Performance forms is as current as the last form refresh.

Note:

The standard deviation is a statistic that tells you how tightly all the values that are used to compute the average are clustered around the average. Large standard deviations warn that the averages appearing in the chart are not a reliable indicator of response times that are experienced by individual users.

5.2 Viewing Open PMUs

Access the Open PMUs - Open PMUs form.

An open PMU is a PMU that started but has not finished prior to an agent reporting performance metrics to the monitor. Information regarding open PMUs are stored in the F95960 table. When the PMU finishes, the collator flags the PMU for deletion and inserts a matching row into the F95961 table, which stores completed PMU data.

If an end user is reporting that a JD Edwards EnterpriseOne form is slow, use the Open PMU form to see where the request has stalled. Search for that user's ID to see the current state of that user's open PMUs.

Before you view current PMU details, you need to enter search criteria. If you do not specify criteria, the form displays all of the open PMUs for the selected system.

User ID

Specifies the code that identifies a user profile.

PMU Set

Categorizes meta-data transaction definitions into a set. Currently, only one definition set exists, and it is reserved for JD Edwards EnterpriseOne development.

PMU ID

Specifies the identifier for a particular PMU you can monitor.

Performance Trace

Identifies the name of the trace used to capture performance data that a user can start and stop to capture specific results.

Context 1, 2, 3

Specifies values (1-3) that are common to the entire user request or a specific tier. PMU metrics contain data specific to an individual PMU.

System ID

Identifies each monitored system. JD Edwards EnterpriseOne automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.

Agent ID

Identifies an agent within a domain. This is automatically generated by the monitor the first time an agent registers.

Duration >=sec

Identifies the duration in milliseconds that a single transaction took to complete.

Duration < (sec)

Identifies the duration in milliseconds that a single transaction took to complete.

Note:

Some of the metrics for various PMUs do not have values until the PMU finishes, so in some cases, metrics may appear with no values.

5.3 Monitoring Individual User Performance

You can monitor individual users' system performance using the User Level Trace application. You set the performance data according to the user override of JD Edwards EnterpriseOne Performance Monitoring level. You can override JD Edwards EnterpriseOne Performance Monitoring level for one user at a time, however you cannot override JD Edwards EnterpriseOne Performance Monitoring level for multiple users.

Access the User Level Trace form.

User ID

Specifies the code that identifies a user profile.

Standard, Verbose, Debug

Select a filter value to view only the information returned of a specific filter level. Each meta-data definition has a filter level set to one of the following: Standard, verbose, or debug.

5.4 Viewing Open PMU Trees

Access the Open PMU Trees - Open PMU Trees form.

Every user request generates a set of PMUs that you can display as a tree. The PMU with the top instance ID is the root of the tree and PMUs with no children are the leaves. A node represents each PMU or child PMU. Clicking a node reveals its detail, or the Select button on the parent nodes reveals its details.

A search may return multiple PMU trees. For example, if a user ID is shared across multiple users, or a single user has initiated multiple browser sessions, then more than one user request may be currently processing, and therefore more than one PMU tree open.

The data that is related to open PMUs is dynamic because the system is currently processing the PMU. Therefore, the composition of trees, and even their presence, is likely to change each time you click Refresh.

Note:

For each PMU in the tree, the duration value represents the period of time that has elapsed since the monitoring system received the start timestamp for each PMU. In some cases, the display may indicate that a child PMU is "older" than its parent. For example, if the application server sent PMU information before the web server sent PMU information, the child PMUs that are running on the application server will display a smaller duration than the associated parent PMUs that are running on the web server.

User ID

Specifies the code that identifies a user profile.

Scripting on this page enhances content navigation, but does not change the content in any way.