Solution Operations Guides SAP Solution Manager 7.1

Solution Operation Guide

SAP Solution

Manager 7.1

Operation Guide

Document Version 1.0 - May 9, 2011

© Copyright 2011 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, and Informix are trademarks or registered trademarks of IBM

Corporation 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 or registered

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.

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 SAP’s Support Services and may not be modified or altered in any

way.

Documentation in the SAP Service Marketplace

You can find this documentation at the following Internet address:

service.sap.com/instguides

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf Germany www.sap.com

Typographic Conventions

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE

TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

SAP Solution Manager Operation Guide

4 May 2011

Contents

1 Getting Started ....................................................................... 6

1.1 Global Definitions ................................................................... 6

1.2 History of Changes ................................................................. 8

2 SAP Solution Manager and Technical System Landscape . 9

2.1 SAP Solution Manager ............................................................ 9

2.2 SAP Solution Manager built-in Software Components ....... 9

2.3 SAP Solution Manager complementary Components .......11

2.3.1 Internet Graphics Server (IGS) ................................................ 11

2.3.2 SAP NetWeaver Search and Classification (TREX) ............... 11

2.3.3 CA Wily Introscope .................................................................. 11

2.4 Release Restrictions .............................................................12

2.5 Installation .............................................................................12

2.6 Upgrade to SAP Solution Manager 7.1................................12

2.7 Business Warehouse (BW) Client Strategy ........................13

2.8 Root Cause Analysis ............................................................13

2.9 SAP Solution Manager Configuration .................................14

2.10 Managed Systems Configuration ......................................15

2.10.1 Required Agent Versions ........................................................ 16

2.10.2 SAP Solution Manager and Trusted RFC ............................... 16

2.10.3 System and Landscape Directory (SLD), Landscape Management Database (LMDB) and SMSY ......................................... 18

2.10.4 Adjust Upgrade of Managed System ...................................... 19

2.11 Moving from SAP Solution Manager Transation DSWP to Work Centers ..............................................................................20

2.12 Solution Transfer ................................................................20

2.13 Service Delivery in SAP Solution Manager ......................21

2.14 Multi-Tier Landscape for SAP Solution Manager .............21

2.15 Sizing for SAP Solution Manager ......................................21

2.16 Related Documentation ......................................................22

3 Monitoring SAP Solution Manager ..................................... 23

3.1 New Monitoring Infrastructure .............................................23

3.1.1 Connection Monitoring ............................................................ 23

3.2 CCMS Monitoring – SAP Solution Manager .......................23

3.2.1 CCMS Monitoring – Internet Graphics Server (IGS) .............. 24

3.3 SAP EarlyWatch Alert in SAP Solution Manager ...............24

3.4 Other Problem Analysis and Monitoring Tools ..................24

3.4.1 Application Monitoring ............................................................ 24

4 Management of SAP Solution Manager ............................. 26

4.1 Solution Manager Administration Work Center .................26


May 2011 5

4.1.1 Landscape View ....................................................................... 26

4.1.2 Infrastructure View ................................................................... 27

4.1.3 Self Diagnosis View ................................................................. 28

4.1.4 Solution View ............................................................................ 28

4.1.5 Project View .............................................................................. 28

4.2 Starting and Stopping ...........................................................28

4.3 Backup and Restore .............................................................29

4.3.1 Backup Introscope Enterprise Manager ................................. 30

4.4 Periodic Tasks .......................................................................30

4.4.1 Background processing in the SAP Solution Manager......... 30

4.5 User Management .................................................................32

4.5.1 User Administration and Authentication ................................ 32

4.5.2 Create Users and Business Partners for End Users ............. 33

4.5.3 Update Authorizations after Support Package Upgrade ....... 35

4.5.4 Adapt Work Center Queries ..................................................... 36

4.5.5 Create End User Roles ............................................................. 36

4.5.6 Assign Roles to Users ............................................................. 37

5 High Availability ................................................................... 38

6 Archiving & Data Deletion in SAP Solution Manager ........ 39

6.1 Achiving functionality in core SAP Solution Manager ......39

6.2 SAP Solution Manager Extended Archiving Functionality40

6.3 Alternative Storage & Deletion Strategies ..........................40

6.4 SAP Notes for Additional/Background Information ..........42

7 Software Change Management ........................................... 43

7.1 Agents Consideration ...........................................................43

7.2 Configuration after Support Package Update ....................43

7.2.1 Guided Procedure - Automatic Update Configuration .......... 43

7.2.2 SAP Reference IMG – Manual Update Configuration ............ 44

7.3 Ensure Basic Functions via SAP Note ................................44

7.4 Support Packages and Patch Implementation ...................45

8 Troubleshooting .................................................................. 46

8.1 Connection to SAP ................................................................46

8.2 SAP EarlyWatch Alert (EWA) ...............................................46

8.3 Self-Diagnosis .......................................................................46

8.4 CA Wily Introscope ...............................................................48

8.5 Logging and Tracing .............................................................48

9 Appendix .............................................................................. 49

9.1 Related Guides ......................................................................49

9.2 Related Information ..............................................................49


6 May 2011

1 Getting Started

This guide does not replace the daily operations handbook, that we recommend customers create for their production operations.

About this Guide

Designing, implementing, and running your SAP applications at peak performance, 24 hours a day, has never been more vital to your business success than today.

This guide is the starting point for managing your SAP applications and maintaining and running them optimally. It contains information about various tasks, and lists the tools that you can use to perform them. It also provides references to the documentation required for these tasks, so you will sometimes also need other guides, such as the Master Guide, Technical Infrastructure Guide, and SAP Library.

Target Groups

Technical Consultants

System Administrators

Solution Consultants

Business Process Owner

Support Specialist

1.1 Global Definitions SAP Application

An SAP application is an SAP software solution that serves a business area such as SAP ERP, SAP CRM, SAP PLM, SAP SRM, or SAP SCM.

Business Scenario

From a micro-economic perspective, a business scenario is a cycle which comprises several interconnected logical processes in time. Typically, a business scenario includes several company departments and business partners. Technically, a business scenario needs at least one SAP application (SAP ERP, SAP SCM, or other) for each cycle, and possibly other third-party systems. A business scenario is an entity which can be implemented separately, and reflects the customer‟s prospective course of business.

Component

A component is the smallest individual unit considered within the Solution Development Lifecycle; components are produced, delivered, installed and maintained separately.

Check regularly for updates of the Application Operations Guide.


May 2011 7

Important SAP Notes

SAP Note Number

Title Comment

1462137 Add. info. about Upgrading to SAP Solution Manager 7.1

This note describes problems that may occur when you upgrade the system and provides you with information on how to solve them.This usually takes the form of references to other notes. The aim of this note is to prevent data loss, upgrade shutdowns and long runtimes. Only database-independent problems are dealt with here.

1552585 SAP Solution Manager - basic functions

Implement the following note to ensure the basic functions in SAP Solution Manager. This note is valid for Solution Manager 7.1 SP01. This note contains additional prerequisite notes that are regularly extended and renewed.

1577909 Supplements to Solution Manager 7.1

This note describes preparatory measures and additional information for the

Upgrade of SAP Solution Manager 7.0 to SAP Solution Manager 7.1

Upgrade of SAP Solution Manager 7.0 Enhancement Package 1 to SAP Solution Manager 7.1

Update of SAP Solution Manager 7.1 (installation) to the stack that is currently available

1583348 Documentation: SAP Solution Manager 7.1

Overview on the available documentation for SAP Solution Manager 7.1

https://service.sap.com/sap/support/notes/1462137





8 May 2011

1.2 History of Changes

Make sure you use the current version of the Application Operations Guide.

The current version of the Application Operations Guide is on SAP Service Marketplace at

http://service.sap.com/instguides → SAP Components → SAP Solution Manager →

Release 7.1.

The following table provides an overview of the most important changes in previous versions.

Document Versions

Document Version

Important Changes

1.00 First version of the SAP Solution Manager Operations Guide for SAP Solution Manager 7.1

http://service.sap.com/instguides


May 2011 9

2 SAP Solution Manager and Technical System Landscape

2.1 SAP Solution Manager

SAP Solution Manager is the central tool for managing your customer solution landscape. It includes several applications and scenarios to support the Application Lifecycle Management (ALM) ensuring business continuity, accelerating innovation, and reducing risk as well as total cost of operations while protecting your investment is the key challenge for each IT organization. Application Lifecycle Management (ALM) adresses this challenge with an integrated ITIL-based approach.

More information about Application Lifecycle Management (ALM) and the SAP Solution Manager can be found in the SAP Service Marketplace or the SAP Help Portal. Another central place for useful information about the supported functions is the Ramp-Up Knowledge Transfer page for the SAP Solution Manager.

Cental Information Sources

Topic Link

Application Lifecycle Management (ALM)

http://service.sap.com/alm

SAP Solution Manager http://service.sap.com/solutionmanager

SAP Help Portal http://help.sap.com/ → SAP Solution Manager

Ramp-Up Knowledge Transfer http://service.sap.com/rkt-solman

2.2 SAP Solution Manager built-in Software Components The SAP Solution Manager comprises several software components. It is based on an SAP NetWeaver platform and includes the SAP CRM add-on, so the tasks and procedures for a standard SAP NetWeaver system generally also apply to SAP Solution Manager. Other software components can be added to SAP Solution Manager, depending on the business scenarios used. This guide refers mostly to SAP Solution Manager-specific tasks and procedures.

You can use the following software components in your system, depending on the scenarios you actually use.

Usage Type SAP Solution Manager

Software component Description

SAP_BASIS SAP Basis Component

SAP_ABA Cross-Application Component

SAP_BS_FND SAP Business Suite Foundation

SAP_BW SAP NetWeaver BI

BI_CONT Business Intelligence Content

SAP_AP SAP Application Platform

ST Solution Manager Tool

ST-A/PI Application Service Tools

ST-SER Solution Manager Service Tools

ST-PI Solution Tools Plug-In

http://service.sap.com/alm

http://service.sap.com/solutionmanager

http://help.sap.com/

http://service.sap.com/rkt-solman


10 May 2011

ST-ICO Solution Manager Implementation Content

BBPCRM BBP/CRM

CPRXRPM SAP Portfolio and Project Management 5.0 (ABAP)

PI_BASIS PI_BASIS

WEBCUIF SAP Web UI Framework

Usage Type Additional Adapers

ST-QCA SAP Adapter for SAP Quality Center by HP

ST-PSM SAP process scheduling adapter

ST-SPA SAP Produktivity Pak

Usage Type Java Application Server

LMSERVICE Root Cause Analysis

Aditional 3rd Party Software

Appsight Blackbox and Console BMC AppSight

Introscope Enterprise Manager CA Wily Introscope

Software Comonents Detailed Information

Support Package levels of SolMan installations / upgrades

SAP Note 781448

Third-Party Integration There are several standard interfaces to third-party tools, which can be used for specific scenarios:

Additional Software

Tool Link

SAP Quality Center by HP https://service.sap.com/solutionmanager → SAP

Solution Manager Adapter for SAP Quality Center by HP.

SAP Central Process Scheduling by Redwood

https://service.sap.com/solutionmanager → Process

Scheduling adapter for SAP Solution Manager.

SAP Productivity Pak by RWD

https://service.sap.com/solutionmanager → SAP

ProductivityPak by RWD adapter for SAP Solution Manager and SAP Note 1131270

BMC Appsight for Client Diagnostics

SAP Note 1034902


https://service.sap.com/solutionmanager






May 2011 11

2.3 SAP Solution Manager complementary Components

2.3.1 Internet Graphics Server (IGS)

The Internet Graphics Server (IGS) generates various graphics or charts in some areas, e.g. in EarlyWatch Alert reports. The server can be administrated in transaction SIGS. You can administrate your Web Dynpro Java IGS via a Web Interface.

Administration of IGS

Topic Transaction Link

Internet Graphics Server (IGS) SIGS http://<IGS host>:<IGS port>

Notes for IGS

SAP Note Short Text

965201 IGS HTTP administration commands

995471 IGS administration via ABAP

514841 Troubleshooting when a problem occurs with the IGS

2.3.2 SAP NetWeaver Search and Classification (TREX) For specific scenarios the SAP NetWeaver Search and Classification (TREX) is used.

Administration of TREX

Topic Transaction Link

SAP Netweaver Search and Classification

http://help.sap.com → SAP NetWeaver → SAP

NetWeaver 7.0 including Enhancement Package 2 → <language> → Technical Operations Manual → Administration of Standalone Engines → Search and Classification (TREX)

Administration of TREX

TREXADMIN http://help.sap.com/saphelp_nwes70/helpdata/en/

46/c96a575b590e5be10000000a1553f7/content.htm

Notes for TREX

SAP Note Short Text

1466273 Work Centers: "TREX is not responding" error message

2.3.3 CA Wily Introscope

CA Wily Introscope is a software component, which collects performance and other system-related data maily from non-ABAP components in your system landscape. SAP Note 797147 “Wily Introscope Installation for SAP Customers” includes a detailed FAQ document as an attachment. This document also includes a detailed troubleshooting section.

For information about installation, see the installation guide on SAP Service Marketplace at

http://service.sap.com/diagnostics → Installation and Configuration.





http://help.sap.com/content/documentation/netweaver/docu_nw_70_design.htm#nw70ehp1


http://help.sap.com/saphelp_nwes70/helpdata/en/46/c96a575b590e5be10000000a1553f7/content.htm

http://help.sap.com/saphelp_nwes70/helpdata/en/46/c96a575b590e5be10000000a1553f7/content.htm



http://service.sap.com/diagnostics


12 May 2011

Wily Introscope

Topic Link

Wily Introscope http://service.sap.com/diagnostics

Notes for Wily Introscope

SAP Note Short Text

797147 Wily Introscope Installation for SAP Customers

1565954 Introscope 9 Release Notes

2.4 Release Restrictions When SAP Solution Manager 7.1 was released, a number of restrictions still applied to the productive use of certain functions. This information is collected in SAP Note 1480419 “Release Restrictions for SAP Solution Manager 7.1“.

SAP Notes

SAP Note Short Text

1480419 Release Restrictions for SAP Solution Manager 7.1

2.5 Installation SAP Solution Manager 7.1 is an SAP system based on Application Server ABAP (AS ABAP) and Application Server Java (AS Java). SAP Solution Manager 7.1 is based on the technology of SAP NetWeaver 7.0 including Enhancement Package 2. For more information about SAP NetWeaver technology, see http://sdn.sap.com/irj/sdn/netweaver.

SAP recommends running SAP Solution Manager on Unicode. All new SAP Solution Manager Installations are on Unicode. For customers that have upgraded from previous releases of SAP Solution Manager 7.1, and are not yet on Unicode, SAP recommends migrating to Unicode. If this is not possible, SAP will support the SAP Solution Manager on non-Unicode, until the customer has completed the Unicode conversion.

SAP Solution Manager Installation

Topic Link

SAP NetWeaver Releases http://sdn.sap.com/irj/sdn/netweaver

SAP Solution Manager Installation http://service.sap.com/instguides

Unicode http://service.sap.com/unicode

2.6 Upgrade to SAP Solution Manager 7.1 To upgrade to SAP Solution Manager 7.1, you require seperate upgrade programs for the ABAP and the Java parts of your SAP Solution Manager system. The upgrade of SAP Solution Manager requires using the upgrade program SAPup for the ABAP part and the SAP Enhancement Package Installer (SAPehpi) for the Java part. For further information please consult the SAP Solution Manager 7.1 Upgrade Guide.






http://sdn.sap.com/irj/sdn/netweaver

http://sdn.sap.com/irj/sdn/netweaver


http://service.sap.com/unicode


May 2011 13

SAP Note 1462137 (“Additional information on upgrading to SAP Solution Manager 7.1”) includes an overview of software components and support package levels that must be installed in your SAP Solution Manager system.

SAP Solution Manager Upgrade

Topic Link

SAP Solution Manager 7.1 Upgrade Guide

http://service.sap.com/instguides → SAP

Components → SAP Solution Manager → Release 7.1

Additional information on upgrading to SAP Solution Manager 7.1

SAP Note 1462137

2.7 Business Warehouse (BW) Client Strategy BW provides important reporting functions to the various SAP Solution Manager processes, e.g. Solution Manager Diagnostics. In general there are two main BW options when planning your system landscape. BW in the Productive SAP Solution Manager Client In this scenario, BW is used in the same productive client as SAP Solution Manager. This makes configuration simpler, and isolates the BW activities for solution life cycle management from the data on a production BW instance. This is SAP’s recommendation. BW in a Separate Client on SAP Solution Manager

In this scenario, BW activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately, and this increases your administration effort. There is no technical benefit.

BW in a Separate Client on SAP Solution Manager

In this scenario, BW activities are conducted in a separate client on the SAP Solution Manager system. This scenario provides increased security, as user access is more restricted. However, you must maintain users separately, and this increases your administration effort. There is no technical benefit.

BW Client Strategy

Topic Note / Link

Where is best to set up BW for the Solution Manager

SAP Note 1487626

2.8 Root Cause Analysis You need information about the basic requirements and possible limitations of end-to-end root cause analysis, delivered with SAP Solution Manager 7.1. The functionality is also called End-to-End Diagnostics or SAP Solution Manager Diagnostics. The configuration of the tool is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP).

Root Cause Analysis

Topic Note / Link

Diagnostics in SAP Solution Manager 7.1

SAP Note 1478974







14 May 2011

Solution Manager 7.1: Root Cause Analysis

SAP Note 1483508

Root Cause Analysis http://service.sap.com/diagnostics

2.9 SAP Solution Manager Configuration After installing the SAP Solution Manager, the basic configuration should be performed. You can initially configure your basic settings with the basic settings wizards. This quickly configures all main settings in a guided procedure. The automatic configuration is accessed via the Solution Manager Configuration Work Center or it can be called by transaction SOLMAN_SETUP. All settings for this Web Dynpro application are made during the installation of SAP Solution Manager. All activities in this wizard are linked to the corresponding Customizing activities in the standard basic settings configuration, in the SAP Reference IMG (transaction SPRO).

The automatic basic settings configuration with SOLMAN_SETUP includes:

System Preparation

o Settings which are prerequisite for the configuration of SAP Solution Manager

Basic Configuration

o Necessary configuration which is needed to use basic scenarios in SAP Solution Manager, for example, connecting to SAP, performing a root cause analysis, using the SAP EarlyWatch Alert, or downloading patches and upgrades

Managed Systems Configuration

o Connect managed systems to SAP Solution Manager

And also configuration steps for specific scenarios:

Technical Monitoring, configures the following sub-scenarios:

o Self-Monitoring: monitors the status of SAP Solution Manager. o System Monitoring: monitors the status of managed systems. o End-User Experience: monitors hosts at various locations which simulate the

availability and performance of business processes from the point of view of the end-user.

o PI Monitoring: monitors XI (SAP Exchange Infrastructure) and PI (SAP Process Integration) systems which allow for data exchange between managed systems.

o Connection Monitoring: monitors connections between managed systems.

Measurement Platform Setup

o Choose all systems for which you later want to perform your SUGEN benchmark measurement.

Data Volume Management

Further Configuration for the following scenarios:

o Test Management

o Quality Gate Management

o Change and Transport System (CTS+)

For more information about configuration, see the Customizing for SAP Solution Manager (transaction SPRO) and the configuration guide on SAP Service Marketplace at

http://service.sap.com/instguides → SAP Components → SAP Solution Manager →

Release 7.1.





May 2011 15

Basic Configuration

Topic Transaction / Link

SAP Reference IMG Transaction SPRO

Configuration Guide http://service.sap.com/instguides → SAP


2.10 Managed Systems Configuration To ensure that all the systems can be managed centrally, the SAP Solution Manager should be connected to all systems in the system landscape. All the systems which are connected to the SAP Solution Manager are called managed systems. The SAP Solution Manager is the central location for the management and setup of the connected managed systems, so you must be able to access those systems. The users should only have the authorizations which are assigned to them in the managed systems. Misuse of the communication connection must be prevented. In SAP Solution Manager this is usually ensured by using a trusted RFC with the same user. The configuration of managed systems for the basic scenarios is in the guided procedure (transaction SOLMAN_SETUP).

In this step, you connect systems to SAP Solution Manager:

1. Select the system you want to configure:

To connect a single system, choose the Technical System tab page.

To connect a double (ABAP and Java) stack system, choose the Technical Scenario tab page.

To connect a standalone database, choose the Database tab page.

The technical systems, technical scenarios, or databases, which are known to the SAP Solution Manager System Landscape Directory, are displayed.

2. Check the status of the configuration:

Gray, red or yellow signals in the following columns require you to take action: - RFC Status (only ABAP): Red: Repair the RFC connections, for example

delete and set up the RFC destination again - Automatic Configuration Status:

Grey: Perform missing steps of the managed system configuration

Red: Repeat failed steps of the managed system configuration - Plugin Status (only ABAP): Red: Install the recent version of the following

software components on the managed system: ST-PI ST-API - To make sure that the technical systems or technical scenarios are correctly known to SAP Solution Manager, select an item and choose the Show Details link. - If the system that you want to connect is not contained in the technical system list, connect the system to an SLD to minimize the effort for maintenance. If required, create the technical system manually.

3. If incorrect system data is displayed, you maintain the technical system or scenario in the system landscape. To do so, choose the Configure Scenario or Configure System



16 May 2011

pushbutton, respectively. Databases are retrieved automatically from LMDB and cannot be created or maintained.

4. To create systems manually, scenarios or databases, choose the System/Scenario/Database Operations pushbutton, respectively, and choose Create. You go to a Guided Procedure.

5. Follow the instructions in the respective Guided Procedure.

Notes for Managed Systems

SAP Note Short Text

1472465 SAP Solution Manager 7.1 - System Landscape Setup Guide

2.10.1 Required Agent Versions

On the Managed System you need different agents for Root-Cause Analysis as well as for the Technical System Monitoring.

Diagnostics Agent

• You can use any version of the Diagnostics Agent (already installed agents do not need to be updated)

• The agent applications are updated automatically from the Solution Manager

• For new installations use the latest available version of the diagnostics agent from http://service.sap.com/swdc Browse Download Catalog SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.1 Agents for managed systems

SAP Host Agent

• You need to install at least patch level 55 of the SAP Host Agent 7.20.

• The installation files are available from http://service.sap.com/swdc Support Packages and Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP HOST AGENT 7.20

• This is installation procedure is described in SAP Note 1031096

• It is recommended to enable the automatic update feature of the SAP Host Agent, so that you can update the Host Agent centrally. This is described in SAP Note 1473974.

Required Agent Versions

Topic Note / Link

Installing Package SAPHOSTAGENT SAP Note 1031096

Using the SAP Host Agent Auto Upgrade Feature

SAP Note 1473974

2.10.2 SAP Solution Manager and Trusted RFC

The trusted RFC connections are setup between the SAP Solution Manager and the connected managed systems. This can be done using transaction SOLMAN_SETUP. SAP Solution Manager does not manage connections between managed systems.

The trusted RFC connections can be used and are acceptable from a security point of view, if the user management for the SAP Solution Manager is as restrictive as for all other productive systems. In particular, the creation of new users and the resetting of passwords must be strictly controlled. The naming conventions for users must be consistent across systems.

Trusted relations between systems can be configured on different levels:


http://service.sap.com/swdc

http://service.sap.com/swdc




May 2011 17

1) Trusted relationships from a system, which offers services to another system (client), within these services. This kind of trusted relationship is usually realized by putting the login data of a service user of the server system, in the client system.

Examples:

a) The login data of a display user (with limited authorization) of the transport management system (TMS) is entered in the RFC destination of the TMS.

b) The login data of a service user (with more extensive authorizations) of the central user administration (CUA) is entered in the RFC destination of the CUA.

2) Trusted relationships between systems where one system accepts the authentication of the other system.

Examples:

a) A Windows client accepts a Kerberos ticket of a Windows domain server, and logs its user in.

b) An SAP backend system accepts the SAP Logon Ticket of the SAP NetWeaver Portal, and logs on the user in the target system, where the login token is entered.

c) An SAP system accepts an SSL client certificate in an https connection, finds the user and logs it in with user ID.

d) An RFC server system accepts the trusted RFC token und logs the user in to the target system, with the same user ID as in the source system.

The trusted RFC can be used for 1b) and 2d).

In case 1b), the login data of a service user is entered in the RFC connection, as in a normal RFC destination. Using trusted RFC you can now gain additional security:

The RFC server system checks the identity of an RFC client system (authorization fields RFC_SYSID and RFC_CLIENT of the authorization object S_RFCACL).

Through the authorizations of the service user for the authorization object S_RFCACL, it is also possible to restrict which users (authorization field RFC_USER) in the RFC client system can use the connection, with which applications (authorization field RFC_TCODE).

In case 2d), no login data is provided in the RFC destination, but the option “same user“ is selected. The users who want to use such a trusted RFC connection, must have authorization for the authorization object S_RFCACL, with the authorization field RFC_EQUSER set to “Y” and the field RFC_USER empty or set to the dummy value „ (inverted comma).

The trusted RFC connection has the following security attributes:

Simple navigation (via Single Sign-On) from RFC client to RFC server.

A user has his personal authorizations in the SAP Solution Manager system as well as in the connected managed systems.

The RFC server system accepts the authorization by the RFC client system.

RFC connections between SAP systems can also be secured by “secure network communication” (SNC), and the authorizations in the RFC client system can be limited by the authorization object S_ICF, to restrict user access rights to RFC connections.

Note for Trusted RFC

SAP Note Short Text

128447 Trusted/Trusting Systems



18 May 2011

2.10.3 System and Landscape Directory (SLD), Landscape Management Database (LMDB) and SMSY

Many functions in SAP Solution Manager rely on up-to-data landscape data. This is especially true for system maintenance, but also for various other applications. Since landscape data is mostly gathered outside the SAP Solution Manager system, the landscape needs to be taken into account. The main landscape management building blocks are the System Landscape Directory (SLD), and the Landscape Management Database (LMDB). This is how to set up landscape data management:

SLD The technical system data is gathered by self-registration of technical systems in the System Landscape Directory (SLD). The SLD contains information on installable software (updated via the SAP Service Marketplace) and technical system data, mostly sent by these systems using data suppliers.

Note: We recommend running one central SLD on an existing Java stack in the landscape, e.g. on an SAP NetWeaver PI system.

For the usage with the Manager Landscape Management Data Base (LMDB) in the SAP Solution Manager certain minimum support packages depending on your SAP NetWeaver version for the SLD applies:

SAP NetWeaver 6.40 – SLD: not supported

SAP NetWeaver 7.0 – SLD: not supported

EHP1 for SAP NetWeaver 7.0 – SLD: not supported

EHP2 for SAP NetWeaver 7.0 – SLD: SP6, Patch 5

SAP NetWeaver 7.1 – SLD: SP9

EHP1 for SAP NetWeaver 7.1 – SLD: all SPs

SAP NetWeaver 7.2 – SLD: all SPs

SAP NetWeaver 7.3 – SLD: all SPs

If your central SLD does not fulfill these requirements, it is also possible to forward the landscape data to an SLD, which is fulfilling the above mentioned requirements and use this for the SAP Solution Manager.

LMDB The data from the SLD is synchronized into the SAP Solution Manager Landscape Management Data Base (LMDB) introduced with Solution Manager 7.1. LMDB is a central, built-in repository for all Solution Manager applications, which consume landscape data. With release 7.1, LMDB becomes the home of all Technical System data. LMDB shares the CIM model with the SLD, plus the automatic content synchronization mechanism, so that all SLD data provided by the productive SLD is propagated into LMDB, without user interaction. Data can be enriched manually in the LMDB. Applications, which use this data include SAP Solution Manager Diagnostics, Monitoring and Alerting, BI Monitoring and PI Monitoring.

SMSY Numerous other applications keep using transaction SMSY for the time being. For compatibility reasons, data for technical systems is replicated to SMSY. In Solution Manager 7.1, the home of Product Systems and Logical Components stays SMSY.

Note: If a local SLD was used in existing SAP Solution Manager environments before 7.1, the LMDB replaces it.


May 2011 19

If productive SLDs are in use, their landscape information can be forwarded to a central SLD, and then to SAP Solution Manager. This forwarding has to be configured manually for each productive system. A central SLD on SAP Solution Manager also allows the maintenance optimizer functions to use the Software Lifecycle Manager (SLM) features. This allows patches and stacks to be downloaded to a central location provided by the SLM.

Note: For landscapes with no productive Java stack outside SAP Solution Manager (as would be used for PI and Web Dynpro Java), implementing the SLD in SAP Solution Manager's own Java stack would be an alternative to connecting all SLD data suppliers.

SAP’s SLD Recommendation Manual maintenance of the system landscape without SLD is not recommended. Best practice is a central SLD in which all systems register themselves, directly or indirectly, via data supplier forwarding. This central SLD can be outside or inside SAP Solution Manager, depending on the conditions above.Configure the central SLD as the source of the Landscape Management Database (LMDB) in Solution Manager. All SLD data is propagated to LMDB automatically.

SLD and LMDB

Topic Link

SLD planning guide https://www.sdn.sap.com/irj/sdn/nw-sld

SLD Topology http://www.sdn.sap.com/irj/scn/weblogs?blog=/p

ub/wlg/17579

Connect a Managed SAP System

Topic Transaction Detailed Description

Connect a Managed SAP System SOLMAN_SETUP Automatic Guided Procedure for Managed System Configuration

Solution Manager System Landscape SMSY Product Systems and Logical Components

2.10.4 Adjust Upgrade of Managed System

You have upgraded a managed system. This section explains how to adjust your settings for this system in the SAP Solution Manager. Prerequisites You have:

SAP Solution Manager projects and solutions in productive use

SLD attached to SAP Solution Manager Procedure 1. Adjust Product Version

a) To adjust the new product version for your upgraded managed system, go to transaction SMSY and choose your system.

b) Go to Header Data tab, and choose Installed Product Version. In the dialog box, choose the product version you have upgraded to.

c) Save. 2. Adjust Logical Component

https://www.sdn.sap.com/irj/sdn/nw-sld

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17579

http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/17579


20 May 2011

a) Create a new logical component for your upgraded managed system. b) In SAP Solution Manager Administration Workcenter deactivate any solutions that contain

the managed system.

If you monitor business processes in this system, deactivate the business process monitoring sessions for it.

c) Go to transaction SOLMAN_DIRECTORY and your solutions, and replace your outdated

logical component with your new logical component. d) Activate your business process monitoring session and solutions again.

In an implementation project, you may want to leave the outdated logical component in your project, for documentation purposes.

Adjust Upgrade of Managed System


Solutions in SAP Solution Manager

SOLMAN_WORKCENTER Adjust Upgrade of Managed System

Solution Directory SOLMAN_DIRECTORY Adjust Upgrade of Managed System

2.11 Moving from SAP Solution Manager Transation DSWP to Work Centers

With the introduction of Work Centers with SAP Solution Manager 7.01 SP15, all new SAP Solution Manager developments have been done exclusively with a focus on Work Centers. In the future, the Work Centers will be the single entry point for all activies. In the past transaction DSWP (or SOLUTION_MANAGER) served as the primary entry point fir Operations and Operations Setup within SAP Solution Manager. As the transaction has become outdated with the SAP Solution Manager 7.1 this transaction was deactivated. For the latest informantion, please review SAP Note 1541013.

Therefore, after all landscape components have been created, the solutions must now be created via the Solution Manager Administration Work Center (Solutions). See the SAP Solution Manager - Solution Concept and Design document in the Service Marketplace, before defining the solution.

Solution Concept and Design

Short Text Note / Link

SAP Solution Manager: Solution for SAP Service Delivery

SAP Note 1117389

Deactivation of transaction DSWP SAP Note 1541013

2.12 Solution Transfer

When a new SAP Solution Manager is installed, you need to transfer some information from the previous SAP Solution Manager, such as issues, service plans, landscape info, business processes etc. to it. You can do this with the transaction SOLUTION_TRANSFER. This process has two steps:

1) Transfer systems and logical components from source to target. This is SMSY data and it is usually transferred from TMS or SLD into SMSY, so there is no need to transfer it manually. Additional steps are:

a. Create a target solution in your target SAP Solution Manager,





May 2011 21

b. Create logical components there, and assign them to a target solution. 2) Transfer the data from your source solution. Business processes are transfered, as well as

business process monitoring configuration data and all data in the service sessions.

Solution Transfer

Short Text Link

Export Solution http://help.sap.com → SAP Solution Manager →

<language> → Basic Settings → Solutions → Manage Solution → Export Solution

Import Solution http://help.sap.com → SAP Solution Manager →

<language> → Basic Settings → Solutions → Manage Solution → Import Solution

2.13 Service Delivery in SAP Solution Manager The SAP Solution Manager is the SAP service delivery platform. This includes self-services, which can be performed by the customer, as well as services which are delivered by SAP, such as EarlyWatch, GoingLive, etc. All services are solution-specific and can be used for all systems in the solution.

Notes for Service Delivery

SAP Note Short Text

91488 SAP Support Services - Central preparatory note

1172939 Technical prerequisites for remote service delivery in SSM

1170668 The role of SAP Solution Manager in Remote Service Delivery

2.14 Multi-Tier Landscape for SAP Solution Manager You can use should use at least a two-tier landscape for your SAP Solution Manager. Test new Support Packages, patches or configuration scenarios on a test system first. If the test is successful, the changes can be installed in the productive SAP Solution Manager. A transport between two SAP Solution Managers is not usually necessary.

You should use a three-tier landscape with transports, if you perform classic customizing or own developments in SAP Solution Manager. In this environment, changes must first be developed in the development system, and transported into the productive SAP Solution Manager after testing in the quality assurance system. The usual scenarios for this case are change request management and/or service desk.

2.15 Sizing for SAP Solution Manager There is a new sizing tool-kit for SAP Solution Manager 7.1, which can be found in the Service Marketplace. It contains components (guides, cookbook, and spreadsheet) to run a sizing project for SAP Solution Manager. This tool-kit:

Finds hardware resources needed to implement SAP Solution Manager for a given landscape.

Determines the corresponding SAP Solution Manager cluster configuration.







22 May 2011

Configures SAP Solution Manager and Wily IS EM to obtain better performance and scalability.

Sizing for SAP Solution Manager

Topic Link

SAP Solution Manager Sizing Tool-Kit http://service.sap.com/sizing-solman

2.16 Related Documentation Related Documentation

Topic Guide/Tool Quick Link on SAP Service Marketplace

(http://service.sap.com)

Detailed scenario description

SAP Solution Manager Master Guide

Instguides → SAP


Support Package-specific configuration guide

SAP Solution Manager Configuration Guide

Instguides → SAP


SAP Solution Manager Upgrade Guide

Upgrade SAP Solution Manager 7.0 EHP 1 to SAP Solution Manager 7.1

Instguides → SAP


Wily Introscope Installation Guide

Wily Introscope - Installation Guide

Diagnostics → Installation and

Configuration

http://service.sap.com/sizing-solman

http://service.sap.com/


May 2011 23

3 Monitoring SAP Solution Manager Monitoring is an essential SAP technology management task.

3.1 New Monitoring Infrastructure Proactive, automated monitoring is the basis for ensuring reliable operation of your SAP system environment. There is a new Solution Manager Self-Monitoring, which is based on the new Monitoring Infrastructure, which is introduced with SAP Solution Manager 7.1. The Self Monitoring Setup is integrated in transaction SOLMAN_SETUP:

Choose the section Technical Monitoring

Choose the scenario SolMan Self Monitoring

Follow the guided procedure

The prerequesites for using the new Self-Monitroing are:

System Preparation & Basic Configuration completed successfully

The Solution Manager itself is successfully setup as a managed system

The SAP Service Marketplace (SAP-OSS) connection is working

New Monitoring Infrastructure

Topic Link

New Monitoring Infrastructure http://help.sap.com → SAP Solution

Manager → SAP Solution Manager 7.1

3.1.1 Connection Monitoring

For the technical operation of the SAP Solution Manager working RFC connections to the managed systems are essential. Therefore you should monitor the RFC connections from the SAP Solution Manager to the managed systems with the Connection Monitoring, which is also part of the new monitoring infrastructure. The setup of the Connection Monitoring is also integrated in transaction SOLMAN_SETUP:

Choose the section Technical Monitoring

Choose the scenario Connection Monitoring

Follow the guided procedure

3.2 CCMS Monitoring – SAP Solution Manager The CCMS Monitoring can still be used as data supplier for new monitoring infrastructure. For more

information about the CCMS monitoring see http://help.sap.com → SAP NetWeaver → SAP

NetWeaver 7.0 including Enhancement Package 2 → <language> → System Administration → Technical Operations Manual for SAP NetWeaver.

You can activate CCMS monitoring for a solution (Work Center Solution Manager Administration → Solutions → <Select a specific Solution> → Solution Settings → CCMS Monitoring of EWA). You can activate and deactivate CCMS monitoring for specified solutions.

If monitoring is active, you will get monitoring objects in transaction RZ20 under the monitoring tree element (MTE) “SOLMAN”. Under this MTE there is another one for each active solution, with the following content:

Rating of EWA for each <SID>

Rating of each SL Report

Successful download of data into the SDCC




24 May 2011

3.2.1 CCMS Monitoring – Internet Graphics Server (IGS) Call transaction SIGS, select the RFC destination and choose Environment → Switch on CCMS. You will get a separate node in transaction RZ20 for “IGS availability”, which tells you if the Internet Graphics Server is available.

3.3 SAP EarlyWatch Alert in SAP Solution Manager SAP EarlyWatch Alert (EWA) is a monitoring service for SAP customers that monitors SAP systems in your solution landscape. SAP recommends that all customers perform centralized system monitoring of all connected managed systems in SAP Solution Manager, to have access to all important information from a central location. You can also use SAP Solution Manager to create service level reports that are tailored to your requirements (for example, by using customizable transactions and threshold values to trigger the creation of the reports).

You can receive a regular E-Mail with the reports for specific systems or solutions, to monitor the content of the SAP EarlyWatch Alert, SAP EarlyWatch Alert for Solutions and Service Level Reports. To configure this goto System Monitoring Work Center → Configure Automatic Reports Mailing → <Select a Solution> → Edit → Create E-Mail Recipient).

3.4 Other Problem Analysis and Monitoring Tools

3.4.1 Application Monitoring

Several SAP Solution Manager components use the application log in transaction SLG1. These components are basic SAP Solution Manager functionalities, but you can monitor the application log also for other applications in the SAP Solution Manager. Beside the usual SAP NetWeaver based Log Object, the most important Log Object for SAP Solution Manager can be found in the following table:

Log Objects in SLG1

Object Suboject Area

/TMWFLOW/CMSCV * Application Log /TMWFLOW/

AISDK * Solution Manager Service Desk

AI_LMDB * Landscape Management

AGSGEN * Generic Extractor

CCDB * Configuration and Change Database

CRM_SOCM * Change Request Management

DIAGNAV * Solution Manager Diagnostics Navigation

E2E_ALERTING * Monitoring and Alerting Infrastructure

E2E-CA * E2E Change Analysis

E2E-DIAG * Solution Manager Diagnostics

E2E-EA * E2E Exception Analysis

E2E-WA * E2E Workload Analysis

EEM * Enduser Experience Monitoring

LMDB * Landscape Managemant Database

RBE40 * Solution Dokumentation Assistant


May 2011 25

SDOK * SAP Knowledge Provider

SMSY_LOG_OBJ * System Landscape Log Object

SOLAR * Solution Manager

Problem Analysis Tool

Component Monitor Detailed Description

SAP Solution Manager SLG1 Application Log


26 May 2011

4 Management of SAP Solution Manager SAP provides an infrastructure to help technical support consultants and system administrators manage all SAP components, and perform technical administration and operation tasks.

For more information see http://help.sap.com → SAP NetWeaver → SAP NetWeaver 7.0

including Enhancement Package 2 → System Administration.

4.1 Solution Manager Administration Work Center SAP Solution Manager 7.1 is introducing a new Solution Manager Administration work center, which provides applications for:

Management of the Solution Manager Landscape

Management of the Solution Manager Infrastructure

Self Diagnosis for

Solution Manager

Managed Systems

Solution Manager Self Monitoring

Maintenance of

Solutions

Projects

In different views various functionalities for administration of the SAP Solution Manager can be accessed.

4.1.1 Landscape View The Landscape view provides you with an overview about all components of a single landscape entity (like system, host, database, …) in SAP Solution Manager. You can start applications single applications for:

System Details

Maintenance of RFC Connections

Extractor Framework

Agent Framework

Change Database

The applications for system status and details contain information about modelling of one technical system to verify how the system landscape is defined in SAP Solution Manager. This includes detailed information about

Different system status providers

The system details in the landscape browser like

Software Components

Clients

Instances

Parameters

Database

…

The Technical System Editor offers the user interface for the landscape management database (LMDM). It is possible to

Create or maintain a technical system

Check maintenance data for consistency

The RFCs of a SAP Solution Manager system to each managed systems can be created, maintained and checked. This includes:





May 2011 27

READ RFC

TMW RFC

RFC for Solution Manager applications:

Login

Trusted

Back RFC

With User

Trusted

4.1.2 Infrastructure View

The Infrastructure view provides you with application for landscape independent administration applications like

Agent Administration

Extractor Framework

Alerting Framework

Root Cause Analysis Content

Wily Introscope

Log Viewer

Landscape Management Database (LMDB)

BW Reporting

The Agent Administration is the cCentral point of maintenance for all Diagnostics-Agents which are installed accorss all managed systems including:

Access to the agent administration

Agent role assignment for data collection

Diagnostics Agent performance metrics

Exceptions from the agent infrastrucutre

The Extractor Framework (EFWK) application allows you to get information about the data extraction accross all managed systems. This includes:

Status information (failed, banned, inconsistent extractors) for extractors and the Resource Manager

Configuration of ressource caps

Detailed configuration of extractors

Activation / Deactivation of single extractors

Perfomance data

Exception from the EFWK

The Alerting Framework view gives you detailed information on the status, configuration, performance and existing exceptions for the main infrastructure elements of the new alerting infrastrucutre:

Status check for Pull and Push data collection

Traces of the Alert Calculation Engine

Load Balancing configuration

Detailed performance metrics

Exceptions of the alerting infrastructure

The Root Cause Analysis Content view includes:

Access to the templates for


28 May 2011

o Configuration and Change Reporting Stores o Extractors o Work Center View Configuration o URL Framework

This section is used for troubleshooting and customization and should be handled with care.

The Introscope application allows you to centrally manage your CA Wily Introscope Enterprise Manager landscape:

See the status / version of the installed Introscope Enterprise Managers (EM)

Perform central user administration for

Import existing installations

Install new EM

Maintain EM configuration parameters

Performance metrics

BW Reporting is one of the main infrastructure components of a SAP Solution Manager System, here you get detailed information on:

The overall status of your BW system

Overall usage data and breakdown of used space per scenario

Reporting Scenario Setup

Detailed log information for each reporting use case with Self Checks for error analysis

4.1.3 Self Diagnosis View The Self Diagnosis view integrates the Self Diagnosis and the Diagnostics Self Check in one infrastructure. Here you can get information on the status of the managing and all managed systems.

4.1.4 Solution View The Solution View gives you access to all solution relevant operations and setup tasks:

Creation of a solution

Solution Settings

Solution copy and transfer

Setup of Operation tasks (EWA, SLR,…)

4.1.5 Project View The Project view gives you access to all project relevant operations and setup tasks:

Creation of a project

Project Administration

Project copy

4.2 Starting and Stopping When you start the SAP System, you start the system database, the application server and the processes of which the system consists. In the simplest case, an SAP System consists of only a database and a single application server.

There are different processes, depending on the SAP system and operating system platform.


May 2011 29

You can start and stop systems and instances centrally, using the SAP Management Console for all platforms (as of SAP NetWeaver 7.0), the System Administration Work Center in SAP Solution Manager, or the Microsoft Management Console under Windows. For details, see For details, see

http://help.sap.com → SAP NetWeaver → SAP NetWeaver 7.0 including Enhancement

Package 2 → <language> → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks → Starting and Stopping SAP NetWeaver ABAP and Java.

4.3 Backup and Restore As the SAP Solution Manager is based on SAP NetWeaver, all general recommendations for an SAP NetWeaver backup and restore strategy apply. Depending on the processes you are running on the SAP Solution Manager, you may also need to backup external components and handle cross-system data dependencies.

The backup and restore strategy for your system landscape should be embedded in overall business requirements and incorporate your company‟s entire process flow, not only SAP systems. The backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. You must ensure that backup devices are not lost along with normal data storage (separation of storage locations).

SAP recommends that you run the database in archive mode This means that all actions on the database that modify data are recorded by the database and written to a transaction log. With regular full backups of your database (either offline or online), as well as a complete set of transaction logs since the last backup, it is possible to restore a crashed database to any point in time before the crash.

Backup your database every day You must backup the log files several times a day. For more information, see SAP Help Portal at:

http://help.sap.com → SAP NetWeaver → SAP NetWeaver 7.0 including

Enhancement Package 2 → <language> → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → Database Administration → <Database Name>.

A backup process allows you to save business data and keep the downtime of the system landscape to a minimum during restoration of the infrastructure and business data. The main issues in a backup and recovery process are:

You must develop a backup concept in the implementation phase. A backup process must ensure logical and physical consistency. Consistency Technology allows you to create a consistent image (or consistent copy) of a federated system landscape, without taking the systems offline. There are currently two different types of consistency technologies available:

Coordinated database suspension

Consistent split technology on storage level

You must consider a detailed backup and recovery concept if you have a distributed business system landscape. This concept must account for both the business data, which is contained in databases, and the runtime infrastructure.

You should not use a backup and recovery concept for your entire system landscape and single system components just for SAP systems. It should be embedded in all business requirements and take into account the entire process flow in your enterprise

You must consider the following elements when you plan a backup and recovery strategy for application, software, and configuration files:








30 May 2011

o Operating system

o Database data files

o Database software

o SAP software and file systems

o Log files (SAP and others)

o Software of other system components (file systems and configuration files)

You perform a backup:

o After the initial installation and configuration of the system landscape

o After changes, such as changes to the configuration, software upgrade of individual

components, or replacement of components made to the system landscape. This depends on the frequency of such changes. You need to back up individual components regularly, to ensure that you can restore and recover them if there is a system failure.

4.3.1 Backup Introscope Enterprise Manager

The Introscope Enterprise Manager is temporary storage for workload-related data. In the standard

setup, this data is transferred once an hour to the BI of the SAP Solution Manager, so a separate

backup of this component is usually not needed.

SAP recommendation: There is no backup strategy to implement for Wily SmartStor.

However, if you want to backup this component, its directories have to be backed up regularly:

Wily supports only Offline backup with the following procedure

Shutdown Enterprise Manager,

Backup SmartStor (file backup)

o The directory „../data‟ contains all agent data

o The directory „../traces‟ contains all Wily trace data.

Restart Enterprise Manager

4.4 Periodic Tasks This chapter describes all automic tasks which run periodically to keep the application running over time. Such tasks may be required on component level and are relevant in each scenario that uses the component. The mapping is in the chapter scenario/component matrix above. Other tasks may be relevant for certain business scenarios only. You must monitor the performance of these tasks regularly.

You should also schedule the standard basis jobs in transaction SM36 in the SAP Solution Manager.

ABAP Standard Jobs

Topic Transaction / Link

ABAP Standard Jobs Transaction SM36 → Goto → Standard Jobs

4.4.1 Background processing in the SAP Solution Manager The background processing in SAP Solution Manager does not require regular administration. The administrator just has to ensure that no jobs are aborted. The SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS. This program minimizes the administration required. The standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP). Some SAP Solution Manager applications may require additional background jobs.


May 2011 31

Some of the most important jobs are:

For more information on background processing in SAP Solution Manager, and a detailed list and short description of the jobs, see SAP Note 894279.

SAP Solution Manager Background Jobs

Job name Program / Variant Recommended Frequency

Detailed Description

SM:SCHEDULER RDSWPJOBSCHEDULER Starts an important job that automatically executes service sessions

EFWK Resource Manager

E2E_EFWK_RESOURCE_MGR This job is scheduled by the diagnostics managed system setup, and starts the extractors in the extractor framework.



32 May 2011

E2E BI HOUSEKEEPING E2E_HK_CONTROLLER BI Housekeeping for diagnostics (for details see note 1480588)

SAP_ALERT_ CALCULATION_ENGINE

ACE_CALCULATION_ CONTROLLER

Central job for new monitoring and alerting infrastructure

Scenario-specific scheduled periodic tasks

Required for scenarios

Program Name/Task

Recommended Frequency

Detailed Description

Partner Service Desk

RNOTIFUPDATE07 every 15 minutes Activates regular data exchange between your system and the SAP global support backbone. It checks if there are new messages for your support team in the SAP global support backbone, and forwards them to your SAP Solution Manager. Conversely, it transfers from your system into the SAP global support backbone

SAP Notes for SAP Solution Manager Background Jobs

SAP Note Short Text

894279 Background processing in SAP Solution Manager

16083 Standard jobs, reorganization jobs

1480588 ST: E2E Diagnostics - BI Housekeeping - Information

4.5 User Management User Management is very important in SAP Solution Manager. SAP Solution Manager is a single-client system, so users can only be separated by an authorization concept. Work centers, which separate functions between different users, have been available since 7.01 SP15.

4.5.1 User Administration and Authentication

A lot of RFC read connections are used in SAP Solution Manager. It is important that the users used are not prevented from getting information from the managed systems or sending data to SAP Solution Manager.

The RFC wizard generates the RFC connections and users automatically, in the managed systems and SAP Solution Manager. If managed systems are in a central user administration, this user must be defined previously in the CUA system. You can use the generated users with the setup. Some applications expect named RFC connections. If this connection is not available, you must authorize the RFC connection user used, manually.

The SAP Solution Manager security guide contains a comprehensive description of users and authorization. There is a detailed description of the user management in the root cause analysis

scenario, in the Service Marketplace at http://service.sap.com/diagnostics.






May 2011 33

There are several user management tools (SAP & third-party systems). The table below provides an overview and a short description of these user management tools.

User Management Setup/Tools

Tool Usage

SAP User Management Engine for ABAP Engine (transaction SU01)

Central User Administration (CUA) for SAP WebAS

Profile Generator (transaction PFCG) Tool for Web AS role administration, especially authorization administration

SAP User Management Engine (UME) Administration Platform

Tool for administration of portal users and roles

SAP J2EE Engine user management using the Visual Administrator

Tool for administration of J2EE users and roles

Business Partners

Business partners must be defined for some specific scenarios (e.g. Service Desk, Change Request Management).

Maintain Business Partners

Tool Usage

Maintain Business Partner (transaction BP)

Maintenance of Business Partners

Further Documentation

Tool Link

Security Guide – SAP Solution Manager


Root Cause Analysis - User Administration Guide


4.5.2 Create Users and Business Partners for End Users

The following lists give an overview of functions that require users in the SAP Solution Manager system and managed systems, and functions that require business partner users in the SAP Solution Manager system: Functions Requiring End Users for SAP Solution Manager and Managed Systems

Implementation: if you use Implementation and subsequently Customizing Distribution to centrally configure your managed systems. Implementation and Customizing Distribution use Trusted RFC connections, which always require users in both systems.

Test Management: if testers have to test in managed systems. Test Management uses Trusted RFC connections, which always require users in both systems.

Service Desk: for Key User (end user), see example below

System Administration and System Monitoring (and Business Process Operations): if the system administrator needs to check transactions in managed systems via SAP Solution Manager trusted RFC connection.

Change Request Management: if the users in the Change Request Management process log on to the managed systems via SAP Solution Manager.




34 May 2011

Root Cause Analyses: user SAPSUPPORT is automatically created in the SAP Solution Manager system as well as the managed systems, during Root Cause Analysis configuration.

Functions Requiring Business Partners Based on Users in SAP Solution Manager

Delivery of SAP Services: if you use Issue Management.

Service Desk: for Key User (end users) and processors of service desk messages see example below.

Change Request Management

Job Scheduling Management

Change Control: functionality Maintenance Optimizer Create Users Using Transaction SU01 This paragraph tells you which area in User Management (transaction SU01) needs attention, and why.

Enter your user and choose change.

Enter the required data and save. Address Data

First Name and Last Name o Function: Digital Signature

E-Mail o Function: Business Process Operations o Function: Solution Directory (Check in / Check out) o Function: Issue Management o Function: Service Desk o Function: E-Learning Management

The user can receive and send e-mails. This e-mail address can be any address, as long as it is known to the mail server (Business Process Operations: for use of auto-reaction methods). Create Business Partner Using Transaction BP_GEN

1. Choose User list → Add system. 2. Select a system from which you want to create business partners. 3. Select users. 4. Choose Edit → Create Business Partner. 5. Confirm your entries.

Example You want to create end users for Service Desk functionality. The system landscape consists of SAP Solution Manager and two managed systems, three systems in total. You have to create all end users known to SAP Solution Manager, as Business Partners, in the SAP Solution Manager system and the managed systems.

1. Create users for all end users in all three systems, as described above. 2. Create business partners for end users, in the SAP Solution Manager system, as

described above.

Create User or Business Partners Automatically To ensure that the users of the managed systems can, for example, check the processing status of support messages in SAP Solution Manager, they must be created as users and business partners in SAP Solution Manager. The report AI_SDK_USER_BP_GEN determines new users in the managed systems.

You can perform the following functions with this report:

List new users by comparing SAP Solution Manager and managed systems:


May 2011 35

o As administrator, check in which managed systems there are new users. o As SAP partner, find new managed systems for a customer and/or new users in a

customer's managed systems.

If your security policy permits it, you can automatically create or update new users and business partners in SAP Solution Manager.

Recommendation Create a variant and schedule the report as a weekly background work process. For more information please consult the corresponding SAP Help. Create Users and Business Partners for End Users


User Management SU01 Create Users

Create Business Partner BP_GEN If you change e-mail addresses for users, you need to update your business partners

Create Users or Business Partners Automatically

Tool Link

Report AI_SDK_USER_BP_GEN http://help.sap.com/saphelp_sm70ehp1_sp2

6/helpdata/en/85/390f6e3c534892b18f5ec42

12d0571/frameset.htm

4.5.3 Update Authorizations after Support Package Upgrade

After the new installation and an update of your SAP Solution Manager system, you need to update your tables with new default field values for authorization objects, in transaction SU25. This is especially relevant for all new authorization objects delivered with an update. Caution When you update your system, you must import new roles and profiles from client 000 into your productive client. Procedure

1. Call transaction SU25. 2. Choose Information.

The dialog explains in detail what you need to do. Recommendation

Perform at least the first step.

Update Authorizations after Support Package Upgrade


Profile Generator: Upgrade and First Installation

SU25 Update Authorizations after Support Package Upgrade

http://help.sap.com/saphelp_sm70ehp1_sp26/helpdata/en/85/390f6e3c534892b18f5ec4212d0571/frameset.htm




36 May 2011

4.5.4 Adapt Work Center Queries End users and system administrators can adjust work centers to their needs. End User See document How to Adapt a Work Center View, in the Service Marketplace. System Administrator

Configuring query settings for all end users, or customize the logon screen for Web Dynpro applications. See document How to Adapt a Work Center View in the Service Marketplace.

Deleting queries from database: Execute program POWL_D01

Refreshing active POWL queries: Execute program POWL_WLOAD More Information See IMG activity Adjust Queries (technical name: SOLMAN_WC_QUERY)

Adapt Work Center Queries


How to Adapt a Work Center View


→ Media Library → How-To Documents

4.5.5 Create End User Roles

You need to grant authorizations for which SAP does not ship template roles, in the SAP Solution Manager and managed systems. To be able to assign the correct authorization, you can create a dedicated role for them. This section describes how to create your own roles, using the example of critical authorizations of transactions SU01 (User Management) and PFCG (Role Management). Create a Role in Transaction PFCG

a) Choose transaction PFCG. b) Enter a role name in your namespace, for instance: ZSU01_PFCG, and choose Single

Role. c) Enter a description for your role, for instance: Full authorization for SU01 and PFCG. d) Go to tab menu and enter transactions SU01 and PFCG.

The authorization objects required in role creation are maintained using transactions. When you enter a transaction in the menu tab in your role, the system traces all authorization objects required for this transaction.

e) Save your role. You are asked for a transport request.

Maintain Authorization Objects Default authorization objects delivered by SAP contain only minimal authorizations. To grant full authorization to authorization objects, you must edit them

a) Choose the Authorizations tab in the Role Maintenance. b) Choose Change. c) Maintain all activity values per authorization object, according to your needs, for

instance, if you want to grant full authorization, always choose all activities.

Caution All authorization objects need to have a green traffic light. If you are not sure about the function of the authorization object, double-click the green line. The system opens the documentation for this object in a separate window.

d) Generate the profile.



May 2011 37

e) To assign this profile to a user, choose User tab, add your user in the table and perform the user comparison.

f) Save.

Create End User Roles


User Management SU01 Create End User Roles

Role Maintenance PFCG Create End User Roles

4.5.6 Assign Roles to Users After you have generated profiles from roles, assign the role to your users, in one of the two ways explained below. Transaction SU01

1. Choose transaction SU01. 2. Enter the user and choose edit. 3. Go to Roles tab. 4. Enter your role. 5. Save.

Transaction PFCG

1. Choose transaction PFCG. 2. Enter your role and choose edit. 3. Go to Users tab. 4. Enter the user name. 5. Choose the User Comparison button. 6. Save.

Assign Roles to Users


User Management SU01 Assign Roles to Users

Role Maintenance PFCG Assign Roles to Users

PFCG: Status of user comparison

SAP Note 1272331



38 May 2011

5 High Availability There are no general High Availability (HA) requirements for the SAP Solution Manager. High-availability applications allow you to maximize downtime security and minimize downtimes. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic.

At SAP, high availability is always focused on business applications and their related components. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure, such as the operating system, database, and hardware. Collaborative business can give you a competitive advantage. This means integrating existing heterogeneous system landscapes to include business partners, customers, and suppliers. You may also have requirements of your own, depending on the availability requirements of the implemented IT management processes.

Components with single point of failure

Component Detailed Description HA Setup Description

<Component 1> Describe the function of this component in this scenario that is a single point of failure.

Refer to the component high availability setup description, if available. Otherwise explain here.

Each of the above components can be a single point of failure in this scenario. To achieve HA for the complete scenario, all components with single point of failures must be set up with HA.

Further Documentation

Tool Link

Service Marketplace – High Availability http://www.sdn.sap.com/irj/sdn/ha

Help Portal http://help.sap.com/ → SAP NetWeaver → SAP

NetWeaver 7.0 including Enhancement Package 2 → <language> → SAP Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → High Availability → SAP High Availability documentation

http://www.sdn.sap.com/irj/sdn/ha





May 2011 39

6 Archiving & Data Deletion in SAP Solution Manager

6.1 Achiving functionality in core SAP Solution Manager

There is only limited archiving functionality in SAP Solution Manager 7.1. In particular, the following objects cannot be archived using default SAP archiving mechanisms:

Solution Manager projects

Solution landscapes

CRM transactions, such as service tickets, change requests, change documents and issues.

Monitoring data in central performance history database

Test packages/test cases These objects do not usually contain a lot of data. Documents in Solution Manager projects The only function which might need a lot of database space is document management in the implementation scenario. Depending on the number, type and frequency of documents checked in, several hundred MBs per week and project might be needed – because usually every version of a document is kept. Those documents (or old versions) in Solution Manager projects can be archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. This report moves the document contents (files) from the built-in knowledge warehouse (KW) layer, to another repository, e.g. an archive. However, the document attributes needed to administer the documents will be kept in SAP Solution Manager. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE, if they can still be deleted. Service reports in solutions Service sessions such as EarlyWatch Alert reports, Service Level reports, and the documents attached to them, can be archived using the ArchiveLink interface. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. SAP Note 1092503 describes how to automate the archiving by a job. The following “Solution Reporting” documents can be archived:

Service Reporting

System Availability Reporting

System Administration Reporting

Change Management Reporting

Service Desk Reporting

Issue und Top Issue Reporting

Expert-on-Demand Reporting CRM-based transactions (incidents, change requests, etc.) There is a generic way to archive CRM-based transactions (e.g. service ticket, change document), but it is not supported in SAP Solution Manager, because many functions, such as test workbench and implementation projects, have links to service tickets or change documents. Archiving these CRM-based transactions would break the links to them, and might cause inconsistencies. For details, see SAP Note 845433. Documents on the generic CRM tabs (transaction CRMD_ORDER) cannot be archived.





40 May 2011

Notes for Archiving

SAP Note Short Text

546685 Archiving in Solution Manager (Operation)

845433 Deleting a service process with support message

1092503 Archiving reporting documents in SAP Solution Manager

6.2 SAP Solution Manager Extended Archiving Functionality

The extension package “Extended Traceability” (ET), shipped with ST400 SP13, and generally available to customers with ST400 SP15, archives the documents (or old versions) in Solution Manager projects, with the report SOLMAN_DOCU_VERSION_ARCHIVE. The report SOLMAN_DOCU_VERSION_DEL can then delete the archived documents. Similar functions are available to archive documents which are added to the CRM transaction tabs (e.g. change documents), but only for those which refer to a Solution Manager project (a function also delivered with the ET extension package). Documents on the generic CRM tabs cannot be archived using this function.

The extension package requires a separate license; it is not part of the SAP Solution Manager core functionality. Without a valid license, these reports will not work.

6.3 Alternative Storage & Deletion Strategies

Although generic archiving is not supported by most scenarios in SAP Solution Manager, there are several functions to reduce the amount of data in the database. A customer can save the objects using other methods (put objects in transport requests using migration functions, store reports on separate file server, use SAP content server for knowledge warehouse documents, keep backup of whole system before data deletion).

Solutions Solutions can be deleted from SAP Solution Manager using the functionality in transaction DSWP, or by directly executing report RDSMOPDELETESOLUTIONS. When deleting a solution, all objects produced within that solution (service sessions, reports etc.) will be deleted – if this is possible. If CRM transactions such as service tickets, which carry an attribute for the solution, have been created, deletion of the solution might not be possible (as it is not possible to delete the related CRM transactions). Service reports in solutions SAP EarlyWatch Alert and service level reports could be stored on a separate file server. They can be deleted from SAP Solution Manager using report RDSMOPREDUCEDATA. Projects SAP Solution Manager projects can be stored in a transport using transaction SOLAR_PROJECT_ADMIN. However, this function will only store the business process structure and all related documents; it will not save referenced data, such as CRM transactions or test workbench items. Solution Manager projects can also be deleted using transaction SOLAR_PROJECT_ADMIN.





May 2011 41

Archiving Projects

Topic Link

SAP Solution Manager Help

http://help.sap.com → SAP Solution Manager

Templates

Contents in templates should also be stored in transport requests, because whenever a new

template version is defined in the template project, the older versions can no longer be accessed

(retrieved). Store the contents in a template transport, if you want to reapply and distribute the

template to other systems, (otherwise it would be sufficient to keep a backup copy of the project

state, as defined under “Projects”).

For more information on how to distinguish template transports and (template) project transports,

and when to use them, see:

Archiving Templates

Topic Link

FAQ - Handling Templates with SAP Solution Manager

http://service.sap.com/solutionmanager → Media Library

→ Technical Papers

Test Management

Test plans and packages are repository objects and can therefore be saved or stored using

transport mechanisms. They can be deleted via transaction STWB_2. Test results can be

consolidated and extracted in a test report, which can be stored as an MS Word document. Test

messages (service tickets created during tests) cannot be archived or deleted – see the section

“Achiving functionality in core SAP Solution Manager”.

Test cases of type “manual” or “external application” are repository objects and can therefore be

saved or stored using transport mechanisms. They can be deleted using transaction SCAT and

STWBM.

eCATT objects (system data container, test data container, test scripts, test configurations) are

repository objects and can therefore be saved or stored using transport mechanisms. They can be

downloaded as .xml files. They can be deleted using transaction SECATT and STWBM. eCATT

logs can be archived - for more information, see the SAP Netweaver online documentation.

CATT objects are repository objects and can therefore be saved or stored using transport

mechanisms. They can be deleted using transaction SCAT and STWBM. CATT scripts should be

migrated to eCATT.

Archiving Test Management

Topic Link

Archiving Logs (SAP Library - eCATT: Extended Computer Aided Test Tool, BC-TWB-TST-ECA)

http://help.sap.com → SAP NetWeaver → SAP NetWeaver

7.0 including Enhancement Package 2 → <language> → SAP

Library → SAP NetWeaver by Key Capability → Solution Life Cycle

Management by Key Capability → Test → eCATT: Extended

Computer Aided Test Tool (BC-TWB-TST-ECA) → Logs →

Archiving Logs

Business partners

Obsolete business partners can be deleted using transaction BUPA_DEL, but only if they have not

been used in a service transaction.



http://help.sap.com/saphelp_nw70/helpdata/en/5d/18c43b4f16ba17e10000000a114084/content.htm



http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ba1bacca960611e10000000a42189b/content.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/c43aa1ca64581de10000000a42189c/content.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/c43aa1ca64581de10000000a42189c/content.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/content.htm

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/content.htm


42 May 2011

Data extracted to BI

If data from SAP Solution Manager has been extracted for Business Intelligence (reporting on EWA

raw data, CPH monitoring data, SMSY data, root cause analysis data, and Business Process

Monitoring data), the BI aggregation and deletion mechanisms can be used to reduce the amount

of data in the BI database.

6.4 SAP Notes for Additional/Background Information

SAP Note Short Text

544295 Basis message: Deletion flag status

546685 Archiving in Solution Manager (Operation)

566225 Report to delete the basis notifications with deletion flag

638785 SAP Solution Manager - reduce data volumes

845433 Deleting a service process with support message

976695 New features for RDSMOPDELETESOLUTIONS in SP08

1077447 Solution Manager: TEST_DSMOPSERSESSN_DELETE

1091497 Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN

1092503 Archiving reporting documents in SAP Solution Manager











May 2011 43

7 Software Change Management Software change management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams.

The goal of software change management is consistent, solution-wide change management, with specified maintenance procedures, global rollouts (including localizations), and open integration with third-party products.

After installing/upgrading/updating SAP Solution Manager, the basic configuration should be checked in transaction SOLMAN_SETUP. After you have implemented a new support package or support package stack, you need to check your configuration settings for new and updated configuration tasks. This is especially important for the basic settings. For instance, with every newly-shipped Web Dynpro application, its ICF service needs to be activated.

7.1 Agents Consideration Before any new Software update in Solution Manager, the SMD Agents connectivity layer must be set in Maintenance Mode in the Agent Administration application. You find this Agent Administration via the Solution Manager Administration Workcenter → Infrastructure → Agent Framework. All agents will be put in „sleep‟ mode waiting to reconnect when Solution Manager will be put back in Normal Operation Mode. Agents contents (runtime + agent application: agelets) are automatically updated to the latest version after an upgrade/update of the Solution manager to which they were connected.

7.2 Configuration after Support Package Update After you have implemented a new support package or support package stack (SAP Enhancement Package), you need to check your configuration settings for new and updated configuration tasks. This is especially important for the basic settings. For instance, with every newly-shipped Web Dynpro application, its ICF service needs to be activated. You should update your basic settings configuration by:

Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP, recommended)

7.2.1 Guided Procedure - Automatic Update Configuration You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). To do this, check all activities in the Overview area in transaction SOLMAN_SETUP, and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). In the following, we give an overview of both procedures. Prerequisites

Initially configure all basic settings using the guided procedure for the automatic basic settings configuration.

Update your authorizations, see SAP Note 1236420.

Using the Overview for Update Activities

1. Call transaction SOLMAN_SETUP. 2. In the Overview, the system displays a configuration table with all activities you need to

perform after updating your system. If you select an entry in this table, the Open Activities column shows the steps you need to execute. In Basic Configuration, this may be the activity Activate BC Sets. The system updates this list automatically.

3. In case of an update, you can specify here whether you have to re-execute activities that have already been executed.



44 May 2011

You can use the existing implementation project to track all information about the setup progress of your basic settings. Call transaction SOLAR02 and choose your project.

Using Guided Procedure – Automatic Update Configuration

Short Text Link

Update your authorizations SAP Note 1236420

Online Help for transaction SOLAR02 and/or Work Center Implementation

http://help.sap.com

SAP Solution Manager <current release>

Tutorial on SAP Solution Manager Configuration (transaction SOLMAN_SETUP)

http://service.sap.com/~sapidb

/011000358700001735062008E

7.2.2 SAP Reference IMG – Manual Update Configuration You can update basic settings configuration and scenario-specific configuration using the SAP Reference IMG (transaction: SPRO).

Recommendation We recommend that you update your basic settings using the automated guided procedure, see section Guided Procedure (transaction SOLMAN_SETUP) - Automated Update Configuration. Activate Release Notes Display release notes by choosing Release Notes. The system flags the release information with a blue information icon in front of the IMG activity. Caution See SAP Note 1575395 for details of new IMG activities, changed IMG activities, and deleted IMG activities.

Using IMG – Manual Update Configuration

Short Text SAP Note

Changes to SAP Solution Manager 7.1 IMG as of SP01 1575395

7.3 Ensure Basic Functions via SAP Note In order to ensure that the basic functions of SAP Solution Manager are running properly, it is recommended to regularly check SAP note 1552585. This central note includes other required notes that are extended and renewed regularly. As soon as a new version of the note exists, you should implement it with the Notes Assistant (transaction SNOTE), in which you can automatically implement all notes included. If these notes contain manual actions, these are only described in the note. The note is valid for Solution Manager 7.1 SP01.

Ensure Basic Functions

Component Transaction Detailed Description

Basic Functions SNOTE Check SAP Note 1552585 regularly



http://service.sap.com/~sapidb/011000358700001735062008E

http://service.sap.com/~sapidb/011000358700001735062008E






May 2011 45

7.4 Support Packages and Patch Implementation The SAP Solution Manager has several software components which have their own release strategy. For further information, see the notes below.

Support Packages and Patch Implementation

SAP Note Short Text

394616 Release strategy for SAP Solution Manager (ST)

539977 Release strategy for add-on ST-PI

569116 Release strategy for Solution Manager Service Tools (ST-SER)

608277 Installing and updating content for SAP Solution Manager

631042 Release strategy for Implementation Content (ST-ICO)

939897 SAP Solution Manager usage data

1109650 SAP Solution Manager 7.x Extension Add-Ons

1575395 Changes to SAP Solution Manager 7.1 IMG as of SP01

1562694 SM 7.1 SP01: Authorizations in SAP Solution Manager system

1552585 SAP Solution Manager: Basic functions 7.1 SP1












46 May 2011

8 Troubleshooting

8.1 Connection to SAP An SAP Support Portal connection is required, to be able to send data to SAP. Usually this connection is created by the SAP Solution Manager Setup, with transaction SOLMAN_SETUP.

In transaction SM59, check if connection SAPOSS works; if not, adjust it as required. For more information, see SAP Note 33135: Guidelines for OSS1.

Check whether the distribution group is set to EWA; if not, adjust it as required. For more information, see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS.

For more information, see the following SAP Notes:

SAP Note Short Text

33135 Guidelines for OSS1

766505 OSS1: Changes to RFC Connection SAPOSS

182308 Incorrect Logon Data in R/3 Destination SAPOSS

8.2 SAP EarlyWatch Alert (EWA) SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections. Therefore check regularly the the functioning of the EWA in the System Monitoring Work Center. You select Reports SAP EarlyWatch Alert and a specific managed system. If there is something is wrong with the EWA data collection, you will find a small red flag or a grey icon in the overview.

In this case check the RFC connections and SDCC. For further information, see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”. For more information, see SAP Note 762696 “Grey rating for EarlyWatch Alert”.

For more information, see the following SAP Notes:

SAP Note Short Text

216952 Service Data Control Center (SDCC) – FAQ

762696 Grey rating for EarlyWatch Alert

8.3 Self-Diagnosis The self-diagnosis checks the system requirements for operating SAP Solution Manager. The self-diagnosis tool is highly configurable and can perform solution-specific or cross-solution self diagnosis. A self-diagnostics module is available in SAP Solution Manager. You can analyze your











May 2011 47

SAP Solution Manager system and/or a solution, with the self-diagnosis function, to identify and solve problems.

You can customize SAP Solution Manager self-monitoring, to avoid red alerts. The self-monitoring functionality can be found in the Solution Manager Administration Work Center → Self-Diagnosis. By pressing the button “Settings” you can select which type should generate an alert and inform you, in the Alert Type area.

The self-diagnostics checks the RFC Connection, batch jobs and performance values. The self-diagnosis analyses run daily, in the background, by default. You can perform a new analysis at any time, e.g. to check whether the problems shown by alerts have been resolved. You can display the self-diagnosis results in various levels of detail:

For the SAP Solution Manager (cross-solution), e.g. to identify SAP Solution Manager system performance problems.

For the SAP Solution Manager single solution, e.g. to check that the master data of a solution is consistent.

Self-Diagnosis

Topic Link

New self diagnosis in SAP Solution Manager: a quick guide

SAP Note 1073382



48 May 2011

8.4 CA Wily Introscope To check whether the CA Wily Introscope is running properly:

1. Connect to your CA Wily Introscope WebView via web browser – usually o http://hostname:8081/webview/jsp/login.jsp. If the logon screen of your WebView

does not appear, CA Wily Introscope Enterprise Manager may not be active. 2. Verify in SMD → Diagnostics Setup → Managed Systems → Introscope Agent for the

system in which the Introscope Agent is running 3. Ensure that the version of your agent is the same as the version of the source on your SAP

Solution Manager. The equal sign icon indicates that the version is up to date. 4. Check that CA Wily Introscope Enterprise Manager receives information from CA Wily

Introscope Agent.

For more information please consult the Wily Introscope User Guide or SAP Note 797147 “Wily Introscope Installation for SAP Customers”, which includes also a detailed troubleshooting section.

Related Information

Content Link

Wily Introscope User Guide http://service.sap.com/diagnostics

Wily Introscope Installation for SAP Customers

SAP Note 797147

8.5 Logging and Tracing Logging and tracing is essential for analyzing problems in the SAP Solution Manager Java-based parts. The Java-based parts all use the standard logging of AS Java. This can be configured by using the log configuration function of the SAP NetWeaver Adminstrator under Problem

Management Logs and Traces Log Configuration. The main logging catogries and tracing locations can be found in the following table,

Logging Categories

Logging Category Comment

/Applications/AdminConsole/* AdminConsole

Tracing Locations

Tracing Location Comment

com.sap.sup.admin.* AdminConsole

com.sap.smd.server.* SMDServer

Related Information

Content Link

SAP Netweaver Administrator http://help.sap.com/saphelp_nwpi71/helpdata/en/44/98320f33bf60d6e10000000a114a6b/content.htm




http://help.sap.com/saphelp_nwpi71/helpdata/en/44/98320f33bf60d6e10000000a114a6b/content.htm

http://help.sap.com/saphelp_nwpi71/helpdata/en/44/98320f33bf60d6e10000000a114a6b/content.htm


May 2011 49

9 Appendix

9.1 Related Guides The master guide is a central starting point for the technical implementation of SAP Solution Manager 7.1, and its scenarios. The configuration guide describes the configuration of SAP Solution Manager and its scenarios and functions. All security-related information, particularly about roles and authorizations, is in the security guide.

9.2 Related Information

Related Information

Content Quick Link to SAP Service Marketplace

(http://service.sap.com)

Master Guide, Installation Guide and Update Guide

Instguides → SAP Components → SAP Solution

Manager

Related SAP Notes Notes

Released Platforms platforms

Network Security securityguide

SAP Solution Manager solutionmanager

Root Cause Analysis diagnostics

http://service.sap.com/

Solution Operations Guides SAP Solution Manager 7.1

Documents

Transcript of Solution Operations Guides SAP Solution Manager 7.1