eG Monitoring
 

Measures reported by PepAppServiceTest

Server processes invoke services to perform application logic and issue SQL to the RDBMS. When a PeopleSoft application sends a request to the application server, it sends a service name and a set of parameters, such as MgrGetObject and its parameters. Tuxedo then queues the transaction request to a specific server process that is designed to handle certain services. When a server process boots, it advertises to the system the predefined services it handles.

If the server process is down or is not ready to handle any requests, then all services it handles will also be unavailable; this can severely hamper request processing by the server. Moreover, if even a single service processes requests slowly, user experience with the application server will be adversely impacted. Using the PepAppServiceTest, administrators can quickly detect such anomalies and initiate measures to correct them, so that requests are serviced promptly. Additionally, the test also periodically reports the count of requests handled by each service, thus highlighting the most popular/busiest services delivered by the application server domain.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Status Indicates the current status of this service.   The values that this measure can report and their corresponding numeric values are discussed in the table below:

Measure Value Numeric value
Available 100
Not Available 0

Note:

By default, this measure reports the Measure Values mentioned above to indicate the current state of a server. The graph of this measure however, represents the same using the numeric equivalent only.
Avg_queue_length Indicates the average length of this queue. Number A consistent rise in the value of this measure is a cause for concern, as it indicates that this server process is not able to process the requests in this queue quickly. Under such circumstances, you may need to add more instances of that particular server process to improve its processing capability.
Request_handle Indicates the number of requests handled by this service since the last measurement period. Number A very high value could indicate that the service is overloaded with requests. You can compare the value of this measure across services to know which services have the maximum number of requests; this way, you can find out which services are most popular or are the busiest.
Request_rate Indicates the rate at which requests were handled by this service. Requests/Sec A consistent dip in the value of this measure is a cause for concern as it indicates that the service is unable to process requests quickly. This could hint at a processing slowdown.