Description
Solution Operation GuideSAP Solution Manager 7.1 Operations Guide Document Version 2.01 - June 14, 2012 SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany www.sap.com © Copyright 2012 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, 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 1 Required Agent Versions .................1 2.........18 2....................15 2.....................................11 Moving from SAP Solution Manager Transation DSWP to Work Centers ...........15 Sizing for SAP Solution Manager ..1 3.14 Multi-Tier Landscape for SAP Solution Manager ...16 Related Documentation .................................9 2 SAP Solution Manager and Technical System Landscape ........................17 2..................2 SAP Solution Manager and Trusted RFC ..........2 Global Definitions .......7 2.....10.8 2............10 Release Restrictions .10....3 System and Landscape Directory (SLD)..................11 CA Wily Introscope ......10 SAP Solution Manager complementary Components . 27 4 June 2012 .............................SAP Solution Manager Operation Guide Contents 1 Getting Started..................7 History of Changes .................11 SAP NetWeaver Search and Classification (TREX) ..................5 2.....................22 2...............2 3..................25 3...............25 4 Management of SAP Solution Manager ...............................................................13 Service Delivery in SAP Solution Manager ...... 24 3.................................21 2.................................22 2.................................................................................................3...................22 2...............3................................24 Connection Monitoring .............................................................................4 Adjust Upgrade of Managed System .......24 CCMS Monitoring – SAP Solution Manager ...............3........................................................ Landscape Management Database (LMDB) and SMSY...........................10............1................17 2.................................................1 1............2 2...............13 Business Warehouse (BW) Client Strategy ........1 2......................13 Root Cause Analysis ............................................2 2......6 2.........14 Managed Systems Configuration ......3 2..........1 SAP EarlyWatch Alert in SAP Solution Manager ...............10............ 7 1.10 SAP Solution Manager built-in Software Components .21 2.............12 2........3.9 2...25 Other Problem Analysis and Monitoring Tools ..............25 Application Monitoring ........................................12 Upgrade to SAP Solution Manager 7.....12 Installation ..................................... 10 2..................................3 New Monitoring Infrastructure ...............................2 3.......1...............20 2............12 Solution Transfer ..1 3................4 2......................................................23 3 Monitoring SAP Solution Manager ..11 Internet Graphics Server (IGS) ......3 3....................1.14 SAP Solution Manager Configuration ..................24 CCMS Monitoring – Internet Graphics Server (IGS) ..............1...........................................3 SAP Solution Manager ........ ......................................................................37 Create End User Roles ..................1....................3 4............................53 Agents Consideration ....................3 Setup related persistent data (Solution Manager ABAP) ........................6................6.2 7..1 4..............................5 Monitoring and Alerting Infrastructure configuration data on Diagnostics Agent side .......3 6.......................................38 4...............................................................1 Starting and Stopping ................39 4...... 50 6 Archiving & Data Deletion in SAP Solution Manager ...........6.6.....1 Periodic Tasks . 51 6.............................................45 4.........................................5......................29 Solution View .............6.....................................1.5........38 4............1 4.......33 User Administration and Authentication ..........52 SAP Notes for Additional/Background Information ....................44 4.......4................2 4.............31 4........6.5.............51 SAP Solution Manager Extended Archiving Functionality52 Alternative Storage & Deletion Strategies ......................................................1 6...27 Landscape View ............49 4........................49 5 High Availability......43 4.................1 Achiving functionality in core SAP Solution Manager ............................................33 Create Users and Business Partners for End Users ..4 4......28 Self Diagnosis View ..................3 4........1.....2 Managed system settings affected by Managed System Configuration .........3 4............................................34 Update Authorizations after Support Package Upgrade ............ 55 June 2012 5 ......................................................................55 Guided Procedure ...................................................37 Assign Roles to Users ...................31 4.........Automatic Update Configuration .............6 User Management ...........................................1 4..............6 Introscope Host Adapter persistent data ....8 Diagnostics Agent .....................1.....6.........43 4.......29 Backup and Restore .29 4.......5.......1 Extractors....................1 7......2 6...................6....48 4.....................6.............4 4......................5 4.......55 Configuration after Support Package Update ...............................SAP Solution Manager Operation Guide 4......1............5.....................................................................2 4.4 7..38 4.........................30 Backup Introscope Enterprise Manager ........2.................................5 Solution Manager Administration Work Center ...................4 4..36 Adapt Work Center Queries.....3.9 E2E Trace Analysis ........................................5.......6 Solution Manager clean-up tasks for no longer relevant managed systems .................6.7 Metrics stored in BW ....................................5 4................29 Project View ..........................27 Infrastructure View ...................................4 Setup related persistent data (Solution Manager Java) ........................31 Background processing in the SAP Solution Manager.....2 4......................................................39 4.....10 End-user Experience Monitoring ...............55 7 Software Change Management ............. .......2 Ensure Basic Functions via SAP Note ..............4 8....................................61 Related Information ............................................... 61 6 June 2012 ..................SAP Solution Manager Operation Guide 7.................2 SAP Reference IMG – Manual Update Configuration ....1 9.........2 8........................................................................................4 8............2......................................................................................................56 Support Packages and Patch Implementation ............................3 8............................................1 8................................5 9....................58 CA Wily Introscope ..................................................58 SAP EarlyWatch Alert (EWA) ..............................58 Self-Diagnosis ... 58 9 Appendix .............61 8 Troubleshooting .....................56 7............60 Related Guides ......57 Connection to SAP ..................................3 7.......60 Logging and Tracing ... Component A component is the smallest individual unit considered within the Solution Development Lifecycle. SAP CRM. Business Scenario From a micro-economic perspective. 24 hours a day.1 Global Definitions SAP Application An SAP application is an SAP software solution that serves a business area such as SAP ERP. June 2012 7 . so you will sometimes also need other guides. components are produced. SAP PLM. A business scenario is an entity which can be implemented separately. installed and maintained separately. Typically. Technically. and SAP Library. and running your SAP applications at peak performance. that we recommend customers create for their production operations. delivered. Target Groups Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist 1. a business scenario is a cycle which comprises several interconnected logical processes in time. and reflects the customer‟s prospective course of business. This guide is the starting point for managing your SAP applications and maintaining and running them optimally. or other) for each cycle. and lists the tools that you can use to perform them. and possibly other third-party systems. About this Guide Designing. SAP SCM. a business scenario needs at least one SAP application (SAP ERP. Technical Infrastructure Guide. such as the Master Guide.SAP Solution Manager Operation Guide 1 Getting Started This guide does not replace the daily operations handbook. has never been more vital to your business success than today. Check regularly for updates of the Application Operations Guide. SAP SRM. It contains information about various tasks. implementing. It also provides references to the documentation required for these tasks. or SAP SCM. a business scenario includes several company departments and business partners. This note describes preparatory measures and additional information for the Upgrade of SAP Solution Manager 7. Only database-independent problems are dealt with here.1 Upgrade of SAP Solution Manager 7.SAP Solution Manager Operation Guide Important SAP Notes SAP Note Number 1462137 Title Add.Basic functions 7.1 Solution Manager: Components for Messages 706705 Overview on the available documentation for SAP Solution Manager 7.Basic functions 7.1 Comment This note describes problems that may occur when you upgrade the system and provides you with information on how to solve them. This SAP Note is the central correction note of SAP Solution Manager 7.1 Support Package 5. Implement the following note to ensure the basic functions in SAP Solution Manager.1 SP2 SAP Solution Manager . 8 June 2012 .1 Support Package 3 This SAP Note is the central correction note of SAP Solution Manager 7.Basic functions SP1 1584162 SAP Solution Manager .Basic functions 7.1 SP4 SAP Solution Manager . info.Basic functions 7. This note is valid for Solution Manager 7.1 SP5 Supplements to Solution Manager 7.1 1613410 1633725 1652693 1577909 1583348 Documentation: SAP Solution Manager 7. about Upgrading to SAP Solution Manager 7. upgrade shutdowns and long runtimes.1 You want to create a customer message related to SAP Solution Manager on the appropriate component.0 to SAP Solution Manager 7.This usually takes the form of references to other notes.1 (installation) to the stack that is currently available 1552585 SAP Solution Manager .1 SP1.1 Update of SAP Solution Manager 7.1 Support Package 2 This SAP Note is the central correction note of SAP Solution Manager 7. The aim of this note is to prevent data loss.1 SP3 SAP Solution Manager .0 Enhancement Package 1 to SAP Solution Manager 7.1 Support Package 4 This SAP Note is the central correction note of SAP Solution Manager 7. 00 2.2 History of Changes Make sure you use the current version of the Application Operations Guide.SAP Solution Manager Operation Guide 1.01 Important Changes First version of the SAP Solution Manager Operations Guide for SAP Solution Manager 7.1. The following table provides an overview of the most important changes in previous versions.00 2.1 Revision for SAP Solution Manager 7.1 SP05 Added chapter 4. Document Versions Document Version 1. The current version of the Application Operations Guide is on SAP Service Marketplace at http://service.7 Metrics stored in BW June 2012 9 .sap.6.com/instguides → SAP Components → SAP Solution Manager → Release 7. 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 business scenarios used. Software Comonents Detailed Information Support Package levels of SolMan installations / upgrades SAP Note 781448 10 June 2012 . This guide refers mostly to SAP Solution Manager-specific tasks and procedures.sap. It includes several applications and scenarios to support the Application Lifecycle Management (ALM) and Run SAP like a Factory ensuring business continuity.com/ → Application Lifecycle Mgmt → SAP Solution Manager http://service. and the SAP Solution Manager can be found in the SAP Service Marketplace or the SAP Help Portal.1 SAP Solution Manager SAP Solution Manager is the central tool for managing your customer solution landscape.1 http://service.sap.SAP Solution Manager Operation Guide 2 SAP Solution Manager and Technical System Landscape 2.sap.sap.sap. You can use the following software components in your system. depending on the scenarios you actually use. accelerating innovation. Cental Information Sources Topic SAP Solution Manager Application Lifecycle Management (ALM) Run SAP like a Factory SAP Help Portal Ramp-Up Knowledge Transfer Business Process Blueprinting Link http://service.com/instguides → SAP Solution Manager → Release 7. Application Lifecycle Management (ALM) and and Run SAP like a Factory (RSLAF) adresses this challenge with an integrated ITIL-based approach.1 → Additional Guides 2.com/alm http://service.com/runfactory http://help. Other software components can be added to SAP Solution Manager.sap.com/instguides → SAP Solution Manager → Release 7. More information about Application Lifecycle Management (ALM).2 SAP Solution Manager built-in Software Components The SAP Solution Manager comprises several software components. and Run SAP like a Factory (RSLAF).1 → Additional Guides. More information about the new BPB (business process blueprinting) functionality can be found in the Service Marketplace and http://service. so the tasks and procedures for a standard SAP NetWeaver system generally also apply to SAP Solution Manager. It is based on an SAP NetWeaver platform and includes the SAP CRM add-on.com/rkt-solman → SAP Solution Manager 7. Another central place for useful information about the supported functions is the RampUp Knowledge Transfer page for the SAP Solution Manager.com/solutionmanager http://service.sap. sap. 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 SAP Note 1285941 SAP Note 1122497 SAP Note 1131270 SAP Note 1034902 2.com/saphelp_nwes70/helpdata/en/ 46/c96a575b590e5be10000000a1553f7/content.3. You can administrate your Web Dynpro Java IGS via a Web Interface.3 SAP Solution Manager complementary Components 2.com → SAP NetWeaver → SAP NetWeaver 7. The server can be administrated in transaction SIGS. Administration of TREX Topic SAP Netweaver Search and Classification Administration of TREX TREXADMIN Transaction Link http://help.2 SAP NetWeaver Search and Classification (TREX) For specific scenarios the SAP NetWeaver Search and Classification (TREX) is used.htm June 2012 11 .g.3. e. in EarlyWatch Alert reports.1 Internet Graphics Server (IGS) The Internet Graphics Server (IGS) generates various graphics or charts in some areas.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.0 including Enhancement Package 2 → <language> → Technical Operations Manual → Administration of Standalone Engines → Search and Classification (TREX) http://help.SAP Solution Manager Operation Guide Third-Party Integration There are several standard interfaces to third-party tools. 1 was released. For more information about SAP NetWeaver technology.sap.sap.1 is based on the technology of SAP NetWeaver 7.sap.1.3 CA Wily Introscope CA Wily Introscope is a software component. see http://sdn. SAP Notes SAP Note 1480419 Short Text Release Restrictions for SAP Solution Manager 7.3. This information is collected in SAP Note 1480419 “Release Restrictions for SAP Solution Manager 7. SAP Note 797147 “Wily Introscope Installation for SAP Customers” includes a detailed FAQ document as an attachment. All new SAP Solution Manager Installations are on Unicode. SAP recommends migrating to Unicode.SAP Solution Manager Operation Guide Notes for TREX SAP Note 1466273 Short Text Using full-text searches in SAP Solution Manager 2.com/diagnostics 2.1“. 12 June 2012 . until the customer has completed the Unicode conversion. 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.4 Release Restrictions When SAP Solution Manager 7. a number of restrictions still applied to the productive use of certain functions.1 2.com/diagnostics → Installation and Configuration. which collects performance and other system-related data maily from non-ABAP components in your system landscape. For customers that have upgraded from previous releases of SAP Solution Manager 7. and are not yet on Unicode.1 is an SAP system based on Application Server ABAP (AS ABAP) and Application Server Java (AS Java). This document also includes a detailed troubleshooting section. SAP Solution Manager 7. SAP recommends running SAP Solution Manager on Unicode.0 including Enhancement Package 2. If this is not possible.com/irj/sdn/netweaver. SAP will support the SAP Solution Manager on non-Unicode. see the installation guide on SAP Service Marketplace at http://service. For information about installation.5 Installation SAP Solution Manager 7. and this increases your administration effort. This is SAP’s recommendation. you must maintain users separately.1”) includes an overview of software components and support package levels that must be installed in your SAP Solution Manager system.com/instguides → SAP Components → SAP Solution Manager → Release 7.sap. Solution Manager Diagnostics. as user access is more restricted.SAP Solution Manager Operation Guide SAP Solution Manager Installation Topic SAP NetWeaver Releases SAP Solution Manager Installation Unicode Link http://sdn. BW in a Separate Client on SAP Solution Manager In this scenario. There is no technical benefit.7 Business Warehouse (BW) Client Strategy BW provides important reporting functions to the various SAP Solution Manager processes. June 2012 13 .1 To upgrade to SAP Solution Manager 7. as user access is more restricted.com/instguides http://service. you must maintain users separately.1. This scenario provides increased security. However. SAP Note 1462137 (“Additional information on upgrading to SAP Solution Manager 7.sap. e. For further information please consult the SAP Solution Manager 7. BW activities are conducted in a separate client on the SAP Solution Manager system. and isolates the BW activities for solution life cycle management from the data on a production BW instance. BW in a Separate Client on SAP Solution Manager In this scenario. you require seperate upgrade programs for the ABAP and the Java parts of your SAP Solution Manager system.g.sap.1 Link http://service.sap. BW activities are conducted in a separate client on the SAP Solution Manager system.6 Upgrade to SAP Solution Manager 7. and this increases your administration effort. SAP Solution Manager Upgrade Topic SAP Solution Manager 7.com/irj/sdn/netweaver http://service.1 Upgrade Guide Additional information on upgrading to SAP Solution Manager 7. This makes configuration simpler.1 SAP Note 1462137 2. This scenario provides increased security. In general there are two main BW options when planning your system landscape. There is no technical benefit. However. BW in the Productive SAP Solution Manager Client In this scenario. 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. BW is used in the same productive client as SAP Solution Manager.com/unicode 2.1 Upgrade Guide. 9 SAP Solution Manager Configuration After installing the SAP Solution Manager.1 Solution Manager 7. This quickly configures all main settings in a guided procedure. in the SAP Reference IMG (transaction SPRO). 14 June 2012 .1: Root Cause Analysis pre-requsites Root Cause Analysis End-to-End Root Cause Analysis Wiki in the SDN Note / Link SAP Note 1478974 SAP Note 1483508 http://service. The functionality is also called End-toEnd Diagnostics or SAP Solution Manager Diagnostics. 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.sdn. Root Cause Analysis Topic Diagnostics in SAP Solution Manager 7. performing a root cause analysis. You can initially configure your basic settings with the basic settings wizards.8 Root Cause Analysis You need information about the basic requirements and possible limitations of end-to-end root cause analysis.sap. All settings for this Web Dynpro application are made during the installation of SAP Solution Manager. The configuration of the tool is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP). configures the following sub-scenarios: o System Monitoring: monitors the status of managed systems.1. for example.sap.com/diagnostics http://wiki. the basic configuration should be performed. using the SAP EarlyWatch Alert. connecting to SAP.com/wiki/display/TechOps/RCA_Home 2. All activities in this wizard are linked to the corresponding Customizing activities in the standard basic settings configuration.SAP Solution Manager Operation Guide BW Client Strategy Topic Where is best to set up BW for the Solution Manager Note / Link SAP Note 1487626 2. 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. o Self-Monitoring: monitors the status of SAP Solution Manager. The automatic configuration is accessed via the Solution Manager Configuration Work Center or it can be called by transaction SOLMAN_SETUP. delivered with SAP Solution Manager 7. The SAP Solution Manager is the central location for the management and setup of the connected managed systems. BW templates and Business Objects jobs. Problem & Request Management o Change Request Management Business Process Monitoring Business Process Change Analyzer Measurement Platform Set Up o Choose all systems for which you later want to perform your SUGEN benchmark measurement.sap.sap. so you must be able to access those systems.com/wiki/display/SMSETUP/Home 2. Data Volume Management SAP Test Accelerator and Optimizer Further Configuration o Test Management o Quality Gate Management o Change and Transport System (CTS+) For more information about configuration. see the Customizing for SAP Solution Manager (transaction SPRO) and the configuration guide on SAP Service Marketplace at http://service. where you can initially configure.10 Managed Systems Configuration To ensure that all the systems can be managed centrally.com/instguides → SAP Components → SAP Solution Manager → Release 7. BW queries. you can monitor process chains. Actual information about SAP Solution Manager Setup & Configuration can also be found in the respective SDN Wiki: http://wiki. the SAP Solution Manager should be connected to all systems in the system landscape.1 http://wiki.sap. Interface Channel Monitoring: BI Monitoring: BI monitoring configuration. the settings for BI Monitoring.sap.1.com/wiki/display/SMSETUP/Home Basic Configuration Topic SAP Reference IMG Configuration Guide SAP Solution Manager Setup & Configuration Wiki Transaction / Link Transaction SPRO http://service.sdn. or subsequently change. All the systems which are connected to the SAP Solution Manager are called managed systems. Connection Monitoring: monitors connections between managed systems.SAP Solution Manager Operation Guide o o o o 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. PI Monitoring: monitors XI (SAP Exchange Infrastructure) and PI (SAP Process Integration) systems which allow for data exchange between managed systems.com/instguides → SAP Components → SAP Solution Manager → Release 7. Using it. IT Service Management o Incident.sdn. June 2012 15 . If required. you connect systems to SAP Solution Manager: 1.System Landscape Setup Guide 16 June 2012 . red or yellow signals in the following columns require you to take action: . Databases are retrieved automatically from LMDB and cannot be created or maintained. connect the system to an SLD to minimize the effort for maintenance. If incorrect system data is displayed.RFC Status (only ABAP): Red: Repair the RFC connections. The technical systems. create the technical system manually. choose the Database tab page. 5.If the system that you want to connect is not contained in the technical system list. Quality Gate Management and Charm. or databases. are displayed. Check the status of the configuration: Gray. In this step.1 . To create systems manually. . choose the System/Scenario/Database Operations pushbutton. To connect a standalone database. which are known to the SAP Solution Manager System Landscape Directory. Notes for Managed Systems SAP Note 1472465 Short Text SAP Solution Manager 7. choose the Technical System tab page. 3. Select the system you want to configure: To connect a single system. Follow the instructions in the respective Guided Procedure. 4. To do so.Plugin Status (only ABAP): Red: Install the recent version of the following software components on the managed system: ST-PI ST-API . To connect a double (ABAP and Java) stack system. In SAP Solution Manager this is usually ensured by using a trusted RFC with the same user.Automatic Configuration Status: Grey: Perform missing steps of the managed system configuration Red: Repeat failed steps of the managed system configuration . choose the Configure Scenario or Configure System pushbutton. The users should only have the authorizations which are assigned to them in the managed systems. Misuse of the communication connection must be prevented. A few managed systems should also be connected to the quality SAP Solution Manager or development SAP Solution Manager. you maintain the technical system or scenario in the system landscape. respectively. 2. for example delete and set up the RFC destination again .SAP Solution Manager Operation Guide To be able to use all cross functionality. for testing purposes. connect all managed systems to the productive Solution Manager at least. scenarios or databases. respectively. technical scenarios. such as Change Analysis. choose the Technical Scenario tab page. The configuration of managed systems for the basic scenarios is in the guided procedure (transaction SOLMAN_SETUP). You go to a Guided Procedure.To make sure that the technical systems or technical scenarios are correctly known to SAP Solution Manager. select an item and choose the Show Details link. and choose Create. the creation of new users and the resetting of passwords must be strictly controlled. In particular. Diagnostics Agent • You can use any version of the Diagnostics Agent (already installed agents do not need to be updated) • The agent applications are updated automatically from the Solution Manager • For new installations use the latest available version of the diagnostics agent from http://service.SAP Solution Manager Operation Guide 2. This can be done using transaction SOLMAN_SETUP. Required Agent Versions Topic Installing Package SAPHOSTAGENT Using the SAP Host Agent Auto Upgrade Feature Note / Link SAP Note 1031096 SAP Note 1473974 2. 2) Trusted relationships between systems where one system accepts the authentication of the other system. Trusted relations between systems can be configured on different levels: 1) Trusted relationships from a system.2 SAP Solution Manager and Trusted RFC The trusted RFC connections are setup between the SAP Solution Manager and the connected managed systems. in the client system. June 2012 17 . 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. within these services. so that you can update the Host Agent centrally.sap. This kind of trusted relationship is usually realized by putting the login data of a service user of the server system. Examples: a) The login data of a display user (with limited authorization) of the transport management system (TMS) is entered in the RFC destination of the TMS. if the user management for the SAP Solution Manager is as restrictive as for all other productive systems.1 Agents for managed systems SAP Host Agent • You need to install at least patch level 55 of the SAP Host Agent 7.10. which offers services to another system (client). The trusted RFC connections can be used and are acceptable from a security point of view.1 Required Agent Versions On the Managed System you need different agents for Root-Cause Analysis as well as for the Technical System Monitoring.sap. The naming conventions for users must be consistent across 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.10.com/swdc Support Packages and Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP HOST AGENT 7.com/swdc Browse Download Catalog SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.20. • The installation files are available from http://service. This is described in SAP Note 1473974. SAP Solution Manager does not manage connections between managed systems. with the same user ID as in the source system. no login data is provided in the RFC destination. with which applications (authorization field RFC_TCODE). RFC connections between SAP systems can also be secured by “secure network communication” (SNC). The trusted RFC can be used for 1b) and 2d). This is how to set up landscape data management: SLD The technical system data is gathered by self-registration of technical systems in the System Landscape Directory (SLD). the landscape needs to be taken into account. c) An SAP system accepts an SSL client certificate in an https connection. the login data of a service user is entered in the RFC connection. with the authorization field RFC_EQUSER set to “Y” and the field RFC_USER empty or set to the dummy value „ (inverted comma). The SLD contains information on installable software (updated via the SAP Service Marketplace) and technical system data. and logs its user in. The trusted RFC connection has the following security attributes: Simple navigation (via Single Sign-On) from RFC client to RFC server. In case 2d). 18 June 2012 . Note for Trusted RFC SAP Note 128447 Short Text Trusted/Trusting Systems 2.3 System and Landscape Directory (SLD). A user has his personal authorizations in the SAP Solution Manager system as well as in the connected managed systems. but the option “same user“ is selected. The users who want to use such a trusted RFC connection. Since landscape data is mostly gathered outside the SAP Solution Manager system. it is also possible to restrict which users (authorization field RFC_USER) in the RFC client system can use the connection. b) An SAP backend system accepts the SAP Logon Ticket of the SAP NetWeaver Portal. Landscape Management Database (LMDB) and SMSY Many functions in SAP Solution Manager rely on up-to-data landscape data. where the login token is entered. must have authorization for the authorization object S_RFCACL. and the authorizations in the RFC client system can be limited by the authorization object S_ICF.SAP Solution Manager Operation Guide Examples: a) A Windows client accepts a Kerberos ticket of a Windows domain server. finds the user and logs it in with user ID. The RFC server system accepts the authorization by the RFC client system. and logs on the user in the target system. but also for various other applications. Through the authorizations of the service user for the authorization object S_RFCACL. as in a normal RFC destination. The main landscape management building blocks are the System Landscape Directory (SLD). This is especially true for system maintenance. 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).10. d) An RFC server system accepts the trusted RFC token und logs the user in to the target system. mostly sent by these systems using data suppliers. to restrict user access rights to RFC connections. and the Landscape Management Database (LMDB). In case 1b). This allows patches and stacks to be downloaded to a central location provided by the SLM.SAP Solution Manager Operation Guide Note: We recommend running one central SLD on an existing Java stack in the landscape. which is fulfilling the above mentioned requirements and use this for the SAP Solution Manager. the home of Product Systems and Logical Components stays SMSY. LMDB shares the CIM model with the SLD. which use this data include SAP Solution Manager Diagnostics. This central SLD can be outside or inside SAP Solution Manager. which consume landscape data.40 – SLD: SAP NetWeaver 7. the LMDB replaces it.0 – SLD: EHP1 for SAP NetWeaver 7. on an SAP NetWeaver PI system.1.1. implementing the SLD in SAP Solution Manager's own Java stack would be an alternative to connecting all SLD data suppliers.1. via data supplier forwarding. without user interaction. Note: If a local SLD was used in existing SAP Solution Manager environments before 7. 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. directly or indirectly.3 – SLD: not supported not supported not supported SP6. built-in repository for all Solution Manager applications. Best practice is a central SLD in which all systems register themselves. data for technical systems is replicated to SMSY. For compatibility reasons. Monitoring and Alerting. Patch 5 SP9 all SPs all SPs all SPs If your central SLD does not fulfill these requirements. In Solution Manager 7. This forwarding has to be configured manually for each productive system. LMDB The data from the SLD is synchronized into the SAP Solution Manager Landscape Management Data Base (LMDB) introduced with Solution Manager 7. so that all SLD data provided by the productive SLD is propagated into LMDB.0 – SLD: SAP NetWeaver 7. Data can be enriched manually in the LMDB.1. BI Monitoring and PI Monitoring. LMDB becomes the home of all Technical System data. it is also possible to forward the landscape data to an SLD. and then to SAP Solution Manager. LMDB is a central. Note: For landscapes with no productive Java stack outside SAP Solution Manager (as would be used for PI and Web Dynpro Java).0 – SLD: EHP2 for SAP NetWeaver 7. e. If productive SLDs are in use.1 – SLD: EHP1 for SAP NetWeaver 7.g. their landscape information can be forwarded to a central SLD.2 – SLD: SAP NetWeaver 7. SAP’s SLD Recommendation Manual maintenance of the system landscape without SLD is not recommended. A central SLD on SAP Solution Manager also allows the maintenance optimizer functions to use the Software Lifecycle Manager (SLM) features. plus the automatic content synchronization mechanism. With release 7.1 – SLD: SAP NetWeaver 7. Applications. SMSY Numerous other applications keep using transaction SMSY for the time being. depending on the June 2012 19 . choose the product version you have upgraded to. 20 June 2012 .SAP Solution Manager Operation Guide conditions above. c) Go to transaction SOLMAN_DIRECTORY and your solutions. All SLD data is propagated to LMDB automatically. Prerequisites You have: SAP Solution Manager projects and solutions in productive use SLD attached to SAP Solution Manager Procedure 1.sdn. 2. and choose Installed Product Version. Adjust Product Version a) To adjust the new product version for your upgraded managed system. c) Save. go to transaction SMSY and choose your system. If you monitor business processes in this system.com/irj/sdn/nw-sld http://www.sap. This section explains how to adjust your settings for this system in the SAP Solution Manager.sap. For more information see SAP Note 669669. Note: When you implement or update a scenario.sdn. and replace your outdated logical component with your new logical component.4 Adjust Upgrade of Managed System You have upgraded a managed system. deactivate the business process monitoring sessions for it. b) In SAP Solution Manager Administration Workcenter deactivate any solutions that contain the managed system. SLD and LMDB Topic SLD planning guide SLD Topology Updating the SAP Component Repository in the SLD 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 Link https://www. you must update the Component Repository Content (CR Content) in the System Landscape Directory (SLD).10. In the dialog box.Configure the central SLD as the source of the Landscape Management Database (LMDB) in Solution Manager. b) Go to Header Data tab.com/irj/scn/weblogs?blog=/p ub/wlg/17579 SAP Note 669669 2. Adjust Logical Component a) Create a new logical component for your upgraded managed system. to it. Additional steps are: a. June 2012 21 . landscape info. for documentation purposes.12 Solution Transfer When a new SAP Solution Manager is installed. so there is no need to transfer it manually. and assign them to a target solution. all new SAP Solution Manager developments have been done exclusively with a focus on Work Centers. 2) Transfer the data from your source solution. This is SMSY data and it is usually transferred from TMS or SLD into SMSY. For the latest informantion. after all landscape components have been created. Solution Concept and Design Short Text SAP Solution Manager: Solution for SAP Service Delivery Deactivation of transactions SOLUTION_MANAGER and DSWP Note / Link SAP Note 1117389 SAP Note 1541013 2. service plans. before defining the solution. This process has two steps: 1) Transfer systems and logical components from source to target. b.1 this transaction was deactivated. You can do this with the transaction SOLUTION_TRANSFER. In an implementation project. you may want to leave the outdated logical component in your project. As the transaction has become outdated with the SAP Solution Manager 7.01 SP15.11 Moving from SAP Solution Manager Transation DSWP to Work Centers With the introduction of Work Centers with SAP Solution Manager 7. Therefore. Adjust Upgrade of Managed System Topic Solutions in SAP Solution Manager Solution Directory Transaction SM_WORKCENTER SOLMAN_DIRECTORY Detailed Description Adjust Upgrade of Managed System Adjust Upgrade of Managed System 2. as well as business process monitoring configuration data and all data in the service sessions. the Work Centers will be the single entry point for all activies. please review SAP Note 1541013. Business processes are transfered. you need to transfer some information from the previous SAP Solution Manager. In the past transaction DSWP (or SOLUTION_MANAGER) served as the primary entry point fir Operations and Operations Setup within SAP Solution Manager. the solutions must now be created via the Solution Manager Administration Work Center (Solutions). such as issues. See the SAP Solution Manager Solution Concept and Design document in the Service Marketplace.SAP Solution Manager Operation Guide d) Activate your business process monitoring session and solutions again. Create logical components there. In the future. business processes etc. Create a target solution in your target SAP Solution Manager. connect all managed systems to the productive Solution Manager at least. Notes for Service Delivery SAP Note 91488 1172939 1170668 Short Text SAP Support Services . such as Change Analysis. This includes self-services. changes must first be developed in the development system. which can be performed by the customer. A few managed systems should also be connected to the quality SAP Solution Manager or development SAP Solution Manager.sap.com → Application Lifecycle Mgmt → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Import Solution Import Solution 2.1. In this environment. Test new Support Packages. for testing purposes. the changes can be installed in the productive SAP Solution Manager. GoingLive. This tool-kit: Finds hardware resources needed to implement SAP Solution Manager for a given landscape.13 Service Delivery in SAP Solution Manager The SAP Solution Manager is the SAP service delivery platform. If the test is successful. and transported into the productive SAP Solution Manager after testing in the quality assurance system. Quality Gate Management and Charm.14 Multi-Tier Landscape for SAP Solution Manager You can use should use at least a two-tier landscape for your SAP Solution Manager. To be able to use all cross functionality. The usual scenarios for this case are change request management and/or service desk.15 Sizing for SAP Solution Manager There is a new sizing tool-kit for SAP Solution Manager 7. Determines the corresponding SAP Solution Manager cluster configuration.SAP Solution Manager Operation Guide Solution Transfer Short Text Export Solution Link http://help. A transport between two SAP Solution Managers is not usually necessary. All services are solution-specific and can be used for all systems in the solution. such as EarlyWatch. as well as services which are delivered by SAP. 22 June 2012 .sap. It contains components (guides. and spreadsheet) to run a sizing project for SAP Solution Manager.Central preparatory note Technical prerequisites for remote service delivery in SSM The role of SAP Solution Manager in Remote Service Delivery 2. etc. cookbook. if you perform classic customizing or own developments in SAP Solution Manager. 2. which can be found in the Service Marketplace. patches or configuration scenarios on a test system first.com → Application Lifecycle Mgmt → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Export Solution http://help. You should use a three-tier landscape with transports. sap. Sizing for SAP Solution Manager Topic SAP Solution Manager Sizing Tool-Kit Link http://service.sap.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.0 EHP 1 to SAP Solution Manager 7.com/sizing-solman 2.SAP Solution Manager Operation Guide Configures SAP Solution Manager and Wily IS EM to obtain better performance and scalability.com) Instguides → SAP Components → SAP Solution Manager → Release 7.Installation Guide June 2012 23 .16 Related Documentation Related Documentation Topic Guide/Tool Quick Link on SAP Service Marketplace (http://service.1 Instguides → SAP Components → SAP Solution Manager → Release 7.1 Instguides → SAP Components → SAP Solution Manager → Release 7.1 Wily Introscope . 1. which is also part of the new monitoring infrastructure.0 including Enhancement Package 2 → <language> → System Administration → Technical Operations Manual for SAP NetWeaver. 3.2 CCMS Monitoring – SAP Solution Manager The CCMS Monitoring can still be used as data supplier for new monitoring infrastructure.1 3. with the following content: Rating of EWA for each <SID> Rating of each SL Report Successful download of data into the SDCC 24 June 2012 . 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. which is based on the new Monitoring Infrastructure.com → SAP NetWeaver → SAP NetWeaver 7. For more information about the CCMS monitoring see http://help. There is a new Solution Manager Self-Monitoring. Under this MTE there is another one for each active solution.com → Application Lifecycle Mgmt → SAP Solution Manager → SAP Solution Manager 7.1. You can activate and deactivate CCMS monitoring for specified solutions. You can activate CCMS monitoring for a solution (Work Center Solution Manager Administration → Solutions → <Select a specific Solution> → Solution Settings → CCMS Monitoring of EWA).SAP Solution Manager Operation Guide 3 Monitoring SAP Solution Manager Monitoring is an essential SAP technology management task. you will get monitoring objects in transaction RZ20 under the monitoring tree element (MTE) “SOLMAN”. automated monitoring is the basis for ensuring reliable operation of your SAP system environment. 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. Therefore you should monitor the RFC connections from the SAP Solution Manager to the managed systems with the Connection Monitoring.sap.1 Connection Monitoring For the technical operation of the SAP Solution Manager working RFC connections to the managed systems are essential. which is introduced with SAP Solution Manager 7.sap. If monitoring is active.1 New Monitoring Infrastructure Proactive.1. 3 CCMS Monitoring – Internet Graphics Server (IGS) Call transaction SIGS. You can receive a regular E-Mail with the reports for specific systems or solutions. You can also use SAP Solution Manager to create service level reports that are tailored to your requirements (for example.1 Application Monitoring Several SAP Solution Manager components use the application log in transaction SLG1. To configure this goto System Monitoring Work Center → Configure Automatic Reports Mailing → <Select a Solution> → Edit → Create E-Mail Recipient). SAP EarlyWatch Alert for Solutions and Service Level Reports. but you can monitor the application log also for other applications in the SAP Solution Manager. 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 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 June 2012 25 .1.2 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. These components are basic SAP Solution Manager functionalities. You will get a separate node in transaction RZ20 for “ IGS availability”. to have access to all important information from a central location.3. SAP recommends that all customers perform centralized system monitoring of all connected managed systems in SAP Solution Manager. 3.3 Other Problem Analysis and Monitoring Tools 3. select the RFC destination and choose Environment → Switch on CCMS. Beside the usual SAP NetWeaver based Log Object. which tells you if the Internet Graphics Server is available. 3.SAP Solution Manager Operation Guide 3. by using customizable transactions and threshold values to trigger the creation of the reports). to monitor the content of the SAP EarlyWatch Alert. SAP Solution Manager Operation Guide RBE40 SDOK SMSY_LOG_OBJ SOLAR * * * * Solution Dokumentation Assistant SAP Knowledge Provider System Landscape Log Object Solution Manager Problem Analysis Tool Component SAP Solution Manager Monitor SLG1 Detailed Description Application Log 26 June 2012 . host. …) in SAP Solution Manager.1 is introducing a new Solution Manager Administration work center.1 Solution Manager Administration Work Center SAP Solution Manager 7.com → SAP NetWeaver → SAP NetWeaver 7.1. For more information see http://help. 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. 4.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. 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). maintained and checked.0 including Enhancement Package 2 → System Administration.1 Landscape View The Landscape view provides you with an overview about all components of a single landscape entity (like system. and perform technical administration and operation tasks. database. This includes: June 2012 27 . 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. 4. 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. SAP Solution Manager Operation Guide READ RFC TMW RFC RFC for Solution Manager applications: Login Trusted Back RFC With User Trusted 4. configuration.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.1. 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. performance and existing exceptions for the main infrastructure elements of the new alerting infrastrucutre: Status check for Pull and Push data collection Traces of the Alert Calculation Engine Load Balancing configuration Detailed performance metrics Exceptions of the alerting infrastructure The Root Cause Analysis Content view includes: Access to the templates for 28 June 2012 . This includes: Status information (failed. banned. June 2012 29 . the application server and the processes of which the system consists.1. depending on the SAP system and operating system platform. In the simplest case.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. 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. 4. SLR. an SAP System consists of only a database and a single application server.1. Here you can get information on the status of the managing and all managed systems. There are different processes.…) 4.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.3 Self Diagnosis View The Self Diagnosis view integrates the Self Diagnosis and the Diagnostics Self Check in one infrastructure. you start the system database.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.2 Starting and Stopping When you start the SAP 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. 3 Backup and Restore As the SAP Solution Manager is based on SAP NetWeaver.sap.com → SAP NetWeaver → SAP NetWeaver 7. all general recommendations for an SAP NetWeaver backup and restore strategy apply. This concept must account for both the business data. as well as a complete set of transaction logs since the last backup. You must ensure that backup devices are not lost along with normal data storage (separation of storage locations). Depending on the processes you are running on the SAP Solution Manager. see http://help.com → SAP NetWeaver → SAP NetWeaver 7. The main issues in a backup and recovery process are: You must develop a backup concept in the implementation phase. you may also need to backup external components and handle cross-system data dependencies. 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 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. 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.sap.SAP Solution Manager Operation Guide You can start and stop systems and instances centrally. using the SAP Management Console for all platforms (as of SAP NetWeaver 7. 4. software. A backup process must ensure logical and physical consistency. without taking the systems offline. the System Administration Work Center in SAP Solution Manager. see SAP Help Portal at: http://help. such as the loss of a data center through fire.0). You should not use a backup and recovery concept for your entire system landscape and single system components just for SAP systems. see For details. or the Microsoft Management Console under Windows. For details. which is contained in databases. not only SAP systems. and the runtime infrastructure. 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. For more information. With regular full backups of your database (either offline or online). and configuration files: 30 June 2012 .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. Consistency Technology allows you to create a consistent image (or consistent copy) of a federated system landscape. The backup and restore strategy for your system landscape should be embedded in overall business requirements and incorporate your company‟s entire process flow.0 including Enhancement Package 2 → <language> → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → Database Administration → <Database Name>. The backup and restore strategy must cover disaster recovery processes. it is possible to restore a crashed database to any point in time before the crash. You need to back up individual components regularly. to ensure that you can restore and recover them if there is a system failure. this data is transferred once an hour to the BI of the SAP Solution Manager. Some SAP Solution Manager applications may require additional background jobs.4 Periodic Tasks This chapter describes all automic tasks which run periodically to keep the application running over time. The administrator just has to ensure that no jobs are aborted. Restart Enterprise Manager 4. 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. if you want to backup this component. You should also schedule the standard basis jobs in transaction SM36 in the SAP Solution Manager.. such as changes to the configuration. In the standard setup. Backup SmartStor (file backup) o o The directory „.3.1 Backup Introscope Enterprise Manager The Introscope Enterprise Manager is temporary storage for workload-related data./data‟ contains all agent data The directory „. You must monitor the performance of these tasks regularly. 4. However. software upgrade of individual components.4. The standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP). This program minimizes the administration required. June 2012 31 . This depends on the frequency of such changes.1 Background processing in the SAP Solution Manager The background processing in SAP Solution Manager does not require regular administration. The SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS. SAP recommendation: There is no backup strategy to implement for Wily SmartStor.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. ABAP Standard Jobs Topic ABAP Standard Jobs Transaction / Link Transaction SM36 → Goto → Standard Jobs 4./traces‟ contains all Wily trace data. its directories have to be backed up regularly: Wily supports only Offline backup with the following procedure Shutdown Enterprise Manager. or replacement of components made to the system landscape. The mapping is in the chapter scenario/component matrix above. so a separate backup of this component is usually not needed. and starts the extractors in the extractor framework. see SAP Note 894279. and a detailed list and short description of the jobs.SAP Solution Manager Operation Guide Some of the most important jobs are: For more information on background processing in SAP Solution Manager. 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. SM:SCHEDULER RDSWPJOBSCHEDULER EFWK Resource Manager E2E_EFWK_RESOURCE_MGR 32 June 2012 . sap. There is a detailed description of the user management in the root cause analysis scenario.com/diagnostics. It checks if there are new messages for your support team in the SAP global support backbone. have been available since 7. in the managed systems and SAP Solution Manager. manually. You can use the generated users with the setup. this user must be defined previously in the CUA system. The SAP Solution Manager security guide contains a comprehensive description of users and authorization. SAP Solution Manager is a singleclient system. reorganization jobs ST: E2E Diagnostics .01 SP15. The RFC wizard generates the RFC connections and users automatically.Information 4. so users can only be separated by an authorization concept. Work centers. It is important that the users used are not prevented from getting information from the managed systems or sending data to SAP Solution Manager. you must authorize the RFC connection user used. Conversely. 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.1 User Administration and Authentication A lot of RFC read connections are used in SAP Solution Manager.5 User Management User Management is very important in SAP Solution Manager. in the Service Marketplace at http://service.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.5. If managed systems are in a central user administration. June 2012 33 . 4. and forwards them to your SAP Solution Manager. Some applications expect named RFC connections. which separate functions between different users.BI Housekeeping . If this connection is not available. Service Desk: for Key User (end user). Service Desk.com/solmaninstguides http://service. Test Management uses Trusted RFC connections.5.SAP Solution Manager Operation Guide There are several user management tools (SAP & third-party systems). which always require users in both systems.g.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.com/diagnostics Usage Maintenance of Business Partners 4.sap. Maintain Business Partners Tool Maintain Business Partner (transaction BP) Further Documentation Tool Security Guide – SAP Solution Manager Root Cause Analysis . which always require users in both systems. Implementation and Customizing Distribution use Trusted RFC connections. 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. 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. 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. 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. Test Management: if testers have to test in managed systems. Change Request Management).User Administration Guide Link http://service.sap. The table below provides an overview and a short description of these user management tools. 34 June 2012 . Confirm your entries. they must be created as users and business partners in SAP Solution Manager. Service Desk: for Key User (end users) and processors of service desk messages see example below. as described above. Enter the required data and save. 2. Select users. You can perform the following functions with this report: List new users by comparing SAP Solution Manager and managed systems: June 2012 35 . as described above. Enter your user and choose change. for example. Choose User list → Add system. 2. 5. 1. as long as it is known to the mail server (Business Process Operations: for use of auto-reaction methods). This e-mail address can be any address. The report AI_SDK_USER_BP_GEN determines new users in the managed systems. 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. Create User or Business Partners Automatically To ensure that the users of the managed systems can. during Root Cause Analysis configuration. Create users for all end users in all three systems. as Business Partners. check the processing status of support messages in SAP Solution Manager. and why. 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. Example You want to create end users for Service Desk functionality.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. in the SAP Solution Manager system and the managed systems. in the SAP Solution Manager system. 3. Create business partners for end users. 4. Functions Requiring Business Partners Based on Users in SAP Solution Manager Delivery of SAP Services: if you use Issue Management. The system landscape consists of SAP Solution Manager and two managed systems. three systems in total. You have to create all end users known to SAP Solution Manager. Create Business Partner Using Transaction BP_GEN 1. Select a system from which you want to create business partners. 2. o o Recommendation Create a variant and schedule the report as a weekly background work process. find new managed systems for a customer and/or new users in a customer's managed systems. Procedure 1.sap. The dialog explains in detail what you need to do. Call transaction SU25. As SAP partner.htm 4.5. Update Authorizations after Support Package Upgrade Topic Profile Generator: Upgrade and First Installation Transaction SU25 Detailed Description Update Authorizations after Support Package Upgrade 36 June 2012 .3 Update Authorizations after Support Package Upgrade After the new installation and an update of your SAP Solution Manager system. If your security policy permits it. For more information please consult the corresponding SAP Help.SAP Solution Manager Operation Guide As administrator. This is especially relevant for all new authorization objects delivered with an update. 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. you need to update your tables with new default field values for authorization objects. you can automatically create or update new users and business partners in SAP Solution Manager.com/saphelp_sm70ehp1_sp2 6/helpdata/en/85/390f6e3c534892b18f5ec42 12d0571/frameset. Recommendation Perform at least the first step. you must import new roles and profiles from client 000 into your productive client. you need to update your business partners Create Users or Business Partners Automatically Tool Report AI_SDK_USER_BP_GEN Link http://help. in transaction SU25. check in which managed systems there are new users. Caution When you update your system. Choose Information. double-click the green line. 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. b) Choose Change. You are asked for a transport request. End User See document How to Adapt a Work Center View.sap. Maintain Authorization Objects Default authorization objects delivered by SAP contain only minimal authorizations. or customize the logon screen for Web Dynpro applications. b) Enter a role name in your namespace. The authorization objects required in role creation are maintained using transactions. according to your needs. e) Save your role. the system traces all authorization objects required for this transaction. If you are not sure about the function of the authorization object. Caution All authorization objects need to have a green traffic light.5. June 2012 37 .SAP Solution Manager Operation Guide 4. you must edit them a) Choose the Authorizations tab in the Role Maintenance. To grant full authorization to authorization objects. in the Service Marketplace. for instance. and choose Single Role. if you want to grant full authorization. Create a Role in Transaction PFCG a) Choose transaction PFCG. you can create a dedicated role for them. d) Go to tab menu and enter transactions SU01 and PFCG. The system opens the documentation for this object in a separate window.5. in the SAP Solution Manager and managed systems.com/solutionmanager → Media Library → How-To Documents 4. using the example of critical authorizations of transactions SU01 (User Management) and PFCG (Role Management). To be able to assign the correct authorization. always choose all activities. for instance: ZSU01_PFCG. c) Maintain all activity values per authorization object.4 Adapt Work Center Queries End users and system administrators can adjust work centers to their needs. When you enter a transaction in the menu tab in your role. This section describes how to create your own roles. for instance: Full authorization for SU01 and PFCG. d) Generate the profile.5 Create End User Roles You need to grant authorizations for which SAP does not ship template roles. See document How to Adapt a Work Center View in the Service Marketplace. System Administrator Configuring query settings for all end users. c) Enter a description for your role. in one of the two ways explained below. assign the role to your users. Enter the user name.5. Enter your role and choose edit. 4. Choose transaction PFCG. choose User tab.6 Solution Manager clean-up tasks for no longer relevant managed systems 4. add your user in the table and perform the user comparison. f) Save. 6. Choose the User Comparison button. Go to Roles tab. 4. which is no longer relevant within this Solution Manager system. 5. Transaction SU01 1.1 Extractors While being logged-in as Solution Managed Administrator.6 Assign Roles to Users After you have generated profiles from roles. Transaction PFCG 1.6. Go to Users tab. Save. 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 4. Create End User Roles Topic User Management Role Maintenance Transaction SU01 PFCG Detailed Description Create End User Roles Create End User Roles 4. 2. 5. Choose transaction SU01. Save. 3.SAP Solution Manager Operation Guide e) To assign this profile to a user. start transaction sm_workcenter and navigate to the “Solution Manager Administration Work Center” and “Landscape”. Enter your role. Enter the user and choose edit. and start the “Extractor Framework” application. Switch to the chang e mode in order to select and delete all 38 June 2012 . 3. Select in the list the Managed System. 2. SAP Solution Manager Operation Guide Extractor entries. The housekeeping will also take care to delete other related data (E2E Resources, etc). 4.6.2 Managed system settings affected by Managed System Configuration The modifications of managed systems done by SOLMAN_SETUP automatic activities can be reverted manually: SSO configuration (ie deleting imported certificated from the managed stack) JVM parameters (ie removing the JVM parameters added by the setup) HTTP logging configuration (ie reverting log settings) User creation (ie deleting created users) All actions done by SOLMAN_SETUP automatic activities are logged in detail when expanding the execution details of each activity, providing the necessary info to undo them manually (cf example screenshot below) 4.6.3 Setup related persistent data (Solution Manager ABAP) Clean-up of Generic storage entries: Generic storage contains several configuration data for solman_setup. In case one or more managed system become obsolete, clean-up of related configuration data might be necessary. The following configuration ids correspond to managed system configuration: AGS_MNGD_RFC June 2012 39 SAP Solution Manager Operation Guide AGS_USER_MNGD_ADMIN AGS_USER_MS_SUPPORT AGS_USER_MS_WILYAGT AGS_USER_MS_SUPPORTJ AGS_USER_MS_SM_COLLJ DIAG_MNGD_JVM RCA_SETUP The tool that lets viewing/editing configuration data can be accessed via transaction SOLMAN_SETUP_ADMIN. When you call the transaction SOLMAN_SETUP_ADMIN, the user should click on „Generic Storage Admin UI‟ button as shown below: Then the field „Configuration id‟ that can be seen below is used to display the relevant configuration id. The user should select each of the configuration ids listed above in order to clean-up unnecessary data. An example will be shown below for the configuration AGS_MNGD_RFC. 40 June 2012 SAP Solution Manager Operation Guide As the selected configuration id is storing store configuration data for each of the existing managed systems, you will see a long list with many “extra key” combinations as shown above. You need to find the configuration data corresponding to the managed system to be deleted. This can be achieved either by using scroll bars or by using filter link on the right hand side of the table: Then the user needs to click on the relevant configuration by selecting one line in the list, and then click on “Edit” button as below: June 2012 41 the only way of re-defining the configuration data is to run again the associated activities in solman_setup transaction.SAP Solution Manager Operation Guide Then depending on the configuration data. This operation must be done very carefully as after saving the configuration data. as shown below: In case the entries were removed by mistake. the user should select all the listed parameters and then click on “Remove entries” button in order to delete the configuration entirely. the whole cofiguration will be deleted. there might be only one or multiple parameters: as the objective is to clean-up the whole configuration data. it would be possible to revert the change by clicking on “Undo Remove” button in case save operation did not take place yet. just below the help window as shown below: 42 June 2012 . and in such a case. Save button can be seen on top of the screen. navigate to the “Applications Configuration” tab.global. See screenshot below: 4.sap. selecting the agent application „com.6. MAI/ISMetricCollectionDefinition. This data can be accessed and deleted using the Agent Administration application. like shown below: June 2012 43 .4 Setup related persistent data (Solution Manager Java) Persistent data with a global scope (ie shared by several RCA applications) is kept in the Diagnostics Agent repository of the Solution Manager java stack. corresponding to the Managed system that is no longer relevant.SAP Solution Manager Operation Guide The clean-up for generic storage configurations can be done by using the same transaction and selecting each of the configuration ids listed at the beginning of this chapter.agent.configuration‟ application and deleting all properties prefixed with the SID of the managed system. press the “Remove” button for each of the following three XML files: MAI/ISAgentMapping.5 Monitoring and Alerting Infrastructure configuration data on Diagnostics Agent side Using the Agent Adminstration UI.6. by navigating to the Applications Configuration tab. selecting the scope of the agent(s) belonging to the managed system.application.xml and MAI/MetricCollectionDefinition. select the application e2emai in the tree and finally in the scope field pick-up the Agent/Host name.xml.xml. 4.smd. In case some Monitoring and Alerting related configurations have been performed. 6. selecting the resource „SapAgentConfig.sap.smd.SAP Solution Manager Operation Guide 4. This file can be accessed and deleted using the Agent Administration application. selecting the scope of the agent(s) belonging to the managed system. See screenshot below: 44 June 2012 .wilyhost‟. by navigating to the Applications Configuration tab. selecting the agent application „com.xml‟.6 Introscope Host Adapter persistent data The introscope Host Adapter xml configuration file generated during setup is kept in the Diagnostics Agent repository of the Solution Manager java stack.agent.application. and deleting the resource (“Remove” button). SAP Solution Manager Operation Guide 4.1 some metrics are kept in so called twin InfoCubes. Info Cube 0CCMARCH 0CCMARSH 0CCMSAEXE 0CCMSATPH 0SMD_ADCH 0SMD_ADCD 0SMD_EA1H 0SMD_EA1D 0SMD_EA2H SAP Solution Manager 7.6. Note that this procedure will configure the so called E2E BI Housekeeping framework to delete the metrics. With Solution Manager 7. For the metrics stored in these Cubes no Managed system specific delete procedure is possible.7 Metrics stored in BW As described in SAP note 1480588 a set of InfoCubes are currently filled with Managed system related metrics in the context of Root Cause Analysis.1 (ST710) X X X X X X X X X June 2012 45 . Therefore the following procedure description has to be applied iteratively for each of the below listed Cubes. Select each time the InfoCube from which you have to delete metrics next. - Select one entry as a template by clicking on the line Menu “Table Entry” “Create with Template” 46 June 2012 .SAP Solution Manager Operation Guide 0SMD_EA2D 0SMD_EA3H 0SMD_EA3D 0SMD_EA4H 0SMD_EA4D 0SMD_EA5H 0SMD_EA5D 0SMD_KACH 0SMD_KACD 0SMD_PE2H 0SMD_PE2D 0SMD_PI2H 0SMD_PI2D Procedure description: - X X X X X X X X X X X X X Start Transaction SE16. Select Table E2E_BI_DELETE. I. The value helps (F4) of the fields SIGN and SELOPTION will tell you more about the available parameters and options. Select the SIGN I for including the selection statement. enter 0SMD_LSID as characteristic under INFOOBJECT. Save the second line of the new Deletor. 2). select the allowed lifetime by reducing the value in $DELTA=N$ Example: In this use case you would to delete data for the specific system after 2 day. enter the System Name as value of the LOW Parameter and choose SIGN and SELOPTION appropriately. for choosing the system. - - - Create a second entry for the new deletor for the second characteristic you want to select In this example. June 2012 47 . For selecting one particular system. Therefore set the Parameter LOW to value $DELTA=1$ Save the first entry of your new Deletor. the Select Option should be “EQ” to include the value under “LOW” into the selection. For the new Deletor ID. Make sure that you use the same Deletor ID you used in the previous step Enter the required selection criteria.E. This will be the ID of the new Deletor you are going to create. The first selection statement in the new Deletor should be for 0CALDAY.SAP Solution Manager Operation Guide - - Choose a Deletor ID that has not yet been assigned (e.g. you should also remove the Deletors that you just created manually.SAP Solution Manager Operation Guide Now. by removing the associated JVM parameters. verify that for your new deletor. Click on the little icon just beside the “Full Host Name” entry corresponding to the no longer relevant Diagnostics Agent (hostname) and select “Delete Offline agent entry”. The entries in the table E2E_BI_DELETE could like this Remember to repeat the above described steps for all listed InfoCubes. 48 June 2012 . ST: E2E Diagnostics . using different Deletor IDs. once the Data has been cleaned from the InfoCubes (after the nightly execution of the Housekeeping job). Remove Offline Agent entry In the Agent Administration UI press the “Show offline agents” button and look -up the Agent that has been uninstalled. else follow the recommendations to also “un-install” the Wily Introscope Byte Code Adapter.6.BI Housekeeping . For further recommendations concering the uninstallation also refer to the associated chapter in the document referenced in SAP note 1365123.Information ST: E2E Diagnostics .BI Housekeeping .8 Diagnostics Agent Uninstall Diagnostics Agent The Diagnostics Agent (Instance) should be uninstalled. Especially make sure for Java Managed systems that the system no longer exists. Finally. in case the associated Logical (or Physical) host that run previously the no longer relevant Managed system is operating no other Managed components.Information SAP Note 1480588 4. June 2012 49 . Results of script executions are not deleted when a script is deleted. Deleting the technical scenario deletes the scenario in LMDB and the trace extractor for this scenario.SAP Solution Manager Operation Guide 4. 4. The Script Excutions performed in the scope of End-user Experience Monitoring are available (jump-in from EEM possible) only 1 day for those who are rated green and 1 week for the red rated ones.6. Delete first all scripts of this/these technical scenario(s) and after that delete the technical scenario(s) itself.9 E2E Trace Analysis No action is needed as Business Transactions and the associated collected server side traces. Deleting a script will remove the script from EEM Repository and as well from all Diagnostics Agents it was deployed on. Just the assignment is deleted.6. Certain Business Transactions could be retained on demand. identify the technical scenarios the system is assigned to.10 End-user Experience Monitoring Frist. by selecting them in E2e Trace Analsysi and placing a “lock”. which are older than 60 days (configureable in the Options tab) get deleted each 24 hours at the time the E2E Trace Analysis tool is started. at the time the housekeeping is running. but not the script it was assigned to. customers. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure. such as the operating system.sdn.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 50 June 2012 . depending on the availability requirements of the implemented IT management processes. 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. At SAP. all components with single point of failures must be set up with HA. Highavailability applications allow you to maximize downtime security and minimize downtimes. if available. You may also have requirements of your own. high availability is always focused on business applications and their related components. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic. To achieve HA for the complete scenario.sap.sap.SAP Solution Manager Operation Guide 5 High Availability There are no general High Availability (HA) requirements for the SAP Solution Manager. Further Documentation Tool Service Marketplace – High Availability Help Portal Link http://www.com/irj/sdn/ha http://help.com/ → SAP NetWeaver → SAP NetWeaver 7. and hardware. Each of the above components can be a single point of failure in this scenario. and suppliers. HA Setup Description Refer to the component high availability setup description. database. Otherwise explain here. Collaborative business can give you a competitive advantage. This means integrating existing heterogeneous system landscapes to include business partners. Service Level reports.1 Achiving functionality in core SAP Solution Manager There is only limited archiving functionality in SAP Solution Manager 7. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. In particular. to another repository. change requests. Service reports in solutions Service sessions such as EarlyWatch Alert reports. the document attributes needed to administer the documents will be kept in SAP Solution Manager. type and frequency of documents checked in. Those documents (or old versions) in Solution Manager projects can be archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. can be archived using the ArchiveLink interface. if they can still be deleted.g. Monitoring data in central performance history database Test packages/test cases These objects do not usually contain a lot of data. change documents and issues. an archive. Depending on the number. several hundred MBs per week and project might be needed – because usually every version of a document is kept. SAP Note 1092503 describes how to automate the archiving by a job. and the documents attached to them.SAP Solution Manager Operation Guide 6 Archiving & Data Deletion in SAP Solution Manager 6. 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 Notes for Archiving SAP Note 546685 1092503 Short Text Archiving in Solution Manager (Operation) Archiving reporting documents in SAP Solution Manager June 2012 51 . Documents in Solution Manager projects The only function which might need a lot of database space is document management in the implementation scenario. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. e. However. This report moves the document contents (files) from the built-in knowledge warehouse (KW) layer.1. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents. such as service tickets. the following objects cannot be archived using default SAP archiving mechanisms: Solution Manager projects Solution landscapes CRM transactions. but only for those which refer to a Solution Manager project (a function also delivered with the ET extension package). with the report SOLMAN_DOCU_VERSION_ARCHIVE. Solutions Solutions can be deleted from SAP Solution Manager using the functionality in transaction DSWP. (otherwise it would be sufficient to keep a backup copy of the project state. have been created. A customer can save the objects using other methods (put objects in transport requests using migration functions.SAP Solution Manager Operation Guide 6. the older versions can no longer be accessed (retrieved). if you want to reapply and distribute the template to other systems. or by directly executing report RDSMOPDELETESOLUTIONS. and when to use them. which carry an attribute for the solution. this function will only store the business process structure and all related documents. use SAP content server for knowledge warehouse documents. Similar functions are available to archive documents which are added to the CRM transaction tabs (e. Archiving Projects Topic SAP Solution Manager Help Link http://help. shipped with ST400 SP13 .3 Alternative Storage & Deletion Strategies Although generic archiving is not supported by most scenarios in SAP Solution Manager. The report SOLMAN_DOCU_VERSION_DEL can then delete the archived documents. The extension package requires a separate license. Projects SAP Solution Manager projects can be stored in a transport using transaction SOLAR_PROJECT_ADMIN. keep backup of whole system before data deletion). archives the documents (or old versions) in Solution Manager projects. If CRM transactions such as service tickets. Documents on the generic CRM tabs cannot be archived using this function. For more information on how to distinguish template transports and (template) project transports. as defined under “Projects”). it is not part of the SAP Solution Manager core functionality. Without a valid license.2 SAP Solution Manager Extended Archiving Functionality The extension package “Extended Traceability” (ET).sap. all objects produced within that solution (service sessions. Store the contents in a template transport.com → Application Lifecycle Mgmt → SAP Solution Manager Templates Contents in templates should also be stored in transport requests.g. They can be deleted from SAP Solution Manager using report RDSMOPREDUCEDATA. change documents). and generally available to customers with ST400 SP15. When deleting a solution. deletion of the solution might not be possible (as it is not possible to delete the related CRM transactions). because whenever a new template version is defined in the template project. reports etc. However. 6. there are several functions to reduce the amount of data in the database.) will be deleted – if this is possible. see: 52 June 2012 . Solution Manager projects can also be deleted using transaction SOLAR_PROJECT_ADMIN. these reports will not work. it will not save referenced data. store reports on separate file server. such as CRM transactions or test workbench items. Service reports in solutions SAP EarlyWatch Alert and service level reports could be stored on a separate file server. which can be stored as an MS Word document. Data extracted to BI If data from SAP Solution Manager has been extracted for Business Intelligence (reporting on EWA raw data.for more information.Handling Templates with SAP Solution Manager Link http://service.sap. Test cases of type “manual” or “external application” are repository objects and can therefore be saved or stored using transport mechanisms.4 544295 546685 566225 SAP Notes for Additional/Background Information Short Text Basis message: Deletion flag status Archiving in Solution Manager (Operation) Report to delete the basis notifications with deletion flag SAP Note June 2012 53 .sap. They can be deleted via transaction STWB_2. test scripts. BC-TWB-TST-ECA) Link http://help. root cause analysis data. They can be downloaded as . Test results can be consolidated and extracted in a test report. CATT scripts should be migrated to eCATT. and Business Process Monitoring data).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. see the SAP Netweaver online documentation. eCATT logs can be archived . but only if they have not been used in a service transaction. They can be deleted using transaction SECATT and STWBM. 6.xml files. They can be deleted using transaction SCAT and STWBM.com → SAP NetWeaver → SAP NetWeaver 7. Test messages (service tickets created during tests) cannot be archived or deleted – see the section “Achiving functionality in core SAP Solution Manager”. SMSY data. Archiving Test Management Topic Archiving Logs (SAP Library . test configurations) are repository objects and can therefore be saved or stored using transport mechanisms. the BI aggregation and deletion mechanisms can be used to reduce the amount of data in the BI database. eCATT objects (system data container. They can be deleted using transaction SCAT and STWBM. CATT objects are repository objects and can therefore be saved or stored using transport mechanisms.SAP Solution Manager Operation Guide Archiving Templates Topic FAQ .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.eCATT: Extended Computer Aided Test Tool. CPH monitoring data. test data container. SAP Solution Manager Operation Guide 638785 845433 976695 1077447 1091497 1092503 SAP Solution Manager .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 54 June 2012 . This is especially important for the basic settings. check all activities in the Overview area in transaction SOLMAN_SETUP.1 Agents Consideration Before any new Software update in Solution Manager. and testing procedures for complex software landscapes and multiple software development platforms. you need to check your configuration settings for new and updated configuration tasks. its ICF service needs to be activated. These functions support your project teams. and open integration with third-party products.2. You should update your basic settings configuration by: Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP. with every newly-shipped Web Dynpro application. see SAP Note 1236420. with every newly-shipped Web Dynpro application. The system updates this list automatically.Automatic Update Configuration You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). global rollouts (including localizations). 7. 2. 3.SAP Solution Manager Operation Guide 7 Software Change Management Software change management standardizes and automates software distribution. recommended) 7.2 Configuration after Support Package Update After you have implemented a new support package or support package stack (SAP Enhancement Package). you need to check your configuration settings for new and updated configuration tasks. For instance. For instance. To do this. In the following. 7. Using the Overview for Update Activities 1. Update your authorizations. the Open Activities column shows the steps you need to execute. this may be the activity Activate BC Sets. Call transaction SOLMAN_SETUP. In case of an update. This is especially important for the basic settings. maintenance. In Basic Configuration. development teams. the basic configuration should be checked in transaction SOLMAN_SETUP. its ICF service needs to be activated. you can specify here whether you have to re-execute activities that have already been executed. the system displays a configuration table with all activities you need to perform after updating your system. and application support teams. After installing/upgrading/updating SAP Solution Manager.1 Guided Procedure . After you have implemented a new support package or support package stack. solution-wide change management. In the Overview. The goal of software change management is consistent. the SMD Agents connectivity layer must be set in Maintenance Mode in the Agent Administration application. 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. Prerequisites Initially configure all basic settings using the guided procedure for the automatic basic settings configuration. June 2012 55 . You find this Agent Administration via the Solution Manager Administration Workcenter → Infrastructure → Agent Framework. we give an overview of both procedures. All agents will be put in „sleep‟ mode waiting to reconnect when Solution Manager will be put back in Normal Operation Mode. If you select an entry in this table. with specified maintenance procedures. and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). 1 SP05. you should implement it with the Notes Assistant (transaction SNOTE). these are only described in the note.2.Automated Update Configuration. Call transaction SOLAR02 and choose your project.com → Application Lifecycle Mgmt → SAP Solution Manager <current release> http://service. If these notes contain manual actions. This central note includes other required notes that are extended and renewed regularly. Using IMG – Manual Update Configuration Short Text Changes to SAP Solution Manager 7. As soon as a new version of the note exists. it is recommended to regularly check SAP note 1652693. and deleted IMG activities. The system flags the release information with a blue information icon in front of the IMG activity. Recommendation We recommend that you update your basic settings using the automated guided procedure.sap.1 IMG as of SP01 SAP Note 1575395 7.2 SAP Reference IMG – Manual Update Configuration You can update basic settings configuration and scenario-specific configuration using the SAP Reference IMG (transaction: SPRO). changed IMG activities.sap. in which you can automatically implement all notes included.3 Ensure Basic Functions via SAP Note In order to ensure that the basic functions of SAP Solution Manager are running properly. Activate Release Notes Display release notes by choosing Release Notes.com/~sapidb /011000358700001735062008E 7.SAP Solution Manager Operation Guide You can use the existing implementation project to track all information about the setup progress of your basic settings. see section Guided Procedure (transaction SOLMAN_SETUP) . The note is valid for Solution Manager 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. Ensure Basic Functions Component Basic Functions Transaction SNOTE Detailed Description Check SAP Note 1652693 regularly 56 June 2012 . Caution See SAP Note 1575395 for details of new IMG activities. 1 IMG as of SP01 SM 7. For further information.4 Support Packages and Patch Implementation The SAP Solution Manager has several software components which have their own release strategy. 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.1 SP1 June 2012 57 .1 SP01: Authorizations in SAP Solution Manager system SAP Solution Manager: Basic functions 7.SAP Solution Manager Operation Guide 7. see the notes below.x Extension Add-Ons Changes to SAP Solution Manager 7. adjust it as required. 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.1 Connection to SAP In transaction SM59. if not. you will find a small red flag or a grey icon in the overview. see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”. You select Reports SAP EarlyWatch Alert and a specific managed system.3 Self-Diagnosis The self-diagnosis checks the system requirements for operating SAP Solution Manager.SAP Solution Manager Operation Guide 8 Troubleshooting 8. For more information. if not. For more information. Usually this connection is created by the SAP Solution Manager Setup. In this case check the RFC connections and SDCC. see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS. For more information. You can analyze your 58 June 2012 .2 SAP EarlyWatch Alert (EWA) SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections. For more information. to be able to send data to SAP. with transaction SOLMAN_SETUP. A self-diagnostics module is available in SAP Solution Manager. For more information. Check whether the distribution group is set to EWA. see SAP Note 33135: Guidelines for OSS1. An SAP Support Portal connection is required. Therefore check regularly the the functioning of the EWA in the System Monitoring Work Center. If there is something is wrong with the EWA data collection. see the following SAP Notes: SAP Note 216952 762696 Short Text Service Data Control Center (SDCC) – FAQ Grey rating for EarlyWatch Alert 8. check if connection SAPOSS works. see SAP Note 762696 “Grey rating for EarlyWatch Alert”. For further information. The selfdiagnosis tool is highly configurable and can perform solution-specific or cross-solution self diagnosis. adjust it as required. Self-Diagnosis Topic New self diagnosis in SAP Solution Manager: a quick guide Link SAP Note 1073382 June 2012 59 . batch jobs and performance values.g. to identify SAP Solution Manager system performance problems.g. in the background. e. For the SAP Solution Manager single solution. By pressing the button “Settings” you can select which type should generate an alert and inform you.SAP Solution Manager Operation Guide SAP Solution Manager system and/or a solution. e. The self-monitoring functionality can be found in the Solution Manager Administration Work Center → Self-Diagnosis. by default. to avoid red alerts. e. The selfdiagnosis analyses run daily. with the self-diagnosis function. to check that the master data of a solution is consistent. The self-diagnostics checks the RFC Connection.g. to check whether the problems shown by alerts have been resolved. You can customize SAP Solution Manager self-monitoring. in the Alert Type area. You can display the self-diagnosis results in various levels of detail: For the SAP Solution Manager (cross-solution). to identify and solve problems. You can perform a new analysis at any time. 4. 2. Check that CA Wily Introscope Enterprise Manager receives information from CA Wily Introscope Agent. If the logon screen of your WebView does not appear. which includes also a detailed troubleshooting section. Connect to your CA Wily Introscope WebView via web browser – usually o http://hostname:8081/webview/jsp/login. Related Information Content Wily Introscope User Guide Wily Introscope Installation for SAP Customers Link http://service.com/saphelp_nwpi71/helpdata/en/44/9 8320f33bf60d6e10000000a114a6b/content.sap.server.jsp. Verify in SMD → Diagnostics Setup → Managed Systems → Introscope Agent for the system in which the Introscope Agent is running 3.sup.sap.4 CA Wily Introscope To check whether the CA Wily Introscope is running properly: 1.admin. The Java-based parts all use the standard logging of AS Java. The equal sign icon indicates that the version is up to date.5 Logging and Tracing Logging and tracing is essential for analyzing problems in the SAP Solution Manager Java-based parts.* Comment AdminConsole SMDServer Related Information Content SAP Netweaver Administrator Link http://help. Logging Categories Logging Category /Applications/AdminConsole/* Comment AdminConsole Tracing Locations Tracing Location com.smd.SAP Solution Manager Operation Guide 8.sap. Ensure that the version of your agent is the same as the version of the source on your SAP Solution Manager. For more information please consult the Wily Introscope User Guide or SAP Note 797147 “Wily Introscope Installation for SAP Customers”. CA Wily Introscope Enterprise Manager may not be active.* com.htm 60 June 2012 . This can be configured by using the log configuration function of the SAP NetWeaver Adminstrator under Problem Management Logs and Traces Log Configuration.com/diagnostics SAP Note 797147 8.sap. The main logging catogries and tracing locations can be found in the following table. SAP Solution Manager Operation Guide 9 Appendix 9. particularly about roles and authorizations.1 Related Guides The master guide is a central starting point for the technical implementation of SAP Solution Manager 7. 9.2 Related Information Quick Link to SAP Service Marketplace (http://service. All security-related information.com) Instguides → SAP Components → SAP Solution Manager Notes platforms securityguide solutionmanager diagnostics Related Information Content Master Guide. The configuration guide describes the configuration of SAP Solution Manager and its scenarios and functions.1.sap. is in the security guide. Installation Guide and Update Guide Related SAP Notes Released Platforms Network Security SAP Solution Manager Root Cause Analysis June 2012 61 . and its scenarios.
Copyright © 2024 DOKUMEN.SITE Inc.