You are on page 1of 95

Root Cause Analysis for SAP MDM 5.

5 SP06 with SAP Solution Manager


Diagnostics

Detlef Thoms, SAP NetWeaver RIG EMEA Patrick Richarts, AGS Markus Breiter, MDM Development March 2008

Authors

Detlef Thoms has ten years of SAP experience that he has gained in Development Support in the software development and as SCM Senior Solution Consultant in SAP projects and numerous SAP implementations. Since January 2006 he is working for SAP NetWeaver RIG in the area of Master Data Management.

Patrick Richarts started at SAP Support in 1998. He was responsible for the development of services and trainings for CRM and Mobile Infrastructure and delivered many onsite and remote services to SAPs customers. Since 2006 he works in the Global Center of Expertise on the integration of various SAP products into the Root Cause Analysis scenario of SAP Solution Manager.

Markus Breiter is a senior developer in SAP MDM and has eleven years of SAP experience that he gained mainly in application development. According to his customer orientation in the last years he focused on the integration of standard SAP support and operation tools to the MDM application. He joined the MDM development team from the start.

Root Cause Analysis with SAP Solution Manager OS and DB Analysis for SAP MDM Workload Analysis for SAP MDM Configuration Reporting for SAP MDM Misc.

Root Cause Analysis with SAP Solution Manager

SAP Solution Manager Overview Introduction to Root Cause Analysis and Monitoring

SAP Solution Manager Scenarios


Implementation of SAP solutions
SAP methods and tools Global rollout Customizing synchronization E-learning management Test management

Solution Monitoring
System monitoring Business process monitoring Central system administration Solution reporting Service level reporting SAP EarlyWatch Alert

CORE BUSINESS PROCESSES

Upgrade of SAP solutions


SAP methods and tools E-learning management Test management

Service Desk
SAP Best Practices for incident management Integration of thirdparty help desks

Change Request Management


Follows ITIL standards Maintenance processes

Root Cause Analysis


Delivery of SAP Services On-site/remote delivery Issue management
Safe remote access Performance measurement Logs and dumps Traces Technical configuration

SAP 2007 / Page 5

Root Cause Analysis with SAP Solution Manager

SAP Solution Manager Overview Introduction to Root Cause Analysis and Monitoring

Diagnostics and Monitoring for MDM customers


CLIX Command Interface

MDM Server Components

Solution Manager 4.0


Browser access to Diagnostics

Diagnostics for SAP MDM


E2E Workload Analysis E2E Change Analysis Wily Introscope EM Remote DB Monitoring

Diagnostics Agent

SAPOSCOL Import Server Syndication Server Layout Server MDM Server

Remote access to CCMS

DB

Netviewer access to MDM GUI tools (only if GUI tools must be analyzed)

Clix Command Interface

EP
File System Browser / MDM Log Display Configuration Reporting

XI

Internet

Win32 client with MDM Client Components


Netviewer Client AppSight BlackBox Data Manager Console

AppSight Console for


analysis of performance problems or crashes of MDM GUI components

CEN
CCMS
MDM Server Monitoring Configuration Reporting

SAP 2007 / Page 7

Logs

MDM log files are stored in a common directory on your MDM Server machine

In addition to the normal informational and error log messages, the MDM server can also write performance data to the MDM Server log The extent of the information that is written to the MDM server log can be controlled with the following mds.ini parameters:
Protocol Log Level Database Log Level

Clix

CLIX is a separate MDM application that allows you to manage the MDM software and MDM repositories using a command line interface instead of the MDM Console

In the case you intend to use external/third-party monitoring tools for MDM monitoring, the MDM CLIX command line utility can be used to monitor specific aspects of the MDM application components

Netviewer Application Sharing Tool for SAP Support


SAP DMZ Netviewer Server

Internet 5
Join session https

4
Customer PC with Netviewer Participant Client https

Start session

Initiate session

Provide ID

1
Logging
User1 Inst . User1 Inst .

Request session

CSS

SAP Support Engineer PC with Netviewer Consultant Client

Central Monitoring System (CEN)


MDM CCMS monitoring is based on the Central Monitoring System (CEN) CCMS monitoring is based on the ABAP stack of a Web AS (Web Application Server). The CCMS application collects the monitoring information for all connected systems and applications in this system.

CCMS Monitoring Template


All MDM-specific monitors are available in the CCMS standard trees

MDM_DLL SAPOSCOL/ ProcMon LogMon ConfMon SAPOSCOL/ ProcMon

MDM_DLL: MDM-specific shared library provides monitoring data, such as availability and performance criteria, to the central monitoring system CEN via CCMS agent. SAPOSCOL: The SAP OS collector SAPOSCOL delivers operating system-specific data to the CEN via the CCMS agent. This includes CPU and memory consumption as well as ProcMon monitoring for monitoring single processes running or not running on the PC.

LogMon monitoring is provided by the CCMS agent and is based on configuration files, while ProcMon monitoring is based on an additional executable to be installed.

CCMS: MDM Server Heartbeat

The MDM alert/heartbeat monitoring for the MDM-based business scenarios


Heartbeat Availability

Servers

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 supported on Unix platforms

Tools for Problem Detection and Resolution

SAP Solution Manager introduces a new layer of diagnostics that aims to isolate the component that is the root cause for an incident. On top of this root cause analysis (problem resolution), Solution Monitoring and IT Reporting aim to detect problems proactively and report on capacity trends, service level agreements, and solution quality. SAP Solution Manager 4.0 features four-cross component diagnostics capabilities:
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 solution landscape E2E Exception Analysis: Isolates exceptional situations, such as fatal entries in logs or dumps in a solution landscape E2E 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 Analysis and E2E Workload Analysis

Tools for Problem Detection and Resolution

IT Reporting Analytics

PROBLEM DETECTION = SOLUTION MONITORING SAP Solution Manager

Health Check Monitor and Alert Cross-Component Diagnostics Isolate Component Component Diagnostics Nail it Down
SAP 2007 / Page 17

Aggregate Evaluate

E2E Change Analysis E2E Workload Analysis E2E Exception Analysis E2E Trace Analysis Select ABAP Java .net .net C(++)

PROBLEM RESOLUTION = ROOT CAUSE ANALYSIS

More aggregation, less skill specialization

End-to-End Root Cause Analysis: Overview


While E2E Change Analysis, E2E Workload Analysis, and E2E Exception Analysis cover the server side, E2E Trace Analysis 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 root cause analysis: Wily Introscope for server-side root cause analysis. It is included in SAP Solution Manager for SAP standard components AppSight for client-side root cause analysis
Client Server

E2E Change Analysis


Introscope

E2E Workload Analysis E2E Exception Analysis

BMC Appsight for SAP Client Diagnostics Introscope


SAP 2007 / Page 18

E2E Trace Analysis

AppSight for client-side root cause analysis


BMC AppSight allows you to log the MDM applications (MDM Servers and MDM clients) on a Windows platform during runtime. For the recording, the customer has to install what is called a BlackBox (for the MDM GUI clients) or a BlackBox Service (for the MDM Servers) and has to attach a specific MDM reporting profile to the BlackBox. The easiest possibility is that the MDM application crash can be reproduced, so after the BlackBox has started recording, the MDM application needs to be started and the log file will be written at the end.

For further information please see: http://service.sap.com/in stallMDM > Operations > MDM 5.5 SP05 - Problem Analysis with Identify Appsight (ZIP File)

Wily Introscope

ABAP

RFC Interface

Introscope Workstation Swing-based UI with two major components: the Console and the Explorer

E2E workload analysis

Reporting / EarlyWatch Alert

e.g., R/3, BW, XI, APO CRM SAP Business Intelligence (BI)

Java
e.g., IPC

Diagnostics Agent Introscope WebView Web-based graphical UI to display Introscopeperformance data, deployed on the SMD J2EE Engine

J2EE

Diagnostics Agent

e.g., Portal, JavaWD, XI, BillerDirect, CRM-ISA

.Net

Diagnostics Agent

Introscope Enterprise Manager Central persistent repository for all Introscope performance data, installed by default on Solution Manager diagnostics machine

e.g., Duet, .Net PDK, MobileClient

SAP Solution Manager (J2EE / ABAP stack)

MDM
SAP 2007 / Page 20

Diagnostics Agent

Statistic performance data for ABAP Aggregated performance data for non-ABAP

Root Cause Analysis with SAP Solution Manager OS and DB Analysis for SAP MDM Workload Analysis for SAP MDM Configuration Reporting for SAP MDM Misc.

Typical Questions
for customer internal and SAP support

Can I see all activities on your host? What is the status of the inbound ports ? What version of MDM is installed?

I would like to check the underlying database

Can I check the MDM server logs please?

SAP 2007 / Page 22

OS and DB Analysis for SAP MDM

MDM Command Console File System Browser and MDM Log Display MDM DB Monitoring

MDM Command Console

The MDM Command Console provides functions to analyze several aspects of the MDM server, repositories and Database. It sends commands to the CLIX command line tool on the MDM server and displays the result in Solution Manager. The commands that can be executed from Solution Manager are nonmanipulative commands that do not change the MDM server.

MDM Command Console


MDM provides local Activity Monitoring on CLIX base. This monitor is also visible within SMD:

On OS level:

SAP 2007 / Page 25

MDM Command Console Example: Activity Monitor


The MDS ActivityOverview command provides a snapshot over all client requests that are currently active or waiting in the MDM server. It provides an overview of MDS activity and can help to analyze performance bottlenecks.

Matching is running (State R), required a Read Repository lock and already gained this lock.

MDM Activity Snapshot


Thread: Thread number of the MDS thread that executes the request User: User who triggered the request Command: Shows the command or MDS method that is currently being processed. Examples for methods are: Login, StartMatching, GetAgencyKeys,

Elapsed: Elapsed time in msec the request is running

Repository: Repository the request is working on

State: Shows whether the thread is active or waiting for a resource W = waiting for some resource, currently a lock, like server lock or repository lock or synchronization locks R = Run

Protocol : Reports the MDM internal protocol used. The different clients can access the MDM server using different MDM specific protocols.

Locks: Shows the locks the request holds or wants to acquire

Connecti on : Connectio n type (e.g Data Manager, Import Server, ..

Locks

R: Read / Shared Lock W: Write / Exclusive lock

Meaning of the different columns:

Columns 1-4: Wait for Lock

Columns 5-8: Hold Lock

Waits for Server Lock

Waits for Repository Lock

Waits for Synchronisation Server Lock

Waits for Synchronisation Repsoitory Lock

Holds Server Lock

Holds Repository Lock

Holds Synchronisation Server Lock

Holds Synchronisation Repsoitory Lock

OS and DB Analysis for SAP MDM

MDM Command Console File System Browser and MDM Log Display MDM DB Monitoring

File System Browser


The File System Browser allows central and safe read-only access to the MDM installation directories. Possibility to browse through the MDM installation directories, to display MDM logs and to display files in the Distribution folders. This allows SMD driven remote access to MDM log files without having direct OS access

SAP 2007 / Page 30

File System Browser


In addition to the plain text log files the browser based display also is available inside SMD

SAP 2007 / Page 31

OS and DB Analysis for SAP MDM

MDM Command Console File System Browser and MDM Log Display MDM DB Monitoring

MDM Database Monitoring


The DBA Cockpit in SAP Solution Manager provides database monitoring similar to the Database Performance Monitor (transaction ST04) in the Netweaver ABAP stack. It allows to check the performance and configuration of the MDM Database and to check the database log for critical DB errors.

SAP 2007 / Page 33

DBA Cockpit Documentation

DBMS Oracle Microsoft SQL Server DB2 UDB MaxDB

SAP Note 1028624 1027512 1027336 1028751 *

* 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 to the CLIX command line tool on the MDM server and displays the result in Solution Manager

The DBA Cockpit provides database monitoring similar to the Database Performance Monitor (transaction ST04) in the Netweaver ABAP stack.

The File System Browser allows central and safe read-only access to the MDM installation directories and MDM Log files.

Root Cause Analysis with SAP Solution Manager OS and DB Analysis for SAP MDM Workload Analysis for SAP MDM Configuration Reporting for SAP MDM Misc.

Workload Analysis for SAP MDM

Overview E2E Workload Analysis Component Workload Analysis with Wily Introscope

End-to-End Workload Analysis: Architecture

ABAP

RFC Interface

E2E workload analysis

Reporting / EarlyWatch Alert

e.g., R/3, BW, XI, APO CRM

Introscope Workstation
SAP Business Intelligence (BI)

Java
e.g., IPC

Diagnostics Agent

Introscope WebView
Diagnostics Agent Introscope Enterprise Manager

J2EE

e.g., Portal, JavaWD, XI, BillerDirect, CRM-ISA

.Net

Diagnostics Agent

e.g., Duet, .Net PDK, MobileClient

SAP Solution Manager (J2EE / ABAP stack)

MDM
SAP 2007 / Page 38

Diagnostics Agent

Statistic performance data for ABAP Aggregated performance data for non-ABAP

MDM Diagnostics Architecture


Monitored Server SAP Solution Manager (J2EE / ABAP stack)

E2E workload analysis

Reporting / EarlyWatch Alert

MDM 5.5. SP06

SAP Business Intelligence (BI)

NCS Library

Introscope Workstation

NCS Profile

Diagnostics Agent

Introscope WebView

SAPOsCol

Introscope Enterprise Manager

E2E Workload Analysis vs Wily Introscope

E2E Workload Analysis


Hourly aggregation of Wily Introscope Data Allows to compare performance data of multiple systems Data can be used for IT Reporting Very flexible data display Starting point for cross-component Root Cause Analysis

Wily Introscope
Non aggregated Performance and resource data Finer granularity than E2E Workload Analysis Can be used for component specific Root Cause Analysis

SAP 2007 / Page 40

Workload Analysis for SAP MDM

Overview E2E Workload Analysis Component Workload Analysis with Wily Introscope

End-to-End Workload Analysis: Overview


Compare important performance KPIs from different systems and software components ( MDM, EP, XI, ERP...)
Select time frame MDM-specific workload metrics

Workload overview for SAP MDM

Select diagram type

End-to-End Workload Analysis: Workload Summary for SAP MDM


Get an overview over the MDM workload in the selected timeframe

MDM Server Workload

Import Server Workload

Syndication Server Workload

MDM Import Server Single Steps


Master Data Import Server (MDIS) Master Data Server (MDS)

Start task

Trigger Port Scan

Read File

Check if file is located in Inbound Port

Structural Transformation

Value Transformation

Trigger Import

Import new Records into Repository

SAX Parser

Thread 1

Thread 2

Thread 3

End-to-End Workload Analysis: MDM Import Server Workload Overview

Scanning Ports

xStructuralTransformer

xImporter

MDM Syndication Server Single Steps (1/2)

Master Data Syndication Server (MDIS)


Sanity Check

Master Data Server (MDS)

DB

Retrieve map

Adjust Map

Trigger query (Begin Syndication)

Execute Query

Set timestamp (per record and client) (Repository Look)

Save timestamp (Last Syndication Attempt)

Request Chunk

Retrieve Chunk

Save New Keys

Write Temp File

MDM Syndication Server Single Steps (2/2)

Master Data Syndication Server (MDIS)


Request Commit

Master Data Server (MDS)


Update time stamp to first attempted timestamp

DB

Update timestamp

Gather temp. files

Send temp file to MDS (Copy to Port)

Unwrap BLOB

Copy to MDS Outbound distrib. ready folder

Copy Log to port

End-to-End Workload Analysis: MDM Syndication Server Workload Overview

Query Execution

Export

Copy to Memory

Copy to Port

End-to-End Workload Analysis: Time profile


Analyze statistics for workload and performance distribution over the hour of the day

SAP 2007 / Page 49

End-to-End Workload Analysis: Time profile

Check the influence of imports and syndications on the MDS performance by comparing the MDSS/MDIS time profiles to the MDS time profile

End-to-End Workload Analysis: Files in Distribution Folder


Identify backlogs (unprocessed files) during imports and syndications

Files in ready and exception folder for inbound and outbound processing

SAP 2007 / Page 51

End-to-End Workload Analysis: Repositories


Get an overview over repository size and growth

Repositories

SAP 2007 / Page 52

End-to-End Workload Analysis: Memory Allocation


Check Memory allocation of MDM server processes

SAP 2007 / Page 53

End-to-End Workload Analysis: CPU & Memory Util.


Check CPU utilization and paging of servers

SAP 2007 / Page 54

End-to-End Workload Analysis: Summary

Workload Analysis for SAP MDM

Overview E2E Workload Analysis Component Workload Analysis with Wily Introscope

Typical Questions

Whats wrong with my MDM host? When did the performance issue occur? Which is the performance bottleneck?

Are there long running locks on my MDM server?

Did the amount of data grow significantly?

SAP 2007 / Page 57

End-to-End Workload Analysis: Architecture

ABAP

RFC Interface

E2E workload analysis

Reporting / EarlyWatch Alert

e.g., R/3, BW, XI, APO CRM

Introscope Workstation
SAP Business Intelligence (BI)

Java
e.g., IPC

Diagnostics Agent

Introscope WebView
Diagnostics Agent Introscope Enterprise Manager

J2EE

e.g., Portal, JavaWD, XI, BillerDirect, CRM-ISA

.Net

Diagnostics Agent

e.g., Duet, .Net PDK, MobileClient

SAP Solution Manager (J2EE / ABAP stack)

MDM
SAP 2007 / Page 58

Diagnostics Agent

Statistic performance data for ABAP Aggregated performance data for non-ABAP

MDM Diagnostics Architecture


Monitored Server SAP Solution Manager (J2EE / ABAP stack)

E2E workload analysis

Reporting / EarlyWatch Alert

MDM 5.5. SP06

SAP Business Intelligence (BI)

NCS Library

Introscope Workstation

NCS Profile

Diagnostics Agent

Introscope WebView

SAPOsCol

Introscope Enterprise Manager

Wily Introscope

Compared to the E2E Workload Analysis, Wily Introscope provides nonaggregated performance and resource data in a finer granularity. The Wily Introscope can be used for Ad hoc analysis of resource consumption and system behavior and the analysis of the health status of the system. It provides live and historical data in graphical form. Performing the component specific Workload Analysis with Wily Introscope is applicable if the E2E Workload Analysis indicates that the root cause of performance problems is in the MDM server and you would like to nail down the problem or you 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 Introscope Webview

Select dashboard 1 SAP MDM Overview to start the analysis

MDM Overview Dashboard


Wily Dashboards combine singular metrics display in complex synchronized charts
e.g. SAP MDM Overview combines Client Requests and Resource Allocation on one screen
MDM Server Workload

Import and Syndication Server Workload

Repository information & OS Ressources

SAP 2007 / Page 62

MDM Overview Dashboard - MDS


Client Requests Max. Response time in msec per 15 sec. interval

Client Requests Average Response time in msec per 15 sec. interval

Hold Cursor over a data point to get detailed information


Host: P127615 Performance Metric reported by Master Data Server Client Request from MDM Data Manager Average Elapsed Time was 38 msec Max Elapsed Time was 141 msec 26 Client Requests from MDM Data Manager were executed during the measurement time interval Measurement Time Interval: Jan. 7, 2008 02:09:00 02:09:15 PM

38

141
01/07/08 02:09:15 PM

SAP 2007 / Page 63

Details for Master Data Server Performance


The dashboard SAP MDM - Master Data Server Performance provides performance details for:
Client Requests Database Locks

SAP 2007 / Page 64

Queue processing/ Locking


Write (exclusive) lock Read (shared) lock

T1

T2

T3

T4
Read Request
waits

T5
Read Request Read Request

Read Request Write Request Read Request Read Request Read Request Read Request Read Request
waits

waits

Read Request Write Request

waits

Write Request Read Request

waits

Hold repository read locks Hold repository read locks Hold repository read locks Holds repository read lock Holds repository write lock

Repository
SAP 2007 / Page 65

Repository

Repository

Repository

Repository

Details for Master Data Server Activity Overview


The dashboard SAP MDM - Master Data Activity Overview provides an overview of the waiting and active requests as well of the number of write and read locks in the selected time interval.
Active or Waiting Requests for : Repository Read Lock Repository Write Lock Server Read Lock Server Write Lock Synchronization Repository Read Lock Synchronization Repository Write Lock Synchronization Server Read Lock Synchronization Server Write Lock

SAP 2007 / Page 66

MDIS and MDSS Performance and Workload Overview


The charts in the second section of the SAP MDM Overview dashboard provide performance and workload overview for the Import and Syndication Server.

Details for Imports and Syndications

The MDIS/ MDSS Performance details dashboard with more detailed metrics for Import and Syndication performance.

Scanning Ports xStructuralTrans. xImporter

Query Execution Export Copy to Memory Copy to Port

Details for Import and Syndication Activities

The MDIS/ MDSS Activity Overview leads to a dashboard with more detailed metrics for current running (Active Counter) import and syndication steps.

Active import and syndication steps

Files to be imported or syndicated in/ from the Ready folder or exception folder of the correspondent ports

Wily Introscope: Summary

Wily Introscope: Summary

MDM Workload with Wily Introscope Example: 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 72

MDM Workload with Wily Introscope Example: Import Server Activities


Import Server activities zoomed to the last 20 minutes

SAP 2007 / Page 73

MDM Workload with Wily Introscope Example: Import Server Activities/ Locking
The import is triggered via the import server. This will require a repository read lock (1) first and then for importing the data to the repository, write locks (2) are required.

MDM Workload with Wily Introscope Example: Import of a file with 7000 records

7000 records and chunk size = 3000

3 chunks

Structural transformation of chunk 2

Structural transformation of chunk 3

Import of chunk 1

Import of chunk 2

Import of chunk 3

Structural transformation of chunk 1

MDM Workload with Wily Introscope Example: Mass Change in Data Manager
A user performs a mass change of records via the MDM Data Manager (1). This will require repository write locks (2) for changing the records in the repository

MDM Workload with Wily Introscope Example: Mass Change and Parallel User Action
A user performs a mass change of records via the MDM Data Manager (1). This will 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 same repository. Due to the write locks of the first operation the average response to gain the lock will increase.

MDM Workload with Wily Introscope Example: Number of Workflows in Memory


The chart shows the number of pre-launched and launched workflow jobs in memory.

One of the three pre launched workflows is 1) Launched 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.

MDM Workload with Wily Introscope


Example: Host OS situation
Checking MDM Host OS situation

The total CPU utilization of the server in % should not exceed 70 - 80 % over a long time.

The paging should not exceed 10% of the server memory / hour.

The disk utilization should not exceed 50% over long time.

SAP 2007 / Page 79

Workload Analysis for SAP MDM

E2E Workload Analysis Hourly aggregation of Wily Introscope Data Allows to compare performance data of multiple systems Data can be used for IT Reporting Very flexible data display Starting point for crosscomponent Root Cause Analysis

Wily Introscope Non aggregated Performance and resource data Finer granularity than E2E Workload Analysis Can be used for component specific Root Cause Analysis

SAP 2007 / Page 80

Root Cause Analysis with SAP Solution Manager OS and DB Analysis for SAP MDM Workload Analysis for SAP MDM Configuration Reporting for SAP MDM Misc.

Typical Questions

Did we change any technical configuration parameters?

How many ABAP/JAVA transports were imported last week?

When did we import ABAP/JAVA support packages?

Is there ONE place where all changes in the solution are listed?

Which systems of my solution were changed?

SAP 2007 / Page 82

E2E Change Analysis

The E2E Change Analysis as well as the Configuration and File Reporting for SAP MDM are applicable if the system behaves differently after a certain date or if you would like to find out which technical parameters were changed. Configuration and file Reporting allows to display the MDM configuration files, to quickly identify modified lines in the configuration files and also to compare 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.

E2E Change Analysis - Details


Overview of number of changes to ini files

SAP 2007 / Page 85

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 86

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 was first created on Oct. 19 2007. The line was changed on Oct 24 and on Oct 25, 2007.
SAP 2007 / Page 87

Configuration Reporting for SAP MDM

Configuration and file Reporting allows to display the MDM configuration files, to quickly identify modified lines in the configuration files and also to compare different versions of the configuration files.

Root Cause Analysis with SAP Solution Manager OS and DB Analysis for SAP MDM Workload Analysis for SAP MDM Configuration Reporting for SAP MDM Misc.

Prerequisites and Availability

MDM 5.5 SP6 P1 Available Q1 08


Wily Introscope Instrumentation for performance and resource consumption measurement on Win32/ Win64 and all MDM UNIX/LINUX platforms Enriched Log/Trace Files Activity Monitor

Solution Manager 4.0 SP15 - Available Feb. 2008


MDM specific Root Cause Analysis content E2E workload analysis for MDM E2E configuration change analysis for MDM Remote DB Monitoring Please see note 662441 and note 1126859

SAP 2007 / Page 90

How to Guides

How to Guides: How to perform Root Cause Analysis for SAP MDM with Solution Manager www.sdn.sap.com/irj/sdn/howtoguides > Data Unification How Tosetup 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/webinars Available in May 2008

Links

http://service.sap.com/diagnostic http://service.sap.com/installMDM www.sdn.sap.com/irj/sdn/howtoguides

SAP 2007 / Page 92

Feedback

SAP NetWeaver RIG and AGS are planning a feedback project on the usage of Solution Manager Diagnostics for MDM Purpose of this is to gather customer feedback about the new functionalities for Root Cause Analysis and Monitoring and roll this feedback 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 of Solution Manager Diagnostics for MDM please let me know

detlef.thoms@sap.com

Thank you!

SAP 2007 / Page 94

Copyright 2007 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. 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 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 and associated 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 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. 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

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte knnen 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 erwhnte SAP-Produkte und Services sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Lndern weltweit. Alle anderen in diesem Dokument erwhnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte knnen lnderspezifische Unterschiede aufweisen. Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit SAP. Dieses Dokument enthlt nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP-Produkts und ist fr SAP nicht bindend, einen bestimmten Geschftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP bernimmt keine Verantwortung fr Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die Richtigkeit oder Vollstndigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewhr, weder ausdrcklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschlielich, hinsichtlich der Gewhrleistung der Marktgngigkeit und der Eignung fr einen bestimmten Zweck sowie fr die Gewhrleistung der Nichtverletzung geltenden Rechts. SAP bernimmt keine Haftung fr Schden jeglicher Art, einschlielich und ohne Einschrnkung fr direkte, spezielle, indirekte oder Folgeschden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschrnkung gilt nicht bei Vorsatz oder grober Fahrlssigkeit. Die gesetzliche Haftung bei Personenschden oder die Produkthaftung bleibt unberhrt. Die Informationen, auf die Sie mglicherweise ber die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP untersttzt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewhrleistungen oder Zusagen ber Internetseiten Dritter ab. Alle Rechte vorbehalten.

SAP 2007 / Page 95