Monitoring System Performance

This chapter provides an overview of system performance monitoring and discusses how to:

Use the system performance home page.
View web server performance.
View application server domain performance.
View Process Scheduler server performance.
View Master Scheduler server performance.
View open PMUs.
View open PMU trees.
View current user sessions.
View recycled processes diagnosis.
Understand the events that monitor resource usage.

System Performance Monitoring

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

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.

PeopleSoft provides a collection of use cases in the form of flow charts for you to use as a framework for learning how to use Performance Monitor to detect performance issues. These flow charts do not appear in this PeopleBook; they are posted on Customer Connection. Refer to the PeopleTools 8.49 Release Notes for the current location of these flow charts.

See PeopleTools 8.46: Performance Monitor Database Schema and Use Cases on Customer Connection.

Note. The information that is presented in the System Performance pages is as current as the last page refresh.

Note. The Standard Deviation (Std. Dev.) is provided on many pages. 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.

Pages Used to Monitor System Performance

Page Name	Object Name	Navigation	Usage
System Performance	PSPMSYSHEALTH	PeopleTools, Performance Monitor, System Monitor, System Performance	Provides a high-level view of the performance of a monitored system displaying performance indices as well as some critical event and PMU data for the servers in your monitored system. This page acts as a "home page" for monitoring system health. For example, from the System Performance page, you can access numerous related pages, such as the Web Server page, Application Server page, the Process Scheduler page, and so on.
Web Server	PSPMWEBDOM	PeopleTools, Performance Monitor, System Monitor, Web Server	Enables you to drill down into the performance data that is related to your web server, such as JVM Status, network status, site performance, and servlet performance.
Application Server	PSPMAPPDOM	PeopleTools, Performance Monitor, System Monitor, Application Server	Enables you to drill down into the status of an application server domain and the individual server processes that are running in that domain.
Process Scheduler Server	PSPMPSCHEDDOM	PeopleTools, Performance Monitor, System Monitor, Process Scheduler Server	Enables you to drill down into the status of a Process Scheduler domain, monitor the individual server processes within a domain, and monitor the resource usage.
Master Scheduler	PSPMMASTSCHED	PeopleTools, Performance Monitor, System Monitor, Master Scheduler	Enables you to view the status of the Master Scheduler distributing workload across multiple Process Schedulers.
Open PMUs	PSPMTRANSCURR	PeopleTools, Performance Monitor, System Monitor, Open PMUs	Provides search criteria by which you can search for open PMUs, which are PMUs that have not yet finished.
Open PMU Trees	PSPMTRANSUSER	PeopleTools, Performance Monitor, System Monitor, Open PMU Trees	Enables you to search open PMUs by user and display each open PMU in a tree format.
Current User Sessions	PSPMCURUSERS	PeopleTools, Performance Monitor, System Health, Current User Sessions	Enables you to view the users who are currently signed on to the system as well as view an individual user's history.
Recycled Processes Diagnosis	PT_PM_RECPROC_DIAG	PeopleTools, Performance Monitor, System Health, Recycled Processes Diagnosis	Shows detail about application server crashes and last service request type.

Using the System Performance Home Page

Access the System Performance page.

The System Performance page provides various health indices as well as a high-level view of the performance of your web servers, application servers, and Process Scheduler server domains. It acts as the "home page" for system performance.

Note. A Status field appears at the top of the page only if the monitoring system detects stale data, which is data that is older than the specified event sampling rate. For example, if your event sample rate is 300 seconds, and no events have been received from a specific domain in over five minutes, then that domain is considered stale. Stale data could indicate an outage on the monitored system or that the monitored system's agent filters are set to 01–Standby. If a domain has been shut down permanently and you don't want it to appear with a stale data warning, go to the Agent Definitions page and set its domain monitor to inactive.

Viewing Performance Indices

User Sessions	Displays the number of users who have signed onto the system within the last 12 hours and have not signed off. Shows all PMU 109s (User Session Began) that do not have an associated 108 PMU (User Session Ended). These PMUs are associated by the session ID (Context 1). The User Sessions value includes only users who have signed on in the last 12 hours and only those users that have signed on since the last time the web server agent sent an Event 901 (Agent Initialization). For details on individual users, click the Current User Sessions link. Note. If users do not click the Sign out link on a PeopleSoft page and instead close the browser or navigate to another site, then the system displays them as current users until the web-server time-out value is reached.
Tuxedo Request Queued	Displays the number of requests queued on all application servers on the monitored system. The value is the sum of all the metric 5s (Total pq) for Event 300s (Host Resource Status) that are sent by all active agents for the current system that are domain monitor agents of type application server. The value includes all Event 300 data that is generated within the defined sampling interval.
PMUs in Past Hour	Displays the number of PMUs that have run in the past hour. This is an indication of the load on the monitored system, the level of monitoring, and whether the monitored system agents are currently communicating with the monitor. The value is the sum of the rows that are inserted into the PSPMTRANSHIST table within the last hour. For more details, click the Open PMUs and the Completed PMUs link.
Alarms in Past Hour	Displays the number of error and warning events that were posted by the monitored system's active agents in the past hour. This is the count of all events with filter levels of error and warning inserted into the PSPMEVENTHIST table in the last hour. For more details, click the Alarm History link.
Batch Jobs in Process	Displays the number of Process Scheduler jobs that are currently running on all the Process Scheduler servers belonging to that monitored system. The value is the sum of all metric 1s for Event 350 (Master Scheduler Status). For more details, click the Master Scheduler link. Note. If a Master Scheduler is not configured for the monitored system, this value is zero.
Batch Jobs in Queue	Displays the number of Process Scheduler jobs that are currently waiting to be assigned by the Master Scheduler. The value is the sum of all metric 2s for Event 350 (Master Scheduler Status). Note. If a Master Scheduler is not configured for the monitored system, this value is zero.

Today's Averages

The Today's Averages chart displays the average duration of various performance factors within your PeopleSoft system. The data applies only to the current day, which refers to all data that has been collected since midnight.

If progress slows in the system anywhere, this chart enables you to identify which tier is affected and enables you to monitor Tuxedo queueing.

User Response

Displays the average amount of time that end users waited for server round trips to finish. A user is waiting for a server round trip to finish when Processing appears in the upper, right-hand corner of a PeopleSoft page.

Note. This average does not include network latency. It is the average duration of all top-level PMU 101s (PIA Request) that the monitoring system has received since midnight.

Jolt Request

Displays the average and standard deviation of all PMU 115s (Jolt Request) received since midnight.

Application Server

Displays the average and standard deviation of the duration of all PMU 400s (Tuxedo Service PeopleCode and SQL Summary) received since midnight.

SQL

Displays the average and standard deviation for the time spent running SQL statements that were initiated from PeopleCode in a single application server request. This value includes the time that was required for SQL Prepare, Execute, Fetch, and Commit.

PeopleCode SQL statements are run by application code that is written using PeopleCode and submitted to the database by way of SQLEXECs or SQL Objects.

This value is derived from metrics 2, 3, and 4 from PMU 400 (Tuxedo Service PeopleCode and SQL Summary). Namely, this value includes PeopleCode SQL, PeopleCode Built-in SQL, and PeopleTools SQL.

Note. This is the average time spent for running all SQL statements of these types in a single application server request. The system calculates this value using all data that has been received since midnight.

Web Server Domains

The Web Server Domains grid contains a row for each active domain-monitor web-server agent. The metric information is derived from Event 150 (JVM status) and Event 151 (Network Status). The system retrieves only the most recent event for each agent. If the most recent event’s monitor date and time is older than the system’s event sample rate, the Stale Data icon appears in the grid row and at the top of the page.

Note. Web server agents do not report performance data until the first user connects to that web server.

Name	Displays the PeopleSoft web-server domain name that is being monitored. Click the name to go to the Web Server page for that web server. It's the same page that you access when you select PeopleTools, Performance Monitor, System Monitor, Web Server and choose that domain.
Host/Port	Identifies the web-server domain host name and listening port numbers for HTTP and HTTPS.
Filter Level	Appears on pages displaying current performance information that is related to servers, such as application servers, web servers, and so on. Displays the current agent filter level. The colors indicate the following filter levels: Blue: Standby, Error, and Warning. Green: Standard. Orange: Verbose. Red: Debug. Move the cursor over the icon to show a pop-up message displaying the agent filter level in text format.
Sessions in Web App	Displays the number of servlet sessions in the portal web application.
%JVM Memory Used	A Java Virtual Machine (JVM) has a specific amount of memory allocated to it. This metric displays the percentage of the allocated memory that the JVM is currently using.
Execute Threads	The number of threads that are used by the web application to service incoming requests.
Established Sockets	The number of sockets in a connected state. This is a measure of the number of active users.
Jolt Traffic	Displays the per second amount (in bytes) of Jolt traffic between the web server and the application server.

Application Server Domains/Process Scheduler Server Domains

The application server and Process Scheduler Server grids contain a row for each active domain monitor agent that is running on the application server or Process Scheduler server. The metric information on each row is derived from Event 300 (Host Resource Status). The system retrieves only the most recent event for each agent. If the most recent event’s monitor date or time is older than the system’s event sample rate, the Stale Data icon appears in the grid row and at the top of the page.

Note. When first booted, an active server may have a stale data warning until a full sampling interval has passed.

Domain Name	Displays the names of the domains that are being monitored. Click the domain name to access the Application Server or the Process Scheduler page for additional details on a particular domain. It's the same page that you access when you select PeopleTools, Performance Monitor, System Monitor, Application Server or Process Scheduler and choose that domain.
Host/Port	Displays the server name or IP address and the Jolt listening port number.
Filter Level	Appears on pages displaying current performance information that is related to servers, such as application servers, web servers, and so on. Displays the current agent filter level. The colors indicate the following levels: Blue: Standby, Error, and Warning. Green: Standard. Orange: Verbose. Red: Debug. Move the cursor over the icon to show a pop-up message displaying the agent filter level in text format.
%CPU Used	Displays the percentage of the CPU capacity that is being used on the host. This percentage includes the entire processing load on the host, not just that of PeopleSoft.
%Memory Used	Displays the percentage of physical memory that is used on the host. This percentage includes all memory used on the host, not just the memory used by PeopleSoft.
Hard Page Faults/Second	This is the number of accesses to virtual memory in the last second that require disk reads on the host. This metric applies to all memory access on the host, not just the memory that is accessed by PeopleSoft.
Total Tuxedo Connections	This is the number of connections to this domain, and it is equivalent to the number of rows that are returned by the Tuxedo command pclt (tmadmin), excluding JSH and WSH connections. This value does not apply to Process Scheduler.
Total Tuxedo Requests Queued	The number of Tuxedo requests that are queued on that domain. A high number indicates that insufficient server processes are configured, or that the load on the host machine is too high. This value does not apply to Process Scheduler.

Ping Test

PeopleSoft Ping is a diagnostic feature that enables you to troubleshoot systemic performance issues. If you enter the ping URLs for the monitored systems in the URL catalog, you can launch the ping test from the monitoring system instead of having to sign on to the monitored system.

The following requirements must be in place:

Single signon must be configured between the monitored and monitoring system.
Current user ID must be a valid user ID in both the monitored and monitoring system.
Current user ID must have permission to access the PSPing page in the monitored system.

Any system that you intend to ping must have an entry in the URL catalog for the PSPing page. The URL must contain PTPERF_TEST for the URL to appear in the ping lists that are associated with the Performance Monitor. For example,

http://server_name/psp/ps[_newwin]/EMPLOYEE/PT_LOCAL/c/UTILITIES.PTPERF_TEST.GBL

Note. In a self-monitoring system, you must append the text "_newwin" to the end of the site name on which you are running the ping test. The "_newwin" indicates to the PeopleSoft system that the content can run in a new window at the same time that content from a different component runs in the previous window.

URL Identifier

Select the URL of the system that you want toping.

Execute PSPing

Click to launch the PeopleSoft Ping page at the URL appearing in the URL Identifier field. The page appears in a new window. If that system is monitored, when you run Ping the system reports the results that are displayed on the Ping page to the monitoring system in the form of Event 600s (PSPING).

View PSPing History

Launches the Event History search page displaying all Event 600 (PSPING) data for the current day on the current system.

Verify that you ping the appropriate system. PeopleSoft runs no internal verification to verify that the system you ping is the system which this page is monitoring.

Viewing Web Server Performance

Access the Web Server page.

The Web Server page displays the most recent performance data that is received from a web server domain monitor. A domain corresponds to the domain that is specified during the PeopleSoft installation.

Domain Name	A domain monitor starts when the first user connects to any site in a PeopleSoft web server domain. The domain name is the name of this site.
Domain Directory	The directory on the web server where the PeopleSoft site that triggered the domain monitor resides.
Filter Level	Appears on pages displaying current performance information that is related to servers, such as application servers, web servers, and so on. Displays the current agent filter level. The colors indicate the following levels: Blue: Standby, Error, and Warning. Green: Standard. Orange: Verbose. Red: Debug. Move the cursor over the icon to show a pop-up message displaying the agent filter level in text format.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always apply to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
Status	Appears only if the system detects stale data. Performance data is stale if no status events have been reported in the last sample interval for the system. For example, Status shows stale data if the web server is not booted.
Host/Port	The host of the web server and the listening ports for HTTP and HTTPS.
Monitor Date/Time	The date and time that the monitoring system inserted the row of performance data into the monitoring database according to the database clock.
Last Page Refresh	Indicates the most recent time that the system refreshed the page either by loading the page into the browser or as a result of a user clicking the Refresh button.
Web Server Snapshot	This link enables you to view historical information snapshots for the current agent. By clicking this link, you see a list of all the domain agent timestamps for the current domain monitor agent Event 150 (JVM Status). After you select a particular timestamp, the system displays the Web Server page containing web server performance information for that particular time. When you are viewing snapshot information, a message appears at the top of the page reminding you that the page contains historical performance data. You can view numerous snapshots using the same method. Note. While viewing snapshots, the Refresh button is not available. To view the most current web server information, you must access the Web Server page using the menu.
System Performance	This link accesses the System Performance page (the home page for system monitoring).

JVM Status

The JVM status applies to the status of the JVM in which the site runs. Multiple web sites within the same PeopleSoft domain can run within the same JVM.

These values are derived from Event 150 (JVM Status). If the latest Event 150 monitor date and time is older than the event sample rate for the current agent’s system, the Stale Data icon appears at the top of the page.

%JVM Memory Used	A JVM has a specific amount of memory allocated to it. This metric displays the percentage of the allocated memory that the JVM is currently using.
Max JVM Memory Available	Indicates the maximum amount of memory that is available for the JVM. This value depends on the Java Runtime Environment (JRE). The maximum JVM memory that is available equals maxMemory – totalMemory + freeMemory.
Sessions in Web-App	Displays the number of servlet sessions in the portal web application.
Execute Threads	The number of threads that are used by the web application to service incoming requests.
Busy Threads	The number of threads that are currently servicing requests.
Domain Count	The number of domain monitors in this web server domain. The domain count will only be greater than 1 if a web server domain has sites belonging to different monitored systems.

The Events and PMUs tab contains links to the Event History, Open PMUs, and Completed PMUs components.

When transferring to the Event History component, the system automatically displays all of the data for the current day’s Event 150 (JVM Status) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system automatically displays all of the data for the current day’s open PMUs for the current host/port and the current system.

When transferring to the Completed PMUs component, the system automatically displays all of the data for the current day’s completed PMUs for the current host/port and the current system.

Network Status

Network status data corresponds to

Output from the domain monitor running the netstat —a command in a shell on the monitored host.
Counters that are maintained by the domain monitor.

These values are derived from Event 151 (Network Status).

If no Event 151 or the Event 151 has an agent date/time that does not match the agent date/time of the Event 150 (JVM Status) shown at the top portion of the page, this grid appears empty.

Time Wait Sockets	The number of sockets in a TCP time wait state on the host on which the web server is running. A high count may mean that the time wait setting for the operating system of the server needs to be decreased, or it may just mean that a very high load is on that server.
Close Wait Sockets	The number of sockets in a TCP close wait state on the host on which the web server is running. A high count means that TCP clients are not closing connections and may indicate network or software configuration issues.
Established Sockets	The number of sockets in a connected state. This is a measure of the number of users who are connected.
Jolt Traffic	Displays in bytes per second the amount of Jolt traffic between the web server and the application server. Note. The Jolt traffic value is zero unless compression is enabled.
HTTP	Indicates the HTTP traffic in bytes per second that is generated by this web server.

The Events and PMUs tab contains links to the associated Event History, Open PMUs, and Completed PMUs.

When transferring to the Event History component, the system automatically displays all of the data for the current day’s Event 151 (Network Status) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system automatically displays all of the data for the current day’s open PMUs for the current host/port and the current system.

When transferring to the Completed PMUs component, the system automatically displays all of the data for the current day’s completed PMUs for the current host/port and the current system.

Sites

The information on this grid applies to all sites on this web server even if they are not monitored sites.

These values are derived from Event 152 (Web Site Status).

If no Event 152 or the Event 152 rows have an agent date/time that does not match the agent date/time of the Event 150 (JVM Status), the grid appears empty.

Site Path	Indicates the directory on the web server where the site resides.
Requests to all Servlets	Indicates the number of requests that have been submitted to all of the servlets running within the site.
Servlet Requests (last minute)	Indicates the number of servlet requests that were submitted to the site in the last minute.
Avg. Request Time (last minute)	Indicates the average duration of the servlet requests that were submitted to the site in the last minute.
Time in all Servlets	Indicates the sum of durations of the servlet requests that were submitted to the site since the web server was last booted.
Current Sessions	The number of sessions that are active within the site. Active sessions are those that are currently waiting for a request to be processed. In most cases, this value is 0. However, if your site is running slowly or a transaction has a long duration, this value is greater than 0.

The Events and PMUs tab contains links to the associated Event History, Open PMUs, and Completed PMUs.

When transferring to the Event History component, the system automatically displays all of the data for the current day’s Event 152 (Web Site Status) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system automatically displays all of the data for the current day’s open PMUs for the current agent and the current system.

When transferring to the Completed PMUs component, the system automatically displays all of the data for the current day’s completed PMUs for the agent and the current system.

Active Servlets

Active servlets are all servlets that are running in the portal web application.

These values are derived from Event 153 (Web Servlet Status).

Servlet Name	Identifies the name of a particular servlet.
Requests to this Servlet	Indicates the number of requests that were submitted to a particular servlet.
Servlet Requests (last minute)	Indicates the number of requests that were submitted to a particular servlet within the last minute.
Avg. Request Time (last minute)	The average duration of the requests that were handled by the servlet in the last minute.
Time in this Servlet	The sum of durations of requests that were handled by this servlet since the web server was last booted.

Viewing Application Server Domain Performance

Access the Application Server Domain page.

The Application Server Domain page displays the most recent performance data that was received from:

An application server domain monitor.
Each active application server agent within that application server domain.

Domain Name	Identifies the name of the current Tuxedo domain.
Domain Directory	Identifies the directory in which the domain is installed.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always applies to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
Status	Appears only if the system detects stale data. Data is stale if no status events have been reported in the last sample interval for the system. For example, Status shows stale data if the application server is not booted.
Host/Port	Identifies the machine name and Jolt listening port of the application server domain.
Application Server Snapshots	This link enables you to view historical information snapshots for the current agent. By clicking this link, you see a list of all the domain agent timestamps for the current agent’s Event 300 (Host Resource Status). After you select a particular timestamp, the system displays the Application Server page containing performance information for that particular time. When you are viewing snapshot information, a message appears at the top of the page reminding you that the page contains historical performance data. You can view numerous snapshots using the same method. Note. While viewing snapshots, the Refresh button is not available. To view the most current information, you must access the Application Server page using the menu.
Monitor Date/Time	The date and time that the monitoring system inserted the row of performance data into the monitoring database according to the database clock.
Last Page Refresh	Indicates the most recent time that the system refreshed the page either by loading the page into the browser or as a result of a user clicking the Refresh button.

See Events That Monitor Resource Usage.

Host Resource Status

The Metrics tab presents the same values that also appear on the System Performance page. The metrics show current resource utilization on the entire host machine, not just the resources that PeopleSoft uses.

The system derives these metrics from the most recent Event 300 (Host Resource Status) for the domain monitor process of that domain.

If the latest Event 300 monitor date or time is older than the event sample rate for the current agent’s system, the Stale Data icon appears at the top of the page.

%CPU Used	Displays the percentage of the CPU capacity being utilized on the host machine.
%Memory Used	Displays the percentage of physical memory being utilized on the host machine.
Hard Page Faults/Second	This is the number of accesses to virtual memory in the last second that require disk reads.
Total Tuxedo Connections	This is the number of connections to this domain, and it is equivalent to the number of rows that are returned by the Tuxedo command pclt (tmadmin), excluding JSH and WSH connections.
Total Tuxedo Requests Queued	The number of Tuxedo requests that are queued on that demand. A high number indicates that insufficient server processes are configured, or that the load on the host machine is too high.

The Events and PMUs tab presents links to the Event History, Open PMUs, and Completed PMUs pages.

When transferring to the Event History component, the system displays all of the data for the current day's Event 300 (Host Resource Status) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system displays all of the data for the current day’s open PMUs for the current host and port and the current system.

When transferring to the Completed PMUs component, the system displays all of the data for the current day’s completed PMUs for the current host and port and the current system.

PQ Event Rows

This section presents the results of the tmadmin pq command (print queue). It enables you to view information that is related to the Tuxedo queues that are used by the server processes running within a domain.

The grid displays all Event 301 (Tuxedo "pq" Row) rows for the current agent with the same agent date or time appearing in the top portion of the page as the Event 300 (Host Resource Status).

Queue Name	Identifies the Tuxedo queue that is associated with a server process.
Server Name	Indicates the server process that is servicing a particular queue.
Server Count	Indicates the number of a particular server process type that are currently running. For example, it indicates that three PSAPPSRV server processes are currently running.
Queue Length	Indicates the current length of the queue, which is measured by the number of requests waiting to be processed. High queue lengths may indicate that more server processes need to be configured to run.

PSR Event Rows

This section presents the results of the tmadmin psr command (print server processes). This command enables you to view information that is related to all the server processes (monitored and unmonitored) running within a domain.

The grid displays all Event 302 (Tuxedo "psr" Row) rows for the current agent with the same agent date or time appearing at the top of the page as the Event 300 (Host Resource Status).

Server Name	Indicates the name of the server process, such as PSAPPSRV, PSMONITORSRV, and so on.
Server Instance ID	This is the instance ID that is assigned by Tuxedo to each server process. This number remains constant across recycles. Even if the PID changes, the instance ID remains constant.
PID	Indicates the operating system process ID on the server.
Total Requests	Indicates the total number of requests that a server process has processed. Tuxedo continues to increment this number for a server instance even if the server recycles.
Current Service	Indicates whether the server process is idle or currently handling a request.

Monitored Servers

This section enables you to view information about the resources that are consumed by the monitored server processes running within a domain.

The grid displays an entry for each active application server agent within the same system and same host and port, and domain directory as the domain monitor agent. For each agent, the system retrieves the latest Event 200 (Resources Per Process) and its metrics are displayed. If no Event 200 exists for a particular agent, the system displays zeros.

The Metrics tab contains the following information.

Server	Identifies the server process being monitored.
Server Instance	This is the instance ID that is assigned by Tuxedo to each server process. This number remains constant across recycles. Even if the PID changes, the instance ID remains constant.
PID	The process ID that is assigned by the server operating system.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always applies to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
%CPU Used	Indicates the percentage of the CPU capacity that a particular server process is using.
CPU Time	The amount of CPU time that the process has consumed.
VM	Indicates the amount of virtual memory that each server process is consuming.

The Events and PMUs tab contains links to the Event History, Open PMUs, and Completed PMUs pages.

When transferring to the Event History component, the system displays all data for the current day’s Event 200 (Resources Per Process) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system displays all data for the current day’s open PMUs for the current agent and the current system.

When transferring to the Completed PMUs component, the system displays all data for the current day’s completed PMUs for the agent and the current system.

Viewing Analytic Server Information

The Analytic Server Summary section in the monitored Application Server Domain page provides generic performance and status information of the analytic Servers running in the application server domain.

Access the Analytic Server Summary page.

Total Configured Servers

The current maximum number of configured analytic servers in the application server domain.

Number Started Servers

The current number of analytic servers, started up and loaded with analytic instances.

Number Free Servers

The current number of analytic servers, started up and free.

Number Loaded Instances Today

Today's total number of analytic instances loaded.

Number Recycled Servers

Today's total number of analytic servers recycled for reuse.

Number Out Servers Today

Today's total number of times that the monitored domain runs out of analytic servers. Each time a client asks to load an analytic instance, a free analytic server gets assigned and dedicated to the analytic instance.

Viewing Process Scheduler Server Performance

Access the Process Scheduler Server page.

The Process Scheduler Server page displays the most recent performance data that is received from:

A Process Scheduler server domain agent.
Each active Process Scheduler server agent within this Process Scheduler domain.

Domain Name	Identifies the name of the current domain.
Domain Directory	Identifies the directory in which the domain is installed.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always applies to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
Status	Appears only if the system detects stale data. Data is stale if no status events have been reported in the last sample interval for the system. For example, Status shows stale data if the Process Scheduler is not booted.
Host/Port	Identifies the machine name of the Process Scheduler server domain.
Process Scheduler Snapshots	This link enables you to view historical information snapshots for the current agent. By clicking this link, you see a list of all the domain monitor timestamps for the current agent’s Event 300 (Host Resource Status). After selecting a particular timestamp, the system displays the Process Scheduler Server page containing performance information for that particular time. When you are viewing snapshot information, a message appears at the top of the page reminding you that the page contains historical performance data. You can view numerous snapshots using the same method. Note. While you are viewing snapshots, the Refresh button is not available. To view the most current information, you must access the Process Scheduler Server page using the menu.
Monitor Date/Time	The date and time that the monitoring system inserted the row of performance data into the monitoring database according to the database clock.
Last Page Refresh	Indicates the most recent time that the system refreshed the page either by loading the page into the browser or as a result of a user clicking the Refresh button.

See Events That Monitor Resource Usage.

Host Resource Status

The Metrics tab presents the values that also appear on the System Performance page.

If the latest Event 300 (Host Resource Status) monitor date and time is older than the event sample rate for the current agent’s system, the Stale Data icon appears at the top of the page.

%CPU Used	Displays the percentage of the Central Processing Unit capacity being utilized on the host machine.
%Memory Used	Displays the percentage of physical memory being utilized on the host machine.
Hard Page Faults/Second	The number of accesses to virtual memory in the last second that require disk reads.
Total Tuxedo Connections	This number is always zero for a Process Scheduler domain.
Total Tuxedo Requests Queued	The number of Tuxedo requests that are queued on that demand. A high number indicates that insufficient server processes are configured, or that the load on the host machine is too high.

The Events and PMUs tab presents links to the Event History, Open PMUs, and Completed PMUs pages.

When transferring to the Event History component, the system displays all of the data for the current day’s Event 300 (Host Resource Status) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system displays all of the data for the current day’s open PMUs for the current host or port and the current system.

When transferring to the Completed PMUs component, the system displays all of the data for the current day’s completed PMUs for the current host port and the current system.

PQ Event Rows

This section presents the results of the tmadmin pq command (print queue). It enables you to view information that is related to the queues that are used by the server processes running within a domain.

The performance data displays all Event 301 (Tuxedo "pq" Row) rows for the current agent with the same agent date and time appearing in the top portion of the page as the Event 300 (Host Resource Status).

Queue Name	Identifies the Tuxedo queue that is associated with a server process.
Server Name	Indicates the server process that is servicing a particular queue.
Server Count	Indicates the number of a particular server process type that are currently running. For example, it indicates that three PSAESRV server processes are currently running.
Queue Length	Indicates the current length of the queue, which is measured by the number of requests that are waiting to be processed.

PSR Event Rows

This section presents the results of the tmadmin psr command (print server processes). This enables you to view information that is related to all the server processes (monitored and unmonitored) running within a domain.

The grid displays all Event 302 (Tuxedo "psr" Row) rows for the current agent with the same agent date and time appearing at the top of the page as the Event 300 (Host Resource Status).

Server Name	Indicates the name of the server process, such as PSAESRV, PSMONITORSRV, and so on.
Server Instance ID	This is the instance ID that is assigned by Tuxedo to each server process. This number remains constant across recycles. Even if the PID changes, the instance ID remains constant.
PID	Indicates the operating system process ID on the server.
Total Requests	Indicates the total number of requests that a server process has processed.
Current Service	Indicates whether the server process is idle or currently handling a request.

Monitored Servers

This section enables you to view information about the resources that are consumed by the monitored server processes running within a domain.

Note. Currently, only PSMONITORSRV and PSMSTPRC are monitored.

The grid displays an entry for each active application server agent within the same system and same host or port and domain directory as the domain monitor agent. For each agent, the system retrieves the latest Event 200 (Resources Per Process) and its metrics are displayed. If no Event 200 exists for a particular agent, the system displays zeros.

The Metrics tab contains the following information.

Server	Identifies the server process that is being monitored.
Server Instance	This is the instance ID that is assigned by Tuxedo to each server process. This number remains constant across recycles. Even if the PID changes, the instance ID remains constant.
PID	The process ID that is assigned by the server operating system.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always apply to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
%CPU Used	Indicates the percentage of the CPU capacity that a particular server process is using.
CPU Time	The amount of CPU time that the process has consumed.
VM	Indicates the amount of virtual memory that each server process is consuming.

The Events and PMUs tab contains links to the Event History, Open PMUs, and Completed PMUs pages.

When transferring to the Event History component, the system displays all data for the current day’s Event 200 (Resources Per Process) rows for the current agent and the current system.

When transferring to the Open PMUs component, the system displays all data for the current day’s open PMUs for the current agent and the current system.

When transferring to the Completed PMUs component, the system displays all data for the current day’s completed PMUs for the agent and the current system.

Viewing Master Scheduler Performance

Access the Master Scheduler page.

This page displays the most recent performance data that wasreceived from a Master Scheduler agent.

Note. The Performance Monitor displays Master Scheduler performance data only if a Master Scheduler has been configured.

System ID	Identifies each monitored system. The PeopleSoft system automatically generates this value incrementally. System definitions are created automatically when the first agent of a monitored system registers with the monitoring system.
Database Name	Reveals the name of the PeopleSoft application database that is running on the monitored system. The monitoring system automatically inserts this value when it recognizes and creates a monitored system.
Agent Date/Time	The date and time according to the agent clock that the domain monitor used when it last sent performance data to the monitor. Note. The date and the time appearing on this page always apply to the system on which the agent runs. Keep this in mind if you are monitoring systems in other time zones.
Status	Appears only if the system detects stale data. Data is stale if it is older than the sample rate for that system. Data is stale if no status events have been reported in the last sample interval for the system. For example, Status shows stale data if the Process Scheduler is not booted.
Monitor Date/Time	The date and time that the monitoring system inserted the row of performance data into the monitoring database according to the database clock
Last Page Refresh	Indicates the most recent time that the system refreshed the page either by loading the page into the browser or as a result of a user clicking the Refresh button.

Process Summary

This process displays the status of the processes that are being managed by the Master Scheduler running on the selected system.

The data in this grid is derived from Event 350 (Master Scheduler Status).

Active Processes	The number of Process Scheduler jobs that are currently processing in this monitored system.
Unused Process Slots	The number of available slots that this Master Scheduler can use to run process requests.
Blocked Processes	A process can be blocked for two reasons: The process is "mutually exclusive" with another process, and the other process is currently running. The process is dependent on a file that another process has yet to create.
Queued Processes	The number of Process Scheduler jobs that are currently waiting to be handled by an available Process Scheduler server.

Servers

The Servers grid contains performance metrics for individual Process Scheduler servers that are running under the Master Scheduler.

This grid displays all Event 351 (Master Scheduler Detail) rows for all active Process Scheduler servers under the current system with the same agent date and time as the latest Event 350 (Master Scheduler Status). The system groups the data by server name and the metrics are accumulated.

Note. If the monitor date and time for an Event 351 is older than the current system’s event sample rate, a Stale Data icon appears at the top of the page.

Server Name

The name of the Process Scheduler server, such as PSNT, PSUNIX, and so on.

The server name is a hyperlink that launches a Server Activity secondary page for that particular server type. The Server Activity page displays all of the individual Event 351 (Master Scheduler Detail) rows. Use the Refresh button on this page to refresh the Processes grid.

Active Processes

The number of jobs that are currently being handled by a Process Scheduler server.

Queue Details

The Queue grid displays the status of the processes that are queued to be processed by the Master Scheduler.

The data is generated from Event 354 (Batch Queue Details) rows for all active Process Scheduler agents in the current system with the same agent date and time as the latest Event 350 (Master Scheduler Status).

Process Type

Displays the type of process that are queued, such as SQR, Application Engine, COBOL, and so on.

Queued Processes

Displays the number of processes that are queued per process type.

Blocked Processes

A process can be blocked for two reasons:

The process is "mutually exclusive" with another process, and the other process is currently running.
The process is dependent on a file that another process has yet to create.

Viewing Open PMUs

Access the Open PMUs page.

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 PSPMTRANSCURR table. When the PMU finishes, the PSPPMSRV flags the PMU for deletion and inserts a matching row into the PSPMTRANSHIST table, which stores completed PMU data.

See Scheduling the Reaper Program.

If an end user is reporting that a PeopleSoft page is slow (displays the "Processing...." message), use the Open PMU page to see where the request has stalled. Search for that user's name 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 don't specify criteria, the page displays all of the open PMUs for the selected system.

User ID	If you want information per user, enter the user ID of the user for which you want to track current PMUs. The user ID prompts against the PSPMOPRDEFN table, which is populated by the Lookup Application Engine program.
Performance Trace Name	You enter the performance trace name to search on currently open PMUs running within a particular trace. If a user has launched a performance trace in the Performance Console, the system labels every PMU that is generated in a business process with a performance trace name. The performance trace name prompts against the PSPMPERFTRACE table, which is populated by the Lookup Application Engine program.
Component	If you want information per component, enter the name of the component for which you want to track completed PMUs. The component prompts against the PSPMPNLGRPDEFN table, which is populated by the Lookup Application Engine program. Note. Searching on component is equivalent to searching on context 1 for application server PMUs.
Market	Select the market that is associated with the component.
PMU Set	Indicates the set to which the PMU definition belongs. A PMU definition set is similar to a message set. To view the complete set of PMU set definitions, select Performance Monitor, Utilities, PMU Definitions. See PMU Definitions.
PMU ID	Identifies the PMU definition within a PMU definition set. To view the complete set of PMU definitions, select Performance Monitor, Utilities, PMU Definitions.
Context 1, 2, 3	PMU metrics contain data that is specific to that PMU. Context values, on the other hand, are common to the entire user request or a specific tier. For example, the component name is stored in a context for all PMU's that are generated by an application server while it is processing that component. The system uses contexts to "flatten" a PMU tree. For example, you do not have to navigate up from a SQL PMU to an ICPanel PMU to see what component generated that SQL statement. In some cases, a parent PMU determines the usage of a child PMU's context fields. In such cases, the context label for the child PMU type is Generic. Use the Context Help button to view the context definitions for a PMU set ID and ID that you've entered. See Context Definitions.
Top Instance	Each PMU that is reported by an agent has a unique instance ID. The instance identifier of the first PMU generated by a particular user request is the top instance. The value of the top instance is then stored with every child PMU within a request. The top instance is the associating value for all PMUs that are generated by the same user request. Use this search field when you already know the top instance of the PMU in which you are interested.
Instance Identifier	Each PMU reported by an agent has a unique instance ID.
Duration >=/<	Specify criteria that is related to the duration of a PMU. The duration is the difference between the current monitor database time and the date and time that the monitor received the open PMU. The system searches for PMUs with a duration greater than or equal to the value that you enter, or less than the value that you enter. The value is in seconds.
Domain Name	Select the application server, web server, or Process Scheduler domain of the agent process that is reporting the PMUs.
Domain Host/Port	Select the host name and port number of the application server, web server, or Process Scheduler domain from which the PMUs were reported.
Agent ID	Select the agent that reported the PMUs.
Agent Type	Select agent type, such as PSAPPSRV, PSQRYSRV, or PSQCKSRV, that reported the PMUs.

Note. Some of the metrics for various PMUs don’t have values until the PMU finishes, so in some cases, metrics may appear with no values.

Open PMUs

The following information appears on the Summary tab.

PMU	Displays the label for that PMU type.
Duration	Displays the duration of the PMU.
PMU Details	The string that is generated by concatenating all of the contexts and metrics that are selected for display in the PMU definition.
User ID	Identifies the user whose request generated the PMU.
Action	The action could be Start or Update. Every PMU has a start, which refers to a request initiating the PMU. The update action applies to long running PMUs, which the Performance Monitor updates periodically with the latest metric values.
Monitor Received Date/Time	Indicates when the monitor system received notification that a PMU had been started or updated.
Agent Start Date/Time	Indicates that time according to the agent clock that the last update was generated.

The Identifiers tab presents the following additional information.

PMU Set	Indicates the set to which the PMU definition belongs. A PMU definition set is similar to a message set. To view the complete set of PMU set definitions, select PeopleTools, Performance Monitor, Administration, Meta-data, PMU Definitions.
PMU ID	Identifies the PMU definition within a PMU definition set. See PMU Definitions.
Agent ID	Identifies the agent that reported the PMU information.
Domain Name	The domain from which the PMU was reported.
Monitor Last Update Date/Time	The monitor date and time of the most recent event of a specific event type that was received from a specific agent.
Agent Last Update Date/Time	Indicates that time according to the agent clock that the last update was received.
PID	The operating system process ID of the process that generated the PMU.
Instance	PMU instance ID. Each PMU has a unique instance ID.
Parent Instance	The instance ID of the parent PMU.
Top Instance	Each PMU that is reported by an agent has a unique instance ID. The instance identifier of the first PMU that is generated by a particular user request is the top instance. The value of the top instance is then stored with every child PMU within a request. The top instance is the associating value for all PMUs that are generated by the same user request.

The Contexts tab displays the context information that is associated with a particular PMU.

The Metrics tab displays the metric information that is associated with a particular PMU.

Viewing Open PMU Trees

Access the Open PMU Trees page.

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 details.

The shaded text flags the node of the currently processing PMU.

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.

If you have an open PMU tree that was captured using the standard agent filter mode, you can drill down to the detail of PMU 400 (Tuxedo Service PCode and SQL). The Current SQL statement shows what has been submitted to the application server. This can aid in troubleshooting long-running SQL or a hung query without increasing the agent filter and asking users to repeat the process. If the open PMU finishes, then the PMU row is marked for deletion by the reaper program. You can't access the current SQL statement if the PMU has finished.

Note. So that the presentation of PMU information is readable and manageable, if a PMU is older than a day, the system displays the date that the PMU ran, not its duration in milliseconds.

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	Enter the user ID of the user who is initiating the PMUs. You must specify a user ID to view open PMU trees.
Total Trees received	The number of currently open PMU trees for the user. Corresponds to the number of open requests for this user.
Currently displaying	Indicates the PMU tree that is currently displayed on the page, providing orientation in a list of returned PMU trees.
Previous Tree/Next Tree	Enables you to navigate within a list of PMU trees.
Open PMU Tree	You can expand or collapse PMU trees by using the folder icon to the left. Click a node to view details regarding that PMU. Use the Left and Right links to navigate within a single tree when the tree is 20 nodes deep.

Viewing Current User Sessions

Access the Current User Sessions page.

A row appears for every PMU 109 (user session began) that was received in the last 12 hours for which a matching PMU 108 (user session ended) has not been received.

Note. If you recycle the web server during this time, the user session is considered closed.

The Session tab contains the following information.

User ID	Identifies the user.
Session ID	Indicates the open session on the web server that is associated with the user.
Monitor Received Date/Time	The date and time that the monitoring system inserted the row of performance data into the monitoring database.
User History	Accesses the User History page. See Viewing User Session History.

The Details tab contains the following additional information.

The latency and user agent data is derived from PMU 116 (redirect after login) with the same session ID (context 1) as the associated PMU 109 (user session began).

IP Address	Indicates the IP address of the machine that the user is using to connect to the PeopleSoft system.
User Agent	The Mozilla user-agent string specification for the user's browser.
Latency	The duration of PMU 116 (redirect after login). The latency value enables you to infer the network latency for a user connection.

Viewing Recycled Processes Diagnosis

The Recycled Processes Diagnosis page is used to determine the causes of application server recycles. Specifically, it can determine what kind of server request was received by application server processes before a restart occurred.

Access the Recycled Processes Diagnosis page.

Events That Monitor Resource Usage

This section provides additional information that may help you to interpret the information that Performance Monitor provides that is related to the events reporting resource usage on host machines. These events are:

Event 150 (JVM Status).
Event 151 (Network Status).
Event 200 (Resources Per Process).
Event 300 (Host Resource Status).
Event 301 (Tuxedo "pq" Row).
Event 302 (Tuxedo "psr" Row).

These events report the usage of machine resources (CPU, memory, network, and so on). These events, except for Event 150 (JVM Status), make calls to external APIs (often specific to the operating system) to retrieve metric information. The monitored system sends each event at the sampling interval that is specified for that system.

Working with Event 150 (JVM Status)

This event applies only to web servers.

This event does not make calls to any operating system-specific API.

Working with Event 151 (Network Status)

This event applies only to web servers.

For Event 151 (Network Status) the system launches a separate executable from Java that invokes the "netstat –n" command. On UNIX, the command runs in a separate shell. When the command finishes, the process ends. PeopleSoft does not run "netstat" with an interval argument.

Warning! On some platforms the "netstat" command can require up to a minute (or more) to finish. If the sampling interval is shorter than the time required for the command to complete, "netstat" commands will be running continuously.

Working with Event 200 (Resources Per Process)

This event applies to the application server and the Process Scheduler server.

The PeopleSoft system makes specific operating system calls to obtain metrics for %CPU that are used by the process, CPU time consumed, virtual memory size, and working set size. Operating systems have slightly different definitions for these quantities and different ways of reporting them. For instance, "working set" memory is a Windows term; "resident set" is the UNIX equivalent. PeopleSoft strives for consistency across platforms. For example, PeopleSoft expresses %CPU within a range from 0 to 100 on all machines even though some vendors scale to N*100% if multiple CPUs (N CPUs) exist.

Microsoft Windows, Tru64, and Linux compute one or more resources as an average of the two measurements at the beginning and end of a sampling interval. On these platforms, the Performance Monitor does not report an Event 200 (Resources Per Process) until the second sampling interval after you boot a server.

Process resource utilization is usually sampled by the operating system and written to a memory location. Windows writes to the registry, while UNIX writes to various files. The system reads the current values for the process, so events change only when the operating system updates the statistics. Most operating systems update these statistics at least once per second.

PeopleSoft obtains all information using lightweight, C++ programmatic APIs. No additional processes or shell commands are run.

Operating System	Description
Windows	Performance Monitor uses Performance Data Helper (PDH) to read registry counters. The information is identical to the Windows Performance Monitor tool. When multiple copies of a process, such as PSAPPSRV, are running, registry counters are assigned arbitrarily. For example, counter 1 and counter 2 can reverse their process assignment when a process reboots. Performance Monitor corrects for this. CPU utilization is "% Processor Time," defined as the fraction of time that the process spends in kernel + user during the last PDH sampling interval (typically one second). Process time is kernel + user, accurate to 1 millisecond. Virtual memory is "Virtual Bytes." Working set memory is "Working Set," which is the same as "Mem Usage," displayed by the Windows Task Manager.
AIX	Performance Monitor reads the psinfo files, which is the same source of information that AIX uses for its "ps" command. CPU utilization is the same as "ps -o pcpu" or the %CPU from "ps v". AIX defines it as a lifetime average: total CPU time that is consumed by the process divided by total time that the process has been running. Process time is system + user, excluding children. Accurate to 10 milliseconds. Virtual memory is the same as "ps -o vsz", or the 1024 * SIZE field from "ps v". Resident set memory is the same as the 1024 * RSS field from "ps v".
HPUX	Performance Monitor reads pst_status using pstat_getproc. CPU utilization is the same as "top" divided by the number of CPUs (on HPUX "top" shows utilization of a single CPU). Process time is system + user, excluding children. Virtual memory is the same as the SIZE field from "top". Resident set memory is the same as the RES field from "top".
Linux	Performance Monitor reads ps information from /proc files. CPU utilization is the same as "top" divided by the number of CPUs (on Linux "top" shows utilization of a single CPU). It is the average utilization over the last sample period. Process time is system + user, excluding children, and accurate to 10 milliseconds. The times for all threads in the process are added together. Warning! Linux kernel 2.4 tracks only the process time of each thread. PeopleSoft searches the /proc directory to find all threads and report the total time of the process. However, on a production system with thousands of threads, accumulating this information may take up to a second of CPU time. Virtual memory is the same as "ps -o vsz" (not visible in "top"). According to the man pages, it counts just text, data, and stack. Resident set memory is the same as "ps -o rss" (not visible in "top"). This value includes just text, data, and stack.
Solaris	Performance Monitor reads psinfo files, which is the same source of information that Solaris uses for its "ps" command. CPU utilization is the same as "top". Solaris computes a moving average with exponential weighting. Process time is system + user, excluding children, and accurate to 10 milliseconds. Virtual memory is the same as "ps -o vsz" or the SIZE field from "top". Resident set memory is the same as "ps -o rss" or the RES field from "top". On Solaris, shared libraries are counted in RES but not in SIZE.
Tru64	Performance Monitor reads psinfo files using the ioctl API. CPU utilization is the same as "top" and "ps", divided by the number of CPUs (on Tru64 each process shows utilization of a single CPU). Tru64 computes a moving average over a period of just a few seconds. PeopleSoft displays utilization measured by CPU time consumed over the last sample period. Process time is system + user, excluding children, and accurate to 10 milliseconds. Virtual memory is the same as "ps -o vsz" or the SIZE field from "top". Resident set memory is the same as "ps -o rss" or the RES field from "top." On Tru64, shared libraries are counted in RES.
OS/390	The only metric that is supported in the current release is Process Time.

Working with Event 300 (Host Resource Status)

This event applies to the application server and the Process Scheduler server.

Performance Monitor makes specific operating system calls to obtain metrics for %CPU use on the host machine, %Memory use, and the hard page fault rate. Operating systems have slightly different definitions for these quantities, and they have different ways of reporting them. In most cases, PeopleSoft expresses %Memory use to reflect utilization of physical memory.

Performance Monitor programmatically queries the Tuxedo management information base (MIB) for total Jolt connections and total requests queued. All platforms compute one or more resources as an average of the two measurements at the beginning and end of a sampling interval. Performance Monitor does not report an Event 300 (Host Resource Status) until the second sampling interval after you boot the server.

PeopleSoft obtains all information using lightweight, C++ programmatic APIs. No additional processes or shell commands are run.

Operating System	Description
Windows	Performance Monitor uses Performance Data Helper (PDH) to read registry counters. The information is identical to the Windows Performance Monitor tool. CPU utilization is "% Processor Time (_Total)", defined as the fraction of time not run by the system idle thread in the last PDH sampling interval (typically one second). Memory utilization is "% Committed Bytes In Use" and will change if the paging file is extended by the system administrator. Page faults is "Pages / sec", which reports actual disk page fetches ("Page Faults /sec" reports soft faults).
AIX	Performance Monitor uses libperfstat API (a wrapper for knlist) to read kernel counters. CPU utilization is the same as "topas" and "vmstat". This is an average over the last sample period, but process CPU use is an average over process lifetime. Therefore, on AIX, it is possible for machine CPU use to be momentarily smaller than CPU use of a process that was previously CPU-intensive. Memory utilization is defined as "free real pages" / "total real memory pages". The "vmstat" command shows the number of free pages, but not the available total. The "topas" field, Real MEMORY, shows "real memory pages." The PAGING SPACE field shows only reserved pages, not free pages. Page faults is the same as "topas" and "vmstat", with the absolute difference averaged over the last sampling time. According to Linux information, this value includes pages faults that do not cause paging activity.
HPUX	Performance Monitor uses pstat_getdyamic (pstat) to read kernel counters. CPU utilization is the same as "top" and "vmstat". This is an average over the last sample period, but process CPU use is an average over a longer time period. Therefore, it is possible on HPUX for machine CPU use to be momentarily smaller than CPU use of a process that was previously CPU-intensive. Memory utilization is defined as "real memory + text pages / physical memory." Neither of these quantities are exposed with vmstat. Page faults is the same as "vmstat -s, zero fill page faults", with the absolute difference averaged to a rate over the last sampling time.
Linux	Performance Monitor reads kernel statistics from files in /proc. CPU utilization is the same as "top", averaged over all processors. This is an average over the last sample period. Memory utilization is the same as "top", or the "free" command "Mem used / (av)ailable" field. It measures physical memory utilization. The "used" field is actually "available - free". The "M" and "K" units of "top" are 1024 * 1024 bytes and 1024 bytes, respectively. Page faults is the first "page" kernel counter from /proc/stat (pages swapped in from disk), with the absolute difference averaged to a rate over the last sampling time.
Solaris	Performance Monitor uses the Kernel Statistics API (kstat) to read kernel counters. CPU utilization is the same as "top, user + kernel". This is an average over the last sample period, but process CPU use is a weighted average over a longer time period. Therefore, it is possible on Solaris for machine CPU use to be momentarily smaller than CPU use of a process that was previously CPU-intensive. Memory utilization is defined as the "used / used + available" fields from "swap -s". This is only an approximation because of allocated but unreserved RAM. See the Sun web site for more information. Page faults is the same as major page faults from "vmstat -s", with the absolute difference averaged to a rate over the last sampling time.
Tru64	Performance Monitor uses the table API (table) to read kernel counters. CPU utilization is the same as "top, user + nice + system". This is an average over the last sample period. Memory utilization is the same as "top, Real Memory", also same as "vmstat -P, Managed Pages, (active + ubx) / Total". To convert to the "M bytes" of "top", multiply by getpagesize and divide by 1024 * 1024. Page faults is the same as zero fill page faults from "vmstat -s", with the absolute difference averaged to a rate over the last sampling time.
OS/390	Performance Monitor uses the ERBSMFI and CVT APIs to report resource use on the logical partition. Higher priority jobs on other partitions can "steal" resources and not appear in these metrics. CPU utilization is the same as RMF "TOTAL/AVERAGE LPAR BUSY TIME PERC" field. Memory utilization is defined from the RMF "AVAILABLE" versus RMF "TOTAL FRAMES" fields. Page faults is not supported for this release.

Working with Event 301 (Tuxedo "pq Rows)

This event applies to the application server and the Process Scheduler server.

The system programmatically queries the Tuxedo management information base (MIB) for the status of each queue.

Working with Event 302 (Tuxedo "psr" Rows)

This event applies to the application server and the Process Scheduler server.

The system programmatically queries the Tuxedo management information base (MIB) for the status of each server. Only PeopleSoft servers appear as Performance Monitor events; the BBL is not reported.

User Response	Displays the average amount of time that end users waited for server round trips to finish. A user is waiting for a server round trip to finish when Processing appears in the upper, right-hand corner of a PeopleSoft page. Note. This average does not include network latency. It is the average duration of all top-level PMU 101s (PIA Request) that the monitoring system has received since midnight.
Jolt Request	Displays the average and standard deviation of all PMU 115s (Jolt Request) received since midnight.
Application Server	Displays the average and standard deviation of the duration of all PMU 400s (Tuxedo Service PeopleCode and SQL Summary) received since midnight.
SQL	Displays the average and standard deviation for the time spent running SQL statements that were initiated from PeopleCode in a single application server request. This value includes the time that was required for SQL Prepare, Execute, Fetch, and Commit. PeopleCode SQL statements are run by application code that is written using PeopleCode and submitted to the database by way of SQLEXECs or SQL Objects. This value is derived from metrics 2, 3, and 4 from PMU 400 (Tuxedo Service PeopleCode and SQL Summary). Namely, this value includes PeopleCode SQL, PeopleCode Built-in SQL, and PeopleTools SQL. Note. This is the average time spent for running all SQL statements of these types in a single application server request. The system calculates this value using all data that has been received since midnight.

Total Configured Servers	The current maximum number of configured analytic servers in the application server domain.
Number Started Servers	The current number of analytic servers, started up and loaded with analytic instances.
Number Free Servers	The current number of analytic servers, started up and free.
Number Loaded Instances Today	Today's total number of analytic instances loaded.
Number Recycled Servers	Today's total number of analytic servers recycled for reuse.
Number Out Servers Today	Today's total number of times that the monitored domain runs out of analytic servers. Each time a client asks to load an analytic instance, a free analytic server gets assigned and dedicated to the analytic instance.