SMD Slides

Diagnostics in
Solution Manager
SAP Active Global Support
Meghan Del Grande

Course description
Introduction
What is it all about ?
Architecture
Diagnostics demo
 SAP AG 2006, Diagnostics for Solution Manager - OM / 2

Instructor Introduction
Instructor name: Meghan Del Grande
E-mail: meghan.del.grande@sap.com

Agenda
Introduction

Solution Manager main features
Advantages of Diagnostics
Architecture
Diagnostics demo

What is at stake ?
You need an efficient and safe way to perform root cause

analysis on incidents for SAP NetWeaver solutions…

Advantages of Diagnostics
SAP
router
SAP SUPPORT SAP CUSTOMER

Safe
access Solution Manager
Operator Diagnostics d only
Rea
access
SAP System
SAP NetWeaver
No Administration Tools
access Solution landscape
EFFICIENT SAFE
Reduced time for root cause analysis No changes to production systems
Central / uniform access thru Solution Manager Access thru Web browser (HTTP)
Standardized SAP best practices for diagnostics Read only access to SAP Netweaver solution.
Integrated with SAP NetWeaver No use of SAP NetWeaver administration tools.
Common internal SAP tool (J2EE commands restricted access)
Enforced customer control for change
System Performance optimization management
Workload distribution and load balancing, load testing
Low training costs

Agenda
Introduction
Architecture
Deployment on site
Diagnostics demo

On site landscape
Diagnostics servers Monitored systems
SA8
EP 6.0 SP16
NetWeaver 2004
6.40 – SP16
J2EE
50000 - P4:50004
Diagnostics
D37 Agent SP09
????:50000
Diagnostics – SP6 Introscope AIX 5.3 ML4
Agent ORACLE 9.2.0.5
NetWeaver 2004s
Introscope 7.0 – SP08
7.0 ABAP J2EE Sandbox Landscape
7.0 / SP58
ITS
????:5??00
IGS AIX 5.3 ML4 (PPC 64)
Port:4??80 ORACLE 10.2.0.2.0 DA8
EP 6.0 SP16
Prod Landscape
NetWeaver 2004
6.40 – SP16
J2EE
50000 - P4:50004
Diagnostics
Agent SP09
????:50000
Introscope AIX 5.3 ML4
Agent ORACLE 9.2.0.5
Dev Landscape

SMD applications GUI: Monitoring
Entry page accessible via Solution Manager menu OR
http://host:port/smd
-> Accessible to SAPSUPPORT user and administrators
Navigation data related to components defined in Solution Manager.

SMD applications GUI: Reporting

SMD applications GUI: Configuration

Overview
SolManDiag
Overview
SMD GUI
Monitoring
Reporting
Configuration

SolManDiag - Monitoring
SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Activity
Thread Dump Analysis

SolManDiag – Thread Dump and GC Analysis
Thread Dump Analysis

Central triggering and scheduling of JVM based thread dumps for
a certain or all J2EE node(s), gathering and transfer generated
thread dumps and analysis of the thread dump data via
appropriate user interface
More

SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Database
J2EE SQL Monitoring
SQL Command Console

SolManDiag – SQL Trace (How to use it)
Typically, you should use the SQL Trace when you need to check the
behavior of a particular application. This is the following scenario:
Launch the SQL Trace application

Activate the SQL Trace.
Run the application that you want to trace
Deactivate the SQL Trace
Set filters optionally
Evaluate the trace
You can also evaluate an already existing trace.

The SQL Trace also provides functions for file administration.

SolManDiag – OpenSQL Monitoring

SolManDiag – OpenSQL Monitoring (Launching SQL Trace)

SolManDiag - Evaluating SQL Trace via Webpage
3
4

SolManDiag - SQL Trace Filtering
The SQL Trace stores information about all database calls issued using Open or
Native SQL. When evaluating the trace using the SQL Trace Web application, however,
you can enter filtering criteria to display only those entries, which are relevant for
your purposes.

SolManDiag – OpenSQL Monitoring (SQL Trace – Features)
Useful Information
The SQL Trace function is an on-demand log of all SQL statements that
are issued against the database through Open and Native JDBC
methods. The SQL trace can be switched on or off dynamically from the
web application. The log format is database independent. Besides the SQL
statement text, each log record contains information about the point in
time when the statement was executed, its duration, its input parameters
and results (where applicable) as well as context information.
The SQL trace is especially useful for:

Development - SQL trace can help enterprise beans, servlet and
JSP developers to learn which kind of database accesses their code
produces.
Performance analysis - Typically, performance issues are caused by

inefficient database accesses. In this case SQL Trace can be used to
show the issued SQL statements and their duration, thus helping to
identify inefficient SQL statements.

SolManDiag
Monitoring
Database
J2EE SQL Monitoring
SQL Command Console

SQL Command Console
Using the SQL Command Console database tables can be viewed

through SMD interface without accessing the Database itself. It
helps to browse around Database installations and run selected
read-only queries on the monitored systems.
More

SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Logs and Traces
Log Viewer

SolManDiag
Monitoring
Logs and Traces
Log Viewer

SolManDiag Log Viewer
The Log Viewer can display structured and unstructured logs. Structured
logs are created by the SAP WebAS with header information and delimiters.
This allows the Log Viewer to recognize fields of the log records, and thus
allows filtering and searching of log records based on field content.
More

SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Operating System
OS Command Console
File System Browser
J2EE Command Console

OS Command Console
The OS Command Console is used to issue OS level commands and

maintain a history of those commands. The OS Command interface is an
embedded GUI which simulates the OS Command prompt.

SolManDiag – OS Command Console
Remote OS Monitoring
The SMD Agent has to be installed on every server (machine) to execute
operating system commands remotely. A limited sets of commands can
be executed within SMD without direct OS access.
Trigger when
command entered
Target host
Command group
Command
Parameters (optional)
Command
output
entry screen of OS Command Console

with chosen command: ipconfig

SolManDiag – OS Command Console
Available commands
Group Command UNIX Windows
Filesystem DF X
FindFile X
SearchInFile X X
Network Ping X X
Tracert X X
IPConfig X
NetStat X X
Java JavaHomeVersion X X
System TaskList X X
VMStat X
IOStat X
DateTime X X
Environment Echo X X
Set X X

SolManDiag
Monitoring
Operating System
OS Command Console
File System Browser

SolManDiag – File System Browser
File System Browser

Based on a SMD Agent, the File System Browser
allows Explorer-like navigation within the directory structure of the
monitored system. Files can be displayed by using of a built-in viewer.
Navigation
entry points
entry screen of File System Browser

File System Browser
The File System Browser is used to browse, format and download files
from the NW instance. The browsersupports some predefined indexes
for the Main Instance (J2EE/ABAP), Local Roots and aliases. Hence,
browsing can be performed extensively without the file system access.

SolManDiag
Monitoring
Operating System
OS Command Console
File System Browser

This feature enables the user to issue SAP J2EE commands and retrieve
results without directly accessing the operating system.
The interface makes a telnet connection to the system which
needs to be monitored.
More

SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Performance
HTTP Analysis
J2EE Server Analysis
Java WebDynpro Monitoring

SolManDiag – HTTP Analysis
HTTP Analysis
Generate performance data which include time components for
client-side and server-side processing for an certain request, data
transfer and data display / interpretation

HTTP Analysis (Big Picture)
Browser
with Monitored
PlugIn System
(Portal)
Network
report.xml responses.0.trc
SMD
HTTP
Analysis
Login_EmptyCache PrePro Time Net Server Time Rendering Time
Login_FilledCache PrePro Time Net Server Time Rendering Time

SolManDiag – HTTP Analysis
Client Browser PlugIn

SolManDiag – HTTP Analysis How to start
4 5

SolManDiag – HTTP Analysis How to stop

SolManDiag – HTTP Analysis Input Client File
13
10
11
15
8 12
14

SolManDiag – HTTP Analysis (Overview - Page)

SolManDiag – HTTP Analysis (Request table)

SolManDiag – HTTP Analysis (Request graphics)

SolManDiag
Monitoring
Performance
HTTP Analysis

SolManDiag – J2EE Server Analysis (Introscope)
J2EE Server Analysis / Wily IntroScope -Monitor on code level

(e.g. average response time of a certain method), provide historical
performance data, correlate with OS performance counters (e.g. File
I/O, Socket I/O, GC runs)
More

SolManDiag
Monitoring
Performance
HTTP Analysis

Monitoring for WebDynpro runtime including information like

usage data (e.g. users), deployed WebDynpro applications, JARM
based performance data and WebDynpro configuration data

SolManDiag – WebDynpro (Measuring Application Performance)

SolManDiag – WebDynpro (Request Performance)
With the Web Dynpro Console administration tool, you can display the
performance data for the times of a request to the J2EE Engine.
In contrast to Web Dynpro Framework, Client, and Applications, this

function gives information about the response times of the individual
steps of a request (starting within the J2EE Engine).

SolManDiag – WebDynpro (Measuring Request Performance I)
Context:
The table lists the requests sorted by the length of time. The required
response time, the number of methods involved, the method taking
the longest time, and the user are listed for each request.
Procedure:
Select a line
You get detailed information for the particular request.
Result
The performance data for a request includes the framework,
application, and backend times.
The detailed information also includes the level of the methods, giving
you information about the call depth of the methods called.
You can thus find out which query took the longest and which methods
within a query consumed time. . .

SolManDiag – WebDynpro (Measuring Request Performance II)

SolManDiag – WebDynpro (Monitoring Performance by User)
The Users function displays performance data for the various

users. This enables you to identify the users who are
encountering performance problems.

SolManDiag
Monitoring
Activity
Database
Logs and Traces
Operating System
Performance
Status

SolManDiag
Monitoring
Status
J2EE System Information
J2EE User Management
System Landscape Directory
Portal Access

J2EE System Information
J2EE System information provides administrators with an overview of

the system configuration and its state. It shows all of the system's
instances and processes, their current state and important parameters.

SolManDiag – System Information
Port
Information
Component
Vendor and
Version
VM
Parameter
System
Parameter

J2EE User Management
J2EE User Management provides administrators with an opportunity
to view and check the assignment of users, groups and roles.

System Landscape Directory
The SAP System Landscape Directory (SLD) provides information about

all SAP software modules in landscape. SLD represents an exact model of
actual system landscape. SLD is a part of Web application server and is
directly integrated into Solution Manager Diagnostics through the WebAS.

Overview
SolManDiag
Overview
SMD GUI
Monitoring
Reporting

SolManDiag - Reporting
SolManDiag
Reporting
Usage Statistics
Configuration and File Management
Software Change Management
J2EE System

SolManDiag – Portal Activity Reporting
The Portal Activity Report display information, such as, the number of
users that logged onto the portal in a given period of time, and the number
of times the logged on users requested a page, or an iView. In addition,
parameters can be defined to filter the report and produce precise details
about the use of a specific page, or iView.

Portal Activity Reporting
Features
Gather information about the activities of portal users and their
use of portal content
Aggregation at different levels (hour, day, month, quarter)
Display data for specific time intervals (hour, day, month, quarter)
about
The number of users logged onto the portal
The number of HTTP sessions created for accessing anonymous
content
How often iViews and pages have been accessed and in how
many different user sessions

SolManDiag – PAR Terms & Definitions I
There are two different values for the Page and iView statistics
Requests: How often a page/iView has been requested?
Visits: In how many different user sessions a page/iView has been
accessed?

SolManDiag – PAR Requests & Visits
User A User B
Request 1 Request 3 Request 2

Request 4
MyPage Requests 0
1
2
3
4
Visits 0
1
2
iView1 Requests 0
1
2
3
4
Visits 0
1
2
iView2 Requests 0
1
2
Visits 0
1
2

SolManDiag – PAR Terms & Definitions II
There are two different values for the User statistics

Named Users: How many different users have logged in to the portal?
Anonymous Users: How many anonymous user sessions have
accessed the anonymous content of the portal?

SolManDiag – PAR Usage (User statistics)
The following information can be displayed and exported by the reporting

iView
Number of anonymous users
Number of named users

SolManDiag – PAR Usage (User statistics sample charts)

SolManDiag – PAR Usage (iView / page statistics)

SolManDiag – PAR Usage (iView / page statistics sample chart)

SolManDiag
Reporting
Usage Statistics
J2EE System

Overview
Collection of configuration parameters and file properties including

user interface to display the collected data and to detect differences
between different points in time (e.g. before and after a maintenance
window), between different cluster instances / nodes of one system and
different landscapes (e.g. QAS and PRD)

Execute Collect Configuration Data Task
The Configuration Data Collect is started by the automatic task Collect

Configuration Data in the Scheduler.
The task can be executed manually at any time.

Check Configuration Change Reporting
The Timestamp field is displaying the latest date when a change in the
configuration has been detected.
No new date will be added unless a change has occurred.

Configuration Change Reporting
Use configStore detail view to the file content

Use filter to display only changes (Show delete Items, Hide Unchanged
items …)
Use Attribute History to get details on Property value

SolManDiag – File Version Reporting (Single Landscape)
Click

SolManDiag – File Version Reporting (Compare 2 Landscapes or 2
Snapshots of the same Landscape)

SolManDiag – File Version Reporting (Compare 2 Landscapes or 2
Snapshots of the same Landscape)
Different value
Additional value

Compare Multiple Instances
It compares multiple instances one at a time and points out

discrepancies. Very often it has been noted that in large
installations with various instances there is a need to comparison
to make sure the configuration data is consistent.

Compare Multiple Instances
Select a
transaction
Select an
Instance

SolManDiag
Reporting
Usage Statistics
J2EE System

Software Change Reporting
Software Change Reporting is very useful in identifying the current

software release on a system and also track changes as they occur. It is
also a very useful reporting tool to gather and display transport logs for
Enterprise Portal content and packages deployed through Software
Deployment Manager.

SolManDiag – SCM (Software Version)
Here you get information about the installed software

versions of your chosen landscape

SolManDiag – SCM (Software Management)
Select an option
Click

SolManDiag
Reporting
Usage Statistics
J2EE System

SolManDiag
Reporting
J2EE System
NWA Plugins
KeyStorage / SSL
LDAP Browser

NWA Plugins
More

SolManDiag
Reporting
J2EE System
NWA Plugins
KeyStorage / SSL
LDAP Browser

KeyStorage / SSL
Access to Keystore and SSL on monitored engines

Keystore
Collection of Keys and Certificates
Available on Server nodes
SSL
Configure SSL connections
Available on Dispatcher nodes

SolManDiag
Reporting
J2EE System
NWA Plugins
KeyStorage / SSL
LDAP Browser

LDAP Browser
Purpose
Using a LDAP Server as datasource for user management (J2EE Engine –
EP…)
Integration to SMD
A SMD agent is running on the monitored host and must be configured in
the administration UI to connect the LDAP Server
Accessible in SMD UI under J2EE Reporting
Use to browse the configuration of a LDAP Server and top search for a
specific entry

Agent Configuration
Agent Configuration
Safe configuration of the LDAP server properties by customer

LDAP Browser
Access and Connection

Reporting -> J2EE System -> LDAP Browser

Search
Search of attributes

Search results
Navigation and Visualization of attributes

Overview
SolManDiag
Overview
SMD GUIs
Monitoring
Reporting
Configuration

SolManDiag
Configuration
Scheduler
Self Check

Questions and answers

Copyright 2006 SAP AG. All Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may
vary.
The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of
these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of
hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web
pages

SMD Slides

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SMD Slides

Uploaded by

Copyright:

Available Formats

Diagnostics in

SAP Active Global Support

Meghan Del Grande

What is it all about ?

 SAP AG 2006, Diagnostics for Solution Manager - OM / 2

Instructor name: Meghan Del Grande

 SAP AG 2006, Diagnostics for Solution Manager - OM / 3

What is it all about ?

 SAP AG 2006, Diagnostics for Solution Manager - OM / 4

You need an efficient and safe way to perform root cause

 SAP AG 2006, Diagnostics for Solution Manager - OM / 5

SAP SUPPORT SAP CUSTOMER

Low training costs

 SAP AG 2006, Diagnostics for Solution Manager - OM / 6

What is it all about ?

 SAP AG 2006, Diagnostics for Solution Manager - OM / 7

 SAP AG 2006, Diagnostics for Solution Manager - OM / 8

-> Accessible to SAPSUPPORT user and administrators

Navigation data related to components defined in Solution Manager.

 SAP AG 2006, Diagnostics for Solution Manager - OM / 9

 SAP AG 2006, Diagnostics for Solution Manager - OM / 10

 SAP AG 2006, Diagnostics for Solution Manager - OM / 11

 SAP AG 2006, Diagnostics for Solution Manager - OM / 12

 SAP AG 2006, Diagnostics for Solution Manager - OM / 13

 SAP AG 2006, Diagnostics for Solution Manager - OM / 14

Thread Dump Analysis

 SAP AG 2006, Diagnostics for Solution Manager - OM / 15

 SAP AG 2006, Diagnostics for Solution Manager - OM / 16

 SAP AG 2006, Diagnostics for Solution Manager - OM / 17

Launch the SQL Trace application

You can also evaluate an already existing trace.

 SAP AG 2006, Diagnostics for Solution Manager - OM / 18

 SAP AG 2006, Diagnostics for Solution Manager - OM / 19

 SAP AG 2006, Diagnostics for Solution Manager - OM / 20

 SAP AG 2006, Diagnostics for Solution Manager - OM / 21

 SAP AG 2006, Diagnostics for Solution Manager - OM / 22

The SQL trace is especially useful for:

Performance analysis - Typically, performance issues are caused by

 SAP AG 2006, Diagnostics for Solution Manager - OM / 23

 SAP AG 2006, Diagnostics for Solution Manager - OM / 24

Using the SQL Command Console database tables can be viewed

 SAP AG 2006, Diagnostics for Solution Manager - OM / 25

 SAP AG 2006, Diagnostics for Solution Manager - OM / 26

 SAP AG 2006, Diagnostics for Solution Manager - OM / 27

 SAP AG 2006, Diagnostics for Solution Manager - OM / 28

 SAP AG 2006, Diagnostics for Solution Manager - OM / 29

 SAP AG 2006, Diagnostics for Solution Manager - OM / 30

File System Browser

J2EE Command Console

 SAP AG 2006, Diagnostics for Solution Manager - OM / 31

The OS Command Console is used to issue OS level commands and

 SAP AG 2006, Diagnostics for Solution Manager - OM / 32

entry screen of OS Command Console

 SAP AG 2006, Diagnostics for Solution Manager - OM / 33

 SAP AG 2006, Diagnostics for Solution Manager - OM / 34

File System Browser

J2EE Command Console

 SAP AG 2006, Diagnostics for Solution Manager - OM / 35

File System Browser

entry screen of File System Browser

 SAP AG 2006, Diagnostics for Solution Manager - OM / 36

 SAP AG 2006, Diagnostics for Solution Manager - OM / 37

File System Browser