Request Overview 

Use

Contains an overview of the completed requests of a portal server in the cluster that had the greatest effect on the performance.

A request can consist of a number of components and subcomponents. The requests are listed in the overview with their names. By clicking on this name you get detailed information about all the components involved and their hierarchy within the request.

The names of the components are defined according to the following convention:

<solution>:<component>:<localization>

<solution>:<component>:<details>    (for actions)

Component name EP:UM:getUser
indicates that the action„get user data“ was executed when component User Management logged onto the portal.

For greater readability, the request and component names are displayed in abbreviated form. The full names are shown in the Quick Info text. If you click on a table cell with the request or component name, the full name is displayed in the lower part of the iView.

Features

The following request data is displayed:

·        Starting Time / Starting Date

·        Request Name

·        User ID
ID of the user who started this request

·        Outgoing Data [byte]

·        Time
Time needed for processing in the corresponding backend system

·        CPU Time
CPU time needed for processing in the corresponding backend system

·        Component Entries
Number of components in this request. Components that are used more than once are counted more than once.

·        Component with the Largest Net Time
The „slowest“ component. The net time of a component is the gross time of the component less the gross time of their subcomponents.

·        Largest Net Time
Time for the component with the longest net time

·        Component with Largest Net CPU Time
The “slowest“ component. The net CPU time of a component is the gross CPU time of the component less the gross CPU time of their subcomponents

·        Net CPU Time
Net CPU time for the component [msec]

A value of 0 bytes for the amount of outbound data means that no data was transferred.
A value of n/a indicates that it is not possible to specify a value.

Activities

Selecting a Portal Server

In the Select Serverdropdown list, select the portal server in the cluster and choose Display.

Defining Sorting

As a default, the requests are listed sorted in descending order of the time needed for processing in the backend system each time the page is called.
To sort the requests in descending order by the amount of outbound data:

·        In the Sorted By dropdown list, select Outbound Data and choose Display.

The requests are displayed sorted by the amount of outbound data. This is limited by the value specified in the page personalization.

Filtering the Display

By default, the requests are listed unfiltered (all items) each time the page is called. You can filter the list individually by:

...

       1.      Selecting only items where  ,

       2.      Selecting or entering the desired filter criteria   and

       3.      Clicking on Display.

The requests are then displayed in filtered form and sorted as you requested.

Displaying Detailed Information about a Request

You can find detailed information about a request by clicking on the request name. Under Executed Components, all components in this request (main component including ins subcomponents) are displayed with the following information:

·        Component Name
Name of the main component or subcomponent

·        Gross Time of Component
Total time for component (including time for all subcomponents involved)

·        Gross CPU Time
Gross CPU time for the component [msec]

·        Net Time of Component
computed from gross time less the gross time of the subcomponents

·        Net CPU Time
Net CPU time for the component [msec]

·        Starting Time / Starting Date

·        Nesting Level
Nesting level of 0 corresponds to the main component, nesting level of 1 means that this component was called by the main component, etc.

To return to the previous display variant, choose Display or define new sorting and/or filter criteria.

Adjusting the Number of Displayed Requests

By default, a maximum of 15 requests are displayed, corresponding to the sort and filter criteria. To change this number:

...

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

       2.      In the field Number of Displayed Requests, enter the correct value (1 to 100).

       3.      Choose Save All Changes.

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 Status of Request column is displayed in the Request Overview.

If the request was handled correctly, OK is displayed.