Performance Monitoring
The performance monitoring functions give you an overview of the data that is specific to the current system and application in the running portal on a Java Virtual Machine. With this data, some of which are averages, you can identify the areas that are causing performance problems. The performance monitoring functions handle all instrumented portal server requests.
A request normally consists of a number of components and subcomponents that can also be nested. The threads can only be evaluated if all the components and subcomponents of a request run in the same thread.
In a cluster environment, the portal applications run in different cluster nodes. The portal monitoring functions give you an overview of the system status for each portal server. It is not possible to get a complete overview of the requests of all the portal servers at the same time on the user interface of the portal.
The performance
monitoring functions are implemented in the portal as components.
Alternatively you can display the data, in the Visual Administrator of the
J2EE Engine or in the CCMS. For more information see
JARM Runtime
Views.
You can start the following performance monitoring functions with System Administration → Monitoring → Portal:
●
Request Summary
Contains the most important performance data for a portal server accumulated
in different categories (for example, total amount of outbound data or total
time for all requests).
●
Request Overview
Contains an overview of the requests which have the greatest effect on the
performance, including detailed information about the components
involved.
●
Component Overview
Contains an overview of the individual components (independent of the
corresponding requests) which have the greatest effect on the
performance.
●
Thread Overview
Contains an overview of the threads currently being used. The active threads
and the components currently involved are displayed.

In all functions, times are specified in milliseconds, and data quantities are specified in bytes.