Logging and Monitoring

Various components, applications and services are shipped with the portal. There are various monitoring and log applications available for monitoring these objects. These applications check and monitor the portal in the background. Applications such as performance monitoring and activity tracing provide information about the status and help locate critical system events. You can use the information delivered by the monitoring, logging, and tracing applications to analyze the system and take appropriate action where necessary.

The portal is installed as an application on the AS Java. Therefore, to understand the monitoring methodology and tool availability, see the section AS Java.

The following list provides information on monitoring and logging functions and tools that you can use. Some functions are supported by multiple tools.

Monitoring

Function	Description	Call
Monitoring with the Generic Request and Message Generator (GRMG)	You can check the availability of portal back-end 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 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.	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.	NetWeaver Administrator – System Management Monitoring Java System Reports Report: Monitor Browser . Portal: For displaying configuration parameters of the PCD: System Administration Support Support Desk . Click 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 .
Monitoring Using JMX	The J2EE Engine monitoring framework provides different monitors that you can use to monitor aspects of the portal in CCMS. For more information about JMX Monitors in CCMS, see Alert Monitor.	Choose Tools CCMS Control Data/Monitoring CCMS Monitor Sets or use Transaction RZ20. In the tree of the CCMS monitor sets under the Portal node, you can access the following monitor nodes: Configuration Portal Runtime String Buffer Pool Portal Runtime Cache
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. Note When using the Activity Report service, the overhead on CPU consumption is up to 10%. You may want to take this into consideration when sizing your system. You can disable the Activity Report service, as follows: Login with the administrator user. Go to System Administration System Configuration Service Configuration , and select the service called `com.sap.portal.activityreport.core` Change the field Activate portal activity report to false, and save the configuration. Restart the service. End of the note.
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 .

Logging and Tracing

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. By default, trace severity is set to Error.

For information about trace locations, see Logging.

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 AS Java, consisting of the Log Manager, and Log Configurator Service.

For information about log categories, see Logging.

Recommendation

Log files enable you to track possible unstable conditions of the portal during development and testing stages. An out-of-the-box portal installation includes various log files containing portal runtime information.

By default, log file severity is set to Info. In a production environment, these log files engage portal resources, and affect overall performance. Therefore, we recommend that you reconfigure the log settings level to Error.

To change SAP AS Java and Portal log and trace severity levels:

Open the SAP NetWeaver Administrator.
Choose System Management Configuration Log Configuration .
From the Show dropdown box, select Logging Categories or Tracing Locations.
For the ROOT CATEGORY/System or ROOT LOCATION/System row, in the Severity column, choose ERROR.
In order for this severity level to be valid for all child log controllers, choose Copy to Subtree.
Choose Save Configuration.
The columns Minimum Severity in Subtree and Maximum Severity in Subtree are automatically set accordingly.

End of the recommendation.