Solution Operation Guide
SAP Solution Manager 7.1 Operation Guide
Document Version 1.0 - May 9, 2011
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany www.sap.com
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.
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
SAP Solution Manager Operation Guide
1 Getting Started....................................................................... 6
1.1 1.2 2.1 2.2 2.3
2.3.1 2.3.2 2.3.3
Global Definitions ...................................................................6 History of Changes .................................................................8 SAP Solution Manager ............................................................9 SAP Solution Manager built-in Software Components .......9 SAP Solution Manager complementary Components .......11
Internet Graphics Server (IGS) ................................................11 SAP NetWeaver Search and Classification (TREX) ...............11 CA Wily Introscope ..................................................................11
2 SAP Solution Manager and Technical System Landscape . 9
2.4 2.5 2.6 2.7 2.8 2.9 2.10
Release Restrictions .............................................................12 Installation .............................................................................12 Upgrade to SAP Solution Manager 7.1................................12 Business Warehouse (BW) Client Strategy ........................13 Root Cause Analysis ............................................................13 SAP Solution Manager Configuration .................................14 Managed Systems Configuration ......................................15
2.10.1 Required Agent Versions ........................................................16 2.10.2 SAP Solution Manager and Trusted RFC ...............................16 2.10.3 System and Landscape Directory (SLD), Landscape Management Database (LMDB) and SMSY .........................................18 2.10.4 Adjust Upgrade of Managed System ......................................19
2.11 Moving from SAP Solution Manager Transation DSWP to Work Centers ..............................................................................20 2.12 Solution Transfer ................................................................20 2.13 Service Delivery in SAP Solution Manager ......................21 2.14 Multi-Tier Landscape for SAP Solution Manager .............21 2.15 Sizing for SAP Solution Manager ......................................21 2.16 Related Documentation ......................................................22
3 Monitoring SAP Solution Manager ..................................... 23
New Monitoring Infrastructure .............................................23
Connection Monitoring ............................................................23
CCMS Monitoring – SAP Solution Manager .......................23
CCMS Monitoring – Internet Graphics Server (IGS) ..............24
SAP EarlyWatch Alert in SAP Solution Manager ...............24 Other Problem Analysis and Monitoring Tools ..................24
Application Monitoring ............................................................24
4 Management of SAP Solution Manager ............................. 26
4.1 Solution Manager Administration Work Center .................26
5....2....3 7.........................33 Update Authorizations after Support Package Upgrade ................................43
Guided Procedure .......... 43
Backup Introscope Enterprise Manager ........30
4...............................32 Create Users and Business Partners for End Users ..........43 SAP Reference IMG – Manual Update Configuration ................44
7 Software Change Management ................28 Backup and Restore .......26 Infrastructure View .............................................2 6...............................3 6......SAP Solution Manager Operation Guide
4..42 Agents Consideration ................46 SAP EarlyWatch Alert (EWA) .....................27 Self Diagnosis View ................................35 Adapt Work Center Queries................................................................5.5
Landscape View ...........................................1 7......................................49 Related Information ........5.................... 38 6 Archiving & Data Deletion in SAP Solution Manager ........40 SAP Notes for Additional/Background Information ...........2 4..3.........................................................................................1.................30
Achiving functionality in core SAP Solution Manager .............................4 8.1.............................4
4........5...............28 Project View .4 7.....5 9.30
Background processing in the SAP Solution Manager.....................44 Support Packages and Patch Implementation ...........................39 SAP Solution Manager Extended Archiving Functionality40 Alternative Storage & Deletion Strategies ......................................................32
User Administration and Authentication ..............................1 8...................48 Related Guides ..............................36 Assign Roles to Users .......................4 4.............1 6.....................................4 4.............................................................4.............................1......46 CA Wily Introscope ...1.................2 4............43 Configuration after Support Package Update ...3 4.46 Self-Diagnosis ......................3 8..............................................Automatic Update Configuration ........6
User Management ............ 49
.......5 4...................3 4..3
Starting and Stopping ............5
4......1.1 9.....................2 4....37
5 High Availability.........................................................5.................1
Periodic Tasks .............................5.............................................................................1 7.....2
Ensure Basic Functions via SAP Note ...........................................2 8..4 8...........................2.......49
8 Troubleshooting .. 39
9 Appendix ...........48 Logging and Tracing .28
4................................28 Solution View ..................................45 Connection to SAP ........36 Create End User Roles .................................................................1 4..
A business scenario is an entity which can be implemented separately. has never been more vital to your business success than today. SAP PLM. and possibly other third-party systems.
Check regularly for updates of the Application Operations Guide. installed and maintained separately. implementing. Technically. and lists the tools that you can use to perform them. This guide is the starting point for managing your SAP applications and maintaining and running them optimally. Business Scenario From a micro-economic perspective. and SAP Library. SAP SRM. Typically. so you will sometimes also need other guides.1
SAP Application An SAP application is an SAP software solution that serves a business area such as SAP ERP.SAP Solution Manager Operation Guide
1 Getting Started
This guide does not replace the daily operations handbook. SAP SCM. Technical Infrastructure Guide. 24 hours a day.
. that we recommend customers create for their production operations. About this Guide Designing. and reflects the customer‟s prospective course of business. a business scenario is a cycle which comprises several interconnected logical processes in time. SAP CRM. or SAP SCM. Component A component is the smallest individual unit considered within the Solution Development Lifecycle. or other) for each cycle. and running your SAP applications at peak performance. a business scenario needs at least one SAP application (SAP ERP. delivered. components are produced. Target Groups Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist
1. It contains information about various tasks. It also provides references to the documentation required for these tasks. a business scenario includes several company departments and business partners. such as the Master Guide.
1 SP01.1 Update of SAP Solution Manager 7.1
.This usually takes the form of references to other notes.1 Comment This note describes problems that may occur when you upgrade the system and provides you with information on how to solve them. Implement the following note to ensure the basic functions in SAP Solution Manager.basic functions
Supplements to Solution Manager 7.SAP Solution Manager Operation Guide
Important SAP Notes SAP Note Number 1462137 Title Add.0 to SAP Solution Manager 7. This note describes preparatory measures and additional information for the Upgrade of SAP Solution Manager 7. The aim of this note is to prevent data loss.1 (installation) to the stack that is currently available
SAP Solution Manager . upgrade shutdowns and long runtimes. This note contains additional prerequisite notes that are regularly extended and renewed.1
Documentation: SAP Solution Manager 7.1 Upgrade of SAP Solution Manager 7. about Upgrading to SAP Solution Manager 7. info.0 Enhancement Package 1 to SAP Solution Manager 7. This note is valid for Solution Manager 7.1
Overview on the available documentation for SAP Solution Manager 7. Only database-independent problems are dealt with here.
.SAP Solution Manager Operation Guide
1.1. Document Versions Document Version 1. The following table provides an overview of the most important changes in previous versions.sap.com/instguides → SAP Components → SAP Solution Manager → Release 7. The current version of the Application Operations Guide is on SAP Service Marketplace at http://service.00 Important Changes First version of the SAP Solution Manager Operations Guide for SAP Solution Manager 7.2
History of Changes
Make sure you use the current version of the Application Operations Guide.
You can use the following software components in your system. Another central place for useful information about the supported functions is the Ramp-Up Knowledge Transfer page for the SAP Solution Manager. so the tasks and procedures for a standard SAP NetWeaver system generally also apply to SAP Solution Manager.com/alm http://service. and reducing risk as well as total cost of operations while protecting your investment is the key challenge for each IT organization. Application Lifecycle Management (ALM) adresses this challenge with an integrated ITIL-based approach. More information about Application Lifecycle Management (ALM) and the SAP Solution Manager can be found in the SAP Service Marketplace or the SAP Help Portal. It is based on an SAP NetWeaver platform and includes the SAP CRM add-on. depending on the scenarios you actually use.com/solutionmanager http://help.sap.com/ → SAP Solution Manager http://service.2
SAP Solution Manager built-in Software Components
The SAP Solution Manager comprises several software components. This guide refers mostly to SAP Solution Manager-specific tasks and procedures.sap. accelerating innovation.sap.com/rkt-solman
2.SAP Solution Manager Operation Guide
2 SAP Solution Manager and Technical System Landscape
2. depending on the business scenarios used. Cental Information Sources Topic Application Lifecycle Management (ALM) SAP Solution Manager SAP Help Portal Ramp-Up Knowledge Transfer Link http://service.1 SAP Solution Manager
SAP Solution Manager is the central tool for managing your customer solution landscape. Usage Type SAP Solution Manager Software component SAP_BASIS SAP_ABA SAP_BS_FND SAP_BW BI_CONT SAP_AP ST ST-A/PI ST-SER ST-PI Description SAP Basis Component Cross-Application Component SAP Business Suite Foundation SAP NetWeaver BI Business Intelligence Content SAP Application Platform Solution Manager Tool Application Service Tools Solution Manager Service Tools Solution Tools Plug-In
. Other software components can be added to SAP Solution Manager. It includes several applications and scenarios to support the Application Lifecycle Management (ALM) ensuring business continuity.sap.
0 (ABAP) PI_BASIS SAP Web UI Framework
SAP Adapter for SAP Quality Center by HP SAP process scheduling adapter SAP Produktivity Pak
Root Cause Analysis
BMC AppSight CA Wily Introscope
Software Comonents Detailed Information Support Package levels of SolMan installations / upgrades SAP Note 781448
There are several standard interfaces to third-party tools.sap.com/solutionmanager → SAP ProductivityPak by RWD adapter for SAP Solution Manager and SAP Note 1131270 SAP Note 1034902
. https://service.com/solutionmanager → Process Scheduling adapter for SAP Solution Manager.com/solutionmanager → SAP Solution Manager Adapter for SAP Quality Center by HP.sap.SAP Solution Manager Operation Guide
ST-ICO BBPCRM CPRXRPM PI_BASIS WEBCUIF Usage Type Additional Adapers ST-QCA ST-PSM ST-SPA Usage Type Java Application Server LMSERVICE Aditional 3rd Party Software Appsight Blackbox and Console Introscope Enterprise Manager
Solution Manager Implementation Content BBP/CRM SAP Portfolio and Project Management 5. which can be used for specific scenarios: Additional Software Tool SAP Quality Center by HP SAP Central Process Scheduling by Redwood SAP Productivity Pak by RWD BMC Appsight for Client Diagnostics Link https://service. https://service.sap.
This document also includes a detailed troubleshooting section.3 CA Wily Introscope
CA Wily Introscope is a software component. For information about installation.3. in EarlyWatch Alert reports.2 SAP NetWeaver Search and Classification (TREX)
For specific scenarios the SAP NetWeaver Search and Classification (TREX) is used.
SAP Solution Manager complementary Components
2. e.sap.3. The server can be administrated in transaction SIGS. Administration of TREX Topic SAP Netweaver Search and Classification Administration of TREX Notes for TREX SAP Note 1466273 Short Text Work Centers: "TREX is not responding" error message TREXADMIN Transaction Link http://help.sap.3.SAP Solution Manager Operation Guide
2.sap.com/diagnostics → Installation and Configuration.0 including Enhancement Package 2 → <language> → Technical Operations Manual → Administration of Standalone Engines → Search and Classification (TREX) http://help. see the installation guide on SAP Service Marketplace at http://service.g. You can administrate your Web Dynpro Java IGS via a Web Interface.com → SAP NetWeaver → SAP NetWeaver 7.com/saphelp_nwes70/helpdata/en/ 46/c96a575b590e5be10000000a1553f7/content. SAP Note 797147 “Wily Introscope Installation for SAP Customers” includes a detailed FAQ document as an attachment. 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.1 Internet Graphics Server (IGS)
The Internet Graphics Server (IGS) generates various graphics or charts in some areas. which collects performance and other system-related data maily from non-ABAP components in your system landscape.
sap.6 Upgrade to SAP Solution Manager 7.1.1
2.SAP Solution Manager Operation Guide
Wily Introscope Topic Wily Introscope Notes for Wily Introscope SAP Note 797147 1565954 Short Text Wily Introscope Installation for SAP Customers Introscope 9 Release Notes Link http://service. until the customer has completed the Unicode conversion.com/diagnostics
2. SAP will support the SAP Solution Manager on non-Unicode. If this is not possible.5 Installation
SAP Solution Manager 7.1“.1 is an SAP system based on Application Server ABAP (AS ABAP) and Application Server Java (AS Java). see http://sdn.1
To upgrade to SAP Solution Manager 7. This information is collected in SAP Note 1480419 “Release Restrictions for SAP Solution Manager 7.sap.1.sap. All new SAP Solution Manager Installations are on Unicode. SAP recommends migrating to Unicode. SAP recommends running SAP Solution Manager on Unicode. SAP Solution Manager Installation Topic SAP NetWeaver Releases SAP Solution Manager Installation Unicode Link http://sdn. For customers that have upgraded from previous releases of SAP Solution Manager 7. SAP Solution Manager 7.4 Release Restrictions
When SAP Solution Manager 7.0 including Enhancement Package 2. a number of restrictions still applied to the productive use of certain functions. 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. you require seperate upgrade programs for the ABAP and the Java parts of your SAP Solution Manager system.1 is based on the technology of SAP NetWeaver 7. and are not yet on Unicode.com/irj/sdn/netweaver.com/irj/sdn/netweaver http://service.com/unicode
2. For further information please consult the SAP Solution Manager 7.com/instguides http://service.
. For more information about SAP NetWeaver technology.1 was released. SAP Notes SAP Note 1480419 Short Text Release Restrictions for SAP Solution Manager 7.sap.sap.1 Upgrade Guide.
delivered with SAP Solution Manager 7. However. This scenario provides increased security.com/instguides → SAP Components → SAP Solution Manager → Release 7. This makes configuration simpler. There is no technical benefit.1 SAP Note 1462137
2.1 Note / Link SAP Note 1478974
. BW Client Strategy Topic Where is best to set up BW for the Solution Manager Note / Link SAP Note 1487626
2. BW activities are conducted in a separate client on the SAP Solution Manager system.1 Link http://service. BW is used in the same productive client as SAP Solution Manager. In general there are two main BW options when planning your system landscape. as user access is more restricted.1.1”) includes an overview of software components and support package levels that must be installed in your SAP Solution Manager system. BW activities are conducted in a separate client on the SAP Solution Manager system. Root Cause Analysis Topic Diagnostics in SAP Solution Manager 7.7 Business Warehouse (BW) Client Strategy
BW provides important reporting functions to the various SAP Solution Manager processes. BW in a Separate Client on SAP Solution Manager In this scenario. The configuration of the tool is integrated in the guided procedure for configuration of SAP Solution Manager (transaction: SOLMAN_SETUP). Solution Manager Diagnostics. The functionality is also called End-toEnd Diagnostics or SAP Solution Manager Diagnostics. BW in a Separate Client on SAP Solution Manager In this scenario.SAP Solution Manager Operation Guide
SAP Note 1462137 (“Additional information on upgrading to SAP Solution Manager 7. you must maintain users separately.g. There is no technical benefit. SAP Solution Manager Upgrade Topic SAP Solution Manager 7. BW in the Productive SAP Solution Manager Client In this scenario. This is SAP’s recommendation. and this increases your administration effort. as user access is more restricted.1 Upgrade Guide Additional information on upgrading to SAP Solution Manager 7.8 Root Cause Analysis
You need information about the basic requirements and possible limitations of end-to-end root cause analysis. and isolates the BW activities for solution life cycle management from the data on a production BW instance. e. However.sap. and this increases your administration effort. This scenario provides increased security. you must maintain users separately.
SAP Solution Manager Configuration
After installing the SAP Solution Manager. performing a root cause analysis. connecting to SAP.com/diagnostics
2. Measurement Platform Setup o Choose all systems for which you later want to perform your SUGEN benchmark measurement. The automatic configuration is accessed via the Solution Manager Configuration Work Center or it can be called by transaction SOLMAN_SETUP. This quickly configures all main settings in a guided procedure. in the SAP Reference IMG (transaction SPRO).
. using the SAP EarlyWatch Alert.1: Root Cause Analysis Root Cause Analysis
SAP Note 1483508 http://service.sap. o System Monitoring: monitors the status of managed systems. 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. the basic configuration should be performed. You can initially configure your basic settings with the basic settings wizards. All activities in this wizard are linked to the corresponding Customizing activities in the standard basic settings configuration.SAP Solution Manager Operation Guide
Solution Manager 7. 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.com/instguides → SAP Components → SAP Solution Manager → Release 7. or downloading patches and upgrades Managed Systems Configuration o Connect managed systems to SAP Solution Manager
And also configuration steps for specific scenarios: Technical Monitoring. configures the following sub-scenarios: o Self-Monitoring: monitors the status of SAP Solution Manager.1. Data Volume Management Further Configuration for the following scenarios: o Test Management o Quality Gate Management o Change and Transport System (CTS+)
For more information about configuration. see the Customizing for SAP Solution Manager (transaction SPRO) and the configuration guide on SAP Service Marketplace at http://service. All settings for this Web Dynpro application are made during the installation of SAP Solution Manager. o PI Monitoring: monitors XI (SAP Exchange Infrastructure) and PI (SAP Process Integration) systems which allow for data exchange between managed systems. o Connection Monitoring: monitors connections between managed systems. for example.sap.
create the technical system manually.
2. technical scenarios. The users should only have the authorizations which are assigned to them in the managed systems. which are known to the SAP Solution Manager System Landscape Directory. The configuration of managed systems for the basic scenarios is in the guided procedure (transaction SOLMAN_SETUP). To connect a standalone database. you connect systems to SAP Solution Manager: 1. In SAP Solution Manager this is usually ensured by using a trusted RFC with the same user. so you must be able to access those systems.RFC Status (only ABAP): Red: Repair the RFC connections. Select the system you want to configure: To connect a single system.SAP Solution Manager Operation Guide
Basic Configuration Topic SAP Reference IMG Configuration Guide Transaction / Link Transaction SPRO http://service. The SAP Solution Manager is the central location for the management and setup of the connected managed systems. choose the Database tab page. choose the Configure Scenario or Configure System
.Plugin Status (only ABAP): Red: Install the recent version of the following software components on the managed system: ST-PI ST-API . If incorrect system data is displayed. you maintain the technical system or scenario in the system landscape. .To make sure that the technical systems or technical scenarios are correctly known to SAP Solution Manager. choose the Technical System tab page. for example delete and set up the RFC destination again . To do so.
3. connect the system to an SLD to minimize the effort for maintenance. Check the status of the configuration: Gray.com/instguides → SAP Components → SAP Solution Manager → Release 7. are displayed. select an item and choose the Show Details link. If required. All the systems which are connected to the SAP Solution Manager are called managed systems. the SAP Solution Manager should be connected to all systems in the system landscape.Automatic Configuration Status: Grey: Perform missing steps of the managed system configuration Red: Repeat failed steps of the managed system configuration .10
Managed Systems Configuration
To ensure that all the systems can be managed centrally. red or yellow signals in the following columns require you to take action: .If the system that you want to connect is not contained in the technical system list.sap. choose the Technical Scenario tab page. The technical systems. or databases. To connect a double (ABAP and Java) stack system. In this step.1
2. Misuse of the communication connection must be prevented.
1 Agents for managed systems SAP Host Agent • You need to install at least patch level 55 of the SAP Host Agent 7. 5.10. so that you can update the Host Agent centrally. Databases are retrieved automatically from LMDB and cannot be created or maintained. the creation of new users and the resetting of passwords must be strictly controlled. Trusted relations between systems can be configured on different levels:
. Follow the instructions in the respective Guided Procedure. scenarios or databases.1
Required Agent Versions
On the Managed System you need different agents for Root-Cause Analysis as well as for the Technical System Monitoring. Diagnostics Agent • You can use any version of the Diagnostics Agent (already installed agents do not need to be updated) • The agent applications are updated automatically from the Solution Manager • For new installations use the latest available version of the diagnostics agent from http://service. The trusted RFC connections can be used and are acceptable from a security point of view. To create systems manually. SAP Solution Manager does not manage connections between managed systems. The naming conventions for users must be consistent across systems. respectively.sap.10.com/swdc Support Packages and Patches Browse Download Catalog SAP Technology Components SAP HOST AGENT SAP HOST AGENT 7. 4.com/swdc Browse Download Catalog SAP Technology Components SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7. This is described in SAP Note 1473974. This can be done using transaction SOLMAN_SETUP.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. respectively. Required Agent Versions Topic Installing Package SAPHOSTAGENT Using the SAP Host Agent Auto Upgrade Feature Note / Link SAP Note 1031096 SAP Note 1473974
SAP Solution Manager and Trusted RFC
The trusted RFC connections are setup between the SAP Solution Manager and the connected managed systems. Notes for Managed Systems SAP Note 1472465 Short Text SAP Solution Manager 7.SAP Solution Manager Operation Guide
pushbutton.System Landscape Setup Guide
2. You go to a Guided Procedure. if the user management for the SAP Solution Manager is as restrictive as for all other productive systems. • The installation files are available from http://service. choose the System/Scenario/Database Operations pushbutton. and choose Create. In particular.
Note for Trusted RFC SAP Note 128447 Short Text Trusted/Trusting Systems
.SAP Solution Manager Operation Guide
1) Trusted relationships from a system. which offers services to another system (client). with the authorization field RFC_EQUSER set to “Y” and the field RFC_USER empty or set to the dummy value „ (inverted comma). Through the authorizations of the service user for the authorization object S_RFCACL. 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). with which applications (authorization field RFC_TCODE). must have authorization for the authorization object S_RFCACL. In case 2d). The RFC server system accepts the authorization by the RFC client system. The trusted RFC connection has the following security attributes: Simple navigation (via Single Sign-On) from RFC client to RFC server. The trusted RFC can be used for 1b) and 2d). Examples: a) A Windows client accepts a Kerberos ticket of a Windows domain server. and logs its user in. with the same user ID as in the source system. and logs on the user in the target system. This kind of trusted relationship is usually realized by putting the login data of a service user of the server system. 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. it is also possible to restrict which users (authorization field RFC_USER) in the RFC client system can use the connection. c) An SAP system accepts an SSL client certificate in an https connection. no login data is provided in the RFC destination. finds the user and logs it in with user ID. The users who want to use such a trusted RFC connection. In case 1b). b) An SAP backend system accepts the SAP Logon Ticket of the SAP NetWeaver Portal. as in a normal RFC destination. where the login token is entered. and the authorizations in the RFC client system can be limited by the authorization object S_ICF. in the client system. 2) Trusted relationships between systems where one system accepts the authentication of the other 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. the login data of a service user is entered in the RFC connection. to restrict user access rights to RFC connections. but the option “same user“ is selected. d) An RFC server system accepts the trusted RFC token und logs the user in to the target system. A user has his personal authorizations in the SAP Solution Manager system as well as in the connected managed systems. RFC connections between SAP systems can also be secured by “secure network communication” (SNC).
SMSY Numerous other applications keep using transaction SMSY for the time being. on an SAP NetWeaver PI system. which use this data include SAP Solution Manager Diagnostics. In Solution Manager 7. Landscape Management Database (LMDB) and SMSY
Many functions in SAP Solution Manager rely on up-to-data landscape data. The main landscape management building blocks are the System Landscape Directory (SLD). Applications.0 – SLD: EHP2 for SAP NetWeaver 7. BI Monitoring and PI Monitoring.SAP Solution Manager Operation Guide
2.1 – SLD: SAP NetWeaver 7. it is also possible to forward the landscape data to an SLD. Since landscape data is mostly gathered outside the SAP Solution Manager system. data for technical systems is replicated to SMSY. the landscape needs to be taken into account. and the Landscape Management Database (LMDB). LMDB becomes the home of all Technical System data. The SLD contains information on installable software (updated via the SAP Service Marketplace) and technical system data. Data can be enriched manually in the LMDB.3 – SLD: not supported not supported not supported SP6. without user interaction.1. mostly sent by these systems using data suppliers. LMDB The data from the SLD is synchronized into the SAP Solution Manager Landscape Management Data Base (LMDB) introduced with Solution Manager 7. the LMDB replaces it.0 – SLD: EHP1 for SAP NetWeaver 7. e.
. For compatibility reasons. so that all SLD data provided by the productive SLD is propagated into LMDB. This is how to set up landscape data management: SLD The technical system data is gathered by self-registration of technical systems in the System Landscape Directory (SLD). the home of Product Systems and Logical Components stays SMSY. LMDB is a central. 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. This is especially true for system maintenance.0 – SLD: SAP NetWeaver 7.1. built-in repository for all Solution Manager applications. plus the automatic content synchronization mechanism.40 – SLD: SAP NetWeaver 7. Note: If a local SLD was used in existing SAP Solution Manager environments before 7.3
System and Landscape Directory (SLD). 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.1. Patch 5 SP9 all SPs all SPs all SPs
If your central SLD does not fulfill these requirements. Monitoring and Alerting.10.1 – SLD: EHP1 for SAP NetWeaver 7. which consume landscape data. but also for various other applications. LMDB shares the CIM model with the SLD.2 – SLD: SAP NetWeaver 7. With release 7.1.g.
SAP’s SLD Recommendation Manual maintenance of the system landscape without SLD is not recommended. Best practice is a central SLD in which all systems register themselves. Adjust Product Version a) To adjust the new product version for your upgraded managed system. This allows patches and stacks to be downloaded to a central location provided by the SLM. In the dialog box. and then to SAP Solution Manager. via data supplier forwarding. This section explains how to adjust your settings for this system in the SAP Solution Manager. A central SLD on SAP Solution Manager also allows the maintenance optimizer functions to use the Software Lifecycle Manager (SLM) features. 2.4
Adjust Upgrade of Managed System
You have upgraded a managed system. Adjust Logical Component
. go to transaction SMSY and choose your system.SAP Solution Manager Operation Guide
If productive SLDs are in use.sdn.com/irj/sdn/nw-sld http://www. and choose Installed Product Version. SLD and LMDB Topic SLD planning guide SLD Topology Link https://www. b) Go to Header Data tab. their landscape information can be forwarded to a central SLD.sdn. depending on the conditions above. Prerequisites You have: SAP Solution Manager projects and solutions in productive use SLD attached to SAP Solution Manager Procedure 1. All SLD data is propagated to LMDB automatically. c) Save.10. directly or indirectly.com/irj/scn/weblogs?blog=/p ub/wlg/17579
Connect a Managed SAP System Topic Connect a Managed SAP System Solution Manager System Landscape Transaction SOLMAN_SETUP SMSY Detailed Description Automatic Guided Procedure for Managed System Configuration Product Systems and Logical Components
2. implementing the SLD in SAP Solution Manager's own Java stack would be an alternative to connecting all SLD data suppliers.sap.Configure the central SLD as the source of the Landscape Management Database (LMDB) in Solution Manager. choose the product version you have upgraded to. This forwarding has to be configured manually for each productive system. Note: For landscapes with no productive Java stack outside SAP Solution Manager (as would be used for PI and Web Dynpro Java).sap. This central SLD can be outside or inside SAP Solution Manager.
In the future. This is SMSY data and it is usually transferred from TMS or SLD into SMSY. the solutions must now be created via the Solution Manager Administration Work Center (Solutions). This process has two steps: 1) Transfer systems and logical components from source to target. before defining the solution. In the past transaction DSWP (or SOLUTION_MANAGER) served as the primary entry point fir Operations and Operations Setup within SAP Solution Manager. you may want to leave the outdated logical component in your project. you need to transfer some information from the previous SAP Solution Manager. business processes etc. to it. for documentation purposes.
. after all landscape components have been created. If you monitor business processes in this system. Create a target solution in your target SAP Solution Manager. You can do this with the transaction SOLUTION_TRANSFER.11
Moving from SAP Solution Manager Transation DSWP to Work Centers
With the introduction of Work Centers with SAP Solution Manager 7. please review SAP Note 1541013. See the SAP Solution Manager Solution Concept and Design document in the Service Marketplace. the Work Centers will be the single entry point for all activies. all new SAP Solution Manager developments have been done exclusively with a focus on Work Centers.01 SP15. b) In SAP Solution Manager Administration Workcenter deactivate any solutions that contain the managed system. c) Go to transaction SOLMAN_DIRECTORY and your solutions.1 this transaction was deactivated. d) Activate your business process monitoring session and solutions again.SAP Solution Manager Operation Guide
a) Create a new logical component for your upgraded managed system.12 Solution Transfer
When a new SAP Solution Manager is installed. Additional steps are: a. service plans. such as issues. Adjust Upgrade of Managed System Topic Solutions in SAP Solution Manager Solution Directory Transaction SOLMAN_WORKCENTER SOLMAN_DIRECTORY Detailed Description Adjust Upgrade of Managed System Adjust Upgrade of Managed System
2. so there is no need to transfer it manually. Solution Concept and Design Short Text SAP Solution Manager: Solution for SAP Service Delivery Deactivation of transaction DSWP Note / Link SAP Note 1117389 SAP Note 1541013
2. As the transaction has become outdated with the SAP Solution Manager 7. Therefore. and replace your outdated logical component with your new logical component. In an implementation project. For the latest informantion. deactivate the business process monitoring sessions for it. landscape info.
2) Transfer the data from your source solution.Central preparatory note Technical prerequisites for remote service delivery in SSM The role of SAP Solution Manager in Remote Service Delivery
2. changes must first be developed in the development system. cookbook. which can be found in the Service Marketplace. and assign them to a target solution.1. Solution Transfer Short Text Export Solution Link http://help.
2. It contains components (guides. A transport between two SAP Solution Managers is not usually necessary. Create logical components there. All services are solution-specific and can be used for all systems in the solution. Business processes are transfered.SAP Solution Manager Operation Guide
b. You should use a three-tier landscape with transports.sap. In this environment.14 Multi-Tier Landscape for SAP Solution Manager
You can use should use at least a two-tier landscape for your SAP Solution Manager. such as EarlyWatch. Notes for Service Delivery SAP Note 91488 1172939 1170668 Short Text SAP Support Services .com → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Export Solution http://help. and transported into the productive SAP Solution Manager after testing in the quality assurance system.sap. as well as services which are delivered by SAP. Test new Support Packages. patches or configuration scenarios on a test system first. if you perform classic customizing or own developments in SAP Solution Manager.
.com → SAP Solution Manager → <language> → Basic Settings → Solutions → Manage Solution → Import Solution
2. If the test is successful. as well as business process monitoring configuration data and all data in the service sessions. which can be performed by the customer. the changes can be installed in the productive SAP Solution Manager. and spreadsheet) to run a sizing project for SAP Solution Manager. This includes self-services. Determines the corresponding SAP Solution Manager cluster configuration.13 Service Delivery in SAP Solution Manager
The SAP Solution Manager is the SAP service delivery platform. The usual scenarios for this case are change request management and/or service desk. This tool-kit: Finds hardware resources needed to implement SAP Solution Manager for a given landscape. etc. GoingLive.15 Sizing for SAP Solution Manager
There is a new sizing tool-kit for SAP Solution Manager 7.
1 Diagnostics → Installation and Configuration
Detailed scenario description Support Package-specific configuration guide SAP Solution Manager Upgrade Guide Wily Introscope Installation Guide
SAP Solution Manager Master Guide SAP Solution Manager Configuration Guide Upgrade SAP Solution Manager 7.Installation Guide
.SAP Solution Manager Operation Guide
Configures SAP Solution Manager and Wily IS EM to obtain better performance and scalability.sap.com) Instguides → SAP Components → SAP Solution Manager → Release 7.com/sizing-solman
2.1 Instguides → SAP Components → SAP Solution Manager → Release 7.16 Related Documentation
Related Documentation Topic Guide/Tool Quick Link on SAP Service Marketplace (http://service.0 EHP 1 to SAP Solution Manager 7. Sizing for SAP Solution Manager Topic SAP Solution Manager Sizing Tool-Kit Link http://service.1 Wily Introscope .sap.1 Instguides → SAP Components → SAP Solution Manager → Release 7.
You can activate CCMS monitoring for a solution (Work Center Solution Manager Administration → Solutions → <Select a specific Solution> → Solution Settings → CCMS Monitoring of EWA).1. you will get monitoring objects in transaction RZ20 under the monitoring tree element (MTE) “SOLMAN”.sap.
3. automated monitoring is the basis for ensuring reliable operation of your SAP system environment.1. The Self Monitoring Setup is integrated in transaction SOLMAN_SETUP: Choose the section Technical Monitoring Choose the scenario SolMan Self Monitoring Follow the guided procedure The prerequesites for using the new Self-Monitroing are: System Preparation & Basic Configuration completed successfully The Solution Manager itself is successfully setup as a managed system The SAP Service Marketplace (SAP-OSS) connection is working New Monitoring Infrastructure Topic New Monitoring Infrastructure Link http://help. If monitoring is active.com → SAP NetWeaver → SAP NetWeaver 7.sap.1
3.1 Connection Monitoring
For the technical operation of the SAP Solution Manager working RFC connections to the managed systems are essential. with the following content: Rating of EWA for each <SID> Rating of each SL Report Successful download of data into the SDCC
. which is based on the new Monitoring Infrastructure. You can activate and deactivate CCMS monitoring for specified solutions. For more information about the CCMS monitoring see http://help.1
New Monitoring Infrastructure
Proactive.SAP Solution Manager Operation Guide
3 Monitoring SAP Solution Manager
Monitoring is an essential SAP technology management task.com → SAP Solution Manager → SAP Solution Manager 7. which is introduced with SAP Solution Manager 7. which is also part of the new monitoring infrastructure.0 including Enhancement Package 2 → <language> → System Administration → Technical Operations Manual for SAP NetWeaver. Under this MTE there is another one for each active solution. Therefore you should monitor the RFC connections from the SAP Solution Manager to the managed systems with the Connection Monitoring.2
CCMS Monitoring – SAP Solution Manager
The CCMS Monitoring can still be used as data supplier for new monitoring infrastructure. There is a new Solution Manager Self-Monitoring. 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. Beside the usual SAP NetWeaver based Log Object.4
Other Problem Analysis and Monitoring Tools
3. but you can monitor the application log also for other applications in the SAP Solution Manager. by using customizable transactions and threshold values to trigger the creation of the reports). the most important Log Object for SAP Solution Manager can be found in the following table: Log Objects in SLG1 Object /TMWFLOW/CMSCV AISDK AI_LMDB AGSGEN CCDB CRM_SOCM DIAGNAV E2E_ALERTING E2E-CA E2E-DIAG E2E-EA E2E-WA EEM LMDB RBE40 Suboject * * * * * * * * * * * * * * * Area Application Log /TMWFLOW/ Solution Manager Service Desk Landscape Management Generic Extractor Configuration and Change Database Change Request Management Solution Manager Diagnostics Navigation Monitoring and Alerting Infrastructure E2E Change Analysis Solution Manager Diagnostics E2E Exception Analysis E2E Workload Analysis Enduser Experience Monitoring Landscape Managemant Database Solution Dokumentation Assistant
. SAP recommends that all customers perform centralized system monitoring of all connected managed systems in SAP Solution Manager.
3.SAP Solution Manager Operation Guide
3. SAP EarlyWatch Alert for Solutions and Service Level Reports.3
SAP EarlyWatch Alert in SAP Solution Manager
SAP EarlyWatch Alert (EWA) is a monitoring service for SAP customers that monitors SAP systems in your solution landscape. You will get a separate node in transaction RZ20 for “IGS availability”. which tells you if the Internet Graphics Server is available.2. You can receive a regular E-Mail with the reports for specific systems or solutions. to have access to all important information from a central location. To configure this goto System Monitoring Work Center → Configure Automatic Reports Mailing → <Select a Solution> → Edit → Create E-Mail Recipient). You can also use SAP Solution Manager to create service level reports that are tailored to your requirements (for example.1 CCMS Monitoring – Internet Graphics Server (IGS)
Call transaction SIGS. These components are basic SAP Solution Manager functionalities.4.1 Application Monitoring
Several SAP Solution Manager components use the application log in transaction SLG1. to monitor the content of the SAP EarlyWatch Alert. select the RFC destination and choose Environment → Switch on CCMS.
SAP Solution Manager Operation Guide
SDOK SMSY_LOG_OBJ SOLAR
* * *
SAP Knowledge Provider System Landscape Log Object Solution Manager
Problem Analysis Tool Component SAP Solution Manager Monitor SLG1 Detailed Description Application Log
maintained and checked.
4. 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.1 Solution Manager Administration Work Center
SAP Solution Manager 7. This includes:
.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. database.sap. …) in SAP Solution Manager.com → SAP NetWeaver → SAP NetWeaver 7. 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.0 including Enhancement Package 2 → System Administration.1 is introducing a new Solution Manager Administration work center. 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. host. 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).1.
4. and perform technical administration and operation tasks. For more information see http://help.1 Landscape View
The Landscape view provides you with an overview about all components of a single landscape entity (like system.
banned.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. 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
. 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.1.SAP Solution Manager Operation Guide
READ RFC TMW RFC RFC for Solution Manager applications: Login Trusted Back RFC With User Trusted
4. configuration. This includes: Status information (failed.
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
.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.1. Here you can get information on the status of the managing and all managed systems. SLR.
The Introscope application allows you to centrally manage your CA Wily Introscope Enterprise Manager landscape: See the status / version of the installed Introscope Enterprise Managers (EM) Perform central user administration for Import existing installations Install new EM Maintain EM configuration parameters Performance metrics
BW Reporting is one of the main infrastructure components of a SAP Solution Manager System. here you get detailed information on: The overall status of your BW system Overall usage data and breakdown of used space per scenario Reporting Scenario Setup Detailed log information for each reporting use case with Self Checks for error analysis
4. the application server and the processes of which the system consists.2 Starting and Stopping
When you start the SAP System. There are different processes. depending on the SAP system and operating system platform.1. In the simplest case. an SAP System consists of only a database and a single application server.1.…)
4. 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.3 Self Diagnosis View
The Self Diagnosis view integrates the Self Diagnosis and the Diagnostics Self Check in one infrastructure.
Consistency Technology allows you to create a consistent image (or consistent copy) of a federated system landscape. see For details. SAP recommends that you run the database in archive mode
This means that all actions on the database that modify data are recorded by the database and written to a transaction log. With regular full backups of your database (either offline or online). and configuration files:
. You must ensure that backup devices are not lost along with normal data storage (separation of storage locations).SAP Solution Manager Operation Guide
You can start and stop systems and instances centrally. software.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. Depending on the processes you are running on the SAP Solution Manager. such as the loss of a data center through fire. and the runtime infrastructure.
4. The main issues in a backup and recovery process are: You must develop a backup concept in the implementation phase. For more information. see http://help.3
Backup and Restore
As the SAP Solution Manager is based on SAP NetWeaver. not only SAP systems. it is possible to restore a crashed database to any point in time before the crash. using the SAP Management Console for all platforms (as of SAP NetWeaver 7. the System Administration Work Center in SAP Solution Manager. Backup your database every day You must backup the log files several times a day. see SAP Help Portal at: http://help. The backup and restore strategy for your system landscape should be embedded in overall business requirements and incorporate your company‟s entire process flow.com → SAP NetWeaver → SAP NetWeaver 7. you may also need to backup external components and handle cross-system data dependencies. The backup and restore strategy must cover disaster recovery processes.
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. For details.0).sap.sap. as well as a complete set of transaction logs since the last backup.
A backup process must ensure logical and physical consistency. 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.com → SAP NetWeaver → SAP NetWeaver 7. You should not use a backup and recovery concept for your entire system landscape and single system components just for SAP systems. It should be embedded in all business requirements and take into account the entire process flow in your enterprise You must consider the following elements when you plan a backup and recovery strategy for application. without taking the systems offline. or the Microsoft Management Console under Windows. which is contained in databases. This concept must account for both the business data.0 including Enhancement Package 2 → <language> → Administrator’s Guide → Technical Operations for SAP NetWeaver → General Administration Tasks → Database Administration → <Database Name>. all general recommendations for an SAP NetWeaver backup and restore strategy apply.
Backup Introscope Enterprise Manager
The Introscope Enterprise Manager is temporary storage for workload-related data. so a separate backup of this component is usually not needed.3. Such tasks may be required on component level and are relevant in each scenario that uses the component. This program minimizes the administration required. Other tasks may be relevant for certain business scenarios only.
Restart Enterprise Manager
. However. or replacement of components made to the system landscape./data‟ contains all agent data The directory „. such as changes to the configuration.4
This chapter describes all automic tasks which run periodically to keep the application running over time. if you want to backup this component. The mapping is in the chapter scenario/component matrix above. SAP recommendation: There is no backup strategy to implement for Wily SmartStor. This depends on the frequency of such changes. You should also schedule the standard basis jobs in transaction SM36 in the SAP Solution Manager.4.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. In the standard setup.. Backup SmartStor (file backup) o o The directory „. The SAP Solution Manager background jobs can be scheduled with the transaction SM_CONFIG_JOBS. ABAP Standard Jobs Topic ABAP Standard Jobs Transaction / Link Transaction SM36 → Goto → Standard Jobs
4. its directories have to be backed up regularly: Wily supports only Offline backup with the following procedure Shutdown Enterprise Manager./traces‟ contains all Wily trace data.1 Background processing in the SAP Solution Manager
The background processing in SAP Solution Manager does not require regular administration. You must monitor the performance of these tasks regularly. Some SAP Solution Manager applications may require additional background jobs.. The standard jobs are scheduled automatically in the SAP Solution Manager setup (transaction SOLMAN_SETUP). this data is transferred once an hour to the BI of the SAP Solution Manager. to ensure that you can restore and recover them if there is a system failure. You need to back up individual components regularly. software upgrade of individual components. The administrator just has to ensure that no jobs are aborted.
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. see SAP Note 894279.
EFWK Resource Manager
. and starts the extractors in the extractor framework.
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.
1 User Administration and Authentication
A lot of RFC read connections are used in SAP Solution Manager. and forwards them to your SAP Solution Manager. in the Service Marketplace at http://service.com/diagnostics. this user must be defined previously in the CUA system.5. Work centers. The SAP Solution Manager security guide contains a comprehensive description of users and authorization.sap. manually. reorganization jobs ST: E2E Diagnostics . Some applications expect named RFC connections.BI Housekeeping . It is important that the users used are not prevented from getting information from the managed systems or sending data to SAP Solution Manager. which separate functions between different users.
. you must authorize the RFC connection user used. There is a detailed description of the user management in the root cause analysis scenario. 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. Conversely. in the managed systems and SAP Solution Manager. If this connection is not available. SAP Solution Manager is a singleclient system.01 SP15. It checks if there are new messages for your support team in the SAP global support backbone. The RFC wizard generates the RFC connections and users automatically. You can use the generated users with the setup.SAP Solution Manager Operation Guide
E2E BI HOUSEKEEPING
BI Housekeeping for diagnostics (for details see note 1480588) Central job for new monitoring and alerting infrastructure
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
User Management is very important in SAP Solution Manager.
4. have been available since 7.Information
4. If managed systems are in a central user administration. so users can only be separated by an authorization concept.
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. 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.5. which always require users in both systems.2 Create Users and Business Partners for End Users
The following lists give an overview of functions that require users in the SAP Solution Manager system and managed systems. Change Request Management). Change Request Management: if the users in the Change Request Management process log on to the managed systems via SAP Solution Manager. Implementation and Customizing Distribution use Trusted RFC connections.g. Test Management uses Trusted RFC connections. Service Desk. which always require users in both systems. Service Desk: for Key User (end user). Test Management: if testers have to test in managed systems.SAP Solution Manager Operation Guide
There are several user management tools (SAP & third-party systems).com/instguides http://service.com/diagnostics Usage Maintenance of Business Partners
4. Maintain Business Partners Tool Maintain Business Partner (transaction BP) Further Documentation Tool Security Guide – SAP Solution Manager Root Cause Analysis . 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.sap.User Administration Guide Link http://service. The table below provides an overview and a short description of these user management tools.sap.
Service Desk: for Key User (end users) and processors of service desk messages see example below. Select a system from which you want to create business partners. check the processing status of support messages in SAP Solution Manager. three systems in total. Create users for all end users in all three systems. Enter your user and choose change. The report AI_SDK_USER_BP_GEN determines new users in the managed systems.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. Create business partners for end users. Create User or Business Partners Automatically To ensure that the users of the managed systems can. and why. in the SAP Solution Manager system and the managed systems. as described above. 5. Confirm your entries. Select users. The system landscape consists of SAP Solution Manager and two managed systems. This e-mail address can be any address. 2. Choose User list → Add system. as long as it is known to the mail server (Business Process Operations: for use of auto-reaction methods). Create Business Partner Using Transaction BP_GEN 1. Choose Edit → Create Business Partner.
Functions Requiring Business Partners Based on Users in SAP Solution Manager Delivery of SAP Services: if you use Issue Management. for example. as Business Partners. during Root Cause Analysis configuration. Example You want to create end users for Service Desk functionality. as described above. in the SAP Solution Manager system. Enter the required data and save. 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. 4. 1. Address Data First Name and Last Name o Function: Digital Signature E-Mail o Function: Business Process Operations o Function: Solution Directory (Check in / Check out) o Function: Issue Management o Function: Service Desk o Function: E-Learning Management The user can receive and send e-mails. 3. 2. You can perform the following functions with this report: List new users by comparing SAP Solution Manager and managed systems:
. You have to create all end users known to SAP Solution Manager. they must be created as users and business partners in SAP Solution Manager.
Update Authorizations after Support Package Upgrade Topic Profile Generator: Upgrade and First Installation Transaction SU25 Detailed Description Update Authorizations after Support Package Upgrade
.5.SAP Solution Manager Operation Guide
As administrator. 2.htm
4. The dialog explains in detail what you need to do. If your security policy permits it.3 Update Authorizations after Support Package Upgrade
After the new installation and an update of your SAP Solution Manager system. you need to update your tables with new default field values for authorization objects. Recommendation Perform at least the first step. Caution When you update your system. find new managed systems for a customer and/or new users in a customer's managed systems.
Recommendation Create a variant and schedule the report as a weekly background work process. Choose Information. As SAP partner. you must import new roles and profiles from client 000 into your productive client. Call transaction SU25. you can automatically create or update new users and business partners in SAP Solution Manager. in transaction SU25.com/saphelp_sm70ehp1_sp2 6/helpdata/en/85/390f6e3c534892b18f5ec42 12d0571/frameset. check in which managed systems there are new users. This is especially relevant for all new authorization objects delivered with an update. you need to update your business partners
Create Users or Business Partners Automatically Tool Report AI_SDK_USER_BP_GEN Link http://help. Create Users and Business Partners for End Users Topic User Management Transaction SU01 Detailed Description Create Users
Create Business Partner
If you change e-mail addresses for users. Procedure 1. For more information please consult the corresponding SAP Help.sap.
5. e) Save your role. See document How to Adapt a Work Center View in the Service Marketplace. or customize the logon screen for Web Dynpro applications.4 Adapt Work Center Queries
End users and system administrators can adjust work centers to their needs. The system opens the documentation for this object in a separate window. if you want to grant full authorization. for instance: ZSU01_PFCG. c) Maintain all activity values per authorization object. according to your needs. you can create a dedicated role for them. System Administrator Configuring query settings for all end users. You are asked for a transport request. To be able to assign the correct authorization. This section describes how to create your own roles. b) Choose Change. for instance: Full authorization for SU01 and PFCG. using the example of critical authorizations of transactions SU01 (User Management) and PFCG (Role Management). the system traces all authorization objects required for this transaction. d) Go to tab menu and enter transactions SU01 and PFCG.5 Create End User Roles
You need to grant authorizations for which SAP does not ship template roles. and choose Single Role. b) Enter a role name in your namespace. for instance. always choose all activities. Create a Role in Transaction PFCG a) Choose transaction PFCG. If you are not sure about the function of the authorization object.sap. in the Service Marketplace.SAP Solution Manager Operation Guide
.com/solutionmanager → Media Library → How-To Documents
4. Maintain Authorization Objects Default authorization objects delivered by SAP contain only minimal authorizations. in the SAP Solution Manager and managed systems. To grant full authorization to authorization objects. The authorization objects required in role creation are maintained using transactions. 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. When you enter a transaction in the menu tab in your role. Caution All authorization objects need to have a green traffic light. c) Enter a description for your role. d) Generate the profile. you must edit them a) Choose the Authorizations tab in the Role Maintenance. double-click the green line. End User See document How to Adapt a Work Center View.
Enter the user name. 5. add your user in the table and perform the user comparison. Create End User Roles Topic User Management Role Maintenance Transaction SU01 PFCG Detailed Description Create End User Roles Create End User Roles
4. 6.5. Choose transaction PFCG. 3. Transaction PFCG 1. Enter the user and choose edit. f) Save. Enter your role. Save. Go to Users tab. in one of the two ways explained below. 2. Go to Roles tab. Enter your role and choose edit. 4. Choose the User Comparison button. 2.6 Assign Roles to Users
After you have generated profiles from roles. Save.SAP Solution Manager Operation Guide
e) To assign this profile to a user. assign the role to your users. choose User tab. 5. 4. Choose transaction SU01. 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
. 3. Transaction SU01 1.
Further Documentation Tool Service Marketplace – High Availability Help Portal Link http://www. all components with single point of failures must be set up with HA.sap.sdn.sap. You may also have requirements of your own.SAP Solution Manager Operation Guide
5 High Availability
There are no general High Availability (HA) requirements for the SAP Solution Manager. You can achieve this by controlling the growth of redundant data and implementing redundant systems control logic. This means integrating existing heterogeneous system landscapes to include business partners.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
. HA Setup Description Refer to the component high availability setup description.
Each of the above components can be a single point of failure in this scenario. and hardware. Otherwise explain here. depending on the availability requirements of the implemented IT management processes. At SAP. such as the operating system. SAP relies on the high availability applications of partner products for components which are mandatory for implementing the infrastructure. To achieve HA for the complete scenario. Collaborative business can give you a competitive advantage. and suppliers. customers.com/ → SAP NetWeaver → SAP NetWeaver 7. high availability is always focused on business applications and their related components. if available.com/irj/sdn/ha http://help. 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. database. Highavailability applications allow you to maximize downtime security and minimize downtimes.
can be archived using the ArchiveLink interface. Monitoring data in central performance history database Test packages/test cases These objects do not usually contain a lot of data.
.g. Those documents (or old versions) in Solution Manager projects can be archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. the following objects cannot be archived using default SAP archiving mechanisms: Solution Manager projects Solution landscapes CRM transactions. Depending on the number. Documents in Solution Manager projects The only function which might need a lot of database space is document management in the implementation scenario. the document attributes needed to administer the documents will be kept in SAP Solution Manager. have links to service tickets or change documents. SAP Note 1092503 describes how to automate the archiving by a job. service ticket. change requests. change documents and issues. because many functions. The following “Solution Reporting” documents can be archived: Service Reporting System Availability Reporting System Administration Reporting Change Management Reporting Service Desk Reporting Issue und Top Issue Reporting Expert-on-Demand Reporting CRM-based transactions (incidents.1 Achiving functionality in core SAP Solution Manager
There is only limited archiving functionality in SAP Solution Manager 7. Archiving these CRM-based transactions would break the links to them. to another repository. However.SAP Solution Manager Operation Guide
6 Archiving & Data Deletion in SAP Solution Manager
6. change requests. e. but it is not supported in SAP Solution Manager. such as service tickets. if they can still be deleted. Service reports in solutions Service sessions such as EarlyWatch Alert reports. For details. type and frequency of documents checked in. change document).) There is a generic way to archive CRM-based transactions (e. etc. several hundred MBs per week and project might be needed – because usually every version of a document is kept. such as test workbench and implementation projects.1. and might cause inconsistencies. and the documents attached to them. Documents on the generic CRM tabs (transaction CRMD_ORDER) cannot be archived. This report moves the document contents (files) from the built-in knowledge warehouse (KW) layer. The report SOLMAN_DOCU_VERSION_DEL deletes interim versions of any documents.g. In particular. SAP Note 546685 “Archiving in Solution Manager (Operation)” explains the functionality and setup in detail. an archive. It deletes all versions in all accessible repositories – particularly those documents which have already been archived using the report SOLMAN_DOCU_VERSION_ARCHIVE. Service Level reports. see SAP Note 845433.
change documents). or by directly executing report RDSMOPDELETESOLUTIONS. all objects produced within that solution (service sessions. Solution Manager projects can also be deleted using transaction SOLAR_PROJECT_ADMIN. Documents on the generic CRM tabs cannot be archived using this function. deletion of the solution might not be possible (as it is not possible to delete the related CRM transactions).SAP Solution Manager Operation Guide
Notes for Archiving SAP Note 546685 845433 1092503 Short Text Archiving in Solution Manager (Operation) Deleting a service process with support message Archiving reporting documents in SAP Solution Manager
6. When deleting a solution. The extension package requires a separate license.2
SAP Solution Manager Extended Archiving Functionality
The extension package “Extended Traceability” (ET).
6. A customer can save the objects using other methods (put objects in transport requests using migration functions. and generally available to customers with ST400 SP15. Without a valid license. use SAP content server for knowledge warehouse documents. Service reports in solutions SAP EarlyWatch Alert and service level reports could be stored on a separate file server. such as CRM transactions or test workbench items.g. They can be deleted from SAP Solution Manager using report RDSMOPREDUCEDATA. have been created.3
Alternative Storage & Deletion Strategies
Although generic archiving is not supported by most scenarios in SAP Solution Manager. keep backup of whole system before data deletion).
. these reports will not work. shipped with ST400 SP13. reports etc. Projects SAP Solution Manager projects can be stored in a transport using transaction SOLAR_PROJECT_ADMIN. but only for those which refer to a Solution Manager project (a function also delivered with the ET extension package). with the report SOLMAN_DOCU_VERSION_ARCHIVE. store reports on separate file server. Solutions Solutions can be deleted from SAP Solution Manager using the functionality in transaction DSWP. which carry an attribute for the solution. Similar functions are available to archive documents which are added to the CRM transaction tabs (e. it is not part of the SAP Solution Manager core functionality. If CRM transactions such as service tickets. this function will only store the business process structure and all related documents. The report SOLMAN_DOCU_VERSION_DEL can then delete the archived documents. it will not save referenced data. there are several functions to reduce the amount of data in the database. archives the documents (or old versions) in Solution Manager projects.) will be deleted – if this is possible. However.
which can be stored as an MS Word document.sap.for more information. but only if they have not been used in a service transaction. They can be deleted using transaction SECATT and STWBM. Test results can be consolidated and extracted in a test report. Archiving Test Management Topic Archiving Logs (SAP Library . BC-TWB-TST-ECA) Link http://help. because whenever a new template version is defined in the template project. eCATT objects (system data container. CATT scripts should be migrated to eCATT. if you want to reapply and distribute the template to other systems. They can be deleted via transaction STWB_2. They can be deleted using transaction SCAT and STWBM.com/solutionmanager → Media Library → Technical Papers
Test Management Test plans and packages are repository objects and can therefore be saved or stored using transport mechanisms. They can be downloaded as .com → SAP NetWeaver → SAP NetWeaver 7. see the SAP Netweaver online documentation. the older versions can no longer be accessed (retrieved).sap. and when to use them. CATT objects are repository objects and can therefore be saved or stored using transport mechanisms. eCATT logs can be archived .xml files.sap.
. For more information on how to distinguish template transports and (template) project transports. Test messages (service tickets created during tests) cannot be archived or deleted – see the section “Achiving functionality in core SAP Solution Manager”.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. Test cases of type “manual” or “external application” are repository objects and can therefore be saved or stored using transport mechanisms. They can be deleted using transaction SCAT and STWBM.eCATT: Extended Computer Aided Test Tool. (otherwise it would be sufficient to keep a backup copy of the project state.com → SAP Solution Manager
Templates Contents in templates should also be stored in transport requests. test configurations) are repository objects and can therefore be saved or stored using transport mechanisms. see: Archiving Templates Topic FAQ .SAP Solution Manager Operation Guide
Archiving Projects Topic SAP Solution Manager Help Link http://help. Store the contents in a template transport. test scripts.Handling Templates with SAP Solution Manager Link http://service. test data container. as defined under “Projects”).
and Business Process Monitoring data). CPH monitoring data.SAP Solution Manager Operation Guide
Data extracted to BI If data from SAP Solution Manager has been extracted for Business Intelligence (reporting on EWA raw data. root cause analysis data.
6.4 AP Notes for Additional/Background Information
SAP Note 544295 546685 566225 638785 845433 976695 1077447 1091497 1092503 Short Text Basis message: Deletion flag status Archiving in Solution Manager (Operation) Report to delete the basis notifications with deletion flag SAP Solution Manager . the BI aggregation and deletion mechanisms can be used to reduce the amount of data in the BI database. SMSY data.reduce data volumes Deleting a service process with support message New features for RDSMOPDELETESOLUTIONS in SP08 Solution Manager: TEST_DSMOPSERSESSN_DELETE Deleting in archive: RDARCH_ARCHIVE_DELETE_SOLMAN Archiving reporting documents in SAP Solution Manager
SAP Solution Manager Operation Guide
7 Software Change Management
Software change management standardizes and automates software distribution. After you have implemented a new support package or support package stack.1 Agents Consideration
Before any new Software update in Solution Manager. All agents will be put in „sleep‟ mode waiting to reconnect when Solution Manager will be put back in Normal Operation Mode. For instance. 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. this may be the activity Activate BC Sets. In case of an update. This is especially important for the basic settings. the SMD Agents connectivity layer must be set in Maintenance Mode in the Agent Administration application. 2.2 Configuration after Support Package Update
After you have implemented a new support package or support package stack (SAP Enhancement Package).
7. the basic configuration should be checked in transaction SOLMAN_SETUP. These functions support your project teams.2. recommended)
7. 3. its ICF service needs to be activated. with specified maintenance procedures. Call transaction SOLMAN_SETUP. development teams. Prerequisites Initially configure all basic settings using the guided procedure for the automatic basic settings configuration. For instance.
Using the Overview for Update Activities 1. you need to check your configuration settings for new and updated configuration tasks. we give an overview of both procedures. the Open Activities column shows the steps you need to execute. This is especially important for the basic settings. You should update your basic settings configuration by: Re-running the Guided Procedure for Automatic Basic Configuration (transaction SOLMAN_SETUP. global rollouts (including localizations).
7. You find this Agent Administration via the Solution Manager Administration Workcenter → Infrastructure → Agent Framework. maintenance. To do this. and open integration with third-party products.Automatic Update Configuration
You can use the guided procedure for the basic settings configuration to update your basic settings (transaction: SOLMAN_SETUP). its ICF service needs to be activated. and use your initially-created project to track update changes (see section Automatic Basic Settings Configuration). you can specify here whether you have to re-execute activities that have already been executed. The system updates this list automatically.
. In the following. After installing/upgrading/updating SAP Solution Manager. In Basic Configuration. The goal of software change management is consistent. If you select an entry in this table. the system displays a configuration table with all activities you need to perform after updating your system. with every newly-shipped Web Dynpro application. Update your authorizations. check all activities in the Overview area in transaction SOLMAN_SETUP. and application support teams. In the Overview. see SAP Note 1236420. you need to check your configuration settings for new and updated configuration tasks. and testing procedures for complex software landscapes and multiple software development platforms.1 Guided Procedure . with every newly-shipped Web Dynpro application. solution-wide change management.
The system flags the release information with a blue information icon in front of the IMG activity.com/~sapidb /011000358700001735062008E
7. Activate Release Notes Display release notes by choosing Release Notes. The note is valid for Solution Manager 7.2 SAP Reference IMG – Manual Update Configuration
You can update basic settings configuration and scenario-specific configuration using the SAP Reference IMG (transaction: SPRO).1 IMG as of SP01 SAP Note 1575395
7. Caution See SAP Note 1575395 for details of new IMG activities. Recommendation We recommend that you update your basic settings using the automated guided procedure.1 SP01.sap. This central note includes other required notes that are extended and renewed regularly. see section Guided Procedure (transaction SOLMAN_SETUP) . 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 1552585. these are only described in the note. in which you can automatically implement all notes included. you should implement it with the Notes Assistant (transaction SNOTE).com SAP Solution Manager <current release> http://service.Automated Update Configuration. If these notes contain manual actions. and deleted IMG activities. changed IMG activities.sap.SAP Solution Manager Operation Guide
You can use the existing implementation project to track all information about the setup progress of your basic settings. 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 1552585 regularly
. Call transaction SOLAR02 and choose your project.2.3
Ensure Basic Functions via SAP Note
In order to ensure that the basic functions of SAP Solution Manager are running properly.
.x Extension Add-Ons Changes to SAP Solution Manager 7.1 SP01: Authorizations in SAP Solution Manager system SAP Solution Manager: Basic functions 7.4
Support Packages and Patch Implementation
The SAP Solution Manager has several software components which have their own release strategy.1 IMG as of SP01 SM 7. For further information.SAP Solution Manager Operation Guide
7. Support Packages and Patch Implementation SAP Note 394616 539977 569116 608277 631042 939897 1109650 1575395 1562694 1552585 Short Text Release strategy for SAP Solution Manager (ST) Release strategy for add-on ST-PI Release strategy for Solution Manager Service Tools (ST-SER) Installing and updating content for SAP Solution Manager Release strategy for Implementation Content (ST-ICO) SAP Solution Manager usage data SAP Solution Manager 7. see the notes below.
adjust it as required. to be able to send data to SAP. If there is something is wrong with the EWA data collection. see SAP Note 33135: Guidelines for OSS1. with transaction SOLMAN_SETUP. For more information. For more information.
An SAP Support Portal connection is required. Usually this connection is created by the SAP Solution Manager Setup. adjust it as required.1
Connection to SAP
In transaction SM59. You can analyze your
.SAP Solution Manager Operation Guide
8. For more information. you will find a small red flag or a grey icon in the overview. see SAP Note 216952 “Service Data Control Center (SDCC) – FAQ”.2 SAP EarlyWatch Alert (EWA)
SAP EarlyWatch Alert is a good indicator for the functioning of the RFC connections. For further information. if not.
Check whether the distribution group is set to EWA. see SAP Note 762696 “Grey rating for EarlyWatch Alert”. see SAP Note 766505: OSS1: Changes to RFC Connection SAPOSS. The selfdiagnosis tool is highly configurable and can perform solution-specific or cross-solution self diagnosis. if not. 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. see the following SAP Notes: SAP Note 216952 762696 Short Text Service Data Control Center (SDCC) – FAQ Grey rating for EarlyWatch Alert
The self-diagnosis checks the system requirements for operating SAP Solution Manager. check if connection SAPOSS works. For more information. Therefore check regularly the the functioning of the EWA in the System Monitoring Work Center. You select Reports SAP EarlyWatch Alert and a specific managed system. A self-diagnostics module is available in SAP Solution Manager.
In this case check the RFC connections and SDCC. For more information.
You can perform a new analysis at any time. to check that the master data of a solution is consistent.
The self-diagnostics checks the RFC Connection. e. The self-monitoring functionality can be found in the Solution Manager Administration Work Center → Self-Diagnosis. By pressing the button “Settings” you can select which type should generate an alert and inform you. The selfdiagnosis analyses run daily. in the Alert Type area. You can customize SAP Solution Manager self-monitoring. batch jobs and performance values. For the SAP Solution Manager single solution.g.
Self-Diagnosis Topic New self diagnosis in SAP Solution Manager: a quick guide Link SAP Note 1073382
. with the self-diagnosis function. You can display the self-diagnosis results in various levels of detail: For the SAP Solution Manager (cross-solution). to avoid red alerts. to check whether the problems shown by alerts have been resolved. to identify SAP Solution Manager system performance problems.SAP Solution Manager Operation Guide
SAP Solution Manager system and/or a solution.g. in the background. by default. to identify and solve problems. e. e.g.
4.sap.* Comment AdminConsole SMDServer
Related Information Content SAP Netweaver Administrator Link http://help. Connect to your CA Wily Introscope WebView via web browser – usually o http://hostname:8081/webview/jsp/login.sap. Ensure that the version of your agent is the same as the version of the source on your SAP Solution Manager. Logging Categories Logging Category /Applications/AdminConsole/* Comment AdminConsole
Tracing Locations Tracing Location com.sup.5
Logging and Tracing
Logging and tracing is essential for analyzing problems in the SAP Solution Manager Java-based parts.SAP Solution Manager Operation Guide
8.admin.server. The Java-based parts all use the standard logging of AS Java. If the logon screen of your WebView does not appear.smd. which includes also a detailed troubleshooting section.htm
. For more information please consult the Wily Introscope User Guide or SAP Note 797147 “Wily Introscope Installation for SAP Customers”. Related Information Content Wily Introscope User Guide Wily Introscope Installation for SAP Customers Link http://service. The main logging catogries and tracing locations can be found in the following table.com/saphelp_nwpi71/helpdata/en/44/9 8320f33bf60d6e10000000a114a6b/content.jsp. 2. The equal sign icon indicates that the version is up to date. This can be configured by using the log configuration function of the SAP NetWeaver Adminstrator under Problem Management Logs and Traces Log Configuration. Check that CA Wily Introscope Enterprise Manager receives information from CA Wily Introscope Agent. CA Wily Introscope Enterprise Manager may not be active.com/diagnostics SAP Note 797147
8.* com. Verify in SMD → Diagnostics Setup → Managed Systems → Introscope Agent for the system in which the Introscope Agent is running 3.4
CA Wily Introscope
To check whether the CA Wily Introscope is running properly: 1.sap.sap.
Quick Link to SAP Service Marketplace (http://service. The configuration guide describes the configuration of SAP Solution Manager and its scenarios and functions.1 Related Guides
The master guide is a central starting point for the technical implementation of SAP Solution Manager 7. is in the security guide.
9. particularly about roles and authorizations. Installation Guide and Update Guide Related SAP Notes Released Platforms Network Security SAP Solution Manager Root Cause Analysis
. All security-related information.com) Instguides → SAP Components → SAP Solution Manager Notes platforms securityguide solutionmanager diagnostics
Related Information Content Master Guide. and its scenarios.SAP Solution Manager Operation Guide