Request Summary 

Use

Contains the most important performance data for the portal server is shown here, collected in different categories.

You can find detailed information about the individual requests, components, and threads by selecting the corresponding entries in the detailed navigation for Portal Monitoring.

Features

The following data is displayed for the portal server by default:

·        Accumulated Amount of Outbound Data [bytes]

·        Time for All Requests [msec]
(Total time needed to process all requests in the backend system)

·        CPU Time for All Requests
Total CPU time needed to process all requests in the backend system [msec]

·        Average Amount of Outbound Data per Request [bytes]

·        Average Number of Component Calls per Request

·        Average Time of a Request [msec]
(average time needed to process a request in the backend system)

·        Average CPU Time of a Request
Average CPU time needed to process a request in the backend system [msec]

·        Number of Calls with Outbound Data

·        Number of Component Calls for all Requests

·        Number of Requests since First Request

·        Requests per Second

·        Time Stamp of Last Reset
(Time when the data set was restarted)

·        Time Stamp of First Request
(Starting time of monitoring)

With these values, 0 bytes can also mean that data was passed, but performance monitoring was not informed of this fact by the programming interface.

Activities

Selecting a Portal Server

·        In the Select Server dropdown list, select the portal server and choose Display.

Deleting Statistics Data

You can delete the existing data of the requests and components on a selected Portal server or on all the servers in your cluster environment by choosing Reset. This action restarts the set and the data evaluation.

Displaying the Instrumentation of Custom Portal Components

...

       1.      In the option menu of the iView, choose Personalize.

       2.      In the Display Instrumentation Columns dropdown list, select yes.

       3.      Choose Save All Changes.

The following columns are added to the table:

·        Number of Requests Handled Correctly
(correct instrumentation)

·        Number of Requests in which some Components are not Correctly Closed
(e.g. loops)

·        Number of Requests which are Closed because of Too Many Components
(Number of requests that contain too many components due to incorrect instrumentation)