Solution Operation Guide

SAP Solution Manager 7.1 Operation Guide

Document Version 1.0 - May 9, 2011

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

© Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address:
service.sap.com/instguides
®

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.

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

Icons Icon Meaning Caution Example Note Recommendation Syntax

Example text

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

SAP Solution Manager Operation Guide

Contents
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 SAP Solution Manager built-in Software Components .......9 SAP Solution Manager complementary Components .......11
Internet Graphics Server (IGS) ................................................11 SAP NetWeaver Search and Classification (TREX) ...............11 CA Wily Introscope ..................................................................11

2 SAP Solution Manager and Technical System Landscape . 9

2.4 2.5 2.6 2.7 2.8 2.9 2.10

Release Restrictions .............................................................12 Installation .............................................................................12 Upgrade to SAP Solution Manager 7.1................................12 Business Warehouse (BW) Client Strategy ........................13 Root Cause Analysis ............................................................13 SAP Solution Manager Configuration .................................14 Managed Systems Configuration ......................................15

2.10.1 Required Agent Versions ........................................................16 2.10.2 SAP Solution Manager and Trusted RFC ...............................16 2.10.3 System and Landscape Directory (SLD), Landscape Management Database (LMDB) and SMSY .........................................18 2.10.4 Adjust Upgrade of Managed System ......................................19

2.11 Moving from SAP Solution Manager Transation DSWP to Work Centers ..............................................................................20 2.12 Solution Transfer ................................................................20 2.13 Service Delivery in SAP Solution Manager ......................21 2.14 Multi-Tier Landscape for SAP Solution Manager .............21 2.15 Sizing for SAP Solution Manager ......................................21 2.16 Related Documentation ......................................................22

3 Monitoring SAP Solution Manager ..................................... 23
3.1
3.1.1

New Monitoring Infrastructure .............................................23
Connection Monitoring ............................................................23

3.2
3.2.1

CCMS Monitoring – SAP Solution Manager .......................23
CCMS Monitoring – Internet Graphics Server (IGS) ..............24

3.3 3.4
3.4.1

SAP EarlyWatch Alert in SAP Solution Manager ...............24 Other Problem Analysis and Monitoring Tools ..................24
Application Monitoring ............................................................24

4 Management of SAP Solution Manager ............................. 26
4.1 Solution Manager Administration Work Center .................26

4

May 2011

...........4 4..5................................................................................................................1 9..............27 Self Diagnosis View ....................................................................................26 Infrastructure View ....................5.....1 Periodic Tasks ...... 39 6.....32 Create Users and Business Partners for End Users ...5 4....1...3 8.........4 4..........48 Related Guides .................35 Adapt Work Center Queries................................1 4......28 Backup and Restore ............ 38 6 Archiving & Data Deletion in SAP Solution Manager ................................................2 8......48 Logging and Tracing ..........................6 User Management ..........................5 4...2 7..............................................39 SAP Solution Manager Extended Archiving Functionality40 Alternative Storage & Deletion Strategies .45 Connection to SAP .......46 SAP EarlyWatch Alert (EWA) ...........5...................5..37 5 High Availability............49 Related Information ........1 7.........................33 Update Authorizations after Support Package Upgrade ...........................Automatic Update Configuration ...3 6.................3 4.........................49 8 Troubleshooting ....................2 4.......................................43 Guided Procedure ...........4 4.....28 Project View .......1 7............28 4...........................................40 SAP Notes for Additional/Background Information ...........................................2..........2 6..............5.............2 Ensure Basic Functions via SAP Note .............................. 43 7.....................................................................30 4.4 7.........................36 Create End User Roles ....5.....................44 Support Packages and Patch Implementation ..........................43 Configuration after Support Package Update ...........2 4....2 4...............................32 User Administration and Authentication ................................30 4.........................3 7.......3....................2...........46 Self-Diagnosis ....................................................1 4........................... 49 May 2011 5 .....5 Landscape View ......................30 Background processing in the SAP Solution Manager..... 46 9 Appendix ........1...............................46 CA Wily Introscope ............4...1 6..........43 SAP Reference IMG – Manual Update Configuration ..3 4......1...........................................................................................1 Starting and Stopping ..........2 Achiving functionality in core SAP Solution Manager .................................................................................................1....................................3 4...............5 9.......................4 8...............................................44 7 Software Change Management ..4 8......SAP Solution Manager Operation Guide 4...................................................42 Agents Consideration ..................1 8.28 Solution View .........29 Backup Introscope Enterprise Manager ...36 Assign Roles to Users ..........1........................

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

upgrade shutdowns and long runtimes.1 SP01.1 Overview on the available documentation for SAP Solution Manager 7.basic functions 1577909 Supplements to Solution Manager 7.0 to SAP Solution Manager 7.1 (installation) to the stack that is currently available 1552585 SAP Solution Manager . info.1 Update of SAP Solution Manager 7. This note contains additional prerequisite notes that are regularly extended and renewed. Implement the following note to ensure the basic functions in SAP Solution Manager. This note is valid for Solution Manager 7. This note describes preparatory measures and additional information for the   Upgrade of SAP Solution Manager 7. about Upgrading to SAP Solution Manager 7.1  1583348 Documentation: SAP Solution Manager 7.0 Enhancement Package 1 to SAP Solution Manager 7. The aim of this note is to prevent data loss.1 May 2011 7 .This usually takes the form of references to other notes.SAP Solution Manager Operation Guide Important SAP Notes SAP Note Number 1462137 Title Add.1 Upgrade of SAP Solution Manager 7. Only database-independent problems are dealt with here.1 Comment This note describes problems that may occur when you upgrade the system and provides you with information on how to solve them.

00 Important Changes First version of the SAP Solution Manager Operations Guide for SAP Solution Manager 7.SAP Solution Manager Operation Guide 1. The following table provides an overview of the most important changes in previous versions.1.1 8 May 2011 . Document Versions Document Version 1.com/instguides → SAP Components → SAP Solution Manager → Release 7.sap. The current version of the Application Operations Guide is on SAP Service Marketplace at http://service.2 History of Changes Make sure you use the current version of the Application Operations Guide.

Cental Information Sources Topic Application Lifecycle Management (ALM) SAP Solution Manager SAP Help Portal Ramp-Up Knowledge Transfer Link http://service.sap.1 SAP Solution Manager SAP Solution Manager is the central tool for managing your customer solution landscape. It includes several applications and scenarios to support the Application Lifecycle Management (ALM) ensuring business continuity.com/rkt-solman 2. It is based on an SAP NetWeaver platform and includes the SAP CRM add-on. More information about Application Lifecycle Management (ALM) and the SAP Solution Manager can be found in the SAP Service Marketplace or the SAP Help Portal.com/alm http://service.com/solutionmanager http://help. so the tasks and procedures for a standard SAP NetWeaver system generally also apply to SAP Solution Manager. accelerating innovation. depending on the business scenarios used.sap. You can use the following software components in your system.sap. This guide refers mostly to SAP Solution Manager-specific tasks and procedures. Usage Type SAP Solution Manager Software component SAP_BASIS SAP_ABA SAP_BS_FND SAP_BW BI_CONT SAP_AP ST ST-A/PI ST-SER ST-PI Description SAP Basis Component Cross-Application Component SAP Business Suite Foundation SAP NetWeaver BI Business Intelligence Content SAP Application Platform Solution Manager Tool Application Service Tools Solution Manager Service Tools Solution Tools Plug-In May 2011 9 .SAP Solution Manager Operation Guide 2 SAP Solution Manager and Technical System Landscape 2.com/ → SAP Solution Manager http://service. Another central place for useful information about the supported functions is the Ramp-Up Knowledge Transfer page for the SAP Solution Manager.2 SAP Solution Manager built-in Software Components The SAP Solution Manager comprises several software components. Other software components can be added to SAP Solution Manager.sap. Application Lifecycle Management (ALM) adresses this challenge with an integrated ITIL-based approach. and reducing risk as well as total cost of operations while protecting your investment is the key challenge for each IT organization. depending on the scenarios you actually use.

com/solutionmanager → Process Scheduling adapter for SAP Solution Manager. which can be used for specific scenarios: Additional Software Tool SAP Quality Center by HP SAP Central Process Scheduling by Redwood SAP Productivity Pak by RWD BMC Appsight for Client Diagnostics Link https://service. https://service.com/solutionmanager → SAP Solution Manager Adapter for SAP Quality Center by HP.0 (ABAP) PI_BASIS SAP Web UI Framework SAP Adapter for SAP Quality Center by HP SAP process scheduling adapter SAP Produktivity Pak Root Cause Analysis BMC AppSight CA Wily Introscope Software Comonents Detailed Information Support Package levels of SolMan installations / upgrades SAP Note 781448 Third-Party Integration There are several standard interfaces to third-party tools.com/solutionmanager → SAP ProductivityPak by RWD adapter for SAP Solution Manager and SAP Note 1131270 SAP Note 1034902 10 May 2011 .SAP Solution Manager Operation Guide ST-ICO BBPCRM CPRXRPM PI_BASIS WEBCUIF Usage Type Additional Adapers ST-QCA ST-PSM ST-SPA Usage Type Java Application Server LMSERVICE Aditional 3rd Party Software Appsight Blackbox and Console Introscope Enterprise Manager Solution Manager Implementation Content BBP/CRM SAP Portfolio and Project Management 5.sap.sap. https://service.sap.

g.3. You can administrate your Web Dynpro Java IGS via a Web Interface. Administration of TREX Topic SAP Netweaver Search and Classification Administration of TREX Notes for TREX SAP Note 1466273 Short Text Work Centers: "TREX is not responding" error message TREXADMIN Transaction Link http://help. SAP Note 797147 “Wily Introscope Installation for SAP Customers” includes a detailed FAQ document as an attachment. For information about installation. The server can be administrated in transaction SIGS.3 CA Wily Introscope CA Wily Introscope is a software component.2 SAP NetWeaver Search and Classification (TREX) For specific scenarios the SAP NetWeaver Search and Classification (TREX) is used.3.0 including Enhancement Package 2 → <language> → Technical Operations Manual → Administration of Standalone Engines → Search and Classification (TREX) http://help. May 2011 11 .3 SAP Solution Manager complementary Components 2.sap. which collects performance and other system-related data maily from non-ABAP components in your system landscape. see the installation guide on SAP Service Marketplace at http://service.1 Internet Graphics Server (IGS) The Internet Graphics Server (IGS) generates various graphics or charts in some areas. This document also includes a detailed troubleshooting section.com → SAP NetWeaver → SAP NetWeaver 7.sap. Administration of IGS Topic Internet Graphics Server (IGS) Notes for IGS SAP Note 965201 995471 514841 Short Text IGS HTTP administration commands IGS administration via ABAP Troubleshooting when a problem occurs with the IGS Transaction SIGS Link http://<IGS host>:<IGS port> 2.SAP Solution Manager Operation Guide 2.sap. e. in EarlyWatch Alert reports.3.htm 2.com/saphelp_nwes70/helpdata/en/ 46/c96a575b590e5be10000000a1553f7/content.com/diagnostics → Installation and Configuration.

com/irj/sdn/netweaver. The upgrade of SAP Solution Manager requires using the upgrade program SAPup for the ABAP part and the SAP Enhancement Package Installer (SAPehpi) for the Java part. SAP recommends running SAP Solution Manager on Unicode. SAP Notes SAP Note 1480419 Short Text Release Restrictions for SAP Solution Manager 7.sap. All new SAP Solution Manager Installations are on Unicode. SAP recommends migrating to Unicode. a number of restrictions still applied to the productive use of certain functions.1 was released.5 Installation SAP Solution Manager 7.1 2.sap.1 To upgrade to SAP Solution Manager 7.sap. until the customer has completed the Unicode conversion.1. This information is collected in SAP Note 1480419 “Release Restrictions for SAP Solution Manager 7. SAP Solution Manager Installation Topic SAP NetWeaver Releases SAP Solution Manager Installation Unicode Link http://sdn.com/irj/sdn/netweaver http://service. and are not yet on Unicode.sap. SAP Solution Manager 7. SAP will support the SAP Solution Manager on non-Unicode. For customers that have upgraded from previous releases of SAP Solution Manager 7. For more information about SAP NetWeaver technology.com/diagnostics 2. If this is not possible.SAP Solution Manager Operation Guide Wily Introscope Topic Wily Introscope Notes for Wily Introscope SAP Note 797147 1565954 Short Text Wily Introscope Installation for SAP Customers Introscope 9 Release Notes Link http://service. 12 May 2011 .sap.1 is based on the technology of SAP NetWeaver 7.0 including Enhancement Package 2. For further information please consult the SAP Solution Manager 7. you require seperate upgrade programs for the ABAP and the Java parts of your SAP Solution Manager system.com/instguides http://service.1 Upgrade Guide. see http://sdn.1“.6 Upgrade to SAP Solution Manager 7.1.com/unicode 2.4 Release Restrictions When SAP Solution Manager 7.1 is an SAP system based on Application Server ABAP (AS ABAP) and Application Server Java (AS Java).

BW in a Separate Client on SAP Solution Manager In this scenario. In general there are two main BW options when planning your system landscape. SAP Solution Manager Upgrade Topic SAP Solution Manager 7.1 Upgrade Guide Additional information on upgrading to SAP Solution Manager 7. you must maintain users separately. There is no technical benefit.1”) includes an overview of software components and support package levels that must be installed in your SAP Solution Manager system. and this increases your administration effort. and isolates the BW activities for solution life cycle management from the data on a production BW instance. The configuration of the tool is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP).sap.1. BW Client Strategy Topic Where is best to set up BW for the Solution Manager Note / Link SAP Note 1487626 2. BW activities are conducted in a separate client on the SAP Solution Manager system.g.SAP Solution Manager Operation Guide SAP Note 1462137 (“Additional information on upgrading to SAP Solution Manager 7. This scenario provides increased security. as user access is more restricted.8 Root Cause Analysis You need information about the basic requirements and possible limitations of end-to-end root cause analysis. BW in the Productive SAP Solution Manager Client In this scenario. BW is used in the same productive client as SAP Solution Manager. as user access is more restricted.com/instguides → SAP Components → SAP Solution Manager → Release 7.1 Note / Link SAP Note 1478974 May 2011 13 . There is no technical benefit. The functionality is also called End-toEnd Diagnostics or SAP Solution Manager Diagnostics. BW in a Separate Client on SAP Solution Manager In this scenario. and this increases your administration effort. This makes configuration simpler. delivered with SAP Solution Manager 7. However. e. you must maintain users separately.1 Link http://service. This scenario provides increased security.1 SAP Note 1462137 2. Root Cause Analysis Topic Diagnostics in SAP Solution Manager 7. BW activities are conducted in a separate client on the SAP Solution Manager system. However. Solution Manager Diagnostics.7 Business Warehouse (BW) Client Strategy BW provides important reporting functions to the various SAP Solution Manager processes. This is SAP’s recommendation.

for example.sap.com/instguides → SAP Components → SAP Solution Manager → Release 7. the basic configuration should be performed. in the SAP Reference IMG (transaction SPRO). All settings for this Web Dynpro application are made during the installation of SAP Solution Manager. Data Volume Management Further Configuration for the following scenarios: o Test Management o Quality Gate Management o Change and Transport System (CTS+)    For more information about configuration. The automatic basic settings configuration with SOLMAN_SETUP includes:   System Preparation o Settings which are prerequisite for the configuration of SAP Solution Manager Basic Configuration o Necessary configuration which is needed to use basic scenarios in SAP Solution Manager. o End-User Experience: monitors hosts at various locations which simulate the availability and performance of business processes from the point of view of the end-user. performing a root cause analysis.sap. This quickly configures all main settings in a guided procedure. connecting to SAP.com/diagnostics 2.SAP Solution Manager Operation Guide Solution Manager 7. Measurement Platform Setup o Choose all systems for which you later want to perform your SUGEN benchmark measurement. or downloading patches and upgrades Managed Systems Configuration o Connect managed systems to SAP Solution Manager  And also configuration steps for specific scenarios:  Technical Monitoring.1. configures the following sub-scenarios: o Self-Monitoring: monitors the status of SAP Solution Manager.9 SAP Solution Manager Configuration After installing the SAP Solution Manager. see the Customizing for SAP Solution Manager (transaction SPRO) and the configuration guide on SAP Service Marketplace at http://service. 14 May 2011 . using the SAP EarlyWatch Alert. All activities in this wizard are linked to the corresponding Customizing activities in the standard basic settings configuration. The automatic configuration is accessed via the Solution Manager Configuration Work Center or it can be called by transaction SOLMAN_SETUP.1: Root Cause Analysis Root Cause Analysis SAP Note 1483508 http://service. You can initially configure your basic settings with the basic settings wizards. o System Monitoring: monitors the status of managed systems. o PI Monitoring: monitors XI (SAP Exchange Infrastructure) and PI (SAP Process Integration) systems which allow for data exchange between managed systems. o Connection Monitoring: monitors connections between managed systems.

sap.10 Managed Systems Configuration To ensure that all the systems can be managed centrally. In SAP Solution Manager this is usually ensured by using a trusted RFC with the same user. choose the Configure Scenario or Configure System May 2011 15 . choose the Technical Scenario tab page.   3. If incorrect system data is displayed.Automatic Configuration Status: Grey: Perform missing steps of the managed system configuration Red: Repeat failed steps of the managed system configuration .To make sure that the technical systems or technical scenarios are correctly known to SAP Solution Manager. which are known to the SAP Solution Manager System Landscape Directory. create the technical system manually. The configuration of managed systems for the basic scenarios is in the guided procedure (transaction SOLMAN_SETUP). you maintain the technical system or scenario in the system landscape. so you must be able to access those systems. the SAP Solution Manager should be connected to all systems in the system landscape. To connect a standalone database. technical scenarios.com/instguides → SAP Components → SAP Solution Manager → Release 7. 2. choose the Technical System tab page.If the system that you want to connect is not contained in the technical system list. Select the system you want to configure:     To connect a single system.1 2. To connect a double (ABAP and Java) stack system. select an item and choose the Show Details link. you connect systems to SAP Solution Manager: 1. Misuse of the communication connection must be prevented. or databases. . connect the system to an SLD to minimize the effort for maintenance. for example delete and set up the RFC destination again . are displayed. Check the status of the configuration:  Gray. 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.RFC Status (only ABAP): Red: Repair the RFC connections. choose the Database tab page. In this step.SAP Solution Manager Operation Guide Basic Configuration Topic SAP Reference IMG Configuration Guide Transaction / Link Transaction SPRO http://service. The technical systems. If required.Plugin Status (only ABAP): Red: Install the recent version of the following software components on the managed system: ST-PI ST-API . To do so. red or yellow signals in the following columns require you to take action: . The users should only have the authorizations which are assigned to them in the managed systems.

20 • This is installation procedure is described in SAP Note 1031096 • It is recommended to enable the automatic update feature of the SAP Host Agent. 4. • The installation files are available from http://service.10. choose the System/Scenario/Database Operations pushbutton.System Landscape Setup Guide 2. 5.1 Required Agent Versions On the Managed System you need different agents for Root-Cause Analysis as well as for the Technical System Monitoring.com/swdc  Support Packages and Patches  Browse Download Catalog  SAP Technology Components  SAP HOST AGENT  SAP HOST AGENT 7. Follow the instructions in the respective Guided Procedure. You go to a Guided Procedure. Notes for Managed Systems SAP Note 1472465 Short Text SAP Solution Manager 7. In particular. To create systems manually. scenarios or databases. The naming conventions for users must be consistent across systems. respectively. the creation of new users and the resetting of passwords must be strictly controlled.SAP Solution Manager Operation Guide pushbutton. respectively. This can be done using transaction SOLMAN_SETUP.sap. if the user management for the SAP Solution Manager is as restrictive as for all other productive systems. This is described in SAP Note 1473974. and choose Create. Databases are retrieved automatically from LMDB and cannot be created or maintained.10. Trusted relations between systems can be configured on different levels: 16 May 2011 .1 .20. SAP Solution Manager does not manage connections between managed systems.sap.com/swdc  Browse Download Catalog  SAP Technology Components  SAP SOLUTION MANAGER  SAP SOLUTION MANAGER 7. Required Agent Versions Topic Installing Package SAPHOSTAGENT Using the SAP Host Agent Auto Upgrade Feature Note / Link SAP Note 1031096 SAP Note 1473974 2. so that you can update the Host Agent centrally. The trusted RFC connections can be used and are acceptable from a security point of view.2 SAP Solution Manager and Trusted RFC The trusted RFC connections are setup between the SAP Solution Manager and the connected managed systems. Diagnostics Agent • You can use any version of the Diagnostics Agent (already installed agents do not need to be updated) • The agent applications are updated automatically from the Solution Manager • For new installations use the latest available version of the diagnostics agent from http://service.1 Agents for managed systems SAP Host Agent • You need to install at least patch level 55 of the SAP Host Agent 7.

SAP Solution Manager Operation Guide 1) Trusted relationships from a system. In case 2d).  The RFC server system accepts the authorization by the RFC client system. b) An SAP backend system accepts the SAP Logon Ticket of the SAP NetWeaver Portal. in the client system. within these services. no login data is provided in the RFC destination. This kind of trusted relationship is usually realized by putting the login data of a service user of the server system. with the same user ID as in the source system. 2) Trusted relationships between systems where one system accepts the authentication of the other system.  Through the authorizations of the service user for the authorization object S_RFCACL. finds the user and logs it in with user ID. but the option “same user“ is selected. with the authorization field RFC_EQUSER set to “Y” and the field RFC_USER empty or set to the dummy value „ (inverted comma). with which applications (authorization field RFC_TCODE). and logs on the user in the target system. as in a normal RFC destination. d) An RFC server system accepts the trusted RFC token und logs the user in to the target system. must have authorization for the authorization object S_RFCACL. which offers services to another system (client). The users who want to use such a trusted RFC connection. RFC connections between SAP systems can also be secured by “secure network communication” (SNC). and logs its user in. to restrict user access rights to RFC connections. the login data of a service user is entered in the RFC connection. it is also possible to restrict which users (authorization field RFC_USER) in the RFC client system can use the connection. 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. A user has his personal authorizations in the SAP Solution Manager system as well as in the connected managed systems. The trusted RFC can be used for 1b) and 2d). The trusted RFC connection has the following security attributes: Simple navigation (via Single Sign-On) from RFC client to RFC server. c) An SAP system accepts an SSL client certificate in an https connection. where the login token is entered. 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. In case 1b). and the authorizations in the RFC client system can be limited by the authorization object S_ICF. Examples: a) A Windows client accepts a Kerberos ticket of a Windows domain server. 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). Note for Trusted RFC SAP Note 128447 Short Text Trusted/Trusting Systems    May 2011 17 .

This is how to set up landscape data management:  SLD The technical system data is gathered by self-registration of technical systems in the System Landscape Directory (SLD). LMDB shares the CIM model with the SLD. Landscape Management Database (LMDB) and SMSY Many functions in SAP Solution Manager rely on up-to-data landscape data.1.  18 May 2011 . Applications. With release 7. For compatibility reasons. Note: If a local SLD was used in existing SAP Solution Manager environments before 7. the LMDB replaces it. Data can be enriched manually in the LMDB. e.10.3 System and Landscape Directory (SLD).g. and the Landscape Management Database (LMDB).3 – SLD: not supported not supported not supported SP6. which consume landscape data. Patch 5 SP9 all SPs all SPs all SPs If your central SLD does not fulfill these requirements. LMDB becomes the home of all Technical System data. Since landscape data is mostly gathered outside the SAP Solution Manager system. built-in repository for all Solution Manager applications. This is especially true for system maintenance. the home of Product Systems and Logical Components stays SMSY. For the usage with the Manager Landscape Management Data Base (LMDB) in the SAP Solution Manager certain minimum support packages depending on your SAP NetWeaver version for the SLD applies:         SAP NetWeaver 6. plus the automatic content synchronization mechanism.0 – SLD: EHP2 for SAP NetWeaver 7. The SLD contains information on installable software (updated via the SAP Service Marketplace) and technical system data. The main landscape management building blocks are the System Landscape Directory (SLD). which use this data include SAP Solution Manager Diagnostics. but also for various other applications. mostly sent by these systems using data suppliers. so that all SLD data provided by the productive SLD is propagated into LMDB. the landscape needs to be taken into account.1.0 – SLD: SAP NetWeaver 7. BI Monitoring and PI Monitoring.SAP Solution Manager Operation Guide 2. Monitoring and Alerting. it is also possible to forward the landscape data to an SLD. without user interaction. Note: We recommend running one central SLD on an existing Java stack in the landscape.0 – SLD: EHP1 for SAP NetWeaver 7.1 – SLD: SAP NetWeaver 7. data for technical systems is replicated to SMSY. which is fulfilling the above mentioned requirements and use this for the SAP Solution Manager. In Solution Manager 7.1 – SLD: EHP1 for SAP NetWeaver 7.1.1. SMSY Numerous other applications keep using transaction SMSY for the time being.2 – SLD: SAP NetWeaver 7.  LMDB The data from the SLD is synchronized into the SAP Solution Manager Landscape Management Data Base (LMDB) introduced with Solution Manager 7.40 – SLD: SAP NetWeaver 7. on an SAP NetWeaver PI system. LMDB is a central.

This section explains how to adjust your settings for this system in the SAP Solution Manager.Configure the central SLD as the source of the Landscape Management Database (LMDB) in Solution Manager. 2. directly or indirectly. SAP’s SLD Recommendation Manual maintenance of the system landscape without SLD is not recommended.4 Adjust Upgrade of Managed System You have upgraded a managed system. their landscape information can be forwarded to a central SLD. depending on the conditions above.sdn. Adjust Product Version a) To adjust the new product version for your upgraded managed system.10.com/irj/scn/weblogs?blog=/p ub/wlg/17579 Connect a Managed SAP System Topic Connect a Managed SAP System Solution Manager System Landscape Transaction SOLMAN_SETUP SMSY Detailed Description Automatic Guided Procedure for Managed System Configuration Product Systems and Logical Components 2. This allows patches and stacks to be downloaded to a central location provided by the SLM. In the dialog box.com/irj/sdn/nw-sld http://www. and then to SAP Solution Manager. go to transaction SMSY and choose your system. and choose Installed Product Version. A central SLD on SAP Solution Manager also allows the maintenance optimizer functions to use the Software Lifecycle Manager (SLM) features. This forwarding has to be configured manually for each productive system. Adjust Logical Component May 2011 19 . Prerequisites You have:  SAP Solution Manager projects and solutions in productive use  SLD attached to SAP Solution Manager Procedure 1.sdn. Note: For landscapes with no productive Java stack outside SAP Solution Manager (as would be used for PI and Web Dynpro Java). c) Save. implementing the SLD in SAP Solution Manager's own Java stack would be an alternative to connecting all SLD data suppliers. Best practice is a central SLD in which all systems register themselves.sap. b) Go to Header Data tab. via data supplier forwarding.SAP Solution Manager Operation Guide If productive SLDs are in use. SLD and LMDB Topic SLD planning guide SLD Topology Link https://www. choose the product version you have upgraded to.sap. This central SLD can be outside or inside SAP Solution Manager. All SLD data is propagated to LMDB automatically.

service plans. such as issues.1 this transaction was deactivated. See the SAP Solution Manager Solution Concept and Design document in the Service Marketplace.01 SP15. please review SAP Note 1541013. As the transaction has become outdated with the SAP Solution Manager 7. and replace your outdated logical component with your new logical component. after all landscape components have been created. so there is no need to transfer it manually. for documentation purposes. Adjust Upgrade of Managed System Topic Solutions in SAP Solution Manager Solution Directory Transaction SOLMAN_WORKCENTER SOLMAN_DIRECTORY Detailed Description Adjust Upgrade of Managed System Adjust Upgrade of Managed System 2. If you monitor business processes in this system. In an implementation project. deactivate the business process monitoring sessions for it. Therefore. to it. Solution Concept and Design Short Text SAP Solution Manager: Solution for SAP Service Delivery Deactivation of transaction DSWP Note / Link SAP Note 1117389 SAP Note 1541013 2. d) Activate your business process monitoring session and solutions again.SAP Solution Manager Operation Guide a) Create a new logical component for your upgraded managed system. the solutions must now be created via the Solution Manager Administration Work Center (Solutions). all new SAP Solution Manager developments have been done exclusively with a focus on Work Centers. In the past transaction DSWP (or SOLUTION_MANAGER) served as the primary entry point fir Operations and Operations Setup within SAP Solution Manager.11 Moving from SAP Solution Manager Transation DSWP to Work Centers With the introduction of Work Centers with SAP Solution Manager 7. Additional steps are: a. you may want to leave the outdated logical component in your project. the Work Centers will be the single entry point for all activies. c) Go to transaction SOLMAN_DIRECTORY and your solutions. Create a target solution in your target SAP Solution Manager. business processes etc. b) In SAP Solution Manager Administration Workcenter deactivate any solutions that contain the managed system. you need to transfer some information from the previous SAP Solution Manager. In the future. You can do this with the transaction SOLUTION_TRANSFER.12 Solution Transfer When a new SAP Solution Manager is installed. before defining the solution. This is SMSY data and it is usually transferred from TMS or SLD into SMSY. For the latest informantion. This process has two steps: 1) Transfer systems and logical components from source to target. landscape info. 20 May 2011 .

and spreadsheet) to run a sizing project for SAP Solution Manager. You should use a three-tier landscape with transports.sap.14 Multi-Tier Landscape for SAP Solution Manager You can use should use at least a two-tier landscape for your SAP Solution Manager.sap. such as EarlyWatch. Notes for Service Delivery SAP Note 91488 1172939 1170668 Short Text SAP Support Services . and transported into the productive SAP Solution Manager after testing in the quality assurance system.15 Sizing for SAP Solution Manager There is a new sizing tool-kit for SAP Solution Manager 7.13 Service Delivery in SAP Solution Manager The SAP Solution Manager is the SAP service delivery platform. This tool-kit:  Finds hardware resources needed to implement SAP Solution Manager for a given landscape. cookbook. changes must first be developed in the development system. Solution Transfer Short Text Export Solution Link http://help. and assign them to a target solution.1.SAP Solution Manager Operation Guide b. A transport between two SAP Solution Managers is not usually necessary. if you perform classic customizing or own developments in SAP Solution Manager. patches or configuration scenarios on a test system first. It contains components (guides. as well as business process monitoring configuration data and all data in the service sessions. etc. If the test is successful. GoingLive. All services are solution-specific and can be used for all systems in the solution. 2) Transfer the data from your source solution.  Determines the corresponding SAP Solution Manager cluster configuration. as well as services which are delivered by SAP. the changes can be installed in the productive SAP Solution Manager. 2. Test new Support Packages. which can be found in the Service Marketplace. May 2011 21 . which can be performed by the customer. The usual scenarios for this case are change request management and/or service desk. Business processes are transfered.com → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Export Solution http://help. In this environment. Create logical components there.Central preparatory note Technical prerequisites for remote service delivery in SSM The role of SAP Solution Manager in Remote Service Delivery 2. This includes self-services.com → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Import Solution Import Solution 2.

1 Instguides → SAP Components → SAP Solution Manager → Release 7.sap.com/sizing-solman  2.com) Instguides → SAP Components → SAP Solution Manager → Release 7.1 Wily Introscope .16 Related Documentation Related Documentation Topic Guide/Tool Quick Link on SAP Service Marketplace (http://service.SAP Solution Manager Operation Guide Configures SAP Solution Manager and Wily IS EM to obtain better performance and scalability. Sizing for SAP Solution Manager Topic SAP Solution Manager Sizing Tool-Kit Link http://service.0 EHP 1 to SAP Solution Manager 7.sap.Installation Guide 22 May 2011 .1 Instguides → SAP Components → SAP Solution Manager → Release 7.1 Diagnostics → Installation and Configuration Detailed scenario description Support Package-specific configuration guide SAP Solution Manager Upgrade Guide Wily Introscope Installation Guide SAP Solution Manager Master Guide SAP Solution Manager Configuration Guide Upgrade SAP Solution Manager 7.

You can activate CCMS monitoring for a solution (Work Center Solution Manager Administration → Solutions → <Select a specific Solution> → Solution Settings → CCMS Monitoring of EWA).1. You can activate and deactivate CCMS monitoring for specified solutions.1 New Monitoring Infrastructure Proactive. For more information about the CCMS monitoring see http://help. you will get monitoring objects in transaction RZ20 under the monitoring tree element (MTE) “SOLMAN”. 3.SAP Solution Manager Operation Guide 3 Monitoring SAP Solution Manager Monitoring is an essential SAP technology management task.1 3.0 including Enhancement Package 2 → <language> → System Administration → Technical Operations Manual for SAP NetWeaver.sap. There is a new Solution Manager Self-Monitoring. 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 May 2011 23 . which is introduced with SAP Solution Manager 7.sap.com → SAP Solution Manager → SAP Solution Manager 7.1. Therefore you should monitor the RFC connections from the SAP Solution Manager to the managed systems with the Connection Monitoring.1 Connection Monitoring For the technical operation of the SAP Solution Manager working RFC connections to the managed systems are essential.com → SAP NetWeaver → SAP NetWeaver 7. If monitoring is active. The setup of the Connection Monitoring is also integrated in transaction SOLMAN_SETUP:  Choose the section Technical Monitoring  Choose the scenario Connection Monitoring  Follow the guided procedure 3. The Self Monitoring Setup is integrated in transaction SOLMAN_SETUP:  Choose the section Technical Monitoring  Choose the scenario SolMan Self Monitoring  Follow the guided procedure The prerequesites for using the new Self-Monitroing are:  System Preparation & Basic Configuration completed successfully  The Solution Manager itself is successfully setup as a managed system  The SAP Service Marketplace (SAP-OSS) connection is working New Monitoring Infrastructure Topic New Monitoring Infrastructure Link http://help. which is also part of the new monitoring infrastructure. which is based on the new Monitoring Infrastructure.2 CCMS Monitoring – SAP Solution Manager The CCMS Monitoring can still be used as data supplier for new monitoring infrastructure. automated monitoring is the basis for ensuring reliable operation of your SAP system environment.

SAP EarlyWatch Alert for Solutions and Service Level Reports. 3. to monitor the content of the SAP EarlyWatch Alert. which tells you if the Internet Graphics Server is available.2. Beside the usual SAP NetWeaver based Log Object.SAP Solution Manager Operation Guide 3. to have access to all important information from a central location. 3. the most important Log Object for SAP Solution Manager can be found in the following table: Log Objects in SLG1 Object /TMWFLOW/CMSCV AISDK AI_LMDB AGSGEN CCDB CRM_SOCM DIAGNAV E2E_ALERTING E2E-CA E2E-DIAG E2E-EA E2E-WA EEM LMDB RBE40 Suboject * * * * * * * * * * * * * * * Area Application Log /TMWFLOW/ Solution Manager Service Desk Landscape Management Generic Extractor Configuration and Change Database Change Request Management Solution Manager Diagnostics Navigation Monitoring and Alerting Infrastructure E2E Change Analysis Solution Manager Diagnostics E2E Exception Analysis E2E Workload Analysis Enduser Experience Monitoring Landscape Managemant Database Solution Dokumentation Assistant 24 May 2011 .4 Other Problem Analysis and Monitoring Tools 3. but you can monitor the application log also for other applications in the SAP Solution Manager. select the RFC destination and choose Environment → Switch on CCMS. You will get a separate node in transaction RZ20 for “IGS availability”. These components are basic SAP Solution Manager functionalities.4.1 CCMS Monitoring – Internet Graphics Server (IGS) Call transaction SIGS. You can receive a regular E-Mail with the reports for specific systems or solutions. SAP recommends that all customers perform centralized system monitoring of all connected managed systems in SAP Solution Manager. by using customizable transactions and threshold values to trigger the creation of the reports).3 SAP EarlyWatch Alert in SAP Solution Manager SAP EarlyWatch Alert (EWA) is a monitoring service for SAP customers that monitors SAP systems in your solution landscape. You can also use SAP Solution Manager to create service level reports that are tailored to your requirements (for example. To configure this goto System Monitoring Work Center → Configure Automatic Reports Mailing → <Select a Solution> → Edit → Create E-Mail Recipient).1 Application Monitoring Several SAP Solution Manager components use the application log in transaction SLG1.

SAP Solution Manager Operation Guide SDOK SMSY_LOG_OBJ SOLAR * * * SAP Knowledge Provider System Landscape Log Object Solution Manager Problem Analysis Tool Component SAP Solution Manager Monitor SLG1 Detailed Description Application Log May 2011 25 .

0 including Enhancement Package 2 → System Administration.1 Solution Manager Administration Work Center SAP Solution Manager 7. For more information see http://help.1 Landscape View The Landscape view provides you with an overview about all components of a single landscape entity (like system. host. …) in SAP Solution Manager. This includes detailed information about  Different system status providers  The system details in the landscape browser like  Software Components  Clients  Instances  Parameters  Database  … The Technical System Editor offers the user interface for the landscape management database (LMDM). and perform technical administration and operation tasks. This includes: 26 May 2011 . maintained and checked.sap. database. 4. 4.com → SAP NetWeaver → SAP NetWeaver 7. It is possible to  Create or maintain a technical system  Check maintenance data for consistency The RFCs of a SAP Solution Manager system to each managed systems can be created.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 components.1 is introducing a new Solution Manager Administration work center.1. You can start applications single applications for:  System Details  Maintenance of RFC Connections  Extractor Framework  Agent Framework  Change Database The applications for system status and details contain information about modelling of one technical system to verify how the system landscape is defined in SAP Solution Manager. which provides applications for:  Management of the Solution Manager Landscape  Management of the Solution Manager Infrastructure  Self Diagnosis for  Solution Manager  Managed Systems  Solution Manager Self Monitoring  Maintenance of  Solutions  Projects In different views various functionalities for administration of the SAP Solution Manager can be accessed.

1.2 Infrastructure View The Infrastructure view provides you with application for landscape independent administration applications like         Agent Administration Extractor Framework Alerting Framework Root Cause Analysis Content Wily Introscope Log Viewer Landscape Management Database (LMDB) BW Reporting The Agent Administration is the cCentral point of maintenance for all Diagnostics-Agents which are installed accorss all managed systems including:     Access to the agent administration Agent role assignment for data collection Diagnostics Agent performance metrics Exceptions from the agent infrastrucutre The Extractor Framework (EFWK) application allows you to get information about the data extraction accross all managed systems.SAP Solution Manager Operation Guide     READ RFC TMW RFC RFC for Solution Manager applications:  Login  Trusted Back RFC  With User  Trusted 4. performance and existing exceptions for the main infrastructure elements of the new alerting infrastrucutre:      Status check for Pull and Push data collection Traces of the Alert Calculation Engine Load Balancing configuration Detailed performance metrics Exceptions of the alerting infrastructure The Root Cause Analysis Content view includes:  Access to the templates for May 2011 27 . banned. This includes:       Status information (failed. inconsistent extractors) for extractors and the Resource Manager Configuration of ressource caps Detailed configuration of extractors Activation / Deactivation of single extractors Perfomance data Exception from the EFWK The Alerting Framework view gives you detailed information on the status. configuration.

the application server and the processes of which the system consists.2 Starting and Stopping When you start the SAP System.1. here you get detailed information on:     The overall status of your BW system Overall usage data and breakdown of used space per scenario Reporting Scenario Setup Detailed log information for each reporting use case with Self Checks for error analysis 4. SLR. There are different processes.3 Self Diagnosis View The Self Diagnosis view integrates the Self Diagnosis and the Diagnostics Self Check in one infrastructure. depending on the SAP system and operating system platform. 4. you start the system database.…) 4.5 Project View The Project view gives you access to all project relevant operations and setup tasks:  Creation of a project  Project Administration  Project copy 4.1.4 Solution View The Solution View gives you access to all solution relevant operations and setup tasks:  Creation of a solution  Solution Settings  Solution copy and transfer  Setup of Operation tasks (EWA. Here you can get information on the status of the managing and all managed systems. an SAP System consists of only a database and a single application server. 28 May 2011 . In the simplest case.1. The Introscope application allows you to centrally manage your CA Wily Introscope Enterprise Manager landscape:       See the status / version of the installed Introscope Enterprise Managers (EM) Perform central user administration for Import existing installations Install new EM Maintain EM configuration parameters Performance metrics BW Reporting is one of the main infrastructure components of a SAP Solution Manager System.SAP Solution Manager Operation Guide  o Configuration and Change Reporting Stores o Extractors o Work Center View Configuration o URL Framework This section is used for troubleshooting and customization and should be handled with care.

software. A backup process must ensure logical and physical consistency. such as the loss of a data center through fire. which is contained in databases.com → SAP NetWeaver → SAP NetWeaver 7. or the Microsoft Management Console under Windows. without taking the systems offline. You must ensure that backup devices are not lost along with normal data storage (separation of storage locations). The backup and restore strategy for your system landscape should be embedded in overall business requirements and incorporate your company‟s entire process flow. The backup and restore strategy must cover disaster recovery processes.  Backup your database every day You must backup the log files several times a day.  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.sap. and configuration files: May 2011 29 . see SAP Help Portal at:  http://help. using the SAP Management Console for all platforms (as of SAP NetWeaver 7. For more information. Depending on the processes you are running on the SAP Solution Manager.0 including Enhancement Package 2 → <language> → Administrator’s Guide → Technical Operations Manual for SAP NetWeaver → General Administration Tasks → Starting and Stopping SAP NetWeaver ABAP and Java. you may also need to backup external components and handle cross-system data dependencies.0).3 Backup and Restore As the SAP Solution Manager is based on SAP NetWeaver.0 including Enhancement Package 2 → <language> → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → Database Administration → <Database Name>. You should not use a backup and recovery concept for your entire system landscape and single system components just for SAP systems.SAP Solution Manager Operation Guide You can start and stop systems and instances centrally.com → SAP NetWeaver → SAP NetWeaver 7. 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. see http://help. 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. With regular full backups of your database (either offline or online). and the runtime infrastructure. not only SAP systems. see For details.sap. For details. as well as a complete set of transaction logs since the last backup. all general recommendations for an SAP NetWeaver backup and restore strategy apply. This concept must account for both the business data. 4. the System Administration Work Center in SAP Solution Manager. The main issues in a backup and recovery process are:  You must develop a backup concept in the implementation phase. 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. Consistency Technology allows you to create a consistent image (or consistent copy) of a federated system landscape.

. Some SAP Solution Manager applications may require additional background jobs. so a separate backup of this component is usually not needed. The standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP). The administrator just has to ensure that no jobs are aborted. In the standard setup.4.. You should also schedule the standard basis jobs in transaction SM36 in the SAP Solution Manager. or replacement of components made to the system landscape.1 Backup Introscope Enterprise Manager The Introscope Enterprise Manager is temporary storage for workload-related data. if you want to backup this component.3. Such tasks may be required on component level and are relevant in each scenario that uses the component. Other tasks may be relevant for certain business scenarios only. However. 4. its directories have to be backed up regularly: Wily supports only Offline backup with the following procedure  Shutdown Enterprise Manager. This depends on the frequency of such changes. You must monitor the performance of these tasks regularly. Restart Enterprise Manager 4. software upgrade of individual components. SAP recommendation: There is no backup strategy to implement for Wily SmartStor./data‟ contains all agent data The directory „.  Backup SmartStor (file backup) o o  The directory „. ABAP Standard Jobs Topic ABAP Standard Jobs Transaction / Link Transaction SM36 → Goto → Standard Jobs 4. The mapping is in the chapter scenario/component matrix above.1 Background processing in the SAP Solution Manager The background processing in SAP Solution Manager does not require regular administration. You need to back up individual components regularly. This program minimizes the administration required. this data is transferred once an hour to the BI of the SAP Solution Manager./traces‟ contains all Wily trace data. 30 May 2011 .SAP Solution Manager Operation Guide  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. to ensure that you can restore and recover them if there is a system failure.4 Periodic Tasks This chapter describes all automic tasks which run periodically to keep the application running over time. such as changes to the configuration. The SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS.

see SAP Note 894279.SAP Solution Manager Operation Guide Some of the most important jobs are: For more information on background processing in SAP Solution Manager. and a detailed list and short description of the jobs. and starts the extractors in the extractor framework. SM:SCHEDULER RDSWPJOBSCHEDULER EFWK Resource Manager E2E_EFWK_RESOURCE_MGR May 2011 31 . SAP Solution Manager Background Jobs Job name Program / Variant Recommend ed Frequency Detailed Description Starts an important job that automatically executes service sessions This job is scheduled by the diagnostics managed system setup.

reorganization jobs ST: E2E Diagnostics .5 User Management User Management is very important in SAP Solution Manager. it transfers from your system into the SAP global support backbone SAP Notes for SAP Solution Manager Background Jobs SAP Note 894279 16083 1480588 Short Text Background processing in SAP Solution Manager Standard jobs. 4. If managed systems are in a central user administration.com/diagnostics.01 SP15. Some applications expect named RFC connections.5.1 User Administration and Authentication A lot of RFC read connections are used in SAP Solution Manager. It checks if there are new messages for your support team in the SAP global support backbone. which separate functions between different users. in the managed systems and SAP Solution Manager. SAP Solution Manager is a singleclient system. in the Service Marketplace at http://service. so users can only be separated by an authorization concept. The RFC wizard generates the RFC connections and users automatically. There is a detailed description of the user management in the root cause analysis scenario. and forwards them to your 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.Information 4. you must authorize the RFC connection user used.sap. Work centers. Conversely. this user must be defined previously in the CUA system. manually. The SAP Solution Manager security guide contains a comprehensive description of users and authorization. 32 May 2011 . have been available since 7. You can use the generated users with the setup.SAP Solution Manager Operation Guide E2E BI HOUSEKEEPING E2E_HK_CONTROLLER BI Housekeeping for diagnostics (for details see note 1480588) Central job for new monitoring and alerting infrastructure SAP_ALERT_ CALCULATION_ENGINE ACE_CALCULATION_ CONTROLLER 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. If this connection is not available.BI Housekeeping .

 Service Desk: for Key User (end user). Maintain Business Partners Tool Maintain Business Partner (transaction BP) Further Documentation Tool Security Guide – SAP Solution Manager Root Cause Analysis .sap.SAP Solution Manager Operation Guide There are several user management tools (SAP & third-party systems). May 2011 33 . which always require users in both systems. 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.  Change Request Management: if the users in the Change Request Management process log on to the managed systems via SAP Solution Manager. The table below provides an overview and a short description of these user management tools. 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.5.com/diagnostics Usage Maintenance of Business Partners 4. Implementation and Customizing Distribution use Trusted RFC connections. especially authorization administration Tool for administration of portal users and roles Tool for administration of J2EE users and roles Business Partners Business partners must be defined for some specific scenarios (e. Service Desk. which always require users in both systems.com/instguides http://service.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).  Test Management: if testers have to test in managed systems.g.sap.User Administration Guide Link http://service. 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. Test Management uses Trusted RFC connections.

 Enter the required data and save. as described above. 2.  Service Desk: for Key User (end users) and processors of service desk messages see example below. 3. The system landscape consists of SAP Solution Manager and two managed systems. Select users. 2. Choose User list → Add system. as described above. as long as it is known to the mail server (Business Process Operations: for use of auto-reaction methods). as Business Partners. You can perform the following functions with this report:  List new users by comparing SAP Solution Manager and managed systems: 34 May 2011 . Create users for all end users in all three systems. check the processing status of support messages in SAP Solution Manager. 5. Create User or Business Partners Automatically To ensure that the users of the managed systems can. Create business partners for end users. Choose Edit → Create Business Partner.  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.SAP Solution Manager Operation Guide  Root Cause Analyses: user SAPSUPPORT is automatically created in the SAP Solution Manager system as well as the managed systems. You have to create all end users known to SAP Solution Manager. Create Business Partner Using Transaction BP_GEN 1. during Root Cause Analysis configuration.  Enter your user and choose change. and why. Select a system from which you want to create business partners. in the SAP Solution Manager system and the managed systems. Functions Requiring Business Partners Based on Users in SAP Solution Manager  Delivery of SAP Services: if you use Issue Management. The report AI_SDK_USER_BP_GEN determines new users in the managed systems. 1. This e-mail address can be any address. Example You want to create end users for Service Desk functionality. they must be created as users and business partners in SAP Solution Manager. in the SAP Solution Manager system. Confirm your entries. 4. for example. 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. three systems in total.

SAP Solution Manager Operation Guide  As administrator. The dialog explains in detail what you need to do. o o Recommendation Create a variant and schedule the report as a weekly background work process. you need to update your tables with new default field values for authorization objects. Recommendation Perform at least the first step. If your security policy permits it.htm 4. Procedure 1. find new managed systems for a customer and/or new users in a customer's managed systems. you must import new roles and profiles from client 000 into your productive client.sap. Choose Information. 2.5. you can automatically create or update new users and business partners in SAP Solution Manager. Update Authorizations after Support Package Upgrade Topic Profile Generator: Upgrade and First Installation Transaction SU25 Detailed Description Update Authorizations after Support Package Upgrade May 2011 35 . 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.3 Update Authorizations after Support Package Upgrade After the new installation and an update of your SAP Solution Manager system. This is especially relevant for all new authorization objects delivered with an update.com/saphelp_sm70ehp1_sp2 6/helpdata/en/85/390f6e3c534892b18f5ec42 12d0571/frameset. For more information please consult the corresponding SAP Help. check in which managed systems there are new users. As SAP partner. Call transaction SU25. in transaction SU25. Caution When you update your system. you need to update your business partners Create Users or Business Partners Automatically Tool Report AI_SDK_USER_BP_GEN Link http://help.

Create a Role in Transaction PFCG a) Choose transaction PFCG.sap. in the SAP Solution Manager and managed systems. System Administrator  Configuring query settings for all end users.5. for instance: ZSU01_PFCG. The authorization objects required in role creation are maintained using transactions. for instance. and choose Single Role. The system opens the documentation for this object in a separate window.5 Create End User Roles You need to grant authorizations for which SAP does not ship template roles. 36 May 2011 . Maintain Authorization Objects Default authorization objects delivered by SAP contain only minimal authorizations.com/solutionmanager → Media Library → How-To Documents 4.SAP Solution Manager Operation Guide 4. in the Service Marketplace. If you are not sure about the function of the authorization object. you must edit them a) Choose the Authorizations tab in the Role Maintenance. you can create a dedicated role for them.5. or customize the logon screen for Web Dynpro applications. You are asked for a transport request. When you enter a transaction in the menu tab in your role. To grant full authorization to authorization objects. See document How to Adapt a Work Center View in the Service Marketplace. b) Enter a role name in your namespace. Caution All authorization objects need to have a green traffic light. d) Go to tab menu and enter transactions SU01 and PFCG. always choose all activities. according to your needs.4 Adapt Work Center Queries End users and system administrators can adjust work centers to their needs. c) Maintain all activity values per authorization object. b) Choose Change. double-click the green line. c) Enter a description for your role. the system traces all authorization objects required for this transaction. To be able to assign the correct authorization.  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. This section describes how to create your own roles. e) Save your role. using the example of critical authorizations of transactions SU01 (User Management) and PFCG (Role Management). if you want to grant full authorization. End User See document How to Adapt a Work Center View. for instance: Full authorization for SU01 and PFCG. d) Generate the profile.

Go to Roles tab. in one of the two ways explained below. 5. 5. Choose transaction PFCG. Enter your role and choose edit. 6. Save. Enter your role. 4. Enter the user and choose edit.SAP Solution Manager Operation Guide e) To assign this profile to a user. 3. Transaction SU01 1. Create End User Roles Topic User Management Role Maintenance Transaction SU01 PFCG Detailed Description Create End User Roles Create End User Roles 4. 2. Enter the user name. Choose transaction SU01. f) Save. Go to Users tab. choose User tab. Save. add your user in the table and perform the user comparison. 3.5. 2. 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 May 2011 37 . 4. Choose the User Comparison button.6 Assign Roles to Users After you have generated profiles from roles. assign the role to your users. Transaction PFCG 1.

com/ → SAP NetWeaver → SAP NetWeaver 7. depending on the availability requirements of the implemented IT management processes. HA Setup Description Refer to the component high availability setup description. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic. all components with single point of failures must be set up with HA. You may also have requirements of your own.0 including Enhancement Package 2 → <language> → SAP Library → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → High Availability → SAP High Availability documentation 38 May 2011 .sap. Highavailability applications allow you to maximize downtime security and minimize downtimes. Collaborative business can give you a competitive advantage. such as the operating system.SAP Solution Manager Operation Guide 5 High Availability There are no general High Availability (HA) requirements for the SAP Solution Manager. if available. customers. This means integrating existing heterogeneous system landscapes to include business partners.sap. 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. Further Documentation Tool Service Marketplace – High Availability Help Portal Link http://www. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure. Otherwise explain here.com/irj/sdn/ha http://help. high availability is always focused on business applications and their related components.sdn. database. Each of the above components can be a single point of failure in this scenario. At SAP. and hardware. and suppliers. To achieve HA for the complete scenario.

SAP Solution Manager Operation Guide 6 Archiving & Data Deletion in SAP Solution Manager 6. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. and the documents attached to them. because many functions. the following objects cannot be archived using default SAP archiving mechanisms: Solution Manager projects Solution landscapes CRM transactions. The following “Solution Reporting” documents can be archived: Service Reporting System Availability Reporting System Administration Reporting Change Management Reporting Service Desk Reporting Issue und Top Issue Reporting Expert-on-Demand Reporting CRM-based transactions (incidents. etc. change requests. This report moves the document contents (files) from the built-in knowledge warehouse (KW) layer.1. In particular. May 2011 39 . change documents and issues. Service Level reports. such as test workbench and implementation projects. change requests. type and frequency of documents checked in. SAP Note 1092503 describes how to automate the archiving by a job. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents. have links to service tickets or change documents. Documents on the generic CRM tabs (transaction CRMD_ORDER) cannot be archived. can be archived using the ArchiveLink interface. Those documents (or old versions) in Solution Manager projects can be archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. Depending on the number. service ticket. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE.1 Achiving functionality in core SAP Solution Manager There is only limited archiving functionality in SAP Solution Manager 7. Archiving these CRM-based transactions would break the links to them. Service reports in solutions Service sessions such as EarlyWatch Alert reports. However. to another repository. and might cause inconsistencies. such as service tickets. e.g. see SAP Note 845433. but it is not supported in SAP Solution Manager. Monitoring data in central performance history database Test packages/test cases These objects do not usually contain a lot of data. the document attributes needed to administer the documents will be kept in SAP Solution Manager. several hundred MBs per week and project might be needed – because usually every version of a document is kept. change document). Documents in Solution Manager projects The only function which might need a lot of database space is document management in the implementation scenario. an archive. For details.) There is a generic way to archive CRM-based transactions (e. if they can still be deleted.g.

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

Test messages (service tickets created during tests) cannot be archived or deleted – see the section “Achiving functionality in core SAP Solution Manager”. but only if they have not been used in a service transaction. May 2011 41 .sap. test scripts.SAP Solution Manager Operation Guide Archiving Projects Topic SAP Solution Manager Help Link http://help.0 including Enhancement Package 2 → <language> → SAP Library → SAP NetWeaver by Key Capability → Solution Life Cycle Management by Key Capability → Test → eCATT: Extended Computer Aided Test Tool (BC-TWB-TST-ECA) → Logs → Archiving Logs Business partners Obsolete business partners can be deleted using transaction BUPA_DEL. eCATT objects (system data container.com → SAP NetWeaver → SAP NetWeaver 7. see the SAP Netweaver online documentation. They can be deleted using transaction SCAT and STWBM. They can be downloaded as .sap. They can be deleted using transaction SCAT and STWBM. Test results can be consolidated and extracted in a test report.eCATT: Extended Computer Aided Test Tool. Archiving Test Management Topic Archiving Logs (SAP Library . Test cases of type “manual” or “external application” are repository objects and can therefore be saved or stored using transport mechanisms. eCATT logs can be archived .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. which can be stored as an MS Word document. They can be deleted using transaction SECATT and STWBM. CATT objects are repository objects and can therefore be saved or stored using transport mechanisms. For more information on how to distinguish template transports and (template) project transports. as defined under “Projects”). BC-TWB-TST-ECA) Link http://help. test data container. because whenever a new template version is defined in the template project. (otherwise it would be sufficient to keep a backup copy of the project state.for more information. They can be deleted via transaction STWB_2. and when to use them.Handling Templates with SAP Solution Manager Link http://service. test configurations) are repository objects and can therefore be saved or stored using transport mechanisms.sap. CATT scripts should be migrated to eCATT.xml files. the older versions can no longer be accessed (retrieved). if you want to reapply and distribute the template to other systems. Store the contents in a template transport.com → SAP Solution Manager Templates Contents in templates should also be stored in transport requests. see: Archiving Templates Topic FAQ .

and Business Process Monitoring data).SAP Solution Manager Operation Guide 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. the BI aggregation and deletion mechanisms can be used to reduce the amount of data in the BI database. 6. root cause analysis data.reduce data volumes Deleting a service process with support message New features for RDSMOPDELETESOLUTIONS in SP08 Solution Manager: TEST_DSMOPSERSESSN_DELETE Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN Archiving reporting documents in SAP Solution Manager S 42 May 2011 .4 AP Notes for Additional/Background Information SAP Note 544295 546685 566225 638785 845433 976695 1077447 1091497 1092503 Short Text Basis message: Deletion flag status Archiving in Solution Manager (Operation) Report to delete the basis notifications with deletion flag SAP Solution Manager .

you need to check your configuration settings for new and updated configuration tasks. To do this. In the following. Agents contents (runtime + agent application: agelets) are automatically updated to the latest version after an upgrade/update of the Solution manager to which they were connected. check all activities in the Overview area in transaction SOLMAN_SETUP.  Update your authorizations.1 Guided Procedure . the system displays a configuration table with all activities you need to perform after updating your system. The goal of software change management is consistent. The system updates this list automatically. After installing/upgrading/updating SAP Solution Manager. the SMD Agents connectivity layer must be set in Maintenance Mode in the Agent Administration application. with every newly-shipped Web Dynpro application. development teams. with specified maintenance procedures. recommended) 7. you can specify here whether you have to re-execute activities that have already been executed. These functions support your project teams. After you have implemented a new support package or support package stack. All agents will be put in „sleep‟ mode waiting to reconnect when Solution Manager will be put back in Normal Operation Mode. In the Overview. and testing procedures for complex software landscapes and multiple software development platforms. May 2011 43 . If you select an entry in this table. Call transaction SOLMAN_SETUP.2 Configuration after Support Package Update After you have implemented a new support package or support package stack (SAP Enhancement Package). 3. 7.SAP Solution Manager Operation Guide 7 Software Change Management Software change management standardizes and automates software distribution. its ICF service needs to be activated. solution-wide change management. global rollouts (including localizations). and open integration with third-party products. its ICF service needs to be activated. This is especially important for the basic settings. see SAP Note 1236420. the Open Activities column shows the steps you need to execute. For instance. In case of an update. maintenance. In Basic Configuration. Prerequisites  Initially configure all basic settings using the guided procedure for the automatic basic settings configuration.1 Agents Consideration Before any new Software update in Solution Manager.2. the basic configuration should be checked in transaction SOLMAN_SETUP. this may be the activity Activate BC Sets. with every newly-shipped Web Dynpro application. You should update your basic settings configuration by:  Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP. 7. You find this Agent Administration via the Solution Manager Administration Workcenter → Infrastructure → Agent Framework.Automatic Update Configuration You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). you need to check your configuration settings for new and updated configuration tasks. This is especially important for the basic settings. and application support teams. we give an overview of both procedures. and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). 2. Using the Overview for Update Activities 1. For instance.

com SAP Solution Manager <current release> http://service. The system flags the release information with a blue information icon in front of the IMG activity.3 Ensure Basic Functions via SAP Note In order to ensure that the basic functions of SAP Solution Manager are running properly. these are only described in the note. see section Guided Procedure (transaction SOLMAN_SETUP) . The note is valid for Solution Manager 7. As soon as a new version of the note exists.1 IMG as of SP01 SAP Note 1575395 7. If these notes contain manual actions. and deleted IMG activities. in which you can automatically implement all notes included.2.SAP Solution Manager Operation Guide You can use the existing implementation project to track all information about the setup progress of your basic settings. Caution See SAP Note 1575395 for details of new IMG activities.1 SP01. Using IMG – Manual Update Configuration Short Text Changes to SAP Solution Manager 7.Automated Update Configuration.com/~sapidb /011000358700001735062008E 7. 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.sap. Call transaction SOLAR02 and choose your project. changed IMG activities.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. you should implement it with the Notes Assistant (transaction SNOTE).sap. Ensure Basic Functions Component Basic Functions Transaction SNOTE Detailed Description Check SAP Note 1552585 regularly 44 May 2011 . it is recommended to regularly check SAP note 1552585. Activate Release Notes Display release notes by choosing Release Notes. This central note includes other required notes that are extended and renewed regularly.

For further information.x Extension Add-Ons Changes to SAP Solution Manager 7. Support Packages and Patch Implementation SAP Note 394616 539977 569116 608277 631042 939897 1109650 1575395 1562694 1552585 Short Text 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 7. see the notes below.4 Support Packages and Patch Implementation The SAP Solution Manager has several software components which have their own release strategy.SAP Solution Manager Operation Guide 7.1 SP1 May 2011 45 .1 SP01: Authorizations in SAP Solution Manager system SAP Solution Manager: Basic functions 7.1 IMG as of SP01 SM 7.

The selfdiagnosis tool is highly configurable and can perform solution-specific or cross-solution self diagnosis. adjust it as required. For more information. For more information. An SAP Support Portal connection is required. You can analyze your 46 May 2011 . see the following SAP Notes: SAP Note 216952 762696 Short Text Service Data Control Center (SDCC) – FAQ Grey rating for EarlyWatch Alert 8. with transaction SOLMAN_SETUP.3 Self-Diagnosis The self-diagnosis checks the system requirements for operating SAP Solution Manager. see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS. see SAP Note 762696 “Grey rating for EarlyWatch Alert”. In this case check the RFC connections and SDCC. For more information. see SAP Note 33135: Guidelines for OSS1. check if connection SAPOSS works. 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. For more information. Therefore check regularly the the functioning of the EWA in the System Monitoring Work Center. Usually this connection is created by the SAP Solution Manager Setup. see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”. if not. if not. Check whether the distribution group is set to EWA. A self-diagnostics module is available in SAP Solution Manager. For further information. If there is something is wrong with the EWA data collection. adjust it as required. to be able to send data to SAP. You select Reports  SAP EarlyWatch Alert and a specific managed system. For more information.1   Connection to SAP In transaction SM59.2 SAP EarlyWatch Alert (EWA) SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections.SAP Solution Manager Operation Guide 8 Troubleshooting 8. you will find a small red flag or a grey icon in the overview.

For the SAP Solution Manager single solution. e. with the self-diagnosis function. to check that the master data of a solution is consistent. in the Alert Type area. in the background. The selfdiagnosis analyses run daily. e. You can customize SAP Solution Manager self-monitoring. batch jobs and performance values. The self-monitoring functionality can be found in the Solution Manager Administration Work Center → Self-Diagnosis.g.SAP Solution Manager Operation Guide SAP Solution Manager system and/or a solution. Self-Diagnosis Topic New self diagnosis in SAP Solution Manager: a quick guide Link SAP Note 1073382 May 2011 47 . to identify and solve problems.g. to check whether the problems shown by alerts have been resolved. The self-diagnostics checks the RFC Connection. You can perform a new analysis at any time. to avoid red alerts. By pressing the button “Settings” you can select which type should generate an alert and inform you. to identify SAP Solution Manager system performance problems. You can display the self-diagnosis results in various levels of detail:   For the SAP Solution Manager (cross-solution). by default.g. e.

Related Information Content Wily Introscope User Guide Wily Introscope Installation for SAP Customers Link http://service. The main logging catogries and tracing locations can be found in the following table. Ensure that the version of your agent is the same as the version of the source on your SAP Solution Manager.SAP Solution Manager Operation Guide 8.admin. Connect to your CA Wily Introscope WebView via web browser – usually o http://hostname:8081/webview/jsp/login. CA Wily Introscope Enterprise Manager may not be active.smd.server.* com.sap.com/diagnostics SAP Note 797147 8.5 Logging and Tracing Logging and tracing is essential for analyzing problems in the SAP Solution Manager Java-based parts.sap. This can be configured by using the log configuration function of the SAP NetWeaver Adminstrator under Problem Management  Logs and Traces  Log Configuration. If the logon screen of your WebView does not appear. Check that CA Wily Introscope Enterprise Manager receives information from CA Wily Introscope Agent.4 CA Wily Introscope To check whether the CA Wily Introscope is running properly: 1.jsp. For more information please consult the Wily Introscope User Guide or SAP Note 797147 “Wily Introscope Installation for SAP Customers”.com/saphelp_nwpi71/helpdata/en/44/9 8320f33bf60d6e10000000a114a6b/content. Verify in SMD → Diagnostics Setup → Managed Systems → Introscope Agent for the system in which the Introscope Agent is running 3. which includes also a detailed troubleshooting section.sap. 2. The equal sign icon indicates that the version is up to date.sap. 4. Logging Categories Logging Category /Applications/AdminConsole/* Comment AdminConsole Tracing Locations Tracing Location com.htm 48 May 2011 . The Java-based parts all use the standard logging of AS Java.* Comment AdminConsole SMDServer Related Information Content SAP Netweaver Administrator Link http://help.sup.

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

Sign up to vote on this title
UsefulNot useful