Monitoring Logging and Tracing the EP 6.0 SP2

© SAP AG 2003, Title of Presentation, Speaker Name / 1

Monitoring, Logging and Tracing the EP 6.0 SP2


Course Structure

EP 6.0 PortalIntroductionStarting & Stopping J2EE and EPMonitoring, Logging & TracingSupport DeskConfiguration ManagementIncident and Problem ManagementChange ControlSoftware Change ManagementBackup & RecoveryOperations HandbookIntroduction to CCMSEP Monitoring InfrastructureComputing Center Management System Solution Manager


Monitoring the Enterprise Portal 6.0

Overview

EP 6.0 Portal

Introduction

Monitoring Objects

SAP J2EE specific monitoring features

Portal specific monitoring features

Application specific monitoring features

Archiving Logs



ContentsMonitoring ObjectsLogging and Tracing in SAP J2EE EngineVisual AdministratorConfig ToolLog ViewerPortal specific monitoringApplication specific monitoringArchiving Logs

ObjectivesAt the end of this unit, you will be able to:

Identify the Enterprise Portal monitoring objectsExplain and use the logging and tracing of the SAP J2EE EngineExplore how to use standard monitoring toolsMonitor and analyze J2EE, Portal and Application specific data Explain the archiving mechanism for log messages


Introduction

A typical SAP solution such as Enterprise Portal at customer site:

• Has many hardware and software components.

• Has many interfaces.

• Has business processes that span multiple components.

• Is complex

What does an administrator have to check?

• Are all components available?

• Are transactions performed with sufficient performance?

• Are all interfaces working properly?

• If a problem occurs: What is the cause of it? How can it be resolved?

• Are yesterday’s backups complete and usable?

• …


Introduction

An administrator’s nightmare:

• Performance of crucial transactions is very low.

• Main components become unavailable.

• Business processes are delayed.

Action required:

• Locate the problem.

• Find out its cause.

• Tackle the problem.

• Prevent this from happening again.


Terms and Definitions

MonitoringDisplay of the status, availability, performance, configuration, etc. of the system and individual components.

LoggingRegular output of messages to confirm that a certain action was performed or triggered.

TracingOutput of errors and warning messages to help find and analyze problems. Tracing is activated by the developer or by a member of the support desk team.

ProfilingAnalysis of resource consumption of an application (e.g. memory and CPU consumption); usually with the aid of an external tool

DebuggingIn-depth analysis of an application on source code level


CCMS Monitoring Architecture Overview

SAPSolution Manager

3rd PartyTools

Non-SAP ComponentNon-SAP Component

SAP InstanceSAP Instance SAP InstanceSAP Instance

SAP Web Application Server

Other SAP Components (EP6.0)Other SAP Components (EP6.0)

Shared MemorySegment




Central Monitoring

SAP Web AS ≥ 6.20

SAPCCMSR SAPCCMSR

SAPCCM3X SAPCCM4X

SAP Web Application Server

Push

Push



Overview

EP 6.0 Portal

Introduction

Monitoring Objects




Archiving Logs


Monitoring objects overview

Monitoring Objects

EP 6.0 Portal

OS resources

Processes

Log Files


Typical EP 6.0 System Landscape

Enterprise PortalFront – End Server

OS Resources

TREX Server

OS Resources

Database Server

OS Resources

LDAP

OS Resources

ITS

OS Resources

Backend Server

OS Resources


OS Resources to be Monitored

Usage of virtual and physical memory

CPU utilization

Utilization of physical disks and file systems

Resource usage of running processes


Monitoring with SAP Agents

Enterprise PortalFront – End Server

OS Resources

TREX Server

OS Resources

Database Server

OS Resources

LDAP

OS Resources

ITS

OS Resources

Backend Server

OS Resources

SAPOSCOL

SAPCCMSR

SAPOSCOL

SAPCCMSR

SAPOSCOL

SAPCCMSR

SAPOSCOL

SAPCCMSR

SAPOSCOL

SAPCCMSR

SAPOSCOL

SAPCCMSR

SAPCCM4X


OS Resource Monitoring with SAPOSCOL

OS Resource Data

SAPOSCOL

Server /Host


Processes to be Monitored

Process nameComponet

e.g.: inetinfoWeb Server

TrexIndexServer

TrexQueueServer

ServerTrexPreprocessor

TrexISAPIRegist

TrexDaemon.exe

TrexFilter.exe

TREX

e.g.: ns-httpd.exens-slapd.exe

LDAP

sqlservr; sqlmangr

TNSLSNR; oracle

DatabaseMS SQL ServerOracle

alone (java)SAP J2EE


Monitoring objects overview

Monitoring Objects

EP 6.0 Portal

OS resources

Processes

Log Files


Where to Find Log Files?

<SAPJ2EE Inst.>/cluster/server/services/servlet_jsp/work/jspTemp/irj/root/WEB-INF/portal/logs

e.g. usermanagement.logportal.logpcd.logknowledgemanagement.0.txt

::

<SAPJ2EE Inst.>/cluster/(dispatcher)server/managers/console_logs

date_time_error.logdate_time_output.log

<MS-SQL Inst.>/MSSQL/LOG

e.g. ERRORLOGexception.log


Monitoring Landscape

EP 6.0


Types of Log Viewer

Integrated Log Viewer (included in the Visual Administrator)This is the online tool where all the logs written from the J2EE Engine and the running applications are automatically registered

Standalone Log Viewer (for central Log Viewing)Consists of Log Viewer server and Log Viewer client. Logs from aSystem Landscape can be viewed centrally in one Standalone Log Viewer client, if one Log Viewer server runs on every host.

Command Line Log ViewerUsage: lv.bat , delivered with the Standalone Log Viewer• Only for viewing local logs on console• Can be switched on while deployment• Converts binary data into human readable data



Overview

EP 6.0 Portal

Introduction

Monitoring Objects




Archiving Logs


SAP J2EE specific monitoring features overview


EP 6.0 Portal

Logging in J2EE-Engine

Visual Administrator

StandAlone Log Viewer


J2EE Engine Console Log Files

J2EE Engine - Console Logs:

Name: YYYY_DD_MM_at_HH_MM_SS_output.log

Path: /usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/console_logs/

Activation: console_logs.properties

Contains: Console Output, e.g. Startup messages, Garbage Collection Trace, Thread Dumps

Name: YYYY_DD_MM_at_HH_MM_SS_error.log

Path: /usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/ managers/console_logs/

Activation: console_logs.properties

Contains: Error and exceptions Messages about all kinds of errors and exceptions

Important: The setting “DaysToKeepLogs” in “console_log.properties” specifies how long (in days) to store the log files (default=7).


Logging Configuration

provides an easy-to-use, non-distributed system to record significant events that have occurred on the elements of the cluster. It stores messages associated with a particular manager. It runs on both dispatcher and server nodes.

Log Manager

is a distributed system that records significant events that haveoccurred on the elements of the cluster.

It stores messages associated with a particular service. This module defines nine types of log messages stored in text format.

It runs on both dispatcher and server nodes of the cluster.

Log Service


Configuring SAP J2EE 6.20

SAP J2EE Engine – Managers and Services

Core Servicesdbms, naming, deploy, admin, security, log, p4, monitor, file

Additional ServicesJ2EE Services

ts, dbpool, eisconnector, jms, ejb, appclient, http, servlet_jsp, javamail

Other Servicesrfcengine, logviewer, telnet, shell, pinger



SAP J2EE Engine – Important Managers

ThreadManager (Application Threads)Starts and manages threads in the Java Virtual MachineImportant Properties

MinThreadCount < MaxThreadCount < OS maximum

SystemThreadManager (System Threads)Manages internal threads

r3startup Managercontrols the processes of the servers started by the R3Startup ServiceCommunicates with the SAP Web Application Server



SAP J2EE Engine – Important Services I

DBPool ServiceCreates and stores db connections so that they can be reusedAlong with Transaction Service, DBPool manages transactions and synchronizes the transactions in the server with those in the database

EISConnector ServiceManages communications between SAP J2EE Engine 6.20 and Enterprise Information Systems (EIS)Using J2EE Connector Architecture it integrates EIS with application servers and enterprise applications

Security ServiceProvides user and group managementManages user authorization for access to system resources



SAP J2EE Engine – Important Services II

Monitor ServiceAllows for obtaining information about system current statusProvides general information and statistics about

Cluster nodesThread count / Memory usage / PerformanceUser sessions

View collected data with Visual Administration Tool, SAP CCMS or by tools that can read comma separated files (.csv)

Deploy ServiceIt manages the deployment of J2EE applications on the corresponding containers and across the cluster



SAP J2EE Engine – Important Services III

HTTP ServiceHandles requests received over the HTTP protocol

Servlet_jsp ServiceWorks as a container for Web ApplicationsDeveloped according to Java Servlet API 2.2 andJavaServer Pages 1.1 specification

RFC EngineEstablishes communication between ABAP-based R/3 applications and Stateless Session Beans

r3startup ServiceEnables the SAP Web Application Server to start and stop the SAP J2EE Engine


Exercise: Learning more with J2EE Administrator

Start the J2EE dispatcher and server if not currently executingImportant Open your J2EE Administrator documention with the following URL in your browser:

http://<server>:50000/Expand folders on left side to read information about managers and services.Select one of the following managers or services:


Exercise: Comparison of Dispatcher and Server Nodes

Exercise 03-01: Comparison of Dispatcher and Server Nodes

Duration: 20 Minutes


Where to Find Properties Files?

J2EE-Engine – Server/Dispatcher – Manager - Properties:Path:/usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/settings/

Contains: Specific information on path and log file name.

J2EE-Engine – Server/Dispatcher – Service - Properties:Path:/usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/services/...

Each service has its own properties file in the corresponding folder

Contains: all service related properties


J2EE Engine Log Files

J2EE Engine – Log Manager:Names: DEBUG.log, TRACE.log, INFO.log, NOTICE.log, WARNING.log,

ERROR.log, CRITICAL.log, ALERT.log, EMERGENCY.log

Path: e.g./usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/log/cluster//usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/log/memory//usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/log/r3startup//usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/log/service//usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/managers/log/timeout/

Activation: via J2EE Administrator Tool or via properties-file of manager

Contains: Specific information on Manager depending on the log level.

J2EE Engine – Log Service:Names: DEBUG.log, TRACE.log, INFO.log, NOTICE.log, WARNING.log,


Path:/usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/services/log/work/

Activation: via J2EE Administrator Tool or ConfigtoolContains: Specific information on Service depending on the log level.


HTTP Service Log File

J2EE Engine – HTTP Service:Names: DEBUG.log, TRACE.log, INFO.log, NOTICE.log, WARNING.log,


Path:/usr/sap/<SID>/j2ee/j2ee_XX/cluster/[server|dispatcher]/services/http/log/

Configuration: via J2EE Administrator Tool or Configtool

Contains: Information related to the HTTP service on the log level.

The HTTP Service is one of the most important services and it has some special issues:

2004-03-26 10:47:38 | http | INFO | | 10.20.19.37 | 10.20.19.37 - - [26/Mar/2004:10:47:38 +0100] "GET /irj/index.html" 200 0 [187] |

2004-03-26 10:48:00 | http | INFO | | 10.20.19.37 | 10.20.19.37 - - [26/Mar/2004:10:48:00 +0100] "GET /irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default" 200 8853 [21953] |

Example messages taken from an services/http/log/INFO.log


Tracing HTTP

All http communication can be traced from the HTTP Service of the Dispatcher Node for problem analysis.

Configuration is done in: /usr/sap/<SID>/j2ee/j2ee_XX/cluster/dispatcher/services/http/properties

The following parameters have to be adjusted:

HttpTrace=[disable|testFull|textHeaders|hexFull|hexHeaders]

HttpTraceRequestOutput=File name or empty for Standard Output

HttpTraceResponseOutput=File name or empty for Standard Output

The HTTP Trace is disabled by default.

For all details about the HTTP Trace please check Note 657765.




EP 6.0 Portal

Logging and Tracing in J2EE-Engine




Visual Administrator Overview

The Visual Administrator includes functions for:

• Obtaining general information about a service or manager (forexample, its name, group, and so on)

• Administering and changing the properties either specific or commonfor each service or manager

• Runtime administration and control

• Deployment of applications on all cluster elements

• Log viewing

Visual Administrator needs an up and running SAP J2EE Engine 6.20.NOTE:


Types of Log Messages

You can view the following types of log messages:


How to start Visual Administrator?


Exercise: Visual Administrator Integrated Log Viewer

Ensure J2EE engine is running

Execute: \<J2EE_Dir>\admin\go.bat

Account: Administrator (case sensitive!), Password: nimda

Select Cluster


LogManager / Log Service Properties

LogManager / Log Service some important properties

LogLevel This is a number from 0 to 8 that specifies the level oflog messages that are written to log files. Logmessages with lower priority than the level specifiedare ignored by the log system.

NormalLogLevel Specifies the types of log messages that have normalpriority. It is a number from 0 to 8 specifying that logmessages within [0,NormalLogLevel] are written inthe DefaultNormalFile. For example, ifNormalLogLevel is set to 4, log messages that are in[0,4] are written to the DefaultNormalFile, and therest to the DefaultCriticalFile.

Specifies the types of log messages that have criticalpriority. It is a number from 0 to 8 specifying that logmessages within [CriticalLogLevel,8] are written in theDefaultCriticalFile.

CriticalLogLevel


Log Levels

The log system recognizes the following types of events and creates nine log file types with the these names:

• EMERGENCY (log level 0) – System is unusable

• ALERT (log level 1) – Immediate action must be taken

• CRITICAL (log level 2) – Critical conditions

• ERROR (log level 3) – Error conditions

• WARNING (log level 4) – Warning conditions

• NOTICE (log level 5) – Normal but significant events for the system

• INFO (log level 6) – Information

• TRACE (log level 7) – Events that occur as a result of application methods execution

• DEBUG (log level 8) – Debug-level messages,


Logging Configuration

Logging Configuration via LogManager / Log Service

1) Select theLogManager

2) Set values in Properties


Monitoring Configuration of the SAP J2EE Engine

SAP J2EE Engine monitoring system consists of a Monitor Server and Monitor Service.

Monitor Service:

establishes a connection between the Monitor Server and the system

Monitor Server:

collects data from the J2EE Engine and reports the informaton and statisticsabout the node and their components to Visual Administrator, CCMS Agent,a file system (in .xls and .html format files) and its own Monitor Server GUItool

For additional information refer to Administration Guide of the J2EE Engine (Administration Manual -> Configuration Tasks -> Using the Log System and Monitoring)


Monitor Server Landscape

Monitoring configuration of the SAP J2EE Engine


monitorServer.properties

Monitoring configuration of the SAP J2EE EngineCheck monitorServer.properties

Unix <J2EE INSTDIR>/tools/monitorServer.properties

MS Windows <J2EE INSTDIR>\tools\monitorServer.properties


Monitor Server Configuration File


Monitor Server Configuration

Details of monitorServer.properties

java.naming.provider.url= your hostname:<p4 port>

If you run multiple installations of the SAP J2EE Engine on the same machine, you must set up a monitor server for each installation.

Replace <p4port> with the port you use to connect via the administrator. You can easy check the default p4 port in the file:

<J2EE_INSTDIR>/ prepconf.log


Visual Administrator (Monitoring)Monitor server configuration


java.naming.security.principal= your Administrator name

Don´t mistake the <j2eeadm> with the Administrator. The administrator Administrator is therefore created with an empty password by default; you should also ensure that you remove the comment symbols in the appropriate lines.

monitor.system.VA.port=<vaport>

Replace <vaport> with some free port (by default the port is 5555)




monitor.system.CCMS.root=<monitor-context>

<monitor-context> is extremely important if you want to connect more than one installations of the SAP J2EE Engine to the same CCMS. It must be system-wide unique. For this purpose, change the default value (SAP J2EE Engine)to some unique identifier that includes, for example, the host name.



Starting the Monitor Server

<J2EE INSTDIR>\tools\monitor

The monitor server tries to connect to all nodes of the entire cluster, this is shown within the stdout.


Launch Visual AdministratorMonitor server configurationLaunch the monitor server via the Visual Administrator


Monitor Server – Reported Data

Workload

Contains all dynamicallychanging information related tothe runtime behavior of thesystem.

Configuration

Provides data, which is related tothe current configuration status ofthe system.


Workload-MemoryMonitor server – reported data (Workload-Memory)

Check that the cluster components not allocatesmore than 75 % of the Memory Limit (UtilizationLevel = 5)!

This will cause an “Out of Memory” report of the cluster component!


Monitor Server – Reported Data (Essential Data)

Type of cluster node Monitoring item Notes

Dispatcher and server Threads->Server Threads

Server Threads are essential resource with big influence on system stability and performance

Dispatcher Connections manipulator

TCP connections established to j2ee engine dispatcher are counted

Dispatcher and server Memory Basic factor of stability

server Threads->Client Threads

Mapped together give overview about customer requests execution environment on the server node

server HTTP sessions summary

server DBpools

cluster heartbeat Checks availability of the cluster


EXERCISE




EP 6.0 Portal

Logging and Tracing in J2EE-Engine




Standalone Log Viewer 6.30

Log Viewer protocol (P4)

J2EE6.30

Host I

Log Viewer Server

Log Viewer Server

J2EE6.30

Host II

WTServer(for example, together with

Solution Manager)

Log Viewer Client

SAProuter

SAP SupportSAP Support


Standalone Log Viewer

Through the Log Viewer user interface you can:

• Connect to and view log files on multiple servers.• Merge logs within and across servers. • Change severity level of logs. • Customize columns by log type. • Perform search for string messages. • Add new log files. • Manage displayed column view. • Use the ’Refresh’ function to view new entries


Standalone Log Viewer Types and Formats

Log TypesThe following are the log types available for Log Viewer:

• ListLog• ASCIILog• SQLTrace• SAPJTrace• SAT Trace

Log FormatsMessages can be configured to be output in different formats. You can configure the formats through the Log Configurator. Following are the different log formats supported by the Log Viewer:

• Trace format• List format• ASCII format• SQL Trace format• SAT Trace format


Installing StandAlone LogViewer

Installing and Configuring the StandAlone LogViewer 6.30 comprises the following steps:

Copy Logviewer-standalone folderAdjust the list of Log FilesAdjust the LogViewerServer.propertiesSet LV_HOME Environmental VariablesStart the LogViewer ServerStart the LogViewer ClientGeneral Settings for monitored log files


Copy Directory logviewer_standalone

Copy the folder Logviewer-standalone from your moni_temp directory

to <J2EE home dir>/tools


Adjust List of Log Files


Adjust LogViewer.properties

Open <J2EE home dir>/tools/logviewer-standalone/server/logViewerServer.properties.

Define the location of logdirectory.xml by modifying the lineLogviewer_LogDirectoryReadFromFile = <file path and name>Example:

Logviewer_LogDirectoryReadFromFile = /logdirectory


Exercise – Standalone Log Viewer

In command prompt, open folder: D:\usr\exercises; run commands below:

Copy directory logviewer_standalone to tools

Adjust List of Log Files

Adjust LogViewer.properties

SolMon02.bat

Extracts monitor application from SAR file to …/moni_temp/build folder

SolMon01.batActionCommand/Bat file


Setting LV_HOME Environmental Variables

Windows:Add the environmental system variable LV_HOME, set to the path C:\usr\sap\EP6T\j2ee\j2ee_00\tools\logviewer-standalone

Add LV_HOME to PATH- UNIX: echo $LV_HOME- Windows: ;%LV_HOME%

Open <J2EE home dir>/tools/logviewer-standalone/server/logViewerServer.properties.


Starting the LogViewer Server

Start the LogViewer Server by executing

- UNIX: server.sh- Windows: server.bat

from directory<J2EE home dir>/tools/logviewer-standalone


Starting the LogViewer Client of Standalone LogViewer

Start the LogViewer Client by executing

- UNIX: client.sh- Windows: client.bat

from directory<J2EE home dir>/tools/logviewer-standalone


Exercises – Standalone Log Viewer

Add environmental variable LV_HOMEAdd ; %LV_HOME% to PATHGo to folder C:\usr\sap\EP6T\j2ee\j2ee_00\tools\logviewer-standalone

Start server.batStart client.bat


Define server data & test the connection

This is the SAPJ2EE Admin Port. It can be calculated by 50000 + SAPJ2EE_instance x 100 + 4.In this example, the J2EE instance = 01 50104


Display logfiles in LogViewer



Overview

EP 6.0 Portal

Introduction

Monitoring Objects




Archiving Logs


Monitoring Features of the Portal Application

The monitoring functions are implemented in the portal as components. You need administration authorization in order to use these functions.

You can find these functions on the System Administration -> Monitoring tab page in top-level navigation

->Portal

•Requests Summary

•Request Overview

•Component Overview

•Thread Overview

•Logged On Users

•Activity Tracing

•Logging Console


Portal Request SummaryUseful information in Request Summary (Use case)

Check the “Average Time of a Request” value and compare it with all other server nodes in the cluster.


Request SummaryMonitoring features of the portal application (Request Summary)

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 following lines are inserted in the iView table:


Request Overview


Request Overview Entries

Portal subsystems as they appear in JARM-based monitoring and single activity trace


Request Overview

Portal subsystems as they appear in JARM-based monitoring and single activity trace


Display Request Entries

The following information is displayed for the individual requests:


Request Overview

Useful information in Request Overview (use case)

To identify the executed components -> click on the request name

To check the caching: - log in several times and compare the values for each log in

Note:

Note:

To find the most expensive request: - sort the table by Duration

Note:


Component Overview


Component Entries

The following information is displayed for the individual components:


Identifying Expensive ContentComponent Overview use case - Identifying Expensive ContentAfter you found the expensive component, check the following:

1. Display the component / iView in the browser if you do not recognize it from the name. Also pay attention to the browser impression: Does the iView “feel” slow?• If the component contains a PCD URL, go to the Portal Content Studio,

navigate to the iView / page location and click preview.• If the component does not contain a PCD URL, directly call the component:

http://server:port/irj/servlet/prt/portal/prtroot/componentname

2. Check the CodeLink property of the iView: What is the Java class behind the component? Is it a standard SAP class (prefix com.sap.*) or is it a customer/3rd

party class? If possible, check with the code owner for any iview-specific tuning options.

3. Check the Caching properties of the iView: Is the iView cached? If not, check if the iView can be cached.

4. If these caching does not help and you are convinced that this iView considerably contributes to overall portal load, iview-specific, may be also code-level optimizations may be required.

5. If you cannot clearly identify a few components that consume most of the elapsed time, the performance problem is possibly not related to any specific content.


Monitoring Features (Thread Overview)


Monitoring Features (Thread Overview)

The following graphic shows the data of a thread overview while a request is running:


Monitoring Features (Thread Overview) List

The following information is displayed in the thread overview:


Using the Thread Overview

To cope with the lengthy PCD URLs, copy the table to an Excel sheet. If you create several samples, consider copying each of them to XLS (e.g., to the same table).


How to Use the Thread Overview

Excel view of the same information:

Based on a few samples, check for the following indicators:• Do you observe high elapsed times for requests or components (one request may

call several components)?

•Can you identify components that repeatedly appear with high elapsed times (e.g. >5000ms)?

•Can you identify specific users or groups of users that trigger these expensive requests? (e.g. a user administrator may always be searching for “*” (all users) when assigning roles.)


Logged On Users


Activity Tracing


SAT Tracing in the Portal

How to change the standard time frame for SAT tracing in the Portal


Change the Standard Timeframe for SAT Tracing

How to change the standard time frame for SAT tracing in the Portal


Single Activity Trace (SAT) in the LogViewer


How to Read the SAT File? (1)

• Red lines indicate requests, the most coarse-grained level of the trace. For a request, only the gross elapsed time is reported. There are two different kinds of requests:

External requests (i.e. HTTP requests from a browser) are prefixed by EP:PRT:. The name is then followed by the name of the root iView contained in the request. External requests and the components called from these requests are processed by Client_Threads.

An external request may trigger one or more internal requests, e.g., to render iViews that are part of a page. Internal requests are prefixed by EP:PRT:ASYNC: and processed by threads from the pool PRT-Async. The complete PCD URL (pcd:/portal_content/…) is listed in the request name.


How to Read the SAT File? (2)

• Blue lines denote (JARM) components. JARM components have a finer granularity than JARM requests. For each component, the gross time and the net time (net time = gross time – sum(time for sub-components)) are reported. Typical component calls include:

Processing of iViews

Calls to other subsystems of the portal, e.g. EP:UME:, EP:PCD_Role:, …

• Grey lines indicate action calls in JARM, i.e. these lines provide additional information in the description field without doing time measurement (gross and net time is always -1).


Identify Performance Problems

SAT use case - Identify Performance Problems

• Look for requests (red lines) with a high gross time. E.g., 3 s, depending on load and requirements.

• Check the components of this request. Can you find a single component that consumes the major part of the response time? If so, this component needs optimization:

If the component is an iView, check the Java class for this component, as listed in the grey line. Is it a standard SAP component? Or is it a custom development?

If the component is a subsystem call (e.g. EP:UME or EP:PCD) check for optimizations in this area: Caching, more efficient role structure, …

• If possible, try to change the content / reason that you identified from the trace and repeat your click sequence. Reactions may be removal of an iView from a page, remove roles from a user/group, etc. Does the change yield any difference?


Activating the Single Activity Trace in the TREX

The TREX processes search, index-create, etc requests in different services. Therefore the activity tracing must be enabled for every service separately. The configuration filesTREXIndexServer.ini, TREXNameServer.ini, TREXPreprocessor.ini,TREXQueueServer.ini, TREXWebServer.ini need to be adapted.

Please open the configuration files and check for these entries; if they don’t exist please create them.

[ccms]record = onsatracer = Jarmlike

[satjarmlike]file = <sat_file>

<sat_file>replace <sat_file> with the destination file of the trace information, use a path relative to <TREX INSTDIR> liketrace/TrexIndexServer.sattrace/TrexNameServer.sattrace/TREXPreprocessor.sattrace/TREXQueueServer.sattrace/Webserver.sat


Logging Console – User Mode


Understand the Logger Mechanism


Understand the Logger MechanismUnderstand the Logger mechanism – logger.xml

<J2EE Inst>\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\system\xml\logger.xml


Logging Console – Administrator Mode


Logging Console Entries

The following table lists the available logger classes.


Portal specific Monitoring

ExercisesIdentifying Expensive Content?



Overview

EP 6.0 Portal

Introduction

Monitoring Objects




Archiving Logs


Knowledge Management

Monitoring features of the knowledge management application

The monitoring functions are implemented in the portal as components. You need administration authorization in order to use these functions.You can find these functions on the System Administration -> Monitoring tab page in top-level navigation

->Knowledge Management

•Component Monitor

•Cache Monitor

•TREX Monitor

•Crawler Monitor

•Application Log


Component Monitor


Component Monitor Legend


Component Monitor Entries


Cache Monitor


Cache Monitor Entries


TREX Monitor


TREX Monitor

Features

You can use the TREX monitor to administrate and monitor the TREX servers (queue, index, and name server) in the portal.

The iView consists of the following areas:

• Server Status

• Display Queues

• Display Queue Entries

• Edit Queue Parameter

• Delete Queue Entries

• Change Queue Status

• Reset Failed Document Entries

• Display Index Details


Checklist for Routine Operation

Monitoring features of the portal application (TREX Monitor)

Checklist for Routine Operation

Were the TREX servers started correctly?

Is sufficient hard disk capacity available for the indexes?

What is the status of the queues managed by the queue server?


Crawler Monitor

For further information please refer to EP6.0 Admin Guide!


Application Log

You can use the Show Options link to call up a register with the following tab pages:

• Filters• Display• Download

You can use these tab pages to define how information in the application log is displayed.

You can set filters that define the columns displayed, or download the log as a file.

For further information please refer to EP6.0 Admin Guide!



Overview

EP 6.0 Portal

Introduction

Monitoring Objects




Archiving Logs


Overview: Archiving Logs

Overview

EP 6.0 Portal

Archiving log messages of SAP J2EE Engine

Archiving log files of the portal


Overview: Archiving

ContentsArchiving log messages

ObjectivesAt the end of this unit, you will be able to:

Understand the archiving mechanism for log messages


Console Logs Location

The error.log and output.log are created every time of restarting the SAP J2EE Engine 6.20


Console Logs

This log system can be managed using console_logs.properties file located in<SAPj2eeEngine_install_dir>/cluster/server(dispatcher)/managers directory. Itcontains three properties with the following keys and values:

• LogConsoleStreams – this property has a boolean value that indicatesif console output is logged. By default, it is set to YES.

• LogDir – specifies the directory where the log files are stored. Bydefault, it is /managers/console_logs.

• DaysToKeepLogs – specifies how long (in days) to store the log files.The default value is 7.


Archiving Log Files of Managers and Services

Path - Managers

<J2EE Inst. Dir>\cluster\dispatcher (server)\managers\log\manager-name\logbackup

Path - Services

<J2EE Inst. Dir>\cluster\dispatcher (server)\services\log\work\logbackup


Log Manager Properties

Log Manager some important properties related to archiving maintained in Visual Administrator.

ZipExpiredFiles Indicates whether log files are archived. It has aboolean value.

MaxZipFiles Specifies the maximum number of archive files to becreated.

Specifies the intervals at which log files are archivedin milliseconds.

DefaultMaxDelayTime

Specifies the maximum length of each log file (in bytes). If it is exceeded, the file is added to the archive.

DefaultMaxFileLength


Log Service Properties

Log Service some important properties related to archiving

ZipDirectory Specifies the directory in which the log files arearchived. It is relative to the “work” directory of theLog service.

MaxFileLength Specifies the maximum size of the log file (in bytes).If it is exceeded, the file is added to the archive.

Specifies the maximum period between twoconsequent archiving of log files. It is specified inmilliseconds.

MaxDelayTime


Overview: Archiving Logs

Overview

EP 6.0 Portal

Archiving log messages of SAP J2EE Engine

Archiving log files of the portal


Archiving Portal Logs

Path – Portal logs

<J2EE Inst. Dir>\cluster\server\services\servlet_jsp\work\jspTemp\irj\root\WEB-INF\portal\logs

Daily archiving of log files


Archiving Portal Logs Maximum Size

Path – Portal logs (maxSize)

Here you can specify aMaximum size for eachLog file


Unit Summary

You are now able to:

Explain most important monitoring features in J2EE Engine installationsUse the standard monitoring toolsSpecify administration toolsExplain most important monitoring features in Enterprise Portal applicationsDetect possible performance problemsExplain the archiving mechanism for log messages

Monitoring Logging and Tracing the EP 6.0 SP2

Documents

Transcript of Monitoring Logging and Tracing the EP 6.0 SP2