solopsguide_ehp1_20090812

Solution Operation Guide

SAP Solution

Manager 7.0 EHP 1

Operation Guide

Document Version 1.04 - August 12, 2009

© Copyright 2009 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 T +49/18 05/34 34 24 F +49/18 05/34 34 20 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 August 2009

Contents

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

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

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

2 Technical System Landscape ............................................... 9

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

2.2 Software Components ............................................................ 9

2.3 Other Components ................................................................10

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

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

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

2.4 Installation .............................................................................11

2.5 Basic Configuration ..............................................................12

2.6 Root Cause Analysis ............................................................13

2.7 Managed Systems .................................................................13

2.7.1 System Landscapes ................................................................. 13

2.7.2 SAP Solution Manager and Trusted RFC ............................... 14

2.7.3 System and Landscape Directory (SLD) ................................ 15

2.7.4 Connect a Managed SAP System ........................................... 16

2.7.5 Adjust Upgrade of Managed System ...................................... 17

2.8 Solutions and Solution Directory ........................................18

2.9 Service Delivery in SAP Solution Manager ........................20

2.10 Multi-Tier Landscape for SAP Solution Manager .............20

2.11 Sizing for SAP Solution Manager ......................................20

2.12 Related Documentation ......................................................20

3 Monitoring SAP Solution Manager ..................................... 22

3.1 SAP EarlyWatch Alert for SAP Solution Manager .............22

3.2 Alert Monitoring with CCMS .................................................22

3.2.1 CCMS Monitoring – SAP Solution Manager ........................... 22

3.2.2 RFC Connections ..................................................................... 22

3.2.3 CCMS Monitoring – Internet Graphics Server (IGS) .............. 23

3.2.4 Component-Specific Monitoring ............................................. 23

3.3 Other Problem Analysis and Monitoring Tools ..................23

3.3.1 Application Monitoring ............................................................ 23

3.3.2 Monitoring with Work Centers ................................................ 24

4 Management of SAP Solution Manager ............................. 25

4.1 Starting and Stopping ...........................................................25

4.2 Backup and Restore .............................................................25


August 2009 5

4.3 Periodic Tasks .......................................................................26

4.3.1 Background processing in the SAP Solution Manager......... 27

4.3.2 SAP Notes for SAP Solution Manager Background Jobs ..... 30

4.4 User Management .................................................................30

4.4.1 User Administration and Authentication ................................ 30

4.4.2 Create Users and Business Partners for End Users ............. 31

4.4.3 Update Authorizations after Support Package Upgrade ....... 32

4.4.4 Adapt Work Center Queries ..................................................... 33

4.4.5 Create End User Roles ............................................................. 33

4.4.6 Assign Roles to Users ............................................................. 34

5 High Availability ................................................................... 36

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

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

6.2 SAP Solution Manager Extended Archiving Functionality38

6.3 Alternative Storage & Deletion Strategies ..........................38

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

7 Software Change Management ........................................... 41

7.1 Configuration after Support Package Update ....................41

7.1.1 Guided Procedure - Automatic Update Configuration .......... 41

7.1.2 SAP Reference IMG – Manual Update Configuration ............ 42

7.2 Ensure Basic Functions via SAP Note ................................42

7.3 Support Packages and Patch Implementation ...................42

8 Troubleshooting .................................................................. 44

8.1 Connection to SAP ................................................................44

8.2 System Landscape Directory (SLD) ....................................44

8.3 SAP EarlyWatch Alert (EWA) ...............................................45

8.4 CA Wily Introscope ...............................................................45

8.5 Self-Diagnosis .......................................................................45

9 Appendix .............................................................................. 47

9.1 Related Guides ......................................................................47

9.2 Related Information ..............................................................47


6 August 2009

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.


August 2009 7

Important SAP Notes

SAP Note Number

Title Comment

394616 Release strategy for SAP Solution Manager

You are planning to install and upgrade SAP Solution Manager

1145779 SAP Solution Manager 7.0 Installation

Additional information and problems discovered after the publication of the installation guide

1172948 SAP Solution Manager - basic function

This note is valid as of ST-400 Support Package 18. Implement the note to ensure the basic functions in SAP Solution Manager.

1244225 Solution Manager 7.0 EHP 1: recommended SAP Note

You are about to update your SAP Solution Manager system to SAP Solution Manager 7.0 EHP 1, or want to import a support package stack for this product version.

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





8 August 2009

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.0 EHP 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

1.01 Include handling of SAP Note 1172948 into chapter 7.1

1.02 Include several chapters for Configuration after Support Package Update and structural changes

1.03 Transaction SOLUTION_MIGRATION deleted, Link to Best Practice SAP Solution Manager - Solution Lifecycle added

1.04 Add information about Business Process Check In/Out into chapter 2.8 and 4.4.2

http://service.sap.com/instguides



August 2009 9

2 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 your IT and application management. More information 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.

Cental Information Sources

Topic Link

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

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

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

2.2 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

CRMUIF CRMUIF for Solution Manager

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

ST-ICO Solution Manager Implementation Content

BBPCRM BBP/CRM

CPRXRPM cProjects and others

PI_BASIS PI_BASIS

http://service.sap.com/solutionmanager

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

http://help.sap.com/


10 August 2009

Usage Type Additional Adapers

ST-PSM SAP process scheduling adapter

ST-QCA SAP Adapter for SAP Quality Center by HP

ST-SPA SAP Produktivity Pak

Usage Type Java Application Server

LMSERVICE Root Cause Analysis

ISAGENTSMD<REL>.SCA CA Wily Introscope agent

Aditional Software

Appsight Blackbox and Console BMC AppSight

Introscope Enterprise Manager CA Wily Introscope

Third-Party Integration

There are several standard interfaces to third-party tools:

Additional Software

Tool Link

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

Solution Manager Extensions → Adapter for SAP Quality Center by HP.

SAP Central Process Scheduling by Redwood

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

Solution Manager Extensions → Process Scheduling adapter for SAP Solution Manager.

SAP Productivity Pak by RWD

SAP Note 1131270

BMC Appsight for Client Diagnostics

SAP Note 1034902

2.3 Other 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) SICS http://<IGS host>:<IGS port>

Notes for IGS

https://service.sap.com/solutionmanager

https://service.sap.com/solutionmanager




August 2009 11

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)

The SAP NetWeaver Search and Classification (TREX) is used for the Solution Database in the Service Desk Scenario.

Administration of TREX

Topic Transaction Link

SAP Netweaver Search and Classification

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

NetWeaver 7.0 including Enhancement Package 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → Administration of Standalone Engines → Search and Classification (TREX)

Administration of TREX

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

NetWeaver Enterprise Search 7.0 → <language> → Appendix → TREX Admin Tool in the SAP System (TREXADMIN).

2.3.3 CA Wily Introscope

CA Wily Introscope is a software component for the root cause analysis scenario and SAP EarlyWatch Alert for Java. It collects performance and other system-related data of non-ABAP components in your system landscape. SAP Note 797147 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.

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

1273028 Introscope 8 Release Notes

2.4 Installation

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.0, and are not yet on Unicode, SAP recommends migrating to Unicode. If this





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








http://service.sap.com/diagnostics




12 August 2009

is not possible, SAP will support the SAP Solution Manager on non-Unicode, until the customer has completed the Unicode conversion.

You can implement functional updates without upgrading your SAP system to a higher release, with SAP enhancement packages (EHPs). This concept is introduced for SAP NetWeaver with SAP EHP 1 for SAP NetWeaver 7.0, and will be available for SAP EHP 1 for SAP Solution Manager 7.0 (this is sometimes also referred to as support package stack 18 for SAP Solution Manager 7.0). For further information see the Update Guide SAP Solution Manager EHP 1.

SAP Solution Manager Installation

Topic Link

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

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

Update Guide SAP Solution Manager http://service.sap.com/instguides

2.5 Basic 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 a Web Dynpro application which is 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 includes:

Basic SAP Solution Manager settings

Integration of managed systems

The scenarios that are covered by this guided procedure are:

Maintenance optimizer

SAP EarlyWatch Alert

Root cause analysis

Basic service desk

Expert on demand

Basic business blueprint and configuration

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.0 EHP 1.


http://service.sap.com/unicode




August 2009 13

Basic Configuration

Topic Transaction / Link

SAP Solution Manager Configuration SOLMAN_SETUP

SAP Reference IMG SPRO

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

Components → SAP Solution Manager → Release 7.0 EHP 1

2.6 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.0 EHP 1. The configuration of root cause analysis is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP).

Root Cause Analysis

Topic Note / Link

End-to-End Diagnostics SP18 SAP Note 1238197

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

2.7 Managed Systems

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 it must be able to access the backend 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). This procedure includes:

Setting up RFC connections

Performing a prerequisites check

Configuration of CA Wily Introscope and root cause analysis

Maintenance of a logical component

2.7.1 System Landscapes

The managed systems must be included in the system landscape (transaction SMSY). The definition of system groups and logical components is based on this. For logical component definition, see the logical component concept guide, in the SAP Service Marketplace.





14 August 2009

Logical Component Concept

Topic Link

Logical Component Concept http://service.sap.com/solutionmanager →

Media Library → Technical Papers

2.7.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:

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).



August 2009 15

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

2.7.3 System and Landscape Directory (SLD)

The System Landscape Directory is the central information repository for your system landscape. The SAP NetWeaver system landscape directory is the central directory of system landscape information for the management of your software life-cycle. A directory of information about all installable software available from SAP, and automatically updated data about systems already installed in a landscape, helps you plan tool support for software life-cycle tasks in your system landscape.

The Landscape Description provides a precise picture of a customer system landscape. It includes the connections between the landscape components which correspond to the core and systems model in CIM. It is a directory of the structural properties of an existing system landscape

The Landscape Description contains all properties to manage changes of the system landscape or its parts:

System topology (addresses and links)

Element structure (components) and version information

Views (administration, transport, technical, ...)

There is usually at least one System Landscape Directory per customer

System Landscape Directory (SLD) Documentation

Topic Source Link

System Landscape Directory

SDN http://www.sdn.sap.com/irj/sdn/nw-sld

SLD Planning Guide SDN http://www.sdn.sap.com/irj/sdn/nw-sld

How to: Exchange System Data between SMSY and SLD

Service Marketplace


→ Media Library → Technical Papers


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

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



16 August 2009

Automatic Data Capture for System Landscape

The System Landscape (transaction SMSY) can be built up automatically, using the transport management system (TMS) and/or the system landscape directory (SLD). Both scenarios get information from the managed systems and put it into the SAP Solution Manager.

SAP recommends using the SLD as data source, and a local SLD, for better usability. This local SLD can be updated from a central SLD over the SLD bridge. Systems can also be put in the solution directory manually.

SAP Solution Manager must be connected to a central SLD system, which is the central information source for the system landscape (see structure node: Register with Central SLD). But SAP Solution Manager should be independent of the central SLD system, to be available in the absence of SLD, so SAP Solution Manager needs a local SLD (see structure node: Use Local SLD). Do not use the local SLD as the central SLD. Automatic data capture can be configured in transaction SMSY_SETUP. You can automatically copy and regularly refresh the following data from SLD, into the SAP Solution Manager system landscape:

ABAP systems

System name and number, message server, clients, installed software components, release, patch level, instances and assigned servers, server data, databases, database servers

JAVA systems

Instances and assigned servers, server roles (types), installed software components, release, patch level

Notes for SLD

SAP Note Short Text

764393 Configuration of the SAP System Landscape Directory

2.7.4 Connect a Managed SAP System

You can connect managed systems to SAP Solution Manager either manually, in transaction SPRO → Basic Settings System Landscape, or in automatic basic settings configuration in transaction SOLMAN_SETUP. Details of the guided procedure in the automatic configuration for managed systems are given below. Prerequisites If you have a production SLD, maintain your system in this SLD, or maintain your system, server and database directly in the SAP Solution Manager system, in transaction SMSY. Procedure

Call transaction SOLMAN_SETUP

Choose view Managed Systems Configuration

Choose the technical system you want to connect. Start configuration by choosing Configure.

1. Connect managed system

a) To be able to enter data, choose Change. b) Enter the users with which you want to make the connection.

The users must have the same name and password in both systems, and at least authorization object S_RFCACL. See section RFC Connection: Trusted.


August 2009 17

c) To decide which RFC connections the system should create, select the RFCs. See section RFC Connections READ, TMW, and BACK for details. d) To start the creation of RFCs, choose Create RFC.

The system automatically:

Creates the selected RFC connections

Creates technical users. See sections on technical users

Activates Service Data Control Center (transaction SDCCN) in the managed system, adds the BACK destination, and defines the SAP Solution Manager system as master system.

2. Check Prerequisites Check all prerequisites and continue to the next step in the guided procedure. 3. Manual Configuration For all activities, read the IMG documentation, execute the steps manually, and set the status. Continue to the next step in the guided procedure. 4. Diagnostics Configuration If a managed system contains a Java stack, for all activities, read the IMG documentation, execute the step manually, and set the status. Continue to the next step in the guided procedure. 5. Wily Introscope Configuration If your managed system contains a Java stack, for all activities, read the IMG documentation, execute the step manually, and set the status. Continue to the next step in the guided procedure. 6. Create Logical Component Create a new logical component for your connected managed system. Result You have attached a new managed system. Check whether SAP EarlyWatch Alert Reports are created and executed by the SAP Solution Manager system. Caution Passwords for technical users are set by the system, automatically. If you encounter problems with RFC connections, check passwords and attached profiles. For profiles, see sections on technical users for infrastructure.

Connect a Managed SAP System

Topic Transaction Detailed Description

SAP Reference IMG SPRO Basic Settings System Landscape

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

Solution Manager System Landscape SMSY Manual Maintenace of system, server and database

2.7.5 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:


18 August 2009

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

a) Create a new logical component for your upgraded managed system. b) In SAP Solution Manager, go to transaction SOLUTION_MANAGER and 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

SOLUTION_MANAGER Adjust Upgrade of Managed System

Solution Directory SOLMAN_DIRECTORY Adjust Upgrade of Managed System

2.8 Solutions and Solution Directory

SAP Solution Manager has its own solution directory. You capture and manage the system landscape, centrally, in SAP Solution Manager, and use it in your implementation and template projects, in change management, Customizing synchronization (customizing scout, customizing distribution), and in operational processing (solution monitoring, services, service desk).

The solution directory is used to:

Create landscape components (server, databases, systems, system components)

Define non-SAP products for use in the system landscape maintenance

Read data automatically and save via ABAP main instances

Give an overview of system groups

Generate RFC destinations in component systems; RFC connection errors are logged

Capture data manually, e.g. servers, non-ABAP and planned systems

Display graphics o Landscape components (servers, databases, systems) o Assign attributes to landscape components

Analyze system landscape by components


August 2009 19

After all landscape components have been created, the solutions must be created in transaction SOLUTION_MANAGER. See the SAP Solution Manager - Solution Concept and Design document in the Service Marketplace, before defining the solution.

To change processes in the Solution Directory, it is recommended to use the Check-in/ Check-out functionality to document the changes in the Business Processes. For this you have assigned a maintenance project with project team members, to your solution, and selected the check-out function in the solution settings. Once the business scenarios or processes are checked out, they can no longer be changed in the Solution Directory.

Solution Concept and Design

Short Text Link

Solution Concept and Design http://service.sap.com/solutionmanager →

Media Library → Technical Papers

SAP Solution Manager: Solution for SAP Service Delivery

SAP Note 1117389

Check Business Processes In/Out http://help.sap.com/saphelp_sm40/helpdata/en

/44/35882eba154cc4e10000000a11466f/content.h

tm

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, 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

Best Practice SAP Solution Manager - Solution Lifecycle

https://service.sap.com/~sapidb/01100035870000

0306702009E/Solution_Lifecyle_v4.pdf



http://help.sap.com/saphelp_sm40/helpdata/en/44/35882eba154cc4e10000000a11466f/content.htm





https://service.sap.com/~sapidb/011000358700000306702009E/Solution_Lifecyle_v4.pdf

https://service.sap.com/~sapidb/011000358700000306702009E/Solution_Lifecyle_v4.pdf


20 August 2009

2.9 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 Service Delivery

1170668 The role of SAP Solution Manager in Remote Service Delivery

2.10 Multi-Tier Landscape for SAP Solution Manager The best way to use SAP Solution Manager is in a two-tier landscape. 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 only need to use a three-tier landscape with transport, 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.11 Sizing for SAP Solution Manager There is a new sizing tool-kit since SAP enhancement package 1 for SAP Solution Manager. 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.

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/diagnostics →

Sizing Toolkit

2.12 Related Documentation

Related Documentation

Topic Guide/Tool Quick Link on SAP Service Marketplace

(http://service.sap.com)

Detailed scenario SAP Solution Manager Instguides → SAP





http://service.sap.com/


August 2009 21

description Master Guide Components → SAP Solution Manager → Release 7.0 EHP 1

Support Package-specific configuration guide

SAP Solution Manager Configuration Guide

Instguides → SAP


SAP Solution Manager Update Guide

Update SAP Solution Manager 7.0 to SAP Solution Manager 7.0 EHP 1

Instguides → SAP


Wily Introscope Installation Guide

Wily Introscope 8.0 - Installation Guide

Diagnostics → Installation and

Configuration


22 August 2009

3 Monitoring SAP Solution Manager Monitoring is an essential SAP technology management task. This section is devoted to it.

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

including Enhancement Package 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver.

3.1 SAP EarlyWatch Alert for 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).

3.2 Alert Monitoring with CCMS

Proactive, automated monitoring is the basis for ensuring reliable operation of your SAP system environment. SAP provides the infrastructure and recommendations to set up alert monitoring to recognize critical situations for SAP Solution Manager, as quickly as possible.

3.2.1 CCMS Monitoring – SAP Solution Manager

You can activate CCMS monitoring for a solution (Transaction SOLUTION_MANAGER → <Select a specific Solution> → Solution Landscape → 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

To enable the CCMS auto-alert mechanism, see SAP Note 617547.

CCMS Monitoring

Topic Link

RZ20: Sending alerts as mail and SMS SAP Note 617547

3.2.2 RFC Connections

OSS connection is essential for collaboration scenarios, such as Service Desk and Delivery of SAP Service, so it is useful to monitor the RFC connections to the OSS with a separate CCMS monitor. The setup for CCMS monitoring of RFC connections is in the “Monitoring Availability of Services and Components” guide.








August 2009 23

RFC Connections

Topic Link

SAP Solution Manager https://www.sdn.sap.com/irj/sdn/operations

→ Knowledge Center → Monitoring Availability

3.2.3 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.2.4 Component-Specific Monitoring

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 (transaction SOLUTION_MANAGER → <Select a Solution> → Edit → Automatic E-Mail transmission).

3.3 Other Problem Analysis and Monitoring Tools

3.3.1 Application Monitoring

Several SAP Solution Manager components use the application log in transaction SLG1. These components are basic SAP Solution Manager functions, e.g. data transfer from SLD, but you must monitor the application log also for the components service desk and change request management, which use the CRM functionality of the SAP Solution Manager. The business process monitoring functionality also uses the application log as the central location for exception information.

Problem Analysis Tool

Component Monitor Detailed Description

SAP Solution Manager SLG1 Application Log

Service Desk SLG1 Application Log

Change Request Management SLG1 Application Log

Business Process Monitoring SLG1 Application Log

https://www.sdn.sap.com/irj/sdn/operations?rid=/webcontent/uuid/00251cd4-3fcb-2a10-de86-a81f0da3eb59


24 August 2009

3.3.2 Monitoring with Work Centers

Several administration and monitoring functions can also be accessed via the work centers in the SAP Solution Manager.

Administration and Monitoring with Work Centers

Work Center Detailed Description

SAP Solution Manager Administration

SAP Solution Manager administration functions

System Monitoring System Monitoring for all connected systems including connectivity monitoring

Root Cause Analysis Monitoring and administration of root cause analysis functions and the connected agents


August 2009 25

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 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver.

4.1 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.

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 http://help.sap.com → SAP NetWeaver → SAP NetWeaver 7.0 including

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

4.2 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 1 → <language> → SAP NetWeaver Library → 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:














26 August 2009

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:

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.

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.

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

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

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

4.3 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.


August 2009 27

ABAP Standard Jobs

Topic Link

ABAP Standard Jobs Transaction SM36 → Goto → Standard Jobs

4.3.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. There are two background processing frameworks (old and new) in SAP Solution Manager. Currently, both frameworks have to be used to schedule jobs in the SAP Solution Manager.

The old framework is based on the periodic job SM:SCHEDULER, which is automatically scheduled when the first solution landscape is created. SM:SCHEDULER schedules all programs in the table DSWPJOB, according to their configuration. The job log is in the overall log of job SM:SCHEDULER.

One important scheduled job is SM:EXEC SERVICES. This job performs services (such as EarlyWatch Alert) and schedules new services. You can set the time that this job is started, in the SAP Solution Manager global settings (in transaction DSWP). The default setting is 6 a.m.

All other jobs are configured by SAP (customizing) in the table DSWPJOB. The table is delivered with a suitable default setting and should not be changed.

Use SAP Solution Manager's own diagnosis function to find out the status of the background processing. If jobs terminate or are not executed, you will find the relevant information there. The table DSWPJOBSTATUS contains information about the last run of programs.

Note: For programs that require a lot of configuration (for example, customer-specific variants), you must use the basic infrastructure of your SAP system (transactions SM37 and SM36). Do not add your own programs.

In the new framework (see screenshot), the SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS. This program minimizes the administration required. These standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP).

Some SAP Solution Manager applications may require additional background jobs.


28 August 2009

Some of the most important jobs are:

Job name Program / Variant Period Description

SM:SCHEDULER RDSWPJOBSCHEDULER Triggers all other jobs in old job framework.

SM:EXEC SERVICES RDSMOPBACK_AUTOSESSIONS Carry out services (like SAP EarlyWatch Alert) and schedule new services.

LANDSCAPE FETCH RSGET_SMSY These periodic jobs update the solution directory with information from SLD or TMS.


August 2009 29

EFWK Resource Manager (01 Minute

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

E2E_HK_CONTROLLER E2E_HK_CONTROLLER This job is scheduled by the diagnostics managing system setup. It aggregates and cleans the BI for diagnostics.

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

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



30 August 2009

4.3.2 SAP Notes for SAP Solution Manager Background Jobs

SAP Notes for SAP Solution Manager Background Jobs

SAP Note Short Text

1154422 CCMS Downtimes: SAP_CCMS_MAPPING_SCHEDULER job aborts

16083 Standard jobs, reorganization jobs

931436 SLCA_LCK_SYNCHOWNERS standard job terminates

662441 Solution Manager: SAP Notes for Support Packages

1084173 CSA: Change of Background Job Scheduling

894279 Background processing in SAP Solution Manager

4.4 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 SP15.

4.4.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 are several root cause analysis 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

There is a detailed description of the user management in the root cause analysis scenario, in the Service Marketplace.










August 2009 31

Business Partners

Business partners must be defined for some scenarios (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.4.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.

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.




32 August 2009

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 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 Business Partners SPRO IMG activity Create Key User (technical name: SOLMAN_SUP_BUSPART)

4.4.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


August 2009 33

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

4.4.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 → Technical Papers

4.4.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.



34 August 2009

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. 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.4.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.


August 2009 35

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



36 August 2009

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://service.sap.com/ha

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

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

http://service.sap.com/ha






August 2009 37

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.0. 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

BI Extraction 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.





38 August 2009

Notes for Archiving

SAP Note Short Text

546685 Archiving in Solution Manager (Operation)

845433 Deleting a service process with support message

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.




August 2009 39

Archiving Projects

Topic Link

SAP Solution Manager Help

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

cProjects Archiving http://help.sap.com → SAP CProjects Suite → Editing Project

Structures → Collaboration Projects → Basic Functions → Archiving

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.





40 August 2009

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 1 → <language> → SAP

Library → SAP NetWeaver 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.

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

1006094 cProjects problems with archiving/resources/deletion

1077447 Solution Manager: TEST_DSMOPSERSESSN_DELETE

1091497 Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN

1092503 Archiving reporting documents in SAP Solution Manager

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/1b/e81c3b84e65e7be10000000a11402f/content.htm

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












August 2009 41

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.

7.1 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 can update your basic settings configuration by either:

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

Checking for new or changed IMG activities in the SAP Reference IMG.

7.1.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.

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




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

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


42 August 2009

7.1.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 903274 for details of new IMG activities, changed IMG activities, and deleted IMG activities up to SP17. For later support packages, see the release notes and SAP Note 1260646.

Using IMG – Manual Update Configuration

Short Text SAP Note

Changes to SAP Solution Manager 7.0 IMG after SP01 903274

Changes to SAP Solution Manager 7.0 IMG as of Enhancement Package 1

1260646

7.2 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 1172948. 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.0 EHP 1 (ST-400 Support Package 18 and 19). SAP Note 1334252 applies to ST-400 Support Package 20.

Ensure Basic Functions

Component Transaction Detailed Description

Basic Functions SNOTE Check SAP Note regularly

1172948 (SP 18 and 19), 1334252 (SP 20)

7.3 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










August 2009 43

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 4.0 Extension Add-Ons

1169247 Upgrading SAP Solution Manager 7.0 to 7.0 EHP 1

1244225 SAP Solution Manager: SAP Notes for support packages

1260646 Changes to SAP Solution Manager customizing (IMG) as of EHP 1

1276022 SAP Solution Manager 7.0 EHP 1 installation

1276263 Roles: SAP Solution Manager 7.0 as of EHP 1

1276895 Additional information on upgrading to SAP Solution Manager 7.0 EHP 1















44 August 2009

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 System Landscape Directory (SLD)

How can I ensure that SLD is working correctly in connection to SAP Solution Manager?

1) Call transaction SMSY on your SAP Solution Manager, and check that the system information is sent from your SLD to SMSY. Verify the data sources of your landscape components (Hosts, Databases, Systems, and System Components).

2) Call transaction SMSY_SETUP, and check that the “Automatic Data Transfer” comes from your SLD (usually local SLD, which is supplied by the central SLD in standard case).

Compare the last refresh dates in SMSY with the last data transfer date in SMSY_SETUP. Different dates could indicate that the landscape information is not correctly supplied by your SLD.







August 2009 45

8.3 SAP EarlyWatch Alert (EWA)

SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections. If there is a small red flag in the solution overview of transaction SOLUTION_MANAGER, something is wrong with the EWA data collection.

In this case, check in the solution, which system in the landscape is affected, and check the RFC connections and SDCC. For further information, see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”.

If the EWA is grey in the overview, there is also a problem.

For more information, see SAP Note 762696 “Grey rating for EarlyWatch Alert”.

8.4 CA Wily Introscope

How can I check that CA Wily Introscope Enterprise Manager is working correctly?

1) Connect to your CA Wily Introscope WebView (which is part of CA Wily Introscope Enterprise Manager, as of release 7.2.0.0) via web browser – usually 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) Go to operating system level and verify whether the Enterprise Manager system process is available

a. Windows: Check Services b. Unix: Check with command ps

How can I check that Wily Introscope Agent is working correctly?

1) Verify in SMD → Diagnostics Setup → Managed Systems → Introscope Agent for the system in which the Introscope Agent is running.

Note: 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.

2) Check that CA Wily Introscope Enterprise Manager receives information from CA Wily Introscope Agent.

8.5 Self-Diagnosis

An enhanced self-diagnosis tool has been delivered with SAP Solution Manager 7.0, Support Package 12. It should be used for troubleshooting, not regular 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



http://hostname:8081/webview/jsp/login.jsp


46 August 2009

diagnosis. A self-diagnostics module is available in SAP Solution Manager. You can analyze your 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 is in the transaction SOLUTION_MANAGER → Settings → Self-Diagnosis.

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

Ramp-up knowledge transfer http://service.sap.com/rkt-solman → Overview

and Setup of SAP Solution Manager


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


August 2009 47

9 Appendix

9.1 Related Guides

The master guide is a central starting point for the technical implementation of SAP enhancement package 1 for SAP Solution Manager 7.0, and its scenarios. The installation guide describes the installation of SAP enhancement package 1 on an existing SAP Solution Manager 7.0 system. 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/