End TO End Diagnostic

SAP Solution Manager 7.0 EhP1

END-TO-END ROOT CAUSE ANALYSIS SYSTEM LANDSCAPE SETUP GUIDEVersion 2.14, November 2010

END-TO-END ROOT CAUSE ANALYSISSystem Landscape Setup Guide

TYPOGRAPHIC CONVENTIONS ICONSType Style Example Text Represents Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example textEXAMPLE TEXT

Icon

Meaning Caution Example Note Recommendation Syntax

Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and 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. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text

EXAMPLE TEXT

END-TO-END ROOT CAUSE ANALYSISSystem Landscape Setup Guide

CONTENTS1 2 How to use this document .................................................................................................................. 8 General setup instructions ................................................................................................................. 8 2.1 Prerequisites ................................................................................................................................ 8 2.2 Managed system configuration .................................................................................................. 9 3 Migration from manual maintenance to SLD ................................................................................... 11 4 Product specific setup ...................................................................................................................... 13 4.1 SAP Solution Manager .............................................................................................................. 13 4.2 Enterprise Portal ........................................................................................................................ 14 4.3 CRM ............................................................................................................................................ 14 4.4 SAP ERP 6.0 / EhPx for SAP ERP 6.0 ....................................................................................... 16 4.4.1 Solution Manager version EhP1 SP5 (SP21) ...................................................................... 16 4.4.2 Solution Manager version < EhP1 SP5 (SP21) ...................................................................... 16 4.5 SAP Netweaver TREX ............................................................................................................. 17 4.6 SRM ............................................................................................................................................ 17 4.7 LiveCache ................................................................................................................................... 18 4.7.1 SLD Configuration.................................................................................................................... 19 4.7.2 SMSY Configuration ................................................................................................................ 21 4.7.3 Diagnostics Configuration ........................................................................................................ 21 4.8 XI / PI ........................................................................................................................................... 24 4.9 BI ................................................................................................................................................. 25 4.10 SAP BW Accelerator (BIA / BWA) ............................................................................................. 25 4.10.1 Sending Data to System Landscape Directory ..................................................................... 25 4.10.2 SMSY Configuration of the Technical System SAP BW Accelerator .................................. 26 4.10.3 Diagnostics Configuration .................................................................................................... 27 4.11 SAP NetWeaver J2EE ................................................................................................................ 29 4.12 Adobe Document Services........................................................................................................ 29 4.13 SAP NetWeaver CE 7.1 .............................................................................................................. 29 4.14 DUET 1.5 on SAP NW 7.0........................................................................................................... 30 4.14.1 Manual creation of MS .NET technical system for DUET 1.5 on SAP NW 7.0 ...................... 30 4.14.2 Duet Managed System Configuration ................................................................................... 32 4.15 Web Dispatcher 7.10 .................................................................................................................. 34 4.15.1 Manual creation of technical system for SAP Web Dispatcher 7.10 ..................................... 34 4.15.2 Diagnostics Configuration .................................................................................................... 36 4.16 SAP MDM 5.5 SP06 and SAP Netweaver MDM 7.1 ................................................................... 38 4.16.1 Manual creation of technical system for MDM ...................................................................... 38 4.16.2 Diagnostics Configuration .................................................................................................... 40 4.16.3 Configuration on managed system ....................................................................................... 42 4.17 SAP GRC Access Control 5.3.................................................................................................... 42 4.17.1 SLD Data Supplier Configuration ......................................................................................... 42 4.17.2 Solution Landscape Definition .............................................................................................. 43

End-to-End Root Cause Analysis System Landscape Setup Guide

4

4.17.3 Managed System Setup Wizard ........................................................................................... 46 4.18 SAP PPM by IDS Scheer 4.1 ...................................................................................................... 47 4.18.1 Manual Creation of Technical System for SAP PPM by IDS Scheer 4.1 ............................... 48 4.18.2 Managed System Setup Wizard ........................................................................................... 50 4.19 SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5..................................................................................... 52 4.19.1 SLD Data Supplier Configuration ......................................................................................... 52 4.19.2 Solution Landscape Definition .............................................................................................. 52 4.19.3 Managed System Setup Wizard ........................................................................................... 56 4.20 SAP Strategy Management 7.0/7.5 ............................................................................................ 58 4.20.1 SLD Data Supplier Configuration ......................................................................................... 58 4.20.2 Solution Landscape Definition .............................................................................................. 59 4.20.3 Managed System Setup Wizard ........................................................................................... 62 4.21 SAP BusinessObjects PCM 11.3 ............................................................................................... 63 4.21.1 Manual Creation of Technical System for SAP BusinessObjects PCM 11.3 ......................... 63 4.21.2 Managed System Setup Wizard ........................................................................................... 66 4.22 SAP BOBJ Extended Analytics 7.0 ........................................................................................... 68 4.22.1 Manual creation of technical system for SAP BOBJ Extended Analytics .............................. 68 4.22.2 Diagnostics Configuration .................................................................................................... 70 4.23 SAP BusinessObjects InterCompany 5.1 ................................................................................. 72 4.23.1 Manual creation of technical system for SAP BusinessObjects InterCompany 5.1 ............... 72 4.23.2 Diagnostics Configuration .................................................................................................... 73 4.24 SAP BusinessObjects Planning Extended 5.3 ......................................................................... 75 4.24.1 Manual creation of technical system for SAP BusinessObjects Planning Extended 5.3 ........ 76 4.24.2 Diagnostics Configuration .................................................................................................... 78 4.25 SAP BOBJ Financial Consolidation (BOFC) 7.0/7.5 or Finance 10.5 (XiR2) ........................... 79 4.25.1 Configuration on managed system ....................................................................................... 79 4.25.2 Manual creation of technical system for SAP BOFC ............................................................. 79 4.25.3 Diagnostics Configuration .................................................................................................... 83 4.26 SAP ePOS 3.1 ............................................................................................................................. 85 4.26.1 Manual creation of technical system for ePOS ..................................................................... 85 4.26.2 Diagnostics Configuration .................................................................................................... 88 4.27 SAP Manufacturing Execution (ME) 5.1 ................................................................................... 89 4.27.1 Sending Data to System Landscape Directory ..................................................................... 89 4.27.2 Configuring Technical System for SAP ME 5.1 .................................................................... 91 4.27.3 Diagnostics Configuration .................................................................................................... 92 4.28 SAP Talent OrgChart 1.1, 2.0 .................................................................................................... 93 4.28.1 Manual creation of technical system for SAP Talent OrgChart 1.1, 2.0 ................................ 94 4.28.2 Diagnostics Configuration .................................................................................................... 96 4.28.3 Configuration on managed system ....................................................................................... 97 4.29 SAP Talent Viewing 1.1, 2.0....................................................................................................... 97 4.29.1 Manual creation of technical system for SAP Talent Viewing 1.1, 2.0................................... 98 4.29.2 Diagnostics Configuration .................................................................................................. 100 4.29.3 Configuration on managed system ..................................................................................... 101 4.30 SAP Talent Planning 1.1, 2.0 ................................................................................................... 101 4.30.1 Manual creation of technical system for SAP Talent Planning 1.1, 2.0 ............................... 102 4.30.2 Diagnostics Configuration .................................................................................................. 104 4.30.3 Configuration on managed system ..................................................................................... 106 4.31 SAP Commodity SL 5.6/7.2 ..................................................................................................... 106 4.31.1 Manual creation of technical system for SAP Commodity SL 5.6/7.2.................................. 106 4.31.2 Diagnostics Configuration .................................................................................................. 109

SAP AG 2008


5

4.32 SAP eLearning Adobe Connect 6.02 ...................................................................................... 111 4.32.1 Manual creation of technical system for SAP elearning Adobe Connect............................. 111 4.32.2 Diagnostics Configuration .................................................................................................. 113 4.33 SAP RA 2.0, 2.7 ........................................................................................................................ 114 4.33.1 Manual creation of technical system for SAP RA................................................................ 115 4.33.2 Diagnostics Configuration .................................................................................................. 117 4.34 SAP ALM by SAP and Sungard 6.0, 6.1, 7.0 ........................................................................... 118 4.34.1 Manual creation of technical system for SAP ALM by Sungard .......................................... 118 4.34.2 Diagnostics Configuration .................................................................................................. 121 4.34.3 CA Wily Introscope Configuration ....................................................................................... 122 4.35 Questra IDM 5.2S ..................................................................................................................... 122 4.35.1 Sending Data to System Landscape Directory ................................................................... 122 4.35.2 Configuring Technical System for Questra IDM 5.2S ......................................................... 123 4.35.3 Diagnostics Configuration .................................................................................................. 125 4.36 SAP Reach Compliance 1.1..................................................................................................... 126 4.36.1 Check solution landscape .................................................................................................. 127 4.36.2 ABAP technical system setup............................................................................................. 129 4.36.3 Java technical system setup............................................................................................... 130 4.37 SAP Commodity SL (NW) 5.6/7.2 ............................................................................................ 131 4.37.1 Configuring Technical System for TPT Commodity SL (NW) .............................................. 132 4.37.2 Diagnostics Configuration .................................................................................................. 135 4.38 SAP BCM 6.0 ............................................................................................................................ 136 4.38.1 Manual creation of technical system for SAP BCM 6.0 ....................................................... 136 4.38.2 Update Component Template for BCM .............................................................................. 138 4.38.3 Diagnostics Configuration .................................................................................................. 138 4.39 SAP BusinessObjects Enterprise XI R2 ................................................................................. 140 4.39.1 Creation of Technical System for BOE platform ................................................................. 140 4.39.2 Creation of Technical System for BOE Web Application Server ......................................... 144 4.39.3 Installation of Diagnostics Agent ........................................................................................ 146 4.39.4 Diagnostics Configuration .................................................................................................. 146 4.39.5 Diagnostics Configuration for Web Application Server ....................................................... 149 4.39.6 Additional setup steps ........................................................................................................ 149 4.40 SAP BusinessObjects Enterprise XI 3.0 & 3.1 ....................................................................... 150 4.40.1 Creation of Technical System for BOE platform ................................................................. 151 4.40.2 Creation of Technical System for BOE Web Application Server ......................................... 155 4.40.3 Creation of Technical System for BOE IIS server ............................................................... 158 4.40.4 Creation of Product System for BOE platform and assignment of Technical System .......... 161 4.40.5 Creation of Product System for BOE WAS and assignment of Technical System .............. 163 4.40.6 Creation of Product System for BOE IIS and assignment of Technical System .................. 164 4.40.7 Managed System Setup of BOE platform Technical System .............................................. 167 4.40.8 Managed System Setup of BOE WAS Technical System ................................................... 170 4.40.9 Managed System Setup of BOE IIS Technical System....................................................... 174 4.40.10 Setup configuration extraction of BOE platform Technical System ..................................... 178 4.40.11 Configuration of Remote Database Monitoring ................................................................... 184 4.41 SAP Business Objects Explorer XI 3.2 ................................................................................... 185 4.41.1 Modification of technical system for SBOP Web Application Server ................................... 185 4.41.2 Modification of technical system for SBOP Explorer ........................................................... 188 4.41.3 Installation of Diagnostics Agent on all hosts...................................................................... 190 4.41.4 Diagnostics Configuration for SBOP Explorer technical system ......................................... 190 4.41.5 Diagnostics Configuration for SBOP Web Application Server ............................................. 193 4.41.6 Diagnostics Configuration for SAP BW Accelerator (BWA) ................................................ 196 4.41.7 Setup database configuration extraction of Business Objects Enterprise ........................... 196

SAP AG 2008


6

4.41.8 Configuration of Remote Database Monitoring for Business Objects Enterprise ................ 196 4.41.9 Additional setup steps ........................................................................................................ 196 4.42 SAP eSourcing 4.2, 5.0 ............................................................................................................ 196 4.42.1 Manual creation of technical system for SAP eSourcing..................................................... 196 4.42.2 Diagnostics Configuration .................................................................................................. 199 4.43 SAP POS 2.0, 2.1, 2.2 and 2.3 .................................................................................................. 202 4.43.1 Manual creation of technical system for SAP POS ............................................................. 202 4.43.2 Diagnostics Configuration .................................................................................................. 205 4.44 SAP Archiving & Document Access by Open Text 9.5.1, 9.6.1 & 9.6.0 ............................... 207 4.44.1 Manual Creation of Technical System for SAP Archiving & Document Access by Open Text 9.5.1, 9.6.1 & 9.6.0 ............................................................................................................................ 207 4.44.2 Managed System Setup Wizard ......................................................................................... 210 4.45 SAP Environmental Compliance 3.0 ....................................................................................... 212 4.45.1 Check solution landscape .................................................................................................. 212 4.45.2 Java technical system setup............................................................................................... 214 4.46 Syclo Agentry Servers ............................................................................................................. 215 4.46.1 Manual creation of technical systems for Syclo Agentry Servers ........................................ 216 4.46.2 Installation of Diagnostics Agent ........................................................................................ 217 4.46.3 Diagnostics Configuration for Syclo Agentry Servers ......................................................... 217 4.46.4 Additional configuration steps............................................................................................. 219 4.47 SAP BPC 5.1/7.0/for Microsoft ................................................................................................ 220 4.47.1 Manual creation of technical systems for SAP BPC 5.1/7.0/for Microsoft ........................... 220 4.47.2 Installation of Diagnostic Agents ........................................................................................ 225 4.47.3 Diagnostics Configuration .................................................................................................. 225 4.47.4 BPC specific configuration of Wily Agents .......................................................................... 228 4.47.5 Configuration of Remote Database Monitoring ................................................................... 228 4.48 SAP BPC 7.0 for SAP Netweaver ............................................................................................ 228 4.48.1 Manual creation of technical systems for the BPC .NET Server ......................................... 228 4.48.2 Creation of technical systems for the BPC ABAP stack ...................................................... 233 4.48.3 Installation of Diagnostic Agents ........................................................................................ 236 4.48.4 Diagnostics Configuration for BPC .NET Server ................................................................. 236 4.48.5 BPC specific configuration of Wily Agents for BPC .NET Server ........................................ 239 4.48.6 Diagnostics Configuration for BPC ABAP stack ................................................................. 239 4.49 SBOP PC 7.5 FOR SAP NW ..................................................................................................... 239 4.49.1 Manual creation of technical systems for the BPC .NET Server ......................................... 239 4.49.2 Creation of technical systems for the BPC ABAP stack ...................................................... 244 4.49.3 Installation of Diagnostic Agents ........................................................................................ 246 4.49.4 Installation of Wily Introscope .NET Agent.......................................................................... 247 4.49.5 Diagnostics Configuration for BPC .NET Server ................................................................. 247 4.49.6 Diagnostics Configuration for BPC ABAP stack ................................................................. 249 4.50 SBOP PC 7.5 for Microsoft ...................................................................................................... 249 4.50.1 Manual creation of technical systems for SBOP PC 7.5 for Microsoft ................................. 249 4.50.2 Hosts and database ........................................................................................................... 249 4.50.3 System Component for BPC .net Server ............................................................................ 251 4.50.4 System Component for Microsoft SQL Server Analysis Services ....................................... 253 4.50.5 System Component for Microsoft SQL Server Reporting Services ..................................... 254 4.50.6 System Component for Microsoft SQL Server Integration Services .................................... 256 4.50.7 BPC System....................................................................................................................... 257 4.50.8 Installation of Diagnostic Agents ........................................................................................ 260 4.50.9 Enable Diagnostics Agents to read Windows Performance Monitor Data ........................... 260 4.50.10 Enable Diagnostics Agents to read Configuration and Log data from Microsoft SQL Server Components ...................................................................................................................................... 260

SAP AG 2008


7

4.50.11 Installation of Wily Introscope .NET Agent.......................................................................... 262 4.50.12 Diagnostics Configuration .................................................................................................. 262 4.50.13 Diagnostics Configuration of MS SQL Server Analysis Services ........................................ 264 4.50.14 Diagnostics Configuration of MS SQL Server Integration Services ..................................... 265 4.50.15 Diagnostics Configuration of MS SQL Server Reporting Services ...................................... 266 4.50.16 Diagnostics Configuration of BPC Server ........................................................................... 267 4.50.17 Configuration of Remote Database Monitoring ................................................................... 268 4.51 Syclo Agentry Servers ............................................................................................................. 268 4.51.1 Manual creation of technical systems for Syclo Agentry Servers ........................................ 268 4.51.2 Installation of Diagnostics Agent ........................................................................................ 269 4.51.3 Diagnostics Configuration for Syclo Agentry Servers ......................................................... 269 4.51.4 Additional Configuration Steps ........................................................................................... 271 4.52 SAP CPS for Netweaver 7.0..................................................................................................... 272 4.52.1 SLD Data Supplier Configuration ....................................................................................... 272 4.52.2 Solution Landscape Definition ............................................................................................ 272 4.52.3 Managed System Setup Wizard ......................................................................................... 273 4.53 SAP WS&O by ClickSoftware 1.0 ............................................................................................ 276 4.53.1 Manual Creation of Technical System for SAP WS&O by ClickSoftware 1.0 ...................... 276 4.54 SAP Alloy ................................................................................................................................. 282 4.55 ACROBAT CON LEARN BY ADOBE 7.0 ................................................................................. 289 4.55.1 Manual creation of technical system for SAP elearning Adobe Connect............................. 290 4.55.2 Diagnostics Configuration .................................................................................................. 291 4.56 NRX VIP 4.4 .............................................................................................................................. 293 4.57 SAP Convergent Charging 2.0 ................................................................................................ 294 4.57.1 Manual creation of technical system for SAP Convergent Charging ................................... 294 4.57.2 Installation of SAP Solution Manager Diagnostics Agent and SAP Host Agent .................. 298 4.57.3 SAP Solution Manager Diagnostics Configuration .............................................................. 298 4.58 SAP EIO by SmartOps 6.3 (Enterprise Inventory Optimization) ........................................... 301 4.58.1 Configuring Technical System for SAP EIO by SmartOps 6.3 ............................................ 301 4.58.2 Diagnostics Configuration .................................................................................................. 304 4.59 SAP Invoice Management (VIM Approval Portal) by Open Text 5.2 ..................................... 305 4.59.1 SLD Data Supplier Configuration ....................................................................................... 305 4.59.2 Solution Landscape Definition ............................................................................................ 306 4.59.3 Managed System Setup Wizard ......................................................................................... 308 4.59.4 CA Wily Introscope Configuration ....................................................................................... 310 4.60 SAP Invoice Capture Center by Open Text 5.2 ...................................................................... 311 4.60.1 SLD Data Supplier Configuration ....................................................................................... 311 4.60.2 Solution Landscape Definition ............................................................................................ 311 4.60.3 Diagnostics Configuration .................................................................................................. 314 4.60.4 CA Wily Introscope Configuration ....................................................................................... 315 4.61 SAP RTOM 7.0 (Real Time Offer Management) ...................................................................... 316 4.61.1 Configuration on managed system ..................................................................................... 316 4.61.2 Manual creation of technical system for SAP RTOM .......................................................... 316 4.61.3 Diagnostics Configuration .................................................................................................. 319 4.62 VERTEX O SERIES 4.0, 5.0 ..................................................................................................... 321 4.62.1 Configuration of Diagnostics & Introscope Agent................................................................ 321 4.62.2 Manual creation of technical system for VERTEX O SERIES ............................................. 321 4.62.3 Diagnostics Configuration .................................................................................................. 325

SAP AG 2008


8

1

How to use this document

Diagnostics in SAP Solution Manager depends on the definition of technical system inside SAP Solution Manager. This document describes the steps needed to create or maintain your technical systems inside the system landscape of SAP Solution Manager. The next chapter contains a general overview of the setup procedure of a managed system. Chapter 3 describes how to resolve conflicts with the conflict resolution wizard provided in SAP Solution Manager. This is especially useful when replacing a manually created solution with a central SLD (System Landscape Directory) based solution. Chapter 4 takes care of all specialties that are needed for certain products that either differ from the general setup procedure or require manual activities to enable all diagnostics functionalities for systems of that product.

22.1

General setup instructionsPrerequisites

Before starting the configuration of a technical system for diagnostics in SAP Solution Manager, you have to ensure that the following prerequisites are all fulfilled: 1. Basic Configuration of SAP Solution Manager is performed You need to perform the basic configuration of your SAP Solution Manager system. Starting with EhP1 for SAP Solution Manager, this can be done using transaction SOLMAN_SETUP. 2. Diagnostics Agent is installed For each system you want to connect a diagnostics agent needs to be installed for each virtual hostname of that system. More Information: http://service.sap.com/diagnostics Installation & Configuration Diagnostics Agent Installation Guide In addition there is a troubleshooting guide available, that explains common installation scenarios (like setup of the agent in clustered or HA environments: http://service.sap.com/diagnostics Media Libraray 3. Plugins are updated on managed system (ABAP only) Before starting the connection of a managed system that is based on ABAP, you need to ensure that the components ST-PI and ST-A/PI are updated in the managed system. More information: SAP Note 1010428 Select the note relevant for your Solution Manager SP 4. Managed System is connected to SLD infrastructure In order to enable a central maintenance of systems in SAP Solution Manager, you need to setup a SLD infrastructure to which each managed system is connected to. There are several possibilities how this infrastructure can be designed. More Information: https://www.sdn.sap.com/irj/sdn/nw-sld Planning Guide - System Landscape Directory 5. Bridge your central SLD to the SAP Solution Manager SLD If your SAP Solution Manager system is not your central SLD system, you need to setup a bridge forwarding from your central SLD to your SAP Solution Manager SLD. More information: SAP Note 1148028 6. Landscape Fetch Job in SAP Solution Manager is scheduled The system landscape maintenance in SAP Solution Manager retrieves the system landscape data regularly from the configured SLD. This is done via the landscape fetch job which is normally scheduled during configuration. You can reschedule this job via transaction SMSY_SETUP.

SAP AG 2008


9

2.2

Managed system configuration

After you have ensured that all prerequisites are met you can start the configuration of a managed system using transaction SOLMAN_SETUP. 1. Open the configuration wizard for SAP Solution Manager (Transaction: SOLMAN_SETUP). 2. Select Managed System Configuration. 3. Select system type of the system you want to configure. 4. For ABAP based systems, you need to select the client that you want to connect to. (This is not needed for non-ABAP system). 5. Select Configure System.

The first step creates the RFC connections to the managed system for ABAP systems. 6. Enter an administration user for the Solution Manager system and for the managed system. 7. Choose which RFC connections shall be created. 8. Select Create RFC.

The prerequisites check checks if all requirements for configuring diagnostics are fulfilled on the managed system. 9. Select Execute to automatically perform the check. 10. The detailed results can be accessed through the Details link in the log table after selecting the line item for the check.

In the manual configuration step all relevant manual configuration activities are listed. The list of steps is not dependent on the product of the selected system. You need to identify the needed steps by reading the documentation (available with the IMG Documentation link) and deciding based on the documentation, if the step needs to be performed for your system. 11. After performing a manual configuration activity use the execution status column to set the status of this activity to performed.

SAP AG 2008


10

The Diagnostics configuration step contains all steps needed for configuring diagnostics for your managed system. Again you only need to perform the necessary steps for your system based on the product or system type. 12. After performing the activities for your system, start the Diagnostics managed system wizard by clicking the description of the activity Configure Diagnostics and perform the wizard based on the documentation available in the IMG Documentation column. The Wily Introscope configuration is only needed for J2EE or .Net based system. 13. Start the Introscope wizard by clicking the description of the activity Configure Wily Introscope Agent and perform the wizard based on the documentation available in the IMG Documentation column. After performing the agent deployment you may need to perform only the necessary steps for your system based on the product or system type. Please refer to the IMG documentation for instructions on how to do this. The last step is to assign your newly connected system to a logical component or create a new one. 14. Select the appropriate product version and main instance, if not automatically proposed. 15. Create a new logical component (if needed). 16. Assign the system to the appropriate role of the logical component. 17. Select Save Logical Components to save your changes.

SAP AG 2008


11

3

Migration from manual maintenance to SLD

Systems created manually in the Solution Manager System maintenance before the landscape fetch from SLD has been enabled may cause duplicate entries for the manually created ones. In case of ABAP and Java systems such conflicts can be resolved by usage of the wizard Manage Conflicts for Technical Systems. Systems manually created after the fetch from SLD will not be considered as duplicates in the wizard. Select Conflict Resolution for Technical Systems from the Related Links of the Managed System Configuration.

Potential conflicts due to duplicate systems are listed in the Duplicates section of this wizard. The details of the selected entry are displayed with the potential conflicts as comparison both duplicate entries. All rows marked with the conflict symbol contain a difference between both systems.

SAP AG 2008


12

The normal procedure would be to select one of the duplicate systems as master and execute one of the options from the radio buttons by clicking the Save button. In case no one of the systems has been assigned to logical components yet there is a free choice of the master system possible. Normally the manually created system is taken as master. Following three options are possible: 1. Use master system as reference and reassign header data from the other system. If the manually created system is master it would get updates via SLD. 2. Use master system as reference and delete the other system. Here no reassignment of data would take place. It might also make sense to select the SLD system. 3. Keep all systems without change. After saving the entry will disappear from the duplicates list. As soon as one of the duplicate systems is assigned to logical components there is no free master selection possible anymore. Here the system assigned to logical components is master by default. When both systems are already assigned to logical components the only option left is to keep both systems without a change. Otherwise the conflict needs to be resolved manually in the system landscape maintenance transaction (SMSY).

SAP AG 2008


13

44.1

Product specific setupSAP Solution Manager

For the Solution Manager the procedure described for the Managed System Configuration needs to be followed. It is important to verify that the correct product instances are selected and marked as relevant.

PRODUCT INSTANCES FOR SAP SOLUTION MANAGER Solution Manager ABAP Stack Solution Manager ABAP Stack

The initial screen of Managed System Configuration shows the Solution Managers Java stack as NOT DIAGNOSTIC RELEVANT, the traffic light is red. 1. Click on the marked link in the Managed Products column to correct this behavior.

2. Deselect the checkbox NOT DIAGNOSTIC RELEVANT. 3. Click Set to save the changes.

The Landscape status changed to green for both Stacks. 4. Continue the setup by pressing the Setup Button below.

SAP AG 2008


14

4.2

Enterprise Portal

For Enterprise Portal the procedure described for the Managed System Configuration needs to be followed. It is important to verify that in the Configure Diagnostics step the correct product instance Enterprise Portal is marked as relevant.

PRODUCT INSTANCES FOR SAP NETWEAVER 04 Enterprise Portal

PRODUCT INSTANCES FOR SAP NETWEAVER 7.0 Enterprise Portal

PRODUCT INSTANCES FOR SAP EHP1 FOR SAP NETWEAVER 7.0 Enterprise Portal

4.3

CRM

For CRM the procedure described for the Managed System Configuration needs to be followed. It is important to verify that the correct product instances are marked as relevant. E.g. the relevant instances for a system running product version CRM 2007 are shown below:

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide Depending on the CRM scenario the following product instances can be marked as relevant within SAP CRM 4.0: PRODUCT INSTANCES FOR SAP CRM 4.0 CRM Application Server ABAP CRM IC Webclient_640 CRM ICS WFM CS_640 CRM Intelligence Connector_640 IPC Web Applications_640 E-Selling_640 CRM_ICSS_640

15

PRODUCT INSTANCES FOR SAP CRM 5.0 CRM Application Server ABAP CRM Application Server Java Mapbox

PRODUCT INSTANCES FOR SAP CRM 5.2 CRM Application Server ABAP CRM Application Server Java

PRODUCT INSTANCES FOR SAP CRM 2007 CRM Application Server ABAP CRM Application Server Java

PRODUCT INSTANCES FOR SAP CRM 7.0 CRM Application Server ABAP CRM Application Server Java

PRODUCT INSTANCES FOR SAP CRM 7.0/NW7.01 CRM Application Server ABAP CRM Application Server Java

SAP AG 2008


16

4.4

SAP ERP 6.0 / EhPx for SAP ERP 6.0

4.4.1 Solution Manager version EhP1 SP5 (SP21)As of Solution Manager version EhP1 SP5 (SP21) E2E Root Cause Analysis applications do not require a manual configuration step in SMSY. EHP x FOR SAP ERP 6.0 should be recognized as product version. In the Managed System Setup, EHP x FOR SAP ERP 6.0 must be marked as relevant for Diagnostics and the setup must include the main instances you want to manage with RCA applications (for example SAP ECC Server VPack successor).

4.4.2 Solution Manager version < EhP1 SP5 (SP21)EHP x FOR SAP ERP 6.0 is not directly supported by E2E Root Cause Analysis applications but requires a manual configuration step in SMSY: You need to assign SAP ERP 6.0 as an additional product version to your EHP x FOR SAP ERP 6.0 system. 1. In SMSY, navigate to your EHP x FOR SAP ERP 6.0 system. 2. On the Header Data tab click Installed Product Versions and add product version SAP ERP 6.0.

In the Managed System Setup, SAP ERP 6.0 must be marked as relevant for Diagnostics and the setup must include the main instances of SAP ERP 6.0 which you want to manage with RCA applications (for example SAP ECC Server). Additional information E2E Root Cause Analysis applications like Change Analysis, Error Analysis or Workload Analysis are based on main instances. For SAP ERP 6.0 the following main instances are supported meaning that content is delivered with Solution Manager to manage these main instances with RCA applications:

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide SAP ECC Server SAP SEM SAP SRM Server SRM-MDM Catalog SAP NW Business Intelligence SAP NW Enterprise Portal SAP NW Process Integration SAP NW Adapter Engine J2EE SAP NW Search and Classif. (TREX) SAP NW Application Server Java SAP NW BI Java For a SAP ERP 6.0 system no manual configuration step in SMSY is required.

17

4.5

SAP Netweaver TREX

To setup a TREX 7.0 / 7.1 technical component you have to setup a Netweaver 7.0 System with the same SID as the TREX. The TREX component has to be linked via SLD to the SMD for details please check chapter Sending Data to System Landscape Directory of the BWA setup. After that, assign in SMSY the TREX System Component to the main instance Search and Classif. (TREX) of the Netweaver System.

4.6

SRM

Also for SAP SRM it is important to verify that the correct product instance SRM Server is marked as relevant. Please note that prerequisite for inclusion of product instance CCM with SRM-MDM Catalog into the diagnostics setup the latest suitable version of the config.xml file from SAP note 1259109 need to be implemented to the Solution Manager. E.g. for a system running product version SAP SRM 7.0 it is shown below:

SAP AG 2008


18

PRODUCT INSTANCES FOR SAP SRM 5.0 SRM Server CCM with SRM-MDM Catalog


PRODUCT INSTANCES FOR SAP SRM 6.0/NW7.01 SRM Server CCM with SRM-MDM Catalog


PRODUCT INSTANCES FOR SAP SRM 7.0/NW7.01 SRM Server CCM with SRM-MDM Catalog

4.7

LiveCache

In the current version SCM-APO is supported, LiveCache support tools will be provided. While the LiveCache ABAP System (Technical System ABAP) can be configured straight forward with the Installation Wizard, some extra configurations have to be performed for the Technical System LIVE_CACHE. To publish LiveCache Data to the Landscape Directory (SLD) some prerequisites have to be fulfilled for the ABAP Instance and also for the SLD Server. These are listed below:

SAP AG 2008


19

SLD RELEASE 640 700 701 710

MIN. SUPPORT PACKAGE Not supported SP 16 Fully Supported Fully Supported

Table 1: SLD Server Prerequisites

SCM SERVER SCM 4.1 SCM 5.0 SCM 2007 SCM 7.0

BASIS VERSION 640 700 700 701

MIN. SUPPORT PACKAGE SP 23 (or SAP Note 1063473) SP 17 (or SAP Note 1063473) SP 17 (or SAP Note 1063473) No Min. Support Package required

Table 2: SCM Server Prerequisites In addition you have to ensure that the latest version of the ST-A/PI plugin is installed on the SCM (or other system) where the LiveCache is connected to.

4.7.1 SLD ConfigurationThe data necessary for the SLD are collected via the data supplier available in ABAP. Start the configuration of the System Landscape Directory (Transaction RZ70) and send the collected data to your System Landscape Directory. 1. Start the configuration of the System Landscape Directory (Transaction RZ70)

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 2. Check your SLD connection information.

20

3. Check that the data collection program for LiveCache is active.

4. Activate the settings.

Known Problems After having implemented the required Support Package or SAP Note 1063473, the Data Supplier LiveCache might not occur on the list. The configuration of the Local SLD Administration has to be reloaded from the Database. Please perform the following steps: 1. Menu Reload. 2. Menu Activate.

SAP AG 2008


21

4.7.2 SMSY Configuration1. After the Landscape fetch was successful the LiveCache should automatically occur in SMSY beyond Landscape Components System Components LiveCache. 2. LiveCache has now to be connected to the corresponding System (see figure below).

SCM system

LiveCache assignment

4.7.3 Diagnostics ConfigurationAfter making sure that your LiveCache system is correctly set up in SLD and SMSYand after having installed a Diagnostics Agent on all servers, you can proceed with the diagnostics configuration for you LiveCache system.

Before you can start the configuration of the LiveCache system, you have to fully perform the setup of the corresponding SCM server.

SAP AG 2008


22

1. Open the diagnostics setup application from the common tasks area of the Root Cause Analysis Workcenter (Transaction: SOLMAN_WORKCENTER). 2. Choose Managed Systems. 3. Choose Setup Wizard.

4. Jump to the SID of your LiveCache.

5. Set the LiveCache as Diagnostics Relevant. 6. Start the Setup using the Setup button.

SAP AG 2008


23

7. In the Setup Parameters step, ensure that the following settings are made: a. The ABAP RFC of the SCM server is automatically shown. This is needed because the extractors are collecting the necessary LiveCache Data via this RFC. b. Please fill in the System Install Path: i. for UNIX: /sapdb/ ii. for Windows: \\\sapdb\ 8. Continue with the setup. 9. After successful setup the LiveCache Extractors are started.

SAP AG 2008


24

4.8

XI / PI

For XI / PI the procedure described for the Managed System Configuration needs to be followed. The XI / PI system can be configured straight forward with the Setup Wizard.

SAP AG 2008


25

4.9

BI

For BI the procedure described for the Managed System Configuration needs to be followed. It is important to verify that the correct product instances are marked as relevant. Relevant product instances for product version SAP Business Warehouse (BW 3.0/3.1) ABAP Stack Business Intelligence Relevant product instances for product version SAP Netweaver 04 (BW 3.5) ABAP Stack Business Intelligence Relevant product instances for product version SAP Netweaver BI 7.0 ABAP Stack Business Intelligence JAVA Stack BI JAVA This is an example of a SAP Netweaver BI 7.0 double-stack system (ABAP+JAVA stack, same SID):

4.10 SAP BW Accelerator (BIA / BWA)Before you setup a SAP BW Accelerator system (Technical System Type = TREX), the setup of the connected BI ABAP Stack (Technical System ABAP) has to be completed. Unlike the setup of the BI system, which can be configured straight forward with the Installation Wizard, some extra configurations have to be performed for the Technical System SAP BI Accelerator.

4.10.1 Sending Data to System Landscape DirectoryTo publish SAP BI Accelerator to the Landscape Directory (SLD), please follow the instructions in SAP Notes: 1147499 "Connection to the System Landscape Directory" => TREX 1018839 "Registering in the System Landscape Directory using sldreg" And check SAP Help for further information: http://help.sap.com/saphelp_nw70/helpdata/EN/42/e33ae230ba3ee2e10000000a1553f6/frameset.htm

SAP AG 2008


26

4.10.2 SMSY Configuration of the Technical System SAP BW Accelerator1. Open the configuration wizard for SAP Solution Manager (Transaction: SOLMAN_SETUP). 2. Select Managed System Configuration. 3. Select Maintain Technical Systems.

4. 5. 6. 7.

Open tray of System Type TREX. Mark the right SID. Select Change. Select Add Main Instance.

8. In the new screen search for BI Accelerator. 9. Open the Product and drill down the hierarchy: Product Product Version Main Instance. 10. Mark the Main Instance BI Accelerator.

11. You can see the new Main Instance BI Accelerator for product version SAP BI Accelerator 7.0. 12. Select Save and Close.

SAP AG 2008


27

4.10.3 Diagnostics ConfigurationAfter setting up the technical system, the Diagnostics configuration needs to be performed. 1. Open the configuration wizard for SAP Solution Manager (Transaction: SOLMAN_SETUP). 2. Select Managed System Configuration. 3. Select system type TREX. 4. Select the previously maintained BIA system. 5. Select Configure System.

6. Select Diagnostics Configuration. 7. Perform the described steps for the managed system of type BIA (detailed description available in the linked IMG documentation as link SAP BIA-Specific Configuration). 8. Set the status of the activity to performed. 9. Start the diagnostics wizard using the link Configure Diagnostics.

10. Your system is pre-selected. 11. To mark the system as diagnostics-relevant open the tray. 12. Unselect the checkbox Not Diagnostic Relevant. 13. Select Set.

14. Select Setup to continue the setup.

15. To maintain details for the system open the tray. 16. Enter the name of the RFC connection from Solution Manager to the ABAP stack of the BI system as ABAP RFC Destination. 17. Select Set. 18. Select Next to perform detailed setup steps.

SAP AG 2008


28

19. Unselect Wilyhost Agent if selected, as we do not deploy any agent on the BIA blades.

20. Select Setup to activate the extractors for the BIA. The BIA extractors will be executed on the ABAP stack of the connected BI system to collect data from the BIA via RFC call.

How to find the name of the connected BI System? The RFC Service Name of the BIA can give you a hint about the connected BI System. Here: Trex_EE1 => EE1 is the SID of the connected BI.

How to find the connection from Solution Manager to the ABAP stack of the BI system? 1. Use transaction SMSY in the SAP GUI of the Solution Manager System. 2. Select Find and enter the SID of the BI ABAP System where the BIA is connected to. 3. Select Find again until you are in the Systems section.

4. Open the tray of the SID to select the Main Instance Business Intelligence. 5. Use the entry of RFC Read Access for the productive client of the BI System. This is the name of the generated RFC connection from Solution Manager to the BI system.

SAP AG 2008


29

4.11 SAP NetWeaver J2EEFor SAP NetWeaver J2EE systems the procedure described for the Managed System Configuration needs to be followed. It is important to verify that the correct product instances are marked as relevant. Relevant product instances for product version SAP NetWeaver J2EE Java Stack Application Server Java

4.12 Adobe Document ServicesFor systems that run the Adobe Document Services the procedure described for the Managed System Configuration needs to be followed. It is important to verify that the correct product instances are marked as relevant. Relevant product instances for product version SAP NetWeaver J2EE Java Stack Application Server Java Adobe Document Services

4.13 SAP NetWeaver CE 7.1For Netweaver CE 7.1 the procedure described for the Managed System Configuration needs to be followed. The Netweaver CE system can be configured straight forward with the Setup Wizard. There are just two important steps at the beginning of setup procedure: Make sure, the product SAP NETWAEVER CE 7.1 is assigned:

Make sure the Main Instance Composite Applications is assigned:

SAP AG 2008


30

For the usage of E2E Trace Application, it is important to make sure, that the ICM http log parameter is correctly set. Therefore please logon to host of managed system and change the parameter file, e.g.: /usr/sap//SYS/profile/_J_. Make sure, this file contains the following entry:###########ICM Logging################# icm/HTTP/logging_ = PREFIX=/, LOGFILE=, LOGFORMAT=SAPSMD2, FILTER=SAPSMD, MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on

Additional information about syntax and usage of parameter values can be found in SAP help under: Profile Parameters for the ICM and SAP Web Dispatcher icm/HTTP/logging_ . After setting the parameter, please restart the instances. No other additional NW CE Specific setup steps have to be performed.

4.14 DUET 1.5 on SAP NW 7.0For DUET 1.5 on NW 7.0 only the JAVA technical system (Duet J2EE) is automatically created via the SLD. The automatic creation of MS .NET technical systems via the SLD is currently not supported. Therefore you need to use the Maintain Technical Systems wizard to create the MS .NET technical systems.

4.14.1 Manual creation of MS .NET technical system for DUET 1.5 on SAP NW 7.0In case the MSFT Request Handler and MSFT Metadata Server are installed on the same server, you only need to create one MS .NET technical systems as described in the steps below. If they are installed on different server you need to create two MS .NET technical systems. Therefore step 3 to step 15 need to be repeated.

SAP AG 2008


31

1. Start transaction SOLMAN_SETUP. 2. Navigate to Managed System Configuration Maintain Technical Systems.

3. Select Create.

4. Enter a System ID for the DUET Microsoft .NET components. In case the MSFT Request Handler and the MSFT Metadata Server are installed on the same server you only need to create one technical system for both. 5. Select type MS .NET. 6. Select Save.

SAP AG 2008


32

7. Select Add Main Instance. 8. Select product DUET product version DUET 1.5 ON SAP NW7.0 main instance SAP Duet OAO Metadata Server. 9. In case the MSFT Request Handler and the MSFT Metadata Server are installed on the same server you can also add the MSFT Request Handler. Therefore select Add Main Instance. 10. Select product DUET product version DUET 1.5 ON SAP NW7.0 main instance SAP Duet OAO RQ Handler

11. Select Save.

12. Select the Instance tab. 13. Enter an instance name following the naming convention IIS_on_, e.g.: IIS_on_vmw2004. 14. Enter a server name. If you cannot select the appropriate server from the value help, create a new server using the New Server button. 15. Select Save.

4.14.2 Duet Managed System ConfigurationFor Duet the procedure described for Managed system configuration needs to be followed. For the MS .NET technical system it is important to verify that in the Configure Diagnostics step the correct instances SAP Duet OAO Metadata Server and SAP Duet OAO RQ Handler are marked as relevant.

SAP AG 2008


33

When you are asked for the system parameters of the MS .NET technical system, enter the Microsoft Internet Information Services (IIS) installation path (which is by default C:\Inetpub) in the System Installation Path and Software Component Path fields.

For the Duet JAVA technical system it is important to verify that in the Configure Diagnostics step the correct instance SAP Duet Java is marked as relevant.

SAP AG 2008


34

4.15 Web Dispatcher 7.10The automatic creation of the technical system for SAP Web Dispatcher 7.10 via SLD is currently not supported. As a consequence the technical system for SAP Web Dispatcher 7.10 has to be created manually before using the managed system wizard.

4.15.1 Manual creation of technical system for SAP Web Dispatcher 7.101. Open the System Maintenance application from the common tasks area of the Root Cause Analysis Workcenter (Transaction: SOLMAN_WORKCENTER).

2. Select Create.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 3. Enter the System ID of your SAP Web Dispatcher into field Technical System, select type Web Dispatcher and enter a description. 4. Select Save.

35

5. Select Add Main Instance. 6. Select the Product SAP NETWEAVER AS ABAP Product Version SAP NETWEAVER AS ABAP 7.1 Main Instance SAP Web Dispatcher. 7. Select OK. 8. Flag the System as Production. 9. Select Save.

10. Select Tab Instances. 11. Enter the SAP Web Dispatcher Instance in the following format: __. 12. Enter the server name. 13. Choose server role WEBDISPATCHER. 14. Select Save.

SAP AG 2008


36

15. Go to transaction SMSY in Solution Manager system. 16. Go to Landscape Components System Components Web Dispatcher. 17. Select the correct Web Dispatcher SID. 18. Click on the Display/Change button.

19. Go to the tab Software Components. 20. Change the release from 7.20 to 7.10. 21. Click on Save.

4.15.2 Diagnostics ConfigurationAfter setting up the technical system, the diagnostics configuration needs to be performed. 1. Open the configuration wizard for SAP Solution Manager (Transaction: SOLMAN_SETUP). 2. Select Managed System Configuration. 3. Select system type WEBDISP. 4. Select the previously created Web Dispatcher system. 5. Select Configure System.

6. Choose Diagnostics Configuration. 7. Start the diagnostics wizard using the link Configure Diagnostics.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 8. Your system is pre-selected. 9. To mark the system as diagnostics relevant open the tray.

37

10. Unselect the checkbox. 11. Select Set.

12. Select Setup to continue.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 13. Enter the file path where the SAP Web Dispatcher is installed (typically /usr/sap/). 14. Enter the instance number of the SAP Web Dispatcher instance. 15. Enter the http port of the Web Dispatcher Admin Page. 16. Enter the relative URL of the Web Dispatcher Admin Page (typically /sap/admin). 17. Select Set to accept the parameters. 18. Select Next to continue the setup.

38

4.16 SAP MDM 5.5 SP06 and SAP Netweaver MDM 7.1For SAP MDM an automated creation of the technical system via the SLD is currently not supported. Therefore you have to maintain the MDM system manually using the Technical Systems wizard. Afterwards perform the Diagnostics Configuration for the MDM system using the Managed System Configuration wizard.

4.16.1 Manual creation of technical system for MDM1. Call transaction SOLMAN_SETUP. 2. Select Managed System Configuration. 3. Select Maintain Technical Systems.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 4. Select Create.

39

5. Enter the System ID of your MDM Server into field Technical System, select type MDM Server and enter a description. 6. Select Save. Please note: SAP MDM 5.5 systems are not installed with a System ID, however, in order to identify the system uniquely in Diagnostics you need to make up and enter a unique system ID here. 7. Select Add Main Instance. 8. Depending on your MDM Product Version, select the Product Version SAP MDM 5.5 or the Product Version SAP Netweaver MDM 7.1. Select the Main Instance Master Data Server. 9. Select Save. 10. Flag the System as Production. 11. Select Save. Please note: If you want to perform the Diagnostics setup for a SAP Netweaver MDM 7.1 system with SAP Solution Manager 7.0 < SP19, please refer to SAP Note 1268326.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 12. Select Tab Instances. 13. Enter the MDM System Instances, the Server and the corresponding Server Roles. For the instance naming convention we recommend the following: __. 14. If you cannot select the appropriate server from the value help, create a new server using the button New Server.

40

15. Select the Tab Database. 16. Enter the MDM Server Database via the value help or create a new database and select Save.

4.16.2 Diagnostics ConfigurationAfter setting up the technical system, the diagnostics configuration steps need to be performed. 1. Open the configuration wizard for SAP Solution Manager (Transaction: SOLMAN_SETUP). 2. Select Managed System Configuration. 3. Select System Type MDM. 4. Select the previously created MDM system. 5. Select Configure System.

SAP AG 2008


41

6. Perform the described activities for the managed system configuration. A description for each activity is available in the linked IMG documentation. For managed systems of type MDM only the following steps and activities are relevant: Step Check Prerequisites. Under step Manual Configuration the activities Install Diagnostics Agent and Configure DBA Cockpit. Under step Diagnostics Configuration the activities SAP MDM-Specific Configuration and Configure Diagnostics. Step Create logical Components. 7. Set the execution status of each activity executed to Performed. 8. The activity Configure Diagnostics starts the Setup Wizard. 9. If the system is marked as Not Diagnostics Relevant, proceed as follows: a. Open the tray. b. Unselect the checkbox Not Diagnostics Relevant. c. Select Set. 10. Select Setup to continue the setup.

11. For each instance you need to enter the system installation path. For MDM 5.5 this is usually D:\Program Files\SAP MDM 5.5 for Windows or /opt/mdm/ for UNIX. For SAP Netweaver MDM 7.1 this is usually D:\usr\sap\ respectively /usr/sap/. 12. In case of SAP Netweaver MDM 7.1 specify additionally the instance path.

SAP AG 2008


42

13. In case of SAP Netweaver MDM 7.1 specify additionally the Software components path for the MDM Server which is the same as the instance path for the MDM Server. This is required for the Command Console to be able to execute the MDM specific commands in the correct directory. 14. After entering the needed information, save the data and continue the setup.

4.16.3 Configuration on managed systemAfter setting up the MDM system using the managed system wizard, you need to perform further activities to enable all functionality of End-to-End Root Cause Analysis for SAP MDM: 1. Switch on reporting of MDM Server specific Wily Introscope metrics: a. Open the MDM Server specific configuration files from the MDM installation directory in an editor (mds.ini for MDM Server, mdis.ini for MDM Import Server, mdss.ini for MDM Syndication Server). b. Set the parameters as follows: Wily Instrumentation=True Wily Instrumentation Level Threshold=10 c. Restart the MDM Server Component. 2. Enable MDM Server Process Monitoring: a. Please refer to SAP Note 1257903.

4.17 SAP GRC Access Control 5.34.17.1 SLD Data Supplier ConfigurationSLD Data supplier is configured to stream its system landscape information to the central SLD. As SAP GRC Access Control 5.3 is hosted on the SAP J2EE Engine, SLD data supplier was successfully configured to report the appropriate data to central SLD.

SAP AG 2008


43

4.17.2 Solution Landscape DefinitionAfter the SLD Data has been transferred over successfully, we define the solution landscape definition in SMSY for GRC Access Control. 1. For further assistance, refer to SAP Note 987835. 2. Enter transaction SMSY in Solution Manager. The following components of the system landscape definition will be automatically created once the SLD data supplier is configured from the managed system: Server Database System Components.

3. Check if the database is created properly as shown. (Landscape components Databases Managed System SID).

4. Check if the system component is created properly as shown. (Landscape components Java Managed System SID).

SAP AG 2008


44

Creation of systems: Systems have to be manually created. The end result of creating a system in SMSY for SAP GRC Access Control 5.3 should look like as follows (NOTE: A SAP Netweaver product version was added manually to complete the creation of a system for SAP GRC Access Control 5.3). Please follow the steps below to complete the creation of a system.

1. Create a system with the following information; use Managed System SID for the System.

2. Under the tab Selection of Main Instances, select GRC Java Components and assign the appropriate SID and its type. (Java in this case).

SAP AG 2008


45

3. Change over to change mode . Under the tab Header Data, click Installed Product Version (highlighted red). 4. A new window should open as shown in the figure below. Check Free Product/Select Product Version, select the product and the product version as shown. 5. Use the Copy button to copy the product in the list below. After savin you should see a new added product SAP Netweaver 7.0.

Very Important Step 6. Because of adding SAP Netweaver to the list of product versions above, another system is automatically added under the name SAP Netweaver. Please scroll down to check under Systems SAP Netweaver . 7. By default, SAP Netweaver system assumes that the component beneath is Application Server ABAP. As SAP GRC Access Control is a Java based product, we need to change the component to Application Server Java. This is achieved by deselecting the Relevant checkbox for Application Server ABAP and selecting the same checkbox for Application Server Java.

SAP AG 2008


46

4.17.3 Managed System Setup WizardThe managed system setup wizard is used after the GRC Access Control 5.3 solution landscape has been designed in SMSY. This is the final step towards completing the Solution Manager Diagnostics setup for GRC Access Control 5.3. 1. In the Managed System Setup Wizard, select the appropriate SID of the managed system.

2. As the product versions SAP GRC Access Control 5.3 and SAP Netweaver 7.0 both were added during the SMSY setup, we should be able to see the same in the wizard. Use the CTRL key to select both product versions and click on Set. The result should like as shown in the figure. Click next to add the System installation path and Instance path of the GRC Access Control 5.3 application. 3. In the figure shown: System Install Path : C:\usr\sap\. Instance Path: C:\usr\sap\\JCxx. Click on Set and Next to finish this step.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 4. Before the setup of managed system setup wizard we should see the following screen.

47

5. After the setup is finished the screen should look like as shown.

4.18 SAP PPM by IDS Scheer 4.1For SAP PPM by IDS Scheer 4.1, an automated creation of the technical system via the SLD is currently not supported. Therefore you have to create the technical system manually and then connect the managed system using the managed system wizard.

SAP AG 2008


48

4.18.1 Manual Creation of Technical System for SAP PPM by IDS Scheer 4.11. Log on to the Solution Manager system. 2. Open the system maintenance application from Common Tasks area of the Root Cause Analysis Workcenter (Transaction SOLMAN_WORKCENTER).

3. Select Create.

SAP AG 2008


49

4. Enter a System ID for your SAP PPM by IDS Scheer 4.1 (LBP) into the field Technical System, select type Unspecified and enter a description, i.e. Technical System for SAP PPM by IDS Scheer 4.1 for SP18. 5. Select Save.

6. Select Add Main Instance. 7. Select the Product Version SAP PPM by IDS 4.1 Main Instance Process Extractor SAP-2-PPM. 8. Repeat the above step to add Process Performance Manager for the above Product Version. 9. Flag the System as Production. 10. Select Save.

11. Select Tab Instances. 12. Enter the LBP System Instance, the Server and the corresponding Operating System and its version. i.e. PPM41_vmw2464. 13. If you cannot select the appropriate server from the value help, create a new server using the button New Server.

SAP AG 2008


50

14. Select Tab Database. 15. Check Maintain Database Use checkbox. 16. Enter the LBP Server Database via the value help or create a new database and select Save.

4.18.2 Managed System Setup WizardAfter setting up the technical system with SMSY Wizard, the managed system setup wizard is used for the SAP PPM by IDS Scheer 4.1 solution manager diagnostics setup. 1. In Solution Manager Diagnostics, go to Diagnostics Setup Managed Systems Setup Wizard and enter the SID in the Jump to SID field.

SAP AG 2008


51

1. Expand the breadcrumb in the detail and un-check Not Diagnostics Relevant. 2. Select product version and click on Set.

3. Set the installation path to D:/ppm4/ and Component Paths as specified Click on Set and Next to finish this step.

4. Before setup, we should see the screen similar to the one shown on the left.

5. After setup, we should see the screen similar to the one shown on the left.

SAP AG 2008


52

4.19 SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.54.19.1 SLD Data Supplier ConfigurationSLD Data supplier is configured to stream its system landscape information to the central SLD. As SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5 is hosted on the SAP J2EE Engine, SLD data supplier was successfully configure to report the appropriate data to central SLD.

4.19.2 Solution Landscape DefinitionAfter the SLD Data has been transferred over successfully, we define the solution landscape definition in SMSY for SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5 1. Log on to the Solution Manager system. 2. For further assistance, refer to SAP Note 987835. 3. Enter transaction SMSY in Solution Manager. The following components of the system landscape definition will be automatically created because of the SLD data supplier from the managed system: Server Database System Components Check if the server is created properly as shown below (i.e. Landscape components Server vmw2464).

SAP AG 2008


53

4. Check if the database is created properly as shown to the left (i.e. Landscape components Databases LB2).

5. Check if the system component is created properly as shown to the left (i.e. Landscape components Java LB2). 6. The PMM components for 6.7, 7.0 and 7.1 should show following PRICE_MANAGER 6.7/7.0/7.1 PRICE_OPTMZER 6.7/7.0/7.1 PROFIT_ANALYZER 6.7/7.0/7.1 DEAL_MANAGER 6.7/7.0/7.1 The PMM component for 7.5 should show PMM_VENDAVO 7.5 Note: If it is not the case as specified in step 6, you can choose the software components specific to your installed product release manually by selecting the From Main Instance command button in change mode.

7. Check the instances are selected.

Fig.1

8. Creation of systems: Systems are created /refreshed via SLD data. The end result of creating a system in SMSY for SAP PMM by Vendavo 6.7 should look like to the left,(NOTE: A SAP Netweaver product version was added manually to complete the creation of a

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide system for SAP PMM by Vendavo 6.7).\

54

Fig 2

In Case of PMM 7.0 the system should have following products assigned ( Fig 1) SAP NETWEAVER 7.0 SAP PRICE & MARGIN MGT 7.0

Fig 3

In Case of PMM 7.1 the system should have following products assigned ( Fig 2) SAP NETWEAVER 7.1 SAP PRICE & MARGIN MGT 7.1

In Case of PMM 7.5 the system should have following products assigned (Fig 3) SAP NETWEAVER CE 7.1 SAP PRICE & MARGIN MGT 7.5

If the Product versions are not assigned as mentioned in step 7 then proceed as follows:-

Fig.4

Switch to change mode

.

Click on Select the Product and Product Versions as mentioned in Fig 6 & 7.

Fig 5

Fig 6.

SAP AG 2008


55

Please use the following instructions to complete the step:

9. Under the tab Selection of Main Instances, select Application Server and assign the appropriate SID (example: LB200001).

10. Change over to change mode . Under the tab Header Data, click Installed Product Version. A new window should open as shown in the figure below. Check Free Product/Select Product Version, select the product and the product version as shown to the left. 11. Use the Copy button to copy the product in the list below. Save the selection and one should see a new product SAP Netweaver 7.0 added. 12. Very Important Step Because of adding SAP Netweaver to the list of product versions above, another system is automatically added under the name SAP Netweaver. Please scroll down to check under Systems SAP Netweaver LBH. By default, SAP Netweaver system assumes that the component beneath is Application Server ABAP. As SAP PMM is a Java based product, we need to change the component to Application Server Java. This is achieved by de-selecting the Relevant checkbox for Application Server ABAP and selecting the same checkbox for Application Server Java. See the figure to the left.

SAP AG 2008


56

4.19.3 Managed System Setup WizardThe managed system setup wizard is used after the SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5 solution landscape has been designed in SMSY. This is the final step towards completing the Solution Manager Diagnostics setup for SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5 1. Using Solution Manager Diagnostics go to Diagnostics Setup Managed Systems Setup Wizard, enter the SID in the Jump to SID field and hit Enter.

SAP AG 2008


57

2. As the product versions SAP PMM by Vendavo 6.7, and SAP Netweaver 7.0 both were added in the previous step, we should be able to see the same in the wizard. Use the CTRL key to select both product versions and click on Set. Note: Based on your installation you have to choose your product version: SAP PMM by Vendavo 6.7, 7.0, 7.1, 7.5

3. The result should like as shown to the left.

4. Click next to add the details in the next screen as shown to the left. Set the install path for PMM 6.7 as follows. Example: D:/Vendavo/ and expand and enter correct optional component path for all the components, i.e. DEAL_MANAGER, PRICE_MANAGER, PRICE_OPTMZER, and PROFIT_ANALYZER to d:/Vendavo/. Set the install path for PMM 7.0,7.1 as follows. Example D:\Vendavo-NetWeaver\7.1\ for the PMM components, i.e. PRICE MANAGER 7.0,7.1, PRICE OPTIMIZER, 7.0,7.1 PROFIT_ANALYZER 7.0,7.1, DEAL MANAGER 7.0,7.1 Set the install path for PMM 7.5 Software component will be

SAP AG 2008


58

D:/PMM_VENDAVO 7.5/

5. Before setup, we should see similar screen as shown to the left.

6. After setup, the results are as shown to the left.

4.20 SAP Strategy Management 7.0/7.54.20.1 SLD Data Supplier Configuration SLD Data supplier is configured to stream its system landscape information to the central SLD. SAP Strategy

SAP AG 2008


59

Management 7.0 or 7.5 is hosted on the SAP J2EE Engine, SLD data supplier can be configured to report the appropriate data to central SLD.

4.20.2 Solution Landscape DefinitionAfter the SLD Data has been transferred over successfully, we define the solution landscape definition in SMSY for SAP Strategy Management 7.0 or 7.5. 1. Log on to the Solution Manager system. 2. For further assistance, refer to SAP Note 987835. 3. Enter transaction SMSY in Solution Manager. The following components of the system landscape definition will be created automatically once the SLD data supplier is defined from the Managed system. Server Database System Components Check if the server is created properly as shown below (i.e. Landscape components Server jhyv00459520b).

Check if the system component is created properly as shown to the left (i.e. Landscape components Java LB2).

SAP AG 2008


60

4. Creation of Systems: Systems have to be manually created. The end result of creating a system in SMSY for SAP Strategy Management 7.5 should look like as follows (NOTE: A SAP Netweaver product version was added manually to complete the creation of a System for SAP Strategy Management 7.5).

Please use the following instructions to complete the Step: 5. Create a system (i.e. CEY).

6. Under the tab Selection of Main Instances, select Application Component on NW CE, Application Server, Frontend Diagram Manager, Frontend Excel Addin, Interactive Publisher and assign the appropriate SID (i.e. CE100002).

SAP AG 2008


61

7. Change over to change mode. Under the tab Header Data, click Installed Product Version. A new window should open as shown in the figure below. Check Free Product/Select Product Version, select the product and the product version as shown to the left.

8. Use the Copy button to copy the product in the list below. Save the selection and one should see a new product SAP Netweaver 7.1 added.

9. Very Important Step Because of adding SAP Netweaver to the list of product versions above, another system is automatically added under the name SAP Netweaver. Please scroll down to check under Systems SAP Netweaver CEA. By default, SAP Netweaver system assumes that the component beneath is Application Server ABAP. As SAP Strategy Management is a Java based product, we need to change the component to Application Server Java. This is achieved by deselecting the Relevant checkbox for Application Server ABAP and selecting the same checkbox for Application Server Java. See the figure to the left.

SAP AG 2008


62

4.20.3 Managed System Setup WizardThe managed system setup wizard is used after the SAP Strategy Management 7.0 or 7.5 Solution Landscape has been defined in SMSY. This is the final step towards completing the Solution Manager Diagnostics setup for SAP Strategy Management 7.0 or 7.5. 1. Using Solution Manager Diagnostics go to Diagnostics Setup Managed Systems Setup Wizard, enter the SID in the Jump to SID field and hit enter.

2. As the product versions SAP Strategy Management 7.0/7.5 and SAP Netweaver 7.1 both were added in Step 14, we should be able to see the same in the wizard. Use the CTRL key to select both product versions and click on Set.

3. The result should look like as shown in the screen on the left.

SAP AG 2008


63

4. Click next to add the details in the next screen as shown to the left. Remember to expand and enter correct optional component path for all the components, i.e. SAP STR. MGM. INT. PUB. 7.5: C:/Program Files/SAP/SSM/InternetPub/ SAP STR. MGM. AP. COMP. 7.5: C:/ And for Install path, use i.e. C:/Program Files/SAP/SSM/. 5. Before setup, we should see the screen similar to the one shown on the left.


4.21 SAP BusinessObjects PCM 11.34.21.1 Manual Creation of Technical System for SAP BusinessObjects PCM 11.3For SAP BusinessObjects PCM 11.3, an automated creation of the technical system via the SLD is currently not supported. Therefore, you have to create the technical system manually and then run managed system setup wizard.

SAP AG 2008


64

1. Log on to the Solution Manager system. Open the system maintenance application from Common Tasks area of the Root Cause Analysis Workcenter (Transaction SOLMAN_WORKCENTER).

2. Select Create.

SAP AG 2008


65

3. Enter a System ID for your SAP BusinessObjects PCM 11.3 (PCM) into the field Technical System, select type Unspecified and enter a description, i.e. Technical System for SAP BusinessObjects PCM 11.3. 4. Select Save.

5. Select Add Main Instance. 6. Select the Product Version BOBJ PCM 11.3 SP1 Main Instance BOBJ ACTIVITY ANALYSIS. 7. Flag the System as Production. 8. Select Save.

9. Select Tab Instances. 10. Enter the PCM System Instance, the Server and the corresponding Operating System and its version. i.e. PCM113_VMW2586. 11. If you cannot select the appropriate server from the value help, create a new server using the button New Server.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 12. Select the Tab Database. 13. Check Maintain Database Use checkbox. 14. Enter the PCM Server Database via the value help or create a new database. 15. Select Save.

66

4.21.2 Managed System Setup WizardAfter setting up the technical system with SMSY Wizard, the managed system setup wizard is used for the SAP BusinessObjects PCM 11.3 solution manager diagnostics setup. 1. In Solution Manager Diagnostics go to Diagnostics Setup Managed Systems Setup Wizard, enter the SID in the Jump to SID field and hit enter.

SAP AG 2008

End-to-End Root Cause Analysis System Landscape Setup Guide 2. Expand the breadcrumb in the detail and Uncheck Not Diagnostics Relevant. 3. Select product version and click on Set.

67

4. Set the installation path (i.e. D:/Program Files/Business Objects/Profitability/) and click Next to finish this step.

5. Before setup, we should see the screen similar to the one shown on the left.

SAP AG 2008


68


4.22 SAP BOBJ Extended Analytics 7.0For SAP BOBJ Extended Analytics an automated creation of the technical system via the SLD is currently not supported. Therefore you have to create the technical system manually and afterwards perform the managed system configuration using the Diagnostics setup wizard.

4.22.1 Manual creation of technical system for SAP BOBJ Extended Analytics1. Go to the transaction /nSOLMAN_WORKCENTER and choose Root Cause Analysis tab. Open the System Maintenance Application from the Common Tasks area

2. Select Create

SAP AG 2008


69

3. Enter a System ID for SAP BOBJ Extended Analytics into the field Technical System, select type MS. Net and enter a description 4. Select Save

5. Select Add Main Instance 6. Select the Product Version BOBJ Extended Analytics 7.0 Main Instance 7. Repeat the above step to add Product Version MS IIS 6.0 Main Instance MS IIS 8. Select the Product Version MSFT .NET 2.0 Main Instance MSFT .Net Framework 9. Flag the System as Production 10. Select Save

11. Select Tab Instances. 12. Enter the BOBJ Extended Analytics 7.0 Instance, the Server and the corresponding Operating

End TO End Diagnostic

Documents

Transcript of End TO End Diagnostic