Component Overview 

Use

Contains an overview of the portal components running in the cluster node that have the largest load on the resources. The components are displayed without taking the corresponding requests into consideration.

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 information is displayed for the individual components:

·        Component Name
Name of the main component or subcomponent

·        Number of Calls
 in total for all requests

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

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

·        Net Time
Total time for all calls, computed from their gross time less the gross time of the subcomponents

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

·        Amount of Outbound Data
Total for all calls

·        Average Gross Time
Average total time of the components for all calls

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

·        Average Net Time
Average net time of the components for all calls

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

For all the data, a value of n/a means that you cannot define a value.
A value of 0 means that the time measured was extremely short.
However, the measured value is not displayed because of the error tolerance for imprecise measurement in the operating system.

Selecting a Portal Server

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

Defining Sorting

As a default, the components are sorted in descending order of the Number of Calls each time the page is called. You can also sort the list of components by average gross time, average net time, or average amount of outbound data.

...

Filtering the Display

As a default, the components are listed unfiltered (Show all items) each time the page is called (to correspond with default sorting and limited to the number defined in the page personalization). 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.

Adjusting the Number of Displayed Components

By default, a maximum of 15 components are displayed corresponding to the sorting and filter criteria. You can adjust this display to your requirements using page personalization:

...

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

       2.      Enter the required value in the Number of Displayed Components field (number must lie between 1 and the selected number of components on which the evaluation is based).

       3.      Choose Save All Changes.

Adjusting the Number of Components on Which Evaluation is Based

As a default, 500 components are used as the basis for the evaluation, depending on the selected sort and filter criteria. To change this number:

...

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

       2.      In the Number of Components to Select From field, enter the required value (number must lie between 1 and 5000).

       3.      Choose Save All Changes.

Selecting a small number will improve the performance of the portal monitoring functions.

Displaying the Instrumentation of Custom Portal Components

...

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

       2.      In the Display Instrumentation Columns field, enter yes.

       3.      Choose Save All Changes.

The columns Calls Closed Correctly (number) and Calls with Subcomponents Closed Correctly (number of calls containing a subcomponent that ended correctly) are also shown in the Component Overview.

Example

Calling the component overview tells you if a component only created a time load once, or if the component is generally slow and reduces system performance. A component can, for example, be slow the first time it is called. If it is called repeatedly, the net time will generally be shorter because data is kept in the cache.

If you sort the slow components by their average net time and the average net time is approximately the same as in the first call, the component will generally reduce performance. In custom components you should check the program coding in such cases.