E2E Diagnostics in Solution ManagerTechnical Service Preparation for RSD

June 2009

Introduction

Solution Manager Diagnostics is necessary to analyze Java based SAP products andproduct components.

This manual shows how to check the SMD for service readiness during the technicalpreparation prior to a service.

This manual applies to Solution Manager 7.0 EHP 1. That means SP 18 or higher.The screen shots might differ slightly from SP to SP. However it is not possible tocover all of them so the screenshots were made on SP 18.

© SAP 2009 / Page 2

Solution Manager DiagnosticsIntroduction (Tech prep perspective)

Solution Manager can be installed as dual stack.

Solution Manager (ABAP)Connection with SAPGUI (e.g. Transactions: DSWP, SMSY, SDCCN etc.)Workcenter driven by ABAP Webdynpro

Solution Manager (JAVA)Connection by http connectionIncludes Solution Manager Diagnostics

Preparation of Solution Manager (ABAP) is already covered by “Extended Preparation”“Extended Preparation” is enhanced hereby to cover the SMD preparation

© SAP 2009 / Page 3

Functionalities needed for RSD

Functionalities needed for Services for Java based SAP products or product componentsGA/GV/EW– E2E Workload Analysis, E2E Change Analysis, Introscope, DBA_CockpitGO/BPPO– E2E Workload Analysis, E2E Change Analysis, E2E Trace Analysis, Introscope, DBA_Cockpit

E2E Workload Analysis– Provides performance and load information– Stores information in Solution Manager BWE2E Change Analysis– Provides information about configuration and changes– Stored in CCDB (Change and Configuration Database)E2E-Trace-Analysis– Runtime analysis of business processes for single userIntroscope– Provides detailed statistics of system activitiesDBA Cockpit– Database analysis

© SAP 2009 / Page 4

Prerequisites

Connection to SMDIn order to work on the SMD HTTP access has to be enabled. This can be done by providinga HTTP connection or an application sharing method.

Logon information for Solution ManagerIn a dual stack installation the users in Solution Manager Diagnostics can be the same as inthe Solution Manager (ABAP)The user should have authorizations SAP_SOLMAN_ONSITE_COMP according to SAP Note834534

© SAP 2009 / Page 5

Service Connection Type Description SAP Note

HTTP Connect - URLAccess provides access to http-based applications 592085

Netviewer Enables collaboration and application sharing access via Netviewer 1036616

Windows Terminal Server enables application sharing access via Windows Terminal Server 605795

Citrix Metaframe enables application sharing access via Citrix Metaframe 701588

T.120 NetMeeting enables application sharing access via NetMeeting 356635

PCanywhere enables application sharing access via Pcanywhere 100740

Logon to Solution Manager Diagnostics

Logon to SAPGUI to Solution Manager(ABAP) or logon to the httpconnection directly to SMDRun transaction DSWPChoose Goto -> Solution ManagerDiagnosticsThe logon screen of the SMD appearsin the browserLogon with SMD user that is in generalthe same user as for SolutionManager (ABAP)After that you see the entry screen ofthe SMD

© SAP 2009 / Page 6

Important work areas for Tech Prep

© SAP 2009 / Page 7

Check ofWorkload AnalysisChange AnalysisE2E-Trace-Analysis

Check of connectionfrom SMD tomanaged system

System connection to SMD

Check if the managed system isconnected correctly to the SMD.Click on “System browsing” in the SMDentry screenEnter the system ID of the managedsystem in the search field and click on"Search„If the system doesn’t appear it is not yetconnected to the SMDIf the system appears mark the line of it(be sure to mark the Java system incase of dual stack systems)Click on the button “Smd Agents”If you see the information “Smd Agentstatus: Started.” the agents are runningIf not, the managed system needs to beconnected to the Solution Manager (referto the next slide)

© SAP 2009 / Page 8

System not connected properly to SMDRecommendation to customer

If the system is not connected properly, the customer has to run the SolutionManager Setup (transaction SOLMAN_SETUP).

Following recommendation should be given to the customer:

Please run the “Managed System Configuration” in transaction SOLMAN_SETUP inorder to connect the managed system XYZ properly to the Solution Manager andSolution Manager Diagnostics.

This is also prerequisite for the trouble shooting guide attached to SAP Note1332428.

© SAP 2009 / Page 9

E2E Workload Analysis (1)Running the Workload Analysis

To check the availability of data for workload analysis click on(1) “End-to-End Analysis”(2) Java Systems(3) Mark the system in focus of the service(4) Workload Analysis

For GA/GO/GV/EW/BPPO

© SAP 2009 / Page 10

E2E Workload Analysis (2)Workload Analysis with values – check okay

© SAP 2009 / Page 11

There is a graph on thechart and the values at thefar right are available

Workload Analysis isworking, nothing hast to bedone

E2E Workload Analysis (3)How it shouldn’t look like – check not okay

© SAP 2009 / Page 12

There is no graph in thechart and the values at thefar right are not available

Point the customer to SAPNote 1332428 – “Missingdata in service sessionsfrom BI/CCDB” and theattached trouble shootingguide

E2E Change Analysis (1)Running the Change Analysis

To check the availability of data for change analysis click on(1) “End-to-End Analysis”(2) Java Systems(3) Mark the system in focus of the service(4) Change Analysis

For GA/GO/GV/EW/BPPO

© SAP 2009 / Page 13

E2E Change Analysis (2)E2E Change Analysis with values

© SAP 2009 / Page 14

Select a timeframe of 6month in the pastIf no data appears try 1yearIf you see bars in thegraphic the change analysisis working

E2E Change Analysis (3)E2E How it shouldn’t look like

© SAP 2009 / Page 15

No values are available

Point the customer to SAP Note 1332428 – “Missing data in service sessions fromBI/CCDB” and the attached trouble shooting guide

E2E Trace AnalysisRunning a trace

© SAP 2009 / Page 16

To check the availability of data for trace analysis click on(1) End-to-End Analysis(2) Java Systems(3) Mark the system in focus of the service(4) Trace Analysis

For GO/BPPO services

E2E Trace AnalysisResult

© SAP 2009 / Page 17

Activate tab “Trace Enabling”The system in focus of the service should be visible.

If an error occurs please point the customer to SAP Notes1332428 – “Missing data in service sessions from BI/CCDB” and the attached troubleshooting guide1252944 – “E2E Trace: Problem retrieving data from managed systems”1323405 – “Technical Preparation of a GO or BPPO service”

Wily IntroscopeCheck

© SAP 2009 / Page 18

Check Wily Introscope to beworkingMark the system and click on“Introscope” -> “Webview”The “Introscope Starter”appears

Click on “Start Introscope”

Check fulfilled: IntroscopeLogin appears

Wily IntroscopeRecommendations

© SAP 2009 / Page 19

If you get an network error it might be problem with the SAProuter. The customer has twopossibilities now.

Create a second http connection to Introscope and maintain SAProuterDirectly maintain the SAProuter (How to add an entry to the router table is explained inSAP Note 30289

If the problem is not related to a network problem or you are unsure than recommend SAPNote 797147 in addition. It describes how to setup and access Wily Introscope.

DBA CockpitCheck

© SAP 2009 / Page 20

DBA Cockpit is needed bywatchers to perform thedatabase analysis manuallyRun transactionDBACOCKPITCheck if the SID appears inthe tableMark the table row and clickon “Test connection”If SID does not appear or theDB connection is not workingrecommend the text below

Database Support ToolsDBA Cockpit (see SAP Note 1028624) allows you to monitor and manage external databases (in both ABAP and non-ABAP systems). Thismonitoring tool therefore enables database issues to be identified quickly and efficiently and is essential for taking full advantage of SAP'sremote services.

Recommendation:Connect this database to DBA Cockpit as an "external database". DBA Cockpit can be used on the Solution Manager system and many othersystems. For more information, see SAP Note 1028624 and the attached documentation.

To obtain data from the database automatically that is analyzed in the EarlyWatch Alert and other systems:(A) The ST-PI version of Solution Manager must be up-to-date (B) In SMSY, a valid DB connection has to be maintained on the "RemoteDatabase Connection" tab page

Database connection maintained in SMSYCheck

© SAP 2009 / Page 21

This check is necessary for the automation of service checkCheck if the DB connection is maintained in SMSYIf not available ask the customer to maintain the database connection

© SAP 2009 / Page 22

Thank you!

© SAP 2009 / Page 23

Copyright 2009 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.