HTG SerDelRead 70

8/12/2019 HTG SerDelRead 70

1/15

SAP Solution Manager

Self-Diagnosis

How to work with functionality

Service Delivery Readiness

Applicable Releases:

From SAP Solution Manager 7.0 SP23

Application Lifecycle Management Process:

System Monitoring

Capability:

Self-Diagnosis

Version 1.0

January 2012


2/15

i

Copyright 2012 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, Informix,

i5/OS, POWER, POWER5, OpenPower and PowerPC are

trademarks or registered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader

are either trademarks or registered trademarks of Adobe

Systems Incorporated 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 orregistered 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.

These materials are subject to change without notice.

These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only,

without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in

the express warranty statements accompanying such

products and services, if any. Nothing herein should be

construed as constituting an additional warranty.

These materials are provided as is 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 not be liable for damages of any kind including

without limitation direct, special, indirect, or consequential

damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the

information, text, graphics, links or other items contained

within these materials. 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.

SAP NetWeaver How-to Guides are intended to simplify

the product implementation. While specific product

features and procedures typically are explained in a

practical business context, it is not implied that those

features and procedures are the only approach in solving a

specific business problem using SAP NetWeaver. Should

you wish to receive additional information, clarification or

support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (Code)

included in this documentation are only examples and are

not intended to be used in a productive system

environment. The Code is only intended better explain and

visualize the syntax and phrasing rules of certain coding.

SAP does not warrant the correctness and completeness of

the Code given herein, and SAP shall not be liable forerrors or damages caused by the usage of the Code, except

if such damages were caused by SAP intentionally or

grossly negligent.

Disclaimer

Some components of this product are based on Java. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is only

to be used by SAPs Support Services and may not be

modified or altered in any way.


3/15

ii

Document History

Document Version Description

1.0 First official release of this guide


4/15

iii

Typographic Conventions

Type Style Description

Example Text Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to otherdocumentation

Example text Emphasized words orphrases in body text, graphictitles, and table titles

Example text File and directory names andtheir paths, messages,names of variables andparameters, source text, andnames of installation,upgrade and database tools.

Example text User entry texts. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

Variable user entry. Angle

brackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2or ENTER.

Icons

Icon Description

Caution

Important

Note

Recommendation or Tip

Example


5/15

iv

Table of Contents

1. Business Scenario ..........................................................................................................12.

Background Information .................................................................................................1

3. Prerequisites....................................................................................................................14. Quick Overview ...............................................................................................................25. Detailed Instructions .......................................................................................................3

5.1 Launch Self-Diagnosis ..............................................................................................35.2 CheckSettingsfor tabs Functionality Status,Alert Types, and Solution.....................4

5.2.1 TabAlert Types by Functionality...................................................................45.2.2 TabAlert Types ............................................................................................65.2.3 TabAlert Types by Solution ..........................................................................6

6. Run Self-Diagnosis ..........................................................................................................86.1 Run Self-Diagnosis automatically (using backgroundjob SM:SELFDIAGNOSIS ) ...86.2 Run Self-Diagnosis manually ....................................................................................86.3 Problems during the transfer of the Service Delivery Readiness results .....................9

7. Review results of Service Delivery Readiness ...............................................................97.1 Tab Processing Info ..................................................................................................97.2 Tab Functionality Status ............................................................................................97.3 Tab Solution Status................................................................................................. 107.4 Additional Information for Individual Alerts ............................................................... 10

7.4.1 Cross Solution Alerts .................................................................................. 107.4.2 Solution Specific Alerts ............................................................................... 10

8. Changes to Service Delivery Readiness....................................................................... 10


6/15


7/15

www.sdn.sap.com/irj/sdn/howtoguides

4. Quick Overview

Below a quick overview over the individual steps is given. This can serve as a To do list whenchanges are made.

...

1. Access Self-Diagnosis

2. Check Settings.

Ensure functionality Service Delivery Readiness (available under tabFunctionalities)isselected. ( Initially the functionality was called Remote Service Delivery)

Ensure all service relevant solutions (available under tab Solutions) are included.

Ensure all service relevant alerts are set to active.

3. Run Self-Diagnosis manually or automatically.

4. Review Results of functionality Service Delivery Readiness.

Tab Processing Info

Tab Functionality Status

Tab Solution Status

5. Transfer results of Service Delivery Readinessto SAP.


8/15


5. Detailed InstructionsThis section provides details on how to set up Self-Diagnosis in such a way that the relevant solutionsand alerts are included, and that the results of functionality Service Delivery Readinesscan betransferred to SAP.

To enable SAP staff to access Self-Diagnosis, an open and correctly configuredHTTP connection is required. In case of problems you can raise a customermessage under the component XX-SER-NET-HTL.

5.1 Launch Self-Diagnosis...

If you log on to the system in English you ensure that the results transferred to SAP are in Englishalso.

1. Launch transaction DSWP

2. Access Solution Overview

3. Choose Self Diagnosis


9/15


5.2 CheckSettingsfor tabs Functionality Status, Alert

Types, and Solution

...

In Self Diagnosis, choose Settings.

Figure 1: Settings

5.2.1 Tab Alert Types by Functionality

1. Set functionality Service Delivery Readiness toActive.

When this is done for the first time, all related individual alerts will also be set to Active.

Figure 2: Alert Types by Functionality


10/15


2. Enable the automatic transfer of the results to SAP (available from ST 7.0 SP 26 )

Data is automatically transferred to SAP when there is any change in the overall rating for theentire functionality.

It is also possible to transfer results manually. This is described later. In all cases SAP-OSS isthe RFC destination used for the transfer.

Figure 3: Alert Types by Functionality

When you select the line for functionality Service Delivery Readiness this option will becomevisible:

Figure 4: Transfer Check Content to SAP

Select the check box, this will ensure that the Service Delivery Readiness resultswill betransferred to SAP when a change in overall rating of the results occurs.


11/15


5.2.2 Tab Alert Types

On this tab you can check that all individual service relevant alerts are set toActive.

In SAP Note 1146994 you will find an overview of the individual alerts available with each SupportPackage.

Figure 5: Alert Types

5.2.3 Tab Alert Types by SolutionOn this tab you can review which solutions are included in Self-Diagnosis.

Ensure that all solutions for which service sessions are booked are marked asActive.

Figure 6: Alert Types by Solution

Once you have reviewed all above tabs, save your settings.


12/15


Figure 7: Save

If you have made changes the new, saved settings are applied only during thenext run of Self-Diagnosis.


13/15


6. Run Self-Diagnosis

6.1 Run Self-Diagnosis automatically

(using background job SM:SELFDIAGNOSIS)

Log on to the system in English, to ensure that the results transferred to SAP are in English also.

Initially job SM:SELFDIAGNOSIS is created via the job SM:SCHEDULER. SM:SCHEDULER getscreated automatically when you create the first solution landscape ("Solution" or "SolutionLandscape") in SAP Solution Manager. SM:SCHEDULER manages all programs that are flagged asactive in the table DSWPJOB according to their relevant configurations. For more information onSM;SCHEDULER see SAP Note894279Background processing in SAP Solution Manager.

Jobs which communicate with SAP should be planned at random times, to avoid failure of RFC calls

due to overload.To ensure that jobs SM:SELFDIAGNOSIS and also SM:SELFDIAGNOSIS_SEND_TO_SAP (fromST7.0 SP 26) are scheduled at random times review also the information in SAP Note1604572.

Job SM:SELFDIAGNOSIS is expected to run daily. The job will provide results for all functions, alerts,and solutions which are selected asActivein Settings.

The job log provides information on the individual alerts that were executed, and whether or not atransfer to SAP was attempted.

From ST 7.0 SP 26 on a transfer to SAP occurs automatically at the end of SM:SELFDIAGNOSIS

when a change in the rating for the overall status of Service Delivery Readiness occurs.

Additionally a monthly job SM:SELFDIAGNOSIS_SEND_TO_SAPshould be planned.This ensures that even if there is no change in the rating of the overall result of Service DeliveryReadiness one set of results is transferred to SAP every 4 weeks.

6.2 Run Self-Diagnosis manually

1. Access Self-Diagnosis as described above.

3. Access Tab Functionality Status.

4. Click on Execute all.

5. Confirm the next pop up.

This will start a run of Self-Diagnosis. In SM37 you can find the corresponding jobSM:SELFDIAGNOSIS under your own user.

SM:SELFDIAGNOSIS will provide results for all functionalities, alerts and solutions which are selectedasActivein Settings. The job log will provide the same information as when the job is runautomatically.

If a change in the rating of the overall status of Service Delivery Readiness occurs the results aretransferred to SAP automatically also (From ST 7.0 SP 26) .
https://service.sap.com/sap/support/notes/894279https://service.sap.com/sap/support/notes/894279https://service.sap.com/sap/support/notes/894279https://service.sap.com/sap/support/notes/1604572https://service.sap.com/sap/support/notes/1604572https://service.sap.com/sap/support/notes/1604572https://service.sap.com/sap/support/notes/1604572https://service.sap.com/sap/support/notes/894279


14/15


6.3 Problems during the transfer of the Service Delivery

Readiness resultsIf any problems have occurred during an attempt to transfer results to SAP you will find thisdocumented in the corresponding job log for SM:SELFDIAGNOSIS *.

The destination used is SAP-OSS.

As this destination is also used to retrieve updates of Service Plans from SAP it is crucial to successfulService Delivery, and needs to be set up correctly. SAP note1172939(Technical prerequisites forremote service delivery in SSM) contains some further information on SAP-OSS.

If you need more help fixing this connection you can open a message in component XX-SER-NET.

7. Review results of Service Delivery Readiness

7.1 Tab Processing InfoAccess Self-Diagnosis as described above.

On tab Processing Infoyou can check whether a job SM:SELFDIAGNOSIS is currently running. Youcan also check the start and end time of the most recent run. The time stamp for the start of the job istransferred to SAP together with the results.

Figure 8: Processing Info

7.2 Tab Functionality StatusHere you can review the results for 'Cross Solution' alerts. The Displaylink for such an alert willprovide detailed information.

On tab Functionality Statusyou will also see the rating for individual alerts which investigate managedsystems in solutions. For such alerts the rating on this tab represents the worst rating for this alertfound in any of the systems in theActivesolutions. To access detailed information about the solutionsand individual managed systems you need to access tab Solution Status.

The overall rating for Service Delivery Readiness takes into account the results of all alerts executedduring the last run, and reflects the worst rating found in any of the alerts.
https://service.sap.com/sap/support/notes/1172939https://service.sap.com/sap/support/notes/1172939https://service.sap.com/sap/support/notes/1172939https://service.sap.com/sap/support/notes/1172939


15/15


7.3 Tab Solution StatusHere you will find results for the solutions set toActiveduring the last Self-Diagnosis run.

Select a line with the solution you are interested in.

A list of alerts will be displayed below. Each alert contains the relevant info for the managed systems

in this solution.The rating represents the worst rating for this alert found in any of the managed systems in thissolution.

The Displaylink for each alert will provide the detailed information on the findings for the individualmanaged systems in this solution.

7.4 Additional Information for Individual Alerts

7.4.1 Cross Solution AlertsService Delivery Readiness alerts of the type Cross Solution provide information on the SAP SolutionManager system itself, and also information that is valid across all solutions set to Active.

7.4.2 Solution Specific Alerts

Service Delivery Readiness alerts of the typeSolution Specific provide information about theproductive managed systems in the solutions set to Active.

7.4.2.1 Role of EarlyWatch Alert

For some of the alerts of the type Solution Specific, the lastEarlyWatch Alert for the managedsystem in question acts as a source of information.

Where this is the case the alert texts carry that information.

7.4.2.2 Role of Connections to Managed Systems

For some of the alerts of the type Solution Specifican RFC call is made to the managed system inquestion.

Where an alert is trying to use a connection to a managed system, and encounters a problem, this isdocumented in the alert text.

8. Changes to Service Delivery Readiness

SAP Note 1146994 provides an overview of the changes which are introduced In ST 7.0, from SP 23on.

Documents

HTG SerDelRead 70