Solution Operation Guide

SAP Solution Manager 7.0 EHP 1 Operation Guide

Document Version 1.04 - August 12, 2009

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20

© 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. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address:

SAP, R/3, mySAP,, 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.

Typographic Conventions
Type Style Example Text Represents 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 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icon Meaning Caution Example Note Recommendation Syntax


Example text

Example text

<Example text>


SAP Solution Manager Operation Guide

1 Getting Started....................................................................... 6
1.1 1.2 2.1 2.2 2.3
2.3.1 2.3.2 2.3.3

Global Definitions ...................................................................6 History of Changes .................................................................8 SAP Solution Manager ............................................................9 Software Components ............................................................9 Other Components ................................................................10
Internet Graphics Server (IGS) ................................................10 SAP NetWeaver Search and Classification (TREX) ...............11 CA Wily Introscope ..................................................................11

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

2.4 2.5 2.6 2.7
2.7.1 2.7.2 2.7.3 2.7.4 2.7.5

Installation .............................................................................11 Basic Configuration ..............................................................12 Root Cause Analysis ............................................................13 Managed Systems .................................................................13
System Landscapes .................................................................13 SAP Solution Manager and Trusted RFC ...............................14 System and Landscape Directory (SLD) ................................15 Connect a Managed SAP System ...........................................16 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 3.2
3.2.1 3.2.2 3.2.3 3.2.4

SAP EarlyWatch Alert for SAP Solution Manager .............22 Alert Monitoring with CCMS.................................................22
CCMS Monitoring – SAP Solution Manager ...........................22 RFC Connections .....................................................................22 CCMS Monitoring – Internet Graphics Server (IGS) ..............23 Component-Specific Monitoring .............................................23

3.3.1 3.3.2

Other Problem Analysis and Monitoring Tools ..................23
Application Monitoring ............................................................23 Monitoring with Work Centers ................................................24

4 Management of SAP Solution Manager ............................. 25
4.1 4.2 Starting and Stopping ...........................................................25 Backup and Restore .............................................................25


August 2009

................................3......................4 4.......... 47 August 2009 5 ...................1 7...........................................3 8...1...............3 4.............................................30 User Administration and Authentication .........45 Self-Diagnosis ........38 SAP Notes for Additional/Background Information .....1 4......4.....2 8................................................................................3 4..................32 Adapt Work Center Queries.........................37 SAP Solution Manager Extended Archiving Functionality38 Alternative Storage & Deletion Strategies ................................42 7 Software Change Management ................................ 36 6 Archiving & Data Deletion in SAP Solution Manager ...4.47 8 Troubleshooting ...........1 6...............44 System Landscape Directory (SLD) ..............5 9.........3 8................1 7....4 8...... 41 7....47 Related Information ..........................2 7...........................................33 Create End User Roles .........................6 User Management ....................45 CA Wily Introscope .2 6........41 Guided Procedure ..............1 4................42 Connection to SAP .........1 9...40 Configuration after Support Package Update ......34 5 High Availability...Automatic Update Configuration ...........4............................. 37 6.....................................1 8....2 4.....33 Assign Roles to Users ..1...........4 4.4......................................4..............................4 7.................................44 SAP EarlyWatch Alert (EWA) .........2 Achiving functionality in core SAP Solution Manager ..... 44 9 Appendix ............2 Periodic Tasks .........27 SAP Notes for SAP Solution Manager Background Jobs .............................2 Ensure Basic Functions via SAP Note ...........30 Create Users and Business Partners for End Users ................31 Update Authorizations after Support Package Upgrade ........................26 Background processing in the SAP Solution Manager........................................3.............................................4........................................30 4................42 Support Packages and Patch Implementation .5 4..41 SAP Reference IMG – Manual Update Configuration ........................3 6....................SAP Solution Manager Operation Guide 4...................................45 Related Guides ....................

SAP Solution Manager Operation Guide 1 Getting Started This guide does not replace the daily operations handbook that we recommend customers create for their production operations. such as the Master Guide. and lists the tools that you can use to perform them. Check regularly for updates of the Application Operations Guide. SAP SCM. a business scenario is a cycle which comprises several interconnected logical processes in time. Component A component is the smallest individual unit considered within the Solution Development Lifecycle. SAP PLM. or SAP SCM. Business Scenario From a micro-economic perspective. SAP SRM. It contains information about various tasks. SAP CRM. delivered.1 Global Definitions SAP Application An SAP application is an SAP software solution that serves a business area such as SAP ERP. a business scenario needs at least one SAP application (SAP ERP. Technical Infrastructure Guide. has never been more vital to your business success than today. a business scenario includes several company departments and business partners. 6 August 2009 . and reflects the customer‟s prospective course of business. This guide is the starting point for managing your SAP applications and maintaining and running them optimally. installed and maintained separately. Technically. implementing. so you will sometimes also need other guides. components are produced. and SAP Library. Target Groups      Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist 1. or other) for each cycle. About this Guide Designing. Typically. A business scenario is an entity which can be implemented separately. and running your SAP applications at peak performance. It also provides references to the documentation required for these tasks. and possibly other third-party systems. 24 hours a day.

SAP Solution Manager Operation Guide Important SAP Notes SAP Note Number 394616 1145779 Title Release strategy for SAP Solution Manager SAP Solution Manager 7.0 Installation SAP Solution Manager .basic function Comment You are planning to install and upgrade SAP Solution Manager Additional information and problems discovered after the publication of the installation guide This note is valid as of ST-400 Support Package 18. 1172948 1244225 Solution Manager 7. You are about to update your SAP Solution Manager system to SAP Solution Manager 7. Implement the note to ensure the basic functions in SAP Solution Manager.0 EHP 1. or want to import a support package stack for this product version.0 EHP 1: recommended SAP Note August 2009 7 .

00 1.4.1 Include several chapters for Configuration after Support Package Update and structural changes Transaction SOLUTION_MIGRATION deleted.8 and 4. The current version of the Application Operations Guide is on SAP Service Marketplace at http://service.02 1. Document Versions Document Version 1.01 EHP 1.2 History of Changes Make sure you use the current version of the Application Operations Guide.2 8 August 2009 .SAP Solution Manager Operation Guide 1.Solution Lifecycle added Add information about Business Process Check In/Out into chapter 2. The following table provides an overview of the most important changes in previous versions. Link to Best Practice SAP Solution Manager .03 1.04 Important Changes First version of the SAP Solution Manager Operations Guide Include handling of SAP Note 1172948 into chapter → SAP Components → SAP Solution Manager → Release 7.

Other software components can be added to SAP Solution Manager.2 Software Components The SAP Solution Manager comprises several software Another central place for useful information about the supported functions is the Ramp-Up Knowledge Transfer page. so the tasks and procedures for a standard SAP NetWeaver system generally also apply to SAP Solution Manager. It is based on an SAP NetWeaver platform and includes the SAP CRM add-on. Usage Type SAP Solution Manager Software component SAP_BASIS SAP_ABA CRMUIF SAP_BW BI_CONT SAP_AP ST ST-A/PI ST-SER ST-PI ST-ICO BBPCRM CPRXRPM PI_BASIS Description SAP Basis Component Cross-Application Component CRMUIF for Solution Manager SAP NetWeaver BI Business Intelligence Content SAP Application Platform Solution Manager Tool Application Service Tools Solution Manager Service Tools Solution Tools Plug-In Solution Manager Implementation Content BBP/CRM cProjects and others PI_BASIS August 2009 9 .sap. More information can be found in the SAP Service Marketplace or the SAP Help Portal. This guide refers mostly to SAP Solution Manager-specific tasks and procedures. It includes several applications and scenarios to support your IT and application management.SAP Solution Manager Operation Guide 2 http://service.1 Technical System Landscape SAP Solution Manager SAP Solution Manager is the central tool for managing your customer solution landscape. depending on the business scenarios used. depending on the scenarios you actually use. Cental Information Sources Topic SAP Solution Manager Ramp-Up Knowledge Transfer SAP Help Portal Link → SAP Solution Manager 2. You can use the following software components in your http://help. → SAP Solution Manager Extensions → Adapter for SAP Quality Center by HP.g.1 Internet Graphics Server (IGS) The Internet Graphics Server (IGS) generates various graphics or charts in some areas. e. The server can be administrated in transaction SIGS. SAP Note 1131270 SAP Note 1034902 SAP Central Process Scheduling by Redwood SAP Productivity Pak by RWD BMC Appsight for Client Diagnostics 2. in EarlyWatch Alert reports.3 Other Components 2.SCA Root Cause Analysis CA Wily Introscope agent Aditional Software Appsight Blackbox and Console Introscope Enterprise Manager BMC AppSight CA Wily Introscope Third-Party Integration There are several standard interfaces to third-party tools: Additional Software Tool SAP Quality Center by HP Link → SAP Solution Manager Extensions → Process Scheduling adapter for SAP Solution Manager.3. Administration of IGS Topic Internet Graphics Server (IGS) Transaction SICS Link http://<IGS host>:<IGS port> Notes for IGS 10 August 2009 .SAP Solution Manager Operation Guide Usage Type Additional Adapers ST-PSM ST-QCA ST-SPA SAP process scheduling adapter SAP Adapter for SAP Quality Center by HP SAP Produktivity Pak Usage Type Java Application Server LMSERVICE ISAGENTSMD<REL>. You can administrate your Web Dynpro Java IGS via a Web https://service.

sap. and are not yet on Unicode.3 CA Wily Introscope CA Wily Introscope is a software component for the root cause analysis scenario and SAP EarlyWatch Alert for Java. SAP Note 797147 includes a detailed FAQ document as an attachment. For customers that have upgraded from previous releases of SAP Solution Manager 7.0 → <language> → Appendix → TREX Admin Tool in the SAP System (TREXADMIN). Administration of TREX Topic SAP Netweaver Search and Classification Administration of TREX TREXADMIN Transaction Link 2.4 Installation SAP recommends running SAP Solution Manager on → Installation and Configuration. If this August 2009 11 .com → SAP NetWeaver → SAP NetWeaver 7. SAP recommends migrating to Unicode. see the installation guide on SAP Service Marketplace at http://service.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) http://help.SAP Solution Manager Operation Guide SAP Note 965201 995471 514841 Short Text IGS HTTP administration commands IGS administration via ABAP Troubleshooting when a problem occurs with the IGS 2. This document also includes a detailed troubleshooting section. For information about installation. Wily Introscope Topic Wily Introscope Link http://service. All new SAP Solution Manager installations are on Unicode. It collects performance and other system-related data of non-ABAP components in your system SAP NetWeaver Search and Classification (TREX) The SAP NetWeaver Search and Classification (TREX) is used for the Solution Database in the Service Desk Notes for Wily Introscope SAP Note 797147 1273028 Short Text Wily Introscope Installation for SAP Customers Introscope 8 Release Notes → SAP NetWeaver → SAP NetWeaver Enterprise Search 7.

You can initially configure your basic settings with the basic settings wizards. see the Customizing for SAP Solution Manager (transaction SPRO) and the configuration guide on SAP Service Marketplace at All settings for this Web Dynpro application are made during the installation of SAP Solution Manager.SAP Solution Manager Operation Guide is not possible. until the customer has completed the Unicode conversion. with SAP enhancement packages (EHPs).sap.0). SAP Solution Manager Installation Topic SAP Solution Manager Installation Unicode Update Guide SAP Solution Manager Link http://service. All activities in this wizard are linked to the corresponding Customizing activities in the standard basic settings configuration. This quickly configures all main settings in a guided procedure. 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 → SAP Components → SAP Solution Manager → Release 7. 12 August 2009 .com/unicode in the SAP Reference IMG (transaction SPRO). the basic configuration should be performed.0. The automatic configuration is accessed via a Web Dynpro application which is called by transaction SOLMAN_SETUP. You can implement functional updates without upgrading your SAP system to a higher release. For further information see the Update Guide SAP Solution Manager EHP 1. This concept is introduced for SAP NetWeaver with SAP EHP 1 for SAP NetWeaver 2. 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 EHP 1. SAP will support the SAP Solution Manager on http://service.5 Basic Configuration After installing the SAP Solution Manager.

in the SAP Service Marketplace.0 EHP 1. Misuse of the communication connection must be prevented.7.0 EHP 1 2. August 2009 13 . so it must be able to access the backend All the systems which are connected to the SAP Solution Manager are called managed systems. For logical component definition.7 Managed Systems To ensure that all the systems can be managed centrally. The definition of system groups and logical components is based on this.1 System Landscapes The managed systems must be included in the system landscape (transaction SMSY). the SAP Solution Manager should be connected to all systems in the system landscape. The configuration of managed systems for the basic scenarios is in the guided procedure (transaction SOLMAN_SETUP).SAP Solution Manager Operation Guide Basic Configuration Topic SAP Solution Manager Configuration SAP Reference IMG Configuration Guide Transaction / Link SOLMAN_SETUP SPRO http://service. The SAP Solution Manager is the central location for the management and setup of the connected managed 2. delivered with SAP Solution Manager 7. see the logical component concept guide. In SAP Solution Manager this is usually ensured by using a trusted RFC with the same user. 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. Root Cause Analysis Topic End-to-End Diagnostics SP18 Root Cause Analysis Note / Link SAP Note 1238197 → SAP Components → SAP Solution Manager → Release 7. The users should only have the authorizations which are assigned to them in the managed systems.6 Root Cause Analysis You need information about the basic requirements and possible limitations of end-to-end root cause analysis. The configuration of root cause analysis is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP).sap.

if the user management for the SAP Solution Manager is as restrictive as for all other productive systems. Trusted relations between systems can be configured on different levels: 1) Trusted relationships from a system. d) An RFC server system accepts the trusted RFC token und logs the user in to the target → Media Library → Technical Papers 2. This can be done using transaction SOLMAN_SETUP. in the client system. finds the user and logs it in with user ID.SAP Solution Manager Operation Guide Logical Component Concept Topic Logical Component Concept Link http://service. 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. In case 1b). In particular. This kind of trusted relationship is usually realized by putting the login data of a service user of the server system. and logs its user in.2 SAP Solution Manager and Trusted RFC The trusted RFC connections are setup between the SAP Solution Manager and the connected managed systems. which offers services to another system (client). and logs on the user in the target system. the login data of a service user is entered in the RFC connection.7. 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. c) An SAP system accepts an SSL client certificate in an https connection. The trusted RFC can be used for 1b) and 2d). the creation of new users and the resetting of passwords must be strictly controlled. within these services. 14 August 2009 . 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. 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). where the login token is with the same user ID as in the source system. as in a normal RFC destination. b) An SAP backend system accepts the SAP Logon Ticket of the SAP NetWeaver Portal. The naming conventions for users must be consistent across systems. it is also possible to restrict which users (authorization field RFC_USER) in the RFC client system can use the connection. Through the authorizations of the service user for the authorization object S_RFCACL. Examples: a) A Windows client accepts a Kerberos ticket of a Windows domain server. with which applications (authorization field RFC_TCODE). 2) Trusted relationships between systems where one system accepts the authentication of the other system.

transport. A directory of information about all installable software available from SAP. technical. The SAP NetWeaver system landscape directory is the central directory of system landscape information for the management of your software life-cycle. The users who want to use such a trusted RFC connection. with the authorization field RFC_EQUSER set to “Y” and the field RFC_USER empty or set to the dummy value „ (inverted comma).sdn.3 System and Landscape Directory (SLD) The System Landscape Directory is the central information repository for your system landscape. 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.  The RFC server system accepts the authorization by the RFC client Note for Trusted RFC SAP Note 128447 Short Text Trusted/Trusting Systems   Solution Manager Operation Guide In case 2d). RFC connections between SAP systems can also be secured by “secure network communication” (SNC). must have authorization for the authorization object S_RFCACL. and the authorizations in the RFC client system can be limited by the authorization object S_ICF. A user has his personal authorizations in the SAP Solution Manager system as well as in the connected managed systems. The trusted RFC connection has the following security attributes: Simple navigation (via Single Sign-On) from RFC client to RFC server.sdn. to restrict user access rights to RFC connections. and automatically updated data about systems already installed in a landscape. but the option “same user“ is selected. helps you plan tool support for software life-cycle tasks in your system → Media Library → Technical Papers August 2009 15 . . The Landscape Description provides a precise picture of a customer system landscape.) There is usually at least one System Landscape Directory per customer System Landscape Directory (SLD) Documentation Topic System Landscape Directory SLD Planning Guide How to: Exchange System Data between SMSY and SLD Source SDN SDN Service Marketplace Link http://www. It includes the connections between the landscape components which correspond to the core and systems model in http://www.. no login data is provided in the RFC destination.

into the SAP Solution Manager system landscape: ABAP systems  System name and number. 1. See section RFC Connection: Trusted. Details of the guided procedure in the automatic configuration for managed systems are given below. SAP Solution Manager must be connected to a central SLD system. installed software components. Procedure  Call transaction SOLMAN_SETUP  Choose view Managed Systems Configuration  Choose the technical system you want to connect. Systems can also be put in the solution directory manually. But SAP Solution Manager should be independent of the central SLD system.4 Connect a Managed SAP System You can connect managed systems to SAP Solution Manager either manually. to be available in the absence of SLD. in transaction SMSY. choose Change. databases. clients. release. The users must have the same name and password in both systems. b) Enter the users with which you want to make the connection. You can automatically copy and regularly refresh the following data from SLD. server and database directly in the SAP Solution Manager system. Automatic data capture can be configured in transaction SMSY_SETUP. Do not use the local SLD as the central SLD. instances and assigned servers. in transaction SPRO → Basic Settings System Landscape. or maintain your system. patch level Notes for SLD SAP Note 764393 Short Text Configuration of the SAP System Landscape Directory 2. maintain your system in this SLD. which is the central information source for the system landscape (see structure node: Register with Central SLD). server roles (types). and at least authorization object S_RFCACL. patch level. or in automatic basic settings configuration in transaction SOLMAN_SETUP.SAP Solution Manager Operation Guide Automatic Data Capture for System Landscape The System Landscape (transaction SMSY) can be built up automatically. and a local SLD. Connect managed system a) To be able to enter data. This local SLD can be updated from a central SLD over the SLD bridge.7. using the transport management system (TMS) and/or the system landscape directory (SLD). 16 August 2009 . database servers JAVA systems  Instances and assigned servers. Both scenarios get information from the managed systems and put it into the SAP Solution Manager. installed software components. message server. Prerequisites If you have a production SLD. Start configuration by choosing Configure. so SAP Solution Manager needs a local SLD (see structure node: Use Local SLD). for better usability. release. server data. SAP recommends using the SLD as data source.

See section RFC Connections READ. Check Prerequisites Check all prerequisites and continue to the next step in the guided procedure. automatically. Manual Configuration For all activities. Wily Introscope Configuration If your managed system contains a Java stack. and defines the SAP Solution Manager system as master system.SAP Solution Manager Operation Guide c) To decide which RFC connections the system should create. server and database 2. and BACK for details. Diagnostics Configuration If a managed system contains a Java stack. Create Logical Component Create a new logical component for your connected managed system. This section explains how to adjust your settings for this system in the SAP Solution Manager. execute the steps manually. For profiles. select the RFCs. read the IMG documentation. Check whether SAP EarlyWatch Alert Reports are created and executed by the SAP Solution Manager system. and set the status.5 Adjust Upgrade of Managed System You have upgraded a managed system. execute the step manually. TMW. Continue to the next step in the guided procedure. execute the step manually. Continue to the next step in the guided procedure. read the IMG documentation. and set the status. Caution Passwords for technical users are set by the system. for all activities. choose Create RFC. Result You have attached a new managed system. If you encounter problems with RFC connections. 5. d) To start the creation of RFCs. 4. 6. see sections on technical users for infrastructure. for all activities. Prerequisites You have: August 2009 17 . 3. read the IMG documentation. adds the BACK destination. 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. Continue to the next step in the guided procedure. and set the status.7. 2. Connect a Managed SAP System Topic SAP Reference IMG Connect a Managed SAP System Solution Manager System Landscape Transaction SPRO SOLMAN_SETUP SMSY Detailed Description Basic Settings System Landscape Automatic Guided Procedure for Managed System Configuration Manual Maintenace of system. check passwords and attached profiles.

deactivate the business process monitoring sessions for it. In an implementation project. databases. servers. Adjust Product Version a) To adjust the new product version for your upgraded managed system. in SAP Solution Manager. Customizing synchronization (customizing scout.SAP Solution Manager Operation Guide   SAP Solution Manager projects and solutions in productive use SLD attached to SAP Solution Manager Procedure 1. RFC connection errors are logged Capture data manually. go to transaction SOLUTION_MANAGER and deactivate any solutions that contain the managed system. and use it in your implementation and template projects. If you monitor business processes in this system. 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. You capture and manage the system landscape. and choose Installed Product Version. systems) o Assign attributes to landscape components Analyze system landscape by components 18 August 2009 . d) Activate your business process monitoring session and solutions again. in change management. b) Go to Header Data tab. 2. c) Go to transaction SOLMAN_DIRECTORY and your solutions. Adjust Upgrade of Managed System Topic Solutions in SAP Solution Manager Solution Directory Transaction SOLUTION_MANAGER SOLMAN_DIRECTORY Detailed Description Adjust Upgrade of Managed System Adjust Upgrade of Managed System 2. The solution directory is used to:         Create landscape components (server. and replace your outdated logical component with your new logical component. In the dialog box. you may want to leave the outdated logical component in your project. service desk). services. for documentation purposes. customizing distribution). go to transaction SMSY and choose your system. databases. Adjust Logical Component a) Create a new logical component for your upgraded managed system.g. c) Save. centrally. non-ABAP and planned systems Display graphics o Landscape components (servers. systems. e.8 Solutions and Solution Directory SAP Solution Manager has its own solution directory. and in operational processing (solution monitoring. choose the product version you have upgraded to. b) In SAP Solution Manager.

to it. Create a target solution in your target SAP Solution Manager. before defining the solution. This process has two steps: 1) Transfer systems and logical components from source to target. it is recommended to use the Check-in/ Check-out functionality to document the changes in the Business Processes. b. service To change processes in the Solution 0306702009E/Solution_Lifecyle_v4. the solutions must be created in transaction SOLUTION_MANAGER. you need to transfer some information from the previous SAP Solution Manager. Additional steps are: a. You can do this with the transaction SOLUTION_TRANSFER. Solution Transfer Short Text Export Solution Link /44/35882eba154cc4e10000000a11466f/content. to your solution. and assign them to a target solution. See the SAP Solution Manager .com → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Import Solution Solution Manager Operation Guide After all landscape components have been created. as well as business process monitoring configuration data and all data in the service → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Export Solution http://help. Once the business scenarios or processes are checked out. such as issues.h tm Solution Transfer When a new SAP Solution Manager is installed. business processes etc. For this you have assigned a maintenance project with project team members. This is SMSY data and it is usually transferred from TMS or SLD into SMSY. landscape info.Solution Concept and Design document in the Service → Media Library → Technical Papers SAP Note 1117389 http://help. so there is no need to transfer it 2) Transfer the data from your source solution. and selected the check-out function in the solution settings. they can no longer be changed in the Solution Directory. Create logical components there. Solution Concept and Design Short Text Solution Concept and Design SAP Solution Manager: Solution for SAP Service Delivery Check Business Processes In/Out Link http://service. Business processes are transfered.pdf Import Solution Best Practice SAP Solution Manager .Solution Lifecycle August 2009 19 .sap.

9 Service Delivery in SAP Solution Manager The SAP Solution Manager is the SAP service delivery platform. as well as services which are delivered by You only need to use a three-tier landscape with transport.  Determines the corresponding SAP Solution Manager cluster configuration. if you perform classic customizing or own developments in SAP Solution Manager. Notes for Service Delivery SAP Note 91488 1172939 1170668 Short Text SAP Support Services . such as EarlyWatch. patches or configuration scenarios on a test system first.11 Sizing for SAP Solution Manager There is a new sizing tool-kit since SAP enhancement package 1 for SAP Solution Manager. All services are solution-specific and can be used for all systems in the solution.10 Multi-Tier Landscape for SAP Solution Manager The best way to use SAP Solution Manager is in a two-tier landscape. Sizing for SAP Solution Manager Topic SAP Solution Manager Sizing Tool-Kit Link http://service. This includes self-services. etc. If the test is successful. GoingLive.Central preparatory note Technical Prerequisites for Service Delivery The role of SAP Solution Manager in Remote Service Delivery Test new Support Packages. cookbook. A transport between two SAP Solution Managers is not usually necessary. It contains components (guides. which can be performed by the customer. and spreadsheet) to run a sizing project for SAP Solution Manager.12 Related Documentation Related Documentation Topic Guide/Tool Quick Link on SAP Service Marketplace (http://service. 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 Instguides → SAP Detailed scenario SAP Solution Manager 20 August 2009 .  Configures SAP Solution Manager and Wily IS EM to obtain better performance and scalability. The usual scenarios for this case are change request management and/or service desk. 2. the changes can be installed in the productive SAP Solution Manager.SAP Solution Manager Operation Guide 2. This tool-kit:  Finds hardware resources needed to implement SAP Solution Manager for a given → Sizing Toolkit 2.

0 EHP 1 Diagnostics → Installation and Configuration August 2009 21 .0 EHP 1 Instguides → SAP Components → SAP Solution Manager → Release 7.0 EHP 1 Wily Introscope 8.SAP Solution Manager Operation Guide description Support Package-specific configuration guide SAP Solution Manager Update Guide Wily Introscope Installation Guide Master Guide SAP Solution Manager Configuration Guide Update SAP Solution Manager 7.0 EHP 1 Instguides → SAP Components → SAP Solution Manager → Release 7.0 to SAP Solution Manager 7.0 Installation Guide Components → SAP Solution Manager → Release 7.

sap. to have access to all important information from a central location. 3.2. such as Service Desk and Delivery of SAP Service.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).SAP Solution Manager Operation Guide 3 Monitoring SAP Solution Manager Monitoring is an essential SAP technology management task. automated monitoring is the basis for ensuring reliable operation of your SAP system environment. in SAP Solution Manager. You can activate and deactivate CCMS monitoring for specified solutions. see SAP Note 617547. 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. 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). For more information see http://help. you will get monitoring objects in transaction RZ20 under the monitoring tree element (MTE) “SOLMAN”.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. so it is useful to monitor the RFC connections to the OSS with a separate CCMS monitor. SAP recommends that all customers perform centralized system monitoring of all connected managed systems. 3. 3. CCMS Monitoring Topic RZ20: Sending alerts as mail and SMS Link SAP Note 617547 3.2 RFC Connections OSS connection is essential for collaboration scenarios. Under this MTE there is another one for each active solution. The setup for CCMS monitoring of RFC connections is in the “Monitoring Availability of Services and Components” guide. as quickly as possible. If monitoring is active. 22 August 2009 .2 Alert Monitoring with CCMS → SAP NetWeaver → SAP NetWeaver 7. SAP provides the infrastructure and recommendations to set up alert monitoring to recognize critical situations for SAP Solution Manager.2. This section is devoted to it.0 including Enhancement Package 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver.

select the RFC destination and choose Environment → Switch on CCMS.3. which use the CRM functionality of the SAP Solution → Knowledge Center → Monitoring Availability 3. to monitor the content of the SAP EarlyWatch Alert. but you must monitor the application log also for the components service desk and change request management. Problem Analysis Tool Component SAP Solution Manager Monitor SLG1 Detailed Description Application Log Service Desk Change Request Management Business Process Monitoring SLG1 SLG1 SLG1 Application Log Application Log Application Log August 2009 23 .1 Application Monitoring Several SAP Solution Manager components use the application log in transaction SLG1.4 Component-Specific Monitoring You can receive a regular E-Mail with the reports for specific systems or solutions. The business process monitoring functionality also uses the application log as the central location for exception information. SAP EarlyWatch Alert for Solutions and Service Level Reports (transaction SOLUTION_MANAGER → <Select a Solution> → Edit → Automatic E-Mail transmission). You will get a separate node in transaction RZ20 for “IGS availability”.sap. 3. e. data transfer from SLD.sdn.3 Other Problem Analysis and Monitoring Tools 3.SAP Solution Manager Operation Guide RFC Connections Topic SAP Solution Manager Link https://www. which tells you if the Internet Graphics Server is available. These components are basic SAP Solution Manager functions.2.3 CCMS Monitoring – Internet Graphics Server (IGS) Call transaction SIGS.g. 3.2.

3.2 Monitoring with Work Centers Several administration and monitoring functions can also be accessed via the work centers in the SAP Solution Manager.SAP Solution Manager Operation Guide 3. Administration and Monitoring with Work Centers Work Center SAP Solution Manager Administration System Monitoring Root Cause Analysis Detailed Description SAP Solution Manager administration functions System Monitoring for all connected systems including connectivity monitoring Monitoring and administration of root cause analysis functions and the connected agents 24 August 2009 .

the System Administration work center in SAP Solution Manager. using the SAP Management Console for all platforms (as of SAP NetWeaver 7. The main issues in a backup and recovery process are: August 2009 25 .  Backup your database every day You must backup the log files several times a day. The backup and restore strategy must cover disaster recovery processes. For more information. You must ensure that backup devices are not lost along with normal data storage (separation of storage locations). and perform technical administration and operation tasks.SAP Solution Manager Operation Guide 4 Management of SAP Solution Manager SAP provides an infrastructure to help technical support consultants and system administrators manage all SAP → SAP NetWeaver → SAP NetWeaver 7. → SAP NetWeaver → SAP NetWeaver 7. 4.  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. it is possible to restore a crashed database to any point in time before the crash. There are different processes. In the simplest case. all general recommendations for an SAP NetWeaver backup and restore strategy → SAP NetWeaver → SAP NetWeaver 7.0). the application server and the processes of which the system consists. or the Microsoft Management Console under Windows. you may also need to backup external components and handle cross-system data dependencies. an SAP System consists of only a database and a single application server. see SAP Help Portal at:  http://help. You can start and stop systems and instances centrally. 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.2 Backup and Restore As the SAP Solution Manager is based on SAP NetWeaver.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. With regular full backups of your database (either offline or online). depending on the SAP system and operating system platform. Depending on the processes you are running on the SAP Solution Manager. For more information see http://help. The backup and restore strategy for your system landscape should be embedded in overall business requirements and incorporate your company‟s entire process flow. see including Enhancement Package 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → Database Administration → <Database Name>. not only SAP systems. as well as a complete set of transaction logs since the last backup. For such as the loss of a data center through fire.1 Starting and Stopping When you start the SAP System.0 including Enhancement Package 1 → <language> → SAP NetWeaver Library → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver. you start the system database.

. without taking the systems offline. This concept must account for both the business data. The mapping is in the chapter scenario/component matrix above. In the standard setup. if you want to backup this component. Other tasks may be relevant for certain business scenarios only. However.3 Periodic Tasks This chapter describes all automic tasks which run periodically to keep the application running over time. this data is transferred once an hour to the BI of the SAP Solution Manager. 26 August 2009 . 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.SAP Solution Manager Operation Guide  You must develop a backup concept in the implementation phase./data‟ contains all agent data The directory „. A backup process must ensure logical and physical consistency.  Backup Introscope Enterprise Manager The Introscope Enterprise Manager is temporary storage for workload-related data. You should also schedule the standard basis jobs in transaction SM36 in the SAP Solution Manager. Such tasks may be required on component level and are relevant in each scenario that uses the component. such as changes to the configuration. software. 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. 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. Consistency Technology allows you to create a consistent image (or consistent copy) of a federated system landscape. and the runtime infrastructure. You must monitor the performance of these tasks regularly. or replacement of components made to the system landscape. 4. software upgrade of individual components. You need to back up individual components regularly. to ensure that you can restore and recover them if there is a system failure. This depends on the frequency of such changes. which is contained in databases./traces‟ contains all Wily trace data. You should not use a backup and recovery concept for your entire system landscape and single system components just for SAP systems.. its directories have to be backed up regularly:   The directory „. so a separate backup of this component is usually not needed.

SM:SCHEDULER schedules all programs in the table DSWPJOB. you must use the basic infrastructure of your SAP system (transactions SM37 and SM36). The table DSWPJOBSTATUS contains information about the last run of programs. The default setting is 6 a. August 2009 27 . You can set the time that this job is started. These standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP). The job log is in the overall log of job SM:SCHEDULER.1 Background processing in the SAP Solution Manager The background processing in SAP Solution Manager does not require regular administration. If jobs terminate or are not executed. Note: For programs that require a lot of configuration (for example.m. Some SAP Solution Manager applications may require additional background jobs. This job performs services (such as EarlyWatch Alert) and schedules new services. Do not add your own programs. Use SAP Solution Manager's own diagnosis function to find out the status of the background processing.    In the new framework (see screenshot). This program minimizes the administration required. All other jobs are configured by SAP (customizing) in the table DSWPJOB. according to their configuration.SAP Solution Manager Operation Guide ABAP Standard Jobs Topic ABAP Standard Jobs Link Transaction SM36 → Goto → Standard Jobs 4. Currently. The administrator just has to ensure that no jobs are aborted.3. customer-specific variants). The old framework is based on the periodic job SM:SCHEDULER. The table is delivered with a suitable default setting and should not be changed.  One important scheduled job is SM:EXEC SERVICES. in the SAP Solution Manager global settings (in transaction DSWP). the SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS. There are two background processing frameworks (old and new) in SAP Solution Manager. both frameworks have to be used to schedule jobs in the SAP Solution Manager. you will find the relevant information there. which is automatically scheduled when the first solution landscape is created.

Carry out services (like SAP EarlyWatch Alert) and schedule new services. SM:EXEC SERVICES RDSMOPBACK_AUTOSESSIONS LANDSCAPE FETCH RSGET_SMSY 28 August 2009 .SAP Solution Manager Operation Guide Some of the most important jobs are: Job name SM:SCHEDULER Program / Variant RDSWPJOBSCHEDULER Period Description Triggers all other jobs in old job framework. These periodic jobs update the solution directory with information from SLD or TMS.

it transfers from your system into the SAP global support backbone August 2009 29 . It aggregates and cleans the BI for diagnostics. Scenario-specific scheduled periodic tasks Required for scenarios Partner Service Desk Program Name/Task RNOTIFUPDATE07 Recommended Frequency every 15 minutes Detailed Description Activates regular data exchange between your system and the SAP global support backbone. Conversely. and a detailed list and short description of the jobs. and starts the extractors in the extractor framework. see SAP Note 894279. This job is scheduled by the diagnostics managing system setup. and forwards them to your SAP Solution Manager. E2E_HK_CONTROLLER E2E_HK_CONTROLLER For more information on background processing in SAP Solution Manager.SAP Solution Manager Operation Guide EFWK Resource Manager (01 Minute E2E_EFWK_RESOURCE_MGR This job is scheduled by the diagnostics managed system setup. It checks if there are new messages for your support team in the SAP global support backbone.

manually. in the managed systems and SAP Solution Manager. especially authorization administration Tool for administration of portal users and roles Tool for administration of J2EE users and roles There is a detailed description of the user management in the root cause analysis scenario. you must authorize the RFC connection user used. You can use the generated users with the setup.3. Work centers. If this connection is not available. Some applications expect named RFC connections. have been available since SP15. so users can only be separated by an authorization concept.1 User Administration and Authentication A lot of RFC read connections are used in SAP Solution Manager. User Management Setup/Tools Tool SAP User Management Engine for ABAP Engine (transaction SU01) Profile Generator (transaction PFCG) SAP User Management Engine (UME) Administration Platform SAP J2EE Engine user management using the Visual Administrator Usage Central User Administration (CUA) for SAP WebAS Tool for Web AS role administration.4.SAP Solution Manager Operation Guide 4.4 User Management User Management is very important in SAP Solution Manager. SAP Solution Manager is a singleclient system. which separate functions between different users. 4. It is important that the users used are not prevented from getting information from the managed systems or sending data to SAP Solution Manager. 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. If managed systems are in a central user administration. in the Service Marketplace. this user must be defined previously in the CUA system. 30 August 2009 . reorganization jobs SLCA_LCK_SYNCHOWNERS standard job terminates Solution Manager: SAP Notes for Support Packages CSA: Change of Background Job Scheduling Background processing in SAP Solution Manager 4. The SAP Solution Manager security guide contains a comprehensive description of users and authorization.2 SAP Notes for SAP Solution Manager Background Jobs SAP Notes for SAP Solution Manager Background Jobs SAP Note 1154422 16083 931436 662441 1084173 894279 Short Text CCMS Downtimes: SAP_CCMS_MAPPING_SCHEDULER job aborts Standard jobs. The RFC wizard generates the RFC connections and users automatically.

com/diagnostics 4. August 2009 31 .  Root Cause Analyses: user SAPSUPPORT is automatically created in the SAP Solution Manager system as well as the managed systems. Change Request Management). 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 http://service. Functions Requiring Business Partners Based on Users in SAP Solution Manager  Delivery of SAP Services: if you use Issue Management.  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.  Enter the required data and during Root Cause Analysis configuration.  Enter your user and choose change. and why. Test Management uses Trusted RFC connections.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.  Change Request Management: if the users in the Change Request Management process log on to the managed systems via SAP Solution Manager. which always require users in both Implementation and Customizing Distribution use Trusted RFC connections.SAP Solution Manager Operation Guide Business Partners Business partners must be defined for some scenarios (Service Desk. which always require users in both systems.  Service Desk: for Key User (end users) and processors of service desk messages see example below. Maintain Business Partners Tool Maintain Business Partner (transaction BP) Usage Maintenance of Business Partners Further Documentation Tool Security Guide – SAP Solution Manager Root Cause Analysis .  Test Management: if testers have to test in managed systems.User Administration Guide Link http://service. 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.  Service Desk: for Key User (end user).

Procedure 32 August 2009 . as described above. you must import new roles and profiles from client 000 into your productive client. Create Business Partner Using Transaction BP_GEN 1. You have to create all end users known to SAP Solution Manager. 2. Choose Edit → Create Business Partner. as described above. Select users. Create users for all end users in all three systems. 1. This e-mail address can be any address. in transaction SU25. Create business partners for end users. you need to update your business partners IMG activity Create Key User (technical name: SOLMAN_SUP_BUSPART) Create Business Partners SPRO 4. Confirm your entries. 5. 2. The system landscape consists of SAP Solution Manager and two managed systems. in the SAP Solution Manager system and the managed systems. Caution When you update your system.4. 4. you need to update your tables with new default field values for authorization objects. Create Users and Business Partners for End Users Topic User Management Transaction SU01 Detailed Description Create Users Create Business Partner BP_GEN If you change e-mail addresses for users. as Business Partners. Select a system from which you want to create business partners. Choose User list → Add system. three systems in total. in the SAP Solution Manager system.SAP Solution Manager Operation Guide 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. 3. as long as it is known to the mail server (Business Process Operations: for use of auto-reaction methods). This is especially relevant for all new authorization objects delivered with an update.3 Update Authorizations after Support Package Upgrade After the new installation and an update of your SAP Solution Manager system. Example You want to create end users for Service Desk functionality.

or customize the logon screen for Web Dynpro applications. August 2009 33 . c) Enter a description for your role. d) Go to tab menu and enter transactions SU01 and PFCG. System Administrator  Configuring query settings for all end users. Update Authorizations after Support Package Upgrade Topic Profile Generator: Upgrade and First Installation Transaction SU25 Detailed Description Update Authorizations after Support Package Upgrade 4.4. The dialog explains in detail what you need to do.SAP Solution Manager Operation Guide 1. Choose Information.4. See document How to Adapt a Work Center View in the Service Marketplace. To be able to assign the correct authorization. you can create a dedicated role for them. and choose Single Role. 2.5 Create End User Roles You need to grant authorizations for which SAP does not ship template roles.  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 Topic How to Adapt a Work Center View Transaction Detailed Description http://service. in the Service Marketplace. for instance: ZSU01_PFCG. for instance: Full authorization for SU01 and PFCG. using the example of critical authorizations of transactions SU01 (User Management) and PFCG (Role Management). End User See document How to Adapt a Work Center View. b) Enter a role name in your namespace. Create a Role in Transaction PFCG a) Choose transaction → Media Library → Technical Papers 4. Call transaction SU25. Recommendation Perform at least the first step.4 Adapt Work Center Queries End users and system administrators can adjust work centers to their needs. This section describes how to create your own roles. in the SAP Solution Manager and managed

6 Assign Roles to Users After you have generated profiles from roles. double-click the green line. When you enter a transaction in the menu tab in your role. 2.4. 6. Enter your role and choose edit. You are asked for a transport request. Go to Users tab. Transaction SU01 1. Save.SAP Solution Manager Operation Guide The authorization objects required in role creation are maintained using transactions. 5. Choose transaction SU01. according to your needs. 3. 4. add your user in the table and perform the user comparison. The system opens the documentation for this object in a separate window. Create End User Roles Topic User Management Role Maintenance Transaction SU01 PFCG Detailed Description Create End User Roles Create End User Roles 4. e) Save your role. choose User tab. Choose the User Comparison button. d) Generate the profile. 2. Enter the user and choose edit. 5. Choose transaction PFCG. Enter the user name. If you are not sure about the function of the authorization object. Maintain Authorization Objects Default authorization objects delivered by SAP contain only minimal authorizations. To grant full authorization to authorization objects. 3. always choose all activities. c) Maintain all activity values per authorization object. Go to Roles tab. Save. e) To assign this profile to a user. f) Save. Enter your role. you must edit them a) Choose the Authorizations tab in the Role Maintenance. Transaction PFCG 1. 4. the system traces all authorization objects required for this transaction. in one of the two ways explained below. Caution All authorization objects need to have a green traffic light. 34 August 2009 . assign the role to your users. for instance. if you want to grant full authorization. b) Choose Change.

SAP Solution Manager Operation Guide Assign Roles to Users Topic User Management Role Maintenance PFCG: Status of user comparison Transaction SU01 PFCG Detailed Description Assign Roles to Users Assign Roles to Users SAP Note 1272331 August 2009 35 .

database. depending on the availability requirements of the implemented IT management processes. Highavailability applications allow you to maximize downtime security and minimize downtimes.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 36 August 2009 . You can achieve this by controlling the growth of redundant data and implementing redundant systems control Components with single point of failure Component <Component 1> Detailed Description Describe the function of this component in this scenario that is a single point of failure. To achieve HA for the complete scenario. Further Documentation Tool Service Marketplace – High Availability Help Portal Link http://service. and suppliers. HA Setup Description Refer to the component high availability setup description. such as the operating system. high availability is always focused on business applications and their related components. all components with single point of failures must be set up with HA. At SAP. and hardware. Each of the above components can be a single point of failure in this scenario. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure. This means integrating existing heterogeneous system landscapes to include business http://help.SAP Solution Manager Operation Guide 5 High Availability There are no general High Availability (HA) requirements for the SAP Solution Manager. Otherwise explain → SAP NetWeaver → SAP NetWeaver 7. if You may also have requirements of your own. Collaborative business can give you a competitive advantage. customers.

In particular. but it is not supported in SAP Solution Manager. because many functions.1 Archiving & Data Deletion in SAP Solution Manager Achiving functionality in core SAP Solution Manager There is only limited archiving functionality in SAP Solution Manager 7. Documents in Solution Manager projects The only function which might need a lot of database space is document management in the implementation scenario.g. 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. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents.SAP Solution Manager Operation Guide 6 6. an archive.0. Service reports in solutions Service sessions such as EarlyWatch Alert reports. the following objects cannot be archived using default SAP archiving mechanisms: Solution Manager projects Solution landscapes CRM transactions.g. However. change documents and issues. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. type and frequency of documents checked in. Service Level reports. see SAP Note 845433.) There is a generic way to archive CRM-based transactions (e. several hundred MBs per week and project might be needed – because usually every version of a document is kept. such as service tickets. Monitoring data in central performance history database Test packages/test cases These objects do not usually contain a lot of data. have links to service tickets or change documents. service ticket. etc. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. and might cause inconsistencies. to another repository. can be archived using the ArchiveLink interface. e. the document attributes needed to administer the documents will be kept in SAP Solution Manager. such as test workbench and implementation projects. change requests. and the documents attached to them. change requests. Documents on the generic CRM tabs (transaction CRMD_ORDER) cannot be archived. August 2009 37 . change document). Archiving these CRM-based transactions would break the links to them. 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. Depending on the number. For details. if they can still be deleted.

it will not save referenced data. it is not part of the SAP Solution Manager core functionality. The extension package requires a separate license. use SAP content server for knowledge warehouse documents. Projects SAP Solution Manager projects can be stored in a transport using transaction SOLAR_PROJECT_ADMIN. Without a valid license. or by directly executing report RDSMOPDELETESOLUTIONS. which carry an attribute for the solution. store reports on separate file server. Service reports in solutions SAP EarlyWatch Alert and service level reports could be stored on a separate file server. If CRM transactions such as service tickets. this function will only store the business process structure and all related documents. They can be deleted from SAP Solution Manager using report RDSMOPREDUCEDATA. these reports will not work. Solutions Solutions can be deleted from SAP Solution Manager using the functionality in transaction DSWP. deletion of the solution might not be possible (as it is not possible to delete the related CRM transactions). reports etc. When deleting a solution. shipped with ST400 SP13. However. there are several functions to reduce the amount of data in the database. all objects produced within that solution (service sessions.SAP Solution Manager Operation Guide Notes for Archiving SAP Note 546685 845433 Short Text Archiving in Solution Manager (Operation) Deleting a service process with support message 6.3 Alternative Storage & Deletion Strategies Although generic archiving is not supported by most scenarios in SAP Solution Manager. 38 August 2009 . with the report SOLMAN_DOCU_VERSION_ARCHIVE.) will be deleted – if this is possible. such as CRM transactions or test workbench items. and generally available to customers with ST400 SP15. have been created. The report SOLMAN_DOCU_VERSION_DEL can then delete the archived documents. 6. A customer can save the objects using other methods (put objects in transport requests using migration functions.g. keep backup of whole system before data deletion). archives the documents (or old versions) in Solution Manager projects. change documents). Similar functions are available to archive documents which are added to the CRM transaction tabs (e. Documents on the generic CRM tabs cannot be archived using this function. Solution Manager projects can also be deleted using transaction SOLAR_PROJECT_ADMIN. but only for those which refer to a Solution Manager project (a function also delivered with the ET extension package).2 SAP Solution Manager Extended Archiving Functionality The extension package “Extended Traceability” (ET).

and when to use them. Test messages (service tickets created during tests) cannot be archived or deleted – see the section “Achiving functionality in core SAP Solution Manager”. eCATT logs can be archived . if you want to reapply and distribute the template to other systems.for more → SAP CProjects Suite → Editing Project Structures → Collaboration Projects → Basic Functions → Archiving Templates Contents in templates should also be stored in transport requests. test data container. They can be deleted using transaction SECATT and STWBM. August 2009 39 .sap. see the SAP Netweaver online documentation. (otherwise it would be sufficient to keep a backup copy of the project state. CATT objects are repository objects and can therefore be saved or stored using transport mechanisms. test configurations) are repository objects and can therefore be saved or stored using transport mechanisms. Test results can be consolidated and extracted in a test report. Store the contents in a template transport. They can be deleted using transaction SCAT and STWBM. CATT scripts should be migrated to eCATT.SAP Solution Manager Operation Guide Archiving Projects Topic SAP Solution Manager Help cProjects Archiving Link http://help.Handling Templates with SAP Solution Manager Link http://service.xml files. Test cases of type “manual” or “external application” are repository objects and can therefore be saved or stored using transport as defined under “Projects”). see: Archiving Templates Topic FAQ . test scripts. eCATT objects (system data container. For more information on how to distinguish template transports and (template) project → SAP Solution Manager http://help. because whenever a new template version is defined in the template → 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 downloaded as . They can be deleted via transaction STWB_2. They can be deleted using transaction SCAT and STWBM. which can be stored as an MS Word document. the older versions can no longer be accessed (retrieved).

sap. SMSY data. 6.reduce data volumes Deleting a service process with support message New features for RDSMOPDELETESOLUTIONS in SP08 cProjects problems with archiving/resources/deletion Solution Manager: TEST_DSMOPSERSESSN_DELETE Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN Archiving reporting documents in SAP Solution Manager SAP Note 1006094 1077447 1091497 1092503 40 August 2009 .com → SAP NetWeaver → SAP NetWeaver 7. BC-TWB-TST-ECA) Link http://help.SAP Solution Manager Operation Guide Archiving Test Management Topic Archiving Logs (SAP Library . CPH monitoring data. the BI aggregation and deletion mechanisms can be used to reduce the amount of data in the BI database. Data extracted to BI If data from SAP Solution Manager has been extracted for Business Intelligence (reporting on EWA raw data.eCATT: Extended Computer Aided Test Tool. root cause analysis data.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-TWBTST-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. and Business Process Monitoring data).4 544295 546685 566225 638785 845433 976695 SAP Notes for Additional/Background Information Short Text Basis message: Deletion flag status Archiving in Solution Manager (Operation) Report to delete the basis notifications with deletion flag SAP Solution Manager .

we give an overview of both procedures. You can use the existing implementation project to track all information about the setup progress of your basic settings. You can update your basic settings configuration by either:  Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP.Automatic Update Configuration You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). development teams. 2. the Open Activities column shows the steps you need to execute. global rollouts (including localizations). the system displays a configuration table with all activities you need to perform after updating your system. recommended) or  Checking for new or changed IMG activities in the SAP Reference IMG.  Update your authorizations. Call transaction SOLMAN_SETUP. This is especially important for the basic settings. and application support teams. Using Guided Procedure – Automatic Update Configuration Short Text Update your authorizations Online Help for transaction SOLAR02 and/or Work Center Implementation Tutorial on SAP Solution Manager Configuration (transaction SOLMAN_SETUP) Link SAP Note 1236420 http://help. In Basic Configuration. you need to check your configuration settings for new and updated configuration tasks.1 Guided Procedure .sap.SAP Solution Manager Operation Guide 7 Software Change Management Software change management standardizes and automates software SAP Solution Manager <current release> http://service. and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). with every newly-shipped Web Dynpro application.1.1 Configuration after Support Package Update After you have implemented a new support package or support package stack (SAP Enhancement Package). you can specify here whether you have to re-execute activities that have already been executed. These functions support your project For instance. its ICF service needs to be activated. see SAP Note 1236420. this may be the activity Activate BC Sets. In the Overview. In case of an update. In the following. To do this. with specified maintenance procedures. The goal of software change management is consistent. check all activities in the Overview area in transaction SOLMAN_SETUP. If you select an entry in this table. solution-wide change management. 3. Call transaction SOLAR02 and choose your project. 7. 7. The system updates this list automatically. and open integration with third-party products. Prerequisites  Initially configure all basic settings using the guided procedure for the automatic basic settings configuration. Using the Overview for Update Activities 1. and testing procedures for complex software landscapes and multiple software development 011000358700001735062008E August 2009 41 . maintenance.

SAP Note 1334252 applies to ST-400 Support Package 20. Activate Release Notes Display release notes by choosing Release Notes.2 Ensure Basic Functions via SAP Note In order to ensure that the basic functions of SAP Solution Manager are running properly.0 EHP 1 (ST-400 Support Package 18 and 19).Automated Update Configuration.0 IMG after SP01 Changes to SAP Solution Manager 7. For further information. Using IMG – Manual Update Configuration Short Text Changes to SAP Solution Manager 7.2 SAP Reference IMG – Manual Update Configuration You can update basic settings configuration and scenario-specific configuration using the SAP Reference IMG (transaction: SPRO). Support Packages and Patch Implementation SAP Note Short Text 42 August 2009 . and deleted IMG activities up to SP17. As soon as a new version of the note exists. This central note includes other required notes that are extended and renewed regularly. The note is valid for Solution Manager 7.SAP Solution Manager Operation Guide 7. you should implement it with the Notes Assistant (transaction SNOTE). see section Guided Procedure (transaction SOLMAN_SETUP) . in which you can automatically implement all notes included. 1334252 (SP 20) 7.1. changed IMG activities. see the release notes and SAP Note 1260646. For later support packages. these are only described in the note. Caution See SAP Note 903274 for details of new IMG activities. Ensure Basic Functions Component Basic Functions Transaction SNOTE Detailed Description Check SAP Note regularly 1172948 (SP 18 and 19). it is recommended to regularly check SAP note 1172948. The system flags the release information with a blue information icon in front of the IMG activity. Recommendation We recommend that you update your basic settings using the automated guided procedure.0 IMG as of Enhancement Package 1 SAP Note 903274 1260646 7.3 Support Packages and Patch Implementation The SAP Solution Manager has several software components which have their own release strategy. If these notes contain manual actions. see the notes below.

0 EHP 1 SAP Solution Manager: SAP Notes for support packages Changes to SAP Solution Manager customizing (IMG) as of EHP 1 SAP Solution Manager 7.SAP Solution Manager Operation Guide 394616 539977 569116 608277 631042 939897 1109650 1169247 1244225 1260646 1276022 1276263 1276895 Release strategy for SAP Solution Manager (ST) Release strategy for add-on ST-PI Release strategy for Solution Manager Service Tools (ST-SER) Installing and updating content for SAP Solution Manager Release strategy for Implementation Content (ST-ICO) SAP Solution Manager usage data SAP Solution Manager 4.0 as of EHP 1 Additional information on upgrading to SAP Solution Manager 7.0 to 7.0 EHP 1 installation Roles: SAP Solution Manager 7.0 Extension Add-Ons Upgrading SAP Solution Manager 7.0 EHP 1 August 2009 43 .

if not. which is supplied by the central SLD in standard case). adjust it as required. see SAP Note 33135: Guidelines for OSS1. and System Components). Compare the last refresh dates in SMSY with the last data transfer date in SMSY_SETUP. For more information. see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS. Databases. Verify the data sources of your landscape components (Hosts. check if connection SAPOSS works. For more information. and check that the “Automatic Data Transfer” comes from your SLD (usually local SLD. with transaction SOLMAN_SETUP. Different dates could indicate that the landscape information is not correctly supplied by your SLD.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.SAP Solution Manager Operation Guide 8 8. Usually this connection is created by the SAP Solution Manager Setup. For more information. Check whether the distribution group is set to EWA. see the following SAP Notes: SAP Note 33135 766505 182308 Short Text Guidelines for OSS1 OSS1: Changes to RFC Connection SAPOSS Incorrect Logon Data in R/3 Destination SAPOSS 8. and check that the system information is sent from your SLD to SMSY. if not. to be able to send data to SAP.   In transaction SM59. 44 August 2009 . Systems.1 Troubleshooting Connection to SAP An SAP Support Portal connection is required. adjust it as required. 2) Call transaction SMSY_SETUP.

In this case. The selfdiagnosis tool is highly configurable and can perform solution-specific or cross-solution self August 2009 45 . The self-diagnosis checks the system requirements for operating SAP Solution Manager. Note: Ensure that the version of your agent is the same as the version of the source on your SAP Solution Manager. CA Wily Introscope Enterprise Manager may not be active.0) via web browser – usually http://hostname:8081/webview/jsp/login. The equal sign icon indicates that the version is up to date. 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. and check the RFC connections and SDCC.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.5 Self-Diagnosis An enhanced self-diagnosis tool has been delivered with SAP Solution Manager 7. see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”.jsp. If the EWA is grey in the overview. there is also a problem.2. If the logon screen of your WebView does not appear. which system in the landscape is affected.0. not regular self-diagnosis. 8. For more information. Support Package 12. If there is a small red flag in the solution overview of transaction SOLUTION_MANAGER. 2) Check that CA Wily Introscope Enterprise Manager receives information from CA Wily Introscope Agent. 8. see SAP Note 762696 “Grey rating for EarlyWatch Alert”. as of release 7.3 SAP EarlyWatch Alert (EWA) SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections. check in the solution.SAP Solution Manager Operation Guide 8. 2) Go to operating system level and verify whether the Enterprise Manager system process is available a. something is wrong with the EWA data collection. For further information.0. It should be used for troubleshooting. Windows: Check Services b.

You can perform a new analysis at any time. to identify SAP Solution Manager system performance problems. e.g. e. The self-monitoring functionality is in the transaction SOLUTION_MANAGER → Settings → Self-Diagnosis. For the SAP Solution Manager single solution. You can display the self-diagnosis results in various levels of detail:   For the SAP Solution Manager (cross-solution). A self-diagnostics module is available in SAP Solution Manager. to check whether the problems shown by alerts have been resolved. to check that the master data of a solution is consistent. You can customize SAP Solution Manager self-monitoring. in the Alert Type area. You can select which type should generate an alert and inform you. You can analyze your SAP Solution Manager system and/or a solution. to identify and solve problems.SAP Solution Manager Operation Guide → Overview and Setup of SAP Solution Manager 46 August 2009 .sap. The self-diagnosis analyses run daily. Self-Diagnosis Topic New self diagnosis in SAP Solution Manager: a quick guide Ramp-up knowledge transfer Link SAP Note 1073382 http://service. in the background. The self-diagnostics checks the RFC Connection. with the self-diagnosis function.g. batch jobs and performance values. by default.g. to avoid red alerts. e.

0.1 Appendix Related Guides The master guide is a central starting point for the technical implementation of SAP enhancement package 1 for SAP Solution Manager 7. The configuration guide describes the configuration of SAP Solution Manager and its scenarios and functions. particularly about roles and authorizations. and its scenarios. Installation Guide and Update Guide Related SAP Notes Released Platforms Network Security SAP Solution Manager Root Cause Analysis August 2009 47 . is in the security Instguides → SAP Components → SAP Solution Manager notes platforms securityguide solutionmanager diagnostics Related Information Content Master Guide. system. All security-related information.2 Related Information Quick Link to SAP Service Marketplace (http://service.SAP Solution Manager Operation Guide 9 9. The installation guide describes the installation of SAP enhancement package 1 on an existing SAP Solution Manager 7.

Sign up to vote on this title
UsefulNot useful