Function

Description

Call

Monitoring with the Generic Request and Message Generator (GRMG)

You can check the availability of portal backend systems, portal servers as well as cluster nodes and URL links.
A prerequisite is the Setting Up GRMG Monitoring of the Portal Infrastructure.

CCMS:
Transaction RZ20 ® SAP CCMS Monitor Templates, ® Availability and Performance Overview.
The availability is displayed in sub-tree GRMG-Tested Availability (Web Components).

Performance Monitoring

The performance monitoring functions give you an overview of the current system and application-specific data of the running portal on a Java Virtual Machine. With this – partially computed – data you can identify areas that cause performance problems. The data is based on the Java Application Response Time Measurement. The performance monitoring functions handle all instrumented portal server requests.

Request Summary
Contains the most important performance data for a portal server, accumulated according to different categories.

Request Overview
Contains an overview of the requests that have the greatest effect on performance.

Component Overview
Contains an overview of the individual components that have the greatest effect on performance.

Thread Overview
Contains an overview of the threads currently being used.

Visual Administrator:
Server ® Services ® Performance Tracing  ®  Runtime ® JARM

Portal:
System Administration ® Monitoring ® Portal

CCMS:
SAP J2EE Monitor Templates ® Engines ® <your system> ® Performance

For performance reasons, not all of the available data is displayed in the CCMS.

Parameter Reporting

You can display the configuration parameters of the Portal Runtime (PRT) and the Portal Content Directory (PCD). You can also check if all the necessary services and filters have been loaded.

Visual Administrator:
Server ® Services ® Monitoring. On tab MonitorTree select Root ® Services ® Portal.

Portal:
For displaying configuration parameters of the PCD: System Administration ® Support ® Support Desk. Click on the Portal Content Directory area and then on the Pcd Configuration tool.

For displaying configuration parameters of the PRT: System Administration ® System Configuration ® Service Configuration. Select Central Configuration in folder Portal Runtime, click with the alternate mouse button, and choose Configure.

CCMS:
SAP J2EE Monitor Templates ® All Systems ® <System_Name> ® J2EE Engines ® <Instance_Name> ® Services ® Portal.

Portal Activity Report

With this function you can create the statistics about user activities (what content they are using – iViews or pages). You can display the following information in a portal activity report:

●     Information and visualization about the number of user logons during a given period of time.

●     Information about the portal users who are logged on.

●     Information about the number of users who viewed certain pages and iViews.

You must have installed and configured the function as a prerequisite.

Portal:
Display in the iView you created for the portal activity report.

User Overview

The user overview service gives you a list of the logon and logoff data (time stamp). You can view detailed information there about the users that are logged on and end user sessions.

Visual Administrator:
Security Provider Service ® Runtime ® Login Sessions.

Activity Tracing

You can sequentially record the activities of individual portal users for a defined time span and then analyze the performance and errors for these activities. Activity tracing is activated and deactivated in the Visual Administrator for a given user or for all users.

Visual Administrator:
Activate or deactivate with
Server ® Services ® Performance Tracing ® Runtime ® Trace Config

Log Viewer:
Display and analyze the data (SAT Trace Format).

Logging

The portal is logged using the standard central logging system of the J2EE Engine, consisting of the Log Manager, Log Configurator Service  and Log Viewer.

Log Viewer:
You can centrally view and analyze all the log data of the portal, the data from activity tracing, and the log data of the J2EE server.