Root Cause Analysis forSAP MDM 5.5 SP06withSAP Solution ManagerDiagnostics
Detlef Thoms, SAP NetWeaver RIG EMEAPatrick Richarts, AGSMarkus Breiter, MDM Development
March 2008
Authors
Detlef Thoms has ten years of SAP experience that he has gained inDevelopment Support in the software development and as SCM SeniorSolution Consultant in SAP projects and numerous SAP implementations.Since January 2006 he is working for SAP NetWeaver RIG in the area ofMaster Data Management.
Patrick Richarts started at SAP Support in 1998. He was responsible for thedevelopment of services and trainings for CRM and Mobile Infrastructure anddelivered many onsite and remote services to SAP’s customers. Since 2006he works in the Global Center of Expertise on the integration of various SAPproducts into the Root Cause Analysis scenario of SAP Solution Manager.
Markus Breiter is a senior developer in SAP MDM and has eleven years ofSAP experience that he gained mainly in application development. Accordingto his customer orientation in the last years he focused on the integration ofstandard SAP support and operation tools to the MDM application. He joinedthe MDM development team from the start.
Configuration Reporting for SAP MDM
OS and DB Analysis for SAP MDM
Root Cause Analysis with SAP SolutionManager
Workload Analysis for SAP MDM
Misc.
SAP Solution Manager OverviewIntroduction to Root Cause Analysis and Monitoring
Root Cause Analysis with SAP Solution Manager
© SAP 2007 / Page 5
Change RequestManagement
Follows ITIL standardsMaintenance processes
SAP Solution Manager Scenarios
Service DeskSAP Best Practices forincident managementIntegration of third-party help desks
Solution MonitoringSystem monitoringBusiness process monitoringCentral system administrationSolution reportingService level reportingSAP EarlyWatch Alert
Upgrade ofSAP solutions
SAP methods and toolsE-learning managementTest management
Implementation of SAPsolutions
SAP methods and toolsGlobal rolloutCustomizing synchronizationE-learning managementTest management CORE
BUSINESSPROCESSES
Delivery ofSAP Services
On-site/remote deliveryIssue management
Root CauseAnalysis
Safe remote accessPerformance measurementLogs and dumpsTracesTechnical configuration
SAP Solution Manager OverviewIntroduction to Root Cause Analysis and Monitoring
Root Cause Analysis with SAP Solution Manager
© SAP 2007 / Page 7
Diagnostics and Monitoring for MDMcustomers
Solution Manager 4.0Diagnostics forSAP MDM
E2E Workload Analysis
E2E Change Analysis
Wily Introscope EM
Clix Command Interface
File System Browser /MDM Log Display
Configuration Reporting
Remote DB Monitoring
MDM Server Components
MDM Server
Import Server
Syndication Server
Layout Server
DB
Dia
gnos
tics
Age
nt SAPOSCOL
EPXI
…
Win32 client with MDMClient Components
Data Manager
Console
…Net
view
erC
lient
Browser access to Diagnostics
Netviewer access to MDMGUI tools (only if GUI toolsmust be analyzed)
AppSight Console foranalysis of performanceproblems or crashes ofMDM GUI components
Remote access to CCMS
CCMSMDM Server Monitoring
Configuration Reporting
App
Sigh
tB
lack
Box
CLIX Command Interface
Internet
CEN
Logs
MDM log files are stored in a common directoryon your MDM Server machine
In addition to the normal informational and error log messages, the MDMserver can also write performance data to the MDM Server log
The extent of the information that is written to the MDM server log can becontrolled with the following mds.ini parameters:
Protocol Log LevelDatabase Log Level
Clix
CLIX is a separate MDM application that allowsyou to manage the MDM software and MDMrepositories using a command line interfaceinstead of the MDM Console
In the case you intend to use external/third-party monitoring tools forMDM monitoring, the MDM CLIX command line utility can be used tomonitor specific aspects of the MDM application components
LoggingUser1 Inst ….User1 Inst ….
Netviewer – Application Sharing Toolfor SAP Support
SAP DMZNetviewer Server
Customer PC withNetviewer ParticipantClient
SAP Support Engineer PC withNetviewer Consultant Client
CSS
Request session1
Initiate session2
3 Provide ID
4 Start session
5 Join session
https
https
Internet
Central Monitoring System (CEN)
MDM CCMS monitoring is based on theCentral Monitoring System (CEN)
CCMS monitoring is based on the ABAPstack of a Web AS (Web Application Server).
The CCMS application collects the monitoring information for all connectedsystems and applications in this system.
CCMS Monitoring Template
MDM_DLLSAPOSCOL/ ProcMonLogMon
MDM_DLL: MDM-specific shared library provides monitoring data, such as availability andperformance criteria, to the central monitoring system CEN via CCMS agent.
SAPOSCOL: The SAP OS collector SAPOSCOL delivers operating system-specific data to theCEN via the CCMS agent. This includes CPU and memory consumption as well as ProcMonmonitoring for monitoring single processes running or not running on the PC.
LogMon monitoring is provided by the CCMS agent and is based onconfiguration files, while
ProcMon monitoring is based on an additional executable to be installed.
ConfMonSAPOSCOL/ ProcMon
All MDM-specific monitors are available in the CCMS standard trees
CCMS: MDM Server Heartbeat
Servers
HeartbeatAvailability
The MDM alert/heartbeat monitoring for the MDM-based businessscenarios
CCMS: MDM Server Repositories
The MDM repository availability monitoring
CCMS and Monitoring for MDM
CCMS and Monitoring for MDM:
service.sap.com/installmdm MDM 5.5 - Monitoring Guides (ZIP File)
Known Restrictions:
In the current release the integration of MDM into CCMS is not supportedon Unix platforms
Tools for Problem Detection and Resolution
SAP Solution Manager introduces a new layer of diagnostics that aims toisolate the component that is the root cause for an incident.
On top of this root cause analysis (problem resolution), SolutionMonitoring and IT Reporting aim to detect problems proactively andreport on capacity trends, service level agreements, and solution quality.
SAP Solution Manager 4.0 features four-cross component diagnosticscapabilities:
E2E Change Analysis: Makes changes to the productive landscape transparent(“Yesterday it worked, today it does not work; What has changed?“)E2E Workload Analysis: Isolates general performance bottlenecks in a solutionlandscapeE2E Exception Analysis: Isolates exceptional situations, such as fatal entries in logs ordumps in a solution landscapeE2E Trace Analysis: Records the activity of a single user or a single process in detail
At the moment SAP MDM is only integrated to E2E Change Analysisand E2E Workload Analysis
© SAP 2007 / Page 17
Tools for Problem Detection and Resolution
.net C(++)ABAP Java .net
ComponentDiagnostics
Cross-ComponentDiagnostics
IT Reporting
Nail it Down
IsolateComponent
Analytics
• E2E Change Analysis• E2E Workload Analysis• E2E Exception Analysis• E2E Trace Analysis
SAP Solution Manager
Mor
e ag
greg
atio
n,le
ss s
kill
spec
ializ
atio
n
Health CheckMonitor and
Alert
Select
Evaluate
Aggregate
PROBLEM RESOLUTION = ROOT CAUSE ANALYSIS
PROBLEM DETECTION = SOLUTION MONITORING
End-to-End Root Cause Analysis:Overview
While E2E Change Analysis, E2EWorkload Analysis, and E2E ExceptionAnalysis cover the server side, E2E TraceAnalysis spans the full cycle of a user request –from client to server to disk.
SAP has licensed two third-party products to complete the key capabilities in rootcause analysis:
Wily Introscope for server-side root cause analysis. It is included in SAPSolution Manager for SAP standard componentsAppSight for client-side root cause analysis
© SAP 2007 / Page 18
E2E Trace Analysis
BMC Appsight forSAP Client Diagnostics
E2E Exception Analysis
E2E Workload AnalysisIntroscope
E2E Change Analysis
Introscope
ServerClient
AppSight for client-side root cause analysis
BMC AppSight® allows you to log the MDM applications (MDM Servers andMDM clients) on a Windows platform during runtime.
For the recording, the customer has to install what is called a BlackBox (for theMDM GUI clients) or a BlackBox Service (for the MDM Servers) and has to attacha specific MDM reporting profile to the BlackBox.
The easiest possibility is that the MDM application crash can be reproduced, soafter the BlackBox has started recording, the MDM application needs to be startedand the log file will be written at the end.
For further informationplease see:
http://service.sap.com/installMDM > Operations >MDM 5.5 SP05 - ProblemAnalysis with IdentifyAppsight (ZIP File)
© SAP 2007 / Page 20
Wily Introscope
ABAP
Java
J2EE
.Net
MDM
e.g., Duet,.Net PDK, MobileClient
e.g., Portal, JavaWD, XI,BillerDirect, CRM-ISA
e.g., IPC
e.g., R/3, BW, XI, APOCRM
E2E workloadanalysis
Introscope Enterprise ManagerCentral persistent repository for all Introscopeperformance data, installed by default onSolution Manager diagnostics machine
Reporting /EarlyWatch Alert
SAP BusinessIntelligence (BI)
SAP Solution Manager(J2EE / ABAP stack)
RFCInterface
Statistic performance data for ABAPAggregated performance data for non-ABAP
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
Introscope WorkstationSwing-based UI with twomajor components: theConsole and the Explorer
Introscope WebViewWeb-based graphical UI to displayIntroscopeperformance data, deployedon the SMD J2EE Engine
Configuration Reporting for SAP MDM
OS and DB Analysis for SAP MDM
Root Cause Analysis with SAP SolutionManager
Workload Analysis for SAP MDM
Misc.
© SAP 2007 / Page 22
Typical Questions
for customer internal and SAP support
I would like tocheck theunderlyingdatabase
What is thestatus of the
inbound ports ?
Can I see allactivities onyour host?
What version ofMDM is
installed?
Can I check theMDM serverlogs please?
MDM Command ConsoleFile System Browser and MDM Log DisplayMDM DB Monitoring
OS and DB Analysis for SAP MDM
MDM Command Console
The MDM Command Console provides functions to analyze severalaspects of the MDM server, repositories and Database.
It sends commands to the CLIX command line tool on the MDM serverand displays the result in Solution Manager.
The commands that can be executed from Solution Manager are non-manipulative commands that do not change the MDM server.
© SAP 2007 / Page 25
MDM Command Console
MDM provides local Activity Monitoring on CLIX base.This monitor is also visible within SMD:
On OS level:
MDM Command ConsoleExample: Activity Monitor
The MDS ActivityOverview command provides a snapshot over all clientrequests that are currently active or waiting in the MDM server. It providesan overview of MDS activity and can help to analyze performancebottlenecks.
“Matching” is running (State R), required a Read Repository lock andalready gained this lock.
MDM Activity Snapshot
Thread: Threadnumber of the
MDS thread thatexecutes the
request
State: Shows whetherthe thread is active orwaiting for a resourceW = waiting for some
resource, currently a lock,like server lock orrepository lock or
synchronization locksR = Run
User: User whotriggered the
request
Protocol : Reportsthe MDM internal
protocol used. Thedifferent clientscan access the
MDM server usingdifferent MDM
specific protocols.
Command: Showsthe command or MDS
method that iscurrently being
processed. Examplesfor methods are:
Login, StartMatching,GetAgencyKeys, …
Locks:Shows
the locksthe
requestholds orwants toacquire
…
Elapsed:Elapsedtime in
msec therequest isrunning
Connection :
Connection type
(e.g DataManager,
ImportServer, ..
Repository:Repository the
request is workingon
Locks
Meaning of the different columns:
R: Read / Shared LockW: Write / Exclusive lock
Columns 1-4:Wait for Lock
Columns 5-8:Hold Lock
HoldsSynchronisationRepsoitory Lock
HoldsSynchronisationServer Lock
HoldsRepositoryLock
HoldsServerLock
Waits forSynchronisationRepsoitory Lock
Waits forSynchronisationServer Lock
Waits forRepositoryLock
WaitsforServerLock
MDM Command ConsoleFile System Browser and MDM Log DisplayMDM DB Monitoring
OS and DB Analysis for SAP MDM
© SAP 2007 / Page 30
File System Browser
The File System Browser allows central and safe read-only access to theMDM installation directories.
Possibility to browse through the MDM installation directories, to displayMDM logs and to display files in the Distribution folders.
This allows SMD driven remote access to MDM log files without havingdirect OS access
© SAP 2007 / Page 31
File System Browser
In addition to the plain text log files the browser based display also isavailable inside SMD
MDM Command ConsoleFile System Browser and MDM Log DisplayMDM DB Monitoring
OS and DB Analysis for SAP MDM
© SAP 2007 / Page 33
MDM Database Monitoring
The DBA Cockpit in SAP Solution Manager provides databasemonitoring similar to the Database Performance Monitor (transaction ST04)in the Netweaver ABAP stack.
It allows to check the performance and configuration of the MDMDatabase and to check the database log for critical DB errors.
DBA Cockpit Documentation
1028751 *MaxDB1027336DB2 UDB1027512Microsoft SQL Server1028624OracleSAP NoteDBMS
* Online documentation for Remote Database Monitoring for MaxDB is available here:http://help.sap.com/saphelp_nw2004s/helpdata/en/fb/3e963c98bdc358e10000000a11405a/frameset.htm
OS and DB Analysis for SAP MDM
The MDM Command Console sends commands tothe CLIX command line tool on the MDM server anddisplays the result in Solution Manager
The File System Browser allows central andsafe read-only access to the MDMinstallation directories and MDM Log files.
The DBA Cockpitprovides databasemonitoring similar tothe DatabasePerformance Monitor(transaction ST04) inthe Netweaver ABAPstack.
Configuration Reporting for SAP MDM
OS and DB Analysis for SAP MDM
Root Cause Analysis with SAP SolutionManager
Workload Analysis for SAP MDM
Misc.
E2E Workload AnalysisComponent Workload Analysis with Wily Introscope
Overview
Workload Analysis for SAP MDM
© SAP 2007 / Page 38
End-to-End Workload Analysis: Architecture
ABAP
Java
J2EE
.Net
MDM
e.g., Duet,.Net PDK, MobileClient
e.g., Portal, JavaWD, XI,BillerDirect, CRM-ISA
e.g., IPC
e.g., R/3, BW, XI, APOCRM
E2E workloadanalysis
IntroscopeEnterprise Manager
Reporting /EarlyWatch Alert
SAP BusinessIntelligence (BI)
SAP Solution Manager(J2EE / ABAP stack)
RFCInterface
Statistic performance data for ABAPAggregated performance data for non-ABAP
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
IntroscopeWorkstation
IntroscopeWebView
MDM Diagnostics Architecture
E2E workloadanalysis
IntroscopeEnterprise Manager
Reporting /EarlyWatch Alert
SAP BusinessIntelligence (BI)
SAP SolutionManager
(J2EE / ABAPstack)
IntroscopeWebView
MDM 5.5.SP06
NCS Library
DiagnosticsAgent
NCS Profile
Monitored Server
SAPOsCol
IntroscopeWorkstation
© SAP 2007 / Page 40
E2E Workload Analysis vs Wily Introscope
E2E Workload AnalysisHourly aggregation of Wily
Introscope DataAllows to compare performance
data of multiple systemsData can be used for IT ReportingVery flexible data displayStarting point for cross-component
Root Cause Analysis
Wily IntroscopeNon aggregated Performance
and resource dataFiner granularity than E2E
Workload AnalysisCan be used for component
specific Root Cause Analysis
E2E Workload AnalysisComponent Workload Analysis with Wily Introscope
Overview
Workload Analysis for SAP MDM
End-to-End Workload Analysis: Overview
Select time frame
Workload overviewfor SAP MDM
Select diagram type
MDM-specific workloadmetrics
Compare important performance KPIs from different systems andsoftware components ( MDM, EP, XI, ERP...)
End-to-End Workload Analysis: WorkloadSummary for SAP MDM
MDMServer
Workload
ImportServer
Workload
SyndicationServer
Workload
Get an overview over the MDM workload in the selected timeframe
MDM Import Server – Single Steps
SAX Parser
Thread 1 Thread 2 Thread 3
Read File
Master Data Server(MDS)
Start task Trigger Port Scan Check if file is locatedin Inbound Port
StructuralTransformation
ValueTransformation Trigger Import Import new Records
into Repository
Master Data Import Server(MDIS)
End-to-End Workload Analysis: MDM ImportServer Workload Overview
Scanning Ports
xStructuralTransformer
xImporter
Master Data SyndicationServer (MDIS)
Master Data Server(MDS)
MDM Syndication Server – Single Steps (1/2)
Sanity Check
Adjust Map
Retrieve Chunk
Trigger query(Begin Syndication) Execute Query
Set timestamp (perrecord and client)(Repository Look)
Request Chunk
Write Temp File
Save timestamp(Last Syndication
Attempt)
Save New Keys
DB
Retrieve map
MDM Syndication Server – Single Steps (2/2)
Master Data SyndicationServer (MDIS)
Master Data Server(MDS)
DB
Send temp file to MDS(Copy to Port)
Gather temp. files
Copy Log to port
Request Commit Update time stamp tofirst attempted timestamp
Copy to MDS Outbounddistrib. ready folder
Unwrap BLOB
Update timestamp
End-to-End Workload Analysis: MDMSyndication Server Workload Overview
Query Execution
Export
Copy to Memory
Copy to Port
© SAP 2007 / Page 49
End-to-End Workload Analysis: Time profile
Analyze statistics for workload and performance distribution over the hourof the day
End-to-End Workload Analysis: Time profile
Check the influence of imports and syndications on the MDS performanceby comparing the MDSS/MDIS time profiles to the MDS time profile
© SAP 2007 / Page 51
End-to-End Workload Analysis: Files inDistribution Folder
Identify backlogs (unprocessed files) during imports and syndications
Files in ready andexception folder for
inbound andoutbound processing
© SAP 2007 / Page 52
End-to-End Workload Analysis: Repositories
Get an overview over repository size and growth
Repositories
© SAP 2007 / Page 53
End-to-End Workload Analysis:Memory Allocation
Check Memory allocation of MDM server processes
© SAP 2007 / Page 54
End-to-End Workload Analysis: CPU & Memory Util.
Check CPU utilization and paging of servers
End-to-End Workload Analysis: Summary
E2E Workload AnalysisComponent Workload Analysis with Wily Introscope
Overview
Workload Analysis for SAP MDM
© SAP 2007 / Page 57
Typical Questions
Are there longrunning lockson my MDM
server?
When did theperformanceissue occur?
What’s wrongwith my MDM
host?
Which is theperformancebottleneck?
Did the amountof data growsignificantly?
© SAP 2007 / Page 58
End-to-End Workload Analysis: Architecture
ABAP
Java
J2EE
.Net
MDM
e.g., Duet,.Net PDK, MobileClient
e.g., Portal, JavaWD, XI,BillerDirect, CRM-ISA
e.g., IPC
e.g., R/3, BW, XI, APOCRM
E2E workloadanalysis
IntroscopeEnterprise Manager
Reporting /EarlyWatch Alert
SAP BusinessIntelligence (BI)
SAP Solution Manager(J2EE / ABAP stack)
RFCInterface
Statistic performance data for ABAPAggregated performance data for non-ABAP
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
DiagnosticsAgent
IntroscopeWorkstation
IntroscopeWebView
MDM Diagnostics Architecture
E2E workloadanalysis
IntroscopeEnterprise Manager
Reporting /EarlyWatch Alert
SAP BusinessIntelligence (BI)
SAP SolutionManager
(J2EE / ABAPstack)
IntroscopeWebView
MDM 5.5.SP06
NCS Library
DiagnosticsAgent
NCS Profile
Monitored Server
SAPOsCol
IntroscopeWorkstation
Wily Introscope
Compared to the E2E Workload Analysis, Wily Introscope provides non-aggregated performance and resource data in a finer granularity.
The Wily Introscope can be used for Ad hoc analysis of resourceconsumption and system behavior and the analysis of the health status ofthe system.
It provides live and historical data in graphical form.
Performing the component specific Workload Analysis with WilyIntroscope is applicable if the E2E Workload Analysis indicates that theroot cause of performance problems is in the MDM server and
you would like to nail down the problem oryou want to analyze the last minutes load on the MDM server as this
information is not yet available in the E2E Workload Analysis.
Introscope Web View
Select dashboard “1 SAP MDM Overview” to start the analysis
Select Introscope Webview
© SAP 2007 / Page 62
MDM Overview Dashboard
MDMServer
Workload
Import andSyndication
ServerWorkload
Repositoryinformation
& OSRessources
Wily Dashboards combine singular metrics display in complexsynchronized charts
e.g. SAP MDM – Overview combines Client Requests and Resource Allocation on onescreen
© SAP 2007 / Page 63
MDM Overview Dashboard - MDS
Client Requests –Average Response
time in msec per15 sec. interval
Client Requests – Max. Responsetime in msec per 15 sec. interval
38 141
01/07/08 02:09:15 PM
Hold Cursor over a data point to getdetailed information
Host: P127615Performance Metric reported by Master Data ServerClient Request from MDM Data ManagerAverage Elapsed Time was 38 msecMax Elapsed Time was 141 msec26 Client Requests from MDM Data Manager were
executed during the measurement time intervalMeasurement Time Interval: Jan. 7,2008 02:09:00 – 02:09:15 PM
Details for Master Data Server Performance
The dashboard “SAP MDM - Master Data Server Performance” providesperformance details for:
Client RequestsDatabaseLocks
© SAP 2007 / Page 64
Queue processing/ Locking
ReadRequest
ReadRequest
ReadRequest
T1
WriteRequest
ReadRequest
ReadRequest
T2
ReadRequest
WriteRequest
ReadRequest
T3
ReadRequest
WriteRequest
T4
ReadRequest
T5
Write (exclusive) lock
Read (shared) lock
ReadRequest
ReadRequest
waits
waits
waits
waits
waits
Repository Repository Repository Repository Repository
Hold repositoryread locks
Hold repositoryread locks
Holds repositoryread lock
Holds repositorywrite lock
Hold repositoryread locks
© SAP 2007 / Page 65
Details for Master Data Server ActivityOverview
The dashboard “SAP MDM - Master Data Activity Overview” provides anoverview of the waiting and active requests as well of the number of writeand read locks in the selected time interval.
© SAP 2007 / Page 66
Active or WaitingRequests for :
Repository Read LockRepository Write LockServer Read LockServer Write LockSynchronization
Repository Read LockSynchronization
Repository Write LockSynchronization Server
Read LockSynchronization Server
Write Lock
MDIS and MDSS Performance and WorkloadOverview
The charts in the second section of the SAP MDM Overview dashboardprovide performance and workload overview for the Import andSyndication Server.
Details for Imports and Syndications
The MDIS/ MDSS Performance details dashboard with more detailedmetrics for Import and Syndication performance.
Scanning PortsxStructuralTrans.xImporter
Query ExecutionExportCopy to MemoryCopy to Port
Details for Import and Syndication Activities
The MDIS/ MDSS Activity Overview leads to a dashboard with moredetailed metrics for current running (Active Counter) import andsyndication steps.
Active importand syndicationsteps
Files to be importedor syndicated in/ fromthe “Ready” folder orexception folder of thecorrespondent ports
Wily Introscope: Summary
Wily Introscope: Summary
© SAP 2007 / Page 72
MDM Workload with Wily IntroscopeExample: Import Server Activities
Import Server activities in 20 minutes between 2 pm and 2.20
Number of Inbound Files / Inbound Exceptions at the given timeframe
© SAP 2007 / Page 73
MDM Workload with Wily IntroscopeExample: Import Server Activities
Import Server activities zoomed to the last 20 minutes
MDM Workload with Wily IntroscopeExample: Import Server Activities/ Locking
The import is triggered via the import server. This will require a repository readlock (1) first and then for importing the data to the repository, write locks (2) arerequired.
1
1
2
2
MDM Workload with Wily IntroscopeExample: Import of a file with 7000 records
Structuraltransformationof chunk 1
Structuraltransformationof chunk 2
Structuraltransformationof chunk 3
Import ofchunk 1
Import ofchunk 2
Import ofchunk 3
7000 records and chunk size = 3000 3 chunks
MDM Workload with Wily IntroscopeExample: Mass Change in Data Manager
A user performs a mass change of records via the MDM Data Manager (1). Thiswill require repository write locks (2) for changing the records in the repository
1
2
MDM Workload with Wily IntroscopeExample: Mass Change and Parallel User Action
A user performs a mass change of records via the MDM Data Manager (1). Thiswill require repository write locks (2) for changing the records in the repository.Now a second user tries to acquire a repository read lock (3) on the samerepository. Due to the write locks of the first operation the average response togain the lock will increase.
3
2
1
MDM Workload with Wily IntroscopeExample: Number of Workflows in Memory
The chart shows the number of pre-launched and launched workflow jobs inmemory.
One of the three pre launched workflows is
2) Completed 3) deleted
The workflow jobs will be kept in memory even if the status is“completed”. Delete the workflow items on a regular basis.
1) Launched
© SAP 2007 / Page 79
MDM Workload with Wily IntroscopeExample: Host OS situation
Checking MDM Host OS situation
The total CPUutilization of theserver in % shouldnot exceed 70 - 80 %over a long time.
The paging shouldnot exceed 10% of theserver memory / hour.
The disk utilizationshould not exceed50% over long time.
© SAP 2007 / Page 80
Workload Analysis for SAP MDM
E2E Workload AnalysisHourly aggregation of Wily
Introscope DataAllows to compare performance
data of multiple systemsData can be used for IT
ReportingVery flexible data displayStarting point for cross-
component Root Cause Analysis
Wily IntroscopeNon aggregated Performance and
resource dataFiner granularity than E2E Workload
AnalysisCan be used for component specific
Root Cause Analysis
Configuration Reporting for SAP MDM
OS and DB Analysis for SAP MDM
Root Cause Analysis with SAP SolutionManager
Workload Analysis for SAP MDM
Misc.
© SAP 2007 / Page 82
Typical Questions
Is there ONEplace where allchanges in the
solution arelisted?
Did we changeany technicalconfigurationparameters?
How manyABAP/JAVA
transports wereimported last
week?
When did weimport
ABAP/JAVAsupport
packages?
Which systemsof my solutionwere changed?
E2E Change Analysis
The E2E Change Analysis as well as the Configuration and File Reportingfor SAP MDM are applicable
if the system behaves differently after a certain date orif you would like to find out which technical parameters were changed.
Configuration and file Reporting allows to display the MDM configurationfiles, to quickly identify modified lines in the configuration files and also tocompare different versions of the configuration files.
E2E Change Analysis – Summary
The screen provides an overview over the MDM Server component(MDS, MDIS, MDSS) where technical parameter changes were applied.
© SAP 2007 / Page 85
E2E Change Analysis - Details
Overview of number of changes to ini files
© SAP 2007 / Page 86
E2E Change Analysis – Details
Which line in the ini file was changed when?What was the initial value ?What is the current value ?
© SAP 2007 / Page 87
Configuration Browser
SMD provides a configuration browser to display the MDM configuration files
The comparison between different states is possible
In this example, the parameter file wasfirst created on Oct. 19 2007.The line was changed on Oct 24 and
on Oct 25, 2007.
Configuration Reporting for SAP MDM
Configuration and file Reporting allows to display the MDM configuration files, toquickly identify modified lines in the configuration files and also to compare differentversions of the configuration files.
Configuration Reporting for SAP MDM
OS and DB Analysis for SAP MDM
Root Cause Analysis with SAP SolutionManager
Workload Analysis for SAP MDM
Misc.
© SAP 2007 / Page 90
Prerequisites and Availability
MDM 5.5 SP6 P1 – Available Q1 08Wily Introscope Instrumentation for performance and resource consumption measurementon Win32/ Win64 and all MDM UNIX/LINUX platformsEnriched Log/Trace FilesActivity Monitor
Solution Manager 4.0 SP15 - Available Feb. 2008MDM specific Root Cause Analysis contentE2E workload analysis for MDME2E configuration change analysis for MDMRemote DB MonitoringPlease see note 662441 and note 1126859
How to Guides
How to Guides:
“How to perform Root Cause Analysis for SAP MDM with SolutionManager “www.sdn.sap.com/irj/sdn/howtoguides > Data Unification
“How To…setup SMD for MDM Root Cause Analysis – MDM 5.5 SP06”
Available in March 2008
Webinar “Root Cause Analysis with SAP Solution Manager”https://www.sdn.sap.com/irj/sdn/event/webinarsAvailable in May 2008
© SAP 2007 / Page 92
Links
http://service.sap.com/diagnostic
http://service.sap.com/installMDM
www.sdn.sap.com/irj/sdn/howtoguides
Feedback
SAP NetWeaver RIG and AGS are planning a feedback project onthe usage of Solution Manager Diagnostics for MDM
Purpose of this is to gather customer feedback about the newfunctionalities for Root Cause Analysis and Monitoring and roll thisfeedback in
The feedback is based on a questionnaire
Time range: March 2008 - August 2008
If you are interested in sharing your experiences with the usage ofSolution Manager Diagnostics for MDM please let me know
© SAP 2007 / Page 94
Thank you!
© SAP 2007 / Page 95
Copyright 2007 SAP AGAll 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 changedwithout prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective 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 andassociated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains 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. 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, orother 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 ofmerchantability, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.
Alle Rechte vorbehalten.