A Guide to End-to-End Root Cause Analysis

  • by Labinot Bytyqi, Senior Technical Consultant, Solution Manager and Extensions Practice Lead — West Region, SAP America, Inc.
  • September 3, 2009
Learn how to set up and use SAP Solution Manager Root Cause Analysis and Wily Introscope Enterprise Manager.
Key Concept

End-to-End Root Cause Analysis offers systematic analysis and resolution of incidents for a distributed environment. End-to-End (E2E) Root Cause Analysis is part of SAP Solution Manager and uses SAP NetWeaver Business Warehouse (SAP NetWeaver BW) and CA Wily Introscope Right to View (RTV) to achieve E2E Root Cause Analysis. CA Wily Introscope is a performance management solution that enables you to monitor complex Web applications in production environments. You can download it from the SAP Service Marketplace. CA Wily Introscope and SAP signed an agreement in July 2006 that allows you to use CA Wily Introscope with SAP-developed dashboards and instrumentation as part of SAP Solution Manager.

To ensure the continuous operation of your applications, you must provide comprehensive support that manages the complexity of systems, risks, costs, and resources. Given the nature of today’s IT environment, which typically involves running diverse software in a highly distributed landscape, managing individual applications has become increasingly difficult. In a distributed, multi-technology solution with multi-channel access through various devices and client applications, analyzing the root cause of an incident requires a systematic top-down approach. By implementing SAP End-to-End (E2E) solution operations, organizations can achieve greater efficiency, transparency, and security in their application management.

Here’s an example of how E2E Root Cause Analysis works. If an end user experiences a browser performance problem, the performance hit could be in the client network or server environment, which comprises various instances of many different technologies. Server-side processing may take place in SAP NetWeaver Portal, reach out to an SAP ERP Central Component (SAP ECC) back end, and finally, call the database and the storage subsystem for data retrieval. A performance problem or functional defect may occur in any of the stages of this “round trip.” E2E Root Cause Analysis can identify the specific component that is causing the performance bottleneck.

The Root Cause Analysis tools do not allow changes by SAP support unless they are explicitly requested by the client and enforced by their change management process. I’ll explain how to use E2E Root Cause Analysis and give step-by-step directions on how to set up Root Cause Analysis in SAP Solution Manager and Wily Introscope Enterprise Manager.

Labinot Bytyqi

Labinot Bytyqi graduated with a degree in computer science and business management and a minor in economics from George Fox University in 2005. Currently, he is pursuing a master’s degree in information technology management. Labinot joined SAP in 2007 as a technical consultant with more than eight years of information technology experience and SAP consulting, particularly in the application lifecycle management area, where he was a lead for an SAP Solution Manager and extensions practice in the West region. Labinot currently is responsible for field services software sales portfolio business development and strategy, as well as for SAP Extended Diagnostics by CA Wily.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.