RCA Inst Upgr Guide SP13

8/10/2019 RCA Inst Upgr Guide SP13

http://slidepdf.com/reader/full/rca-inst-upgr-guide-sp13 1/38

SAP Solution Manager 7.0

End-to-End Root Cause Analysis

Root Cause Analysis

Installation and Upgrade Guide

Document Version 2.10 – May 2008

Valid for SAP Solution Manager 7.0 SP13



© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted

in any form or for any purpose without the express

permission of SAP AG. The information contained herein

may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks

or registered trademarks of IBM Corporation in the United

States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks

of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

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.

Documentation on SAP Service Marketplace

You can find this documentation atservice.sap.com/instguidesNW04

SAP AG

Dietmar-Hopp-Allee 1669190 Walldorf GermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com



T y p o g r a p h i c C o n v e n t i o n s

Type Style Represents

ExampleText

Words or characters quotedfrom the screen. Theseinclude field names, screentitles, pushbuttons labels,menu names, menu paths,and menu options.

Cross-references to other documentation.

Exampletext

Emphasized words or phrases in body text,graphic titles, and tabletitles.

EXAMPLETEXT

Technical names of systemobjects. These includereport names, programnames, transaction codes,table names, and keyconcepts of a programming

language when they aresurrounded by body text, for example, SELECT andINCLUDE.

Exampl et ext

Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variables and parameters,source text, and names of installation, upgrade anddatabase tools.

Exampletext Exact user entry. These arewords or characters that youenter in the system exactlyas they appear in thedocumentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries inthe system.

EXAMPLE

TEXT

Keys on the keyboard, for

example, F2 or ENTER.

I c o n s

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



Contents May 2008

Root Cause Analysis Installation and Upgrade Guide I

Contents

1 SUMMARY ..................................................................................................................... 1

2 IMPORTANT INFORMATION ......................................................................................... 22.1 SAP Notes f or the Implementation ...................................................................... 22.2 Information Avail able on SAP Service Marketpl ace ........................................... 2

3 IMPLEMENTATION METHODOLOGY ........................................................................... 33.1 Implementation Planning ..................................................................................... 33.2 Installation and Conf igurati on ............................................................................. 53.3 Updating from <=SP12 t o SP13 ........................................................................... 7

4 SAP SOLUTION MANAGER LANDSCAPE PLANNING ................................................ 84.1 Distribut ion of SAP Solution Manager Components .......................................... 84.2 Hardware for SAP Solution Manager .................................................................. 9

5 INSTALLATION/UPGRADE OF SAP SOLUTION MANAGER 7.0.................................. 95.1 Installation/Upgrade Guides for SAP Solution Manager 7.0 .............................. 95.2 Conf igure SLD .................................................................................................... 105.3 Software prerequisites for Root Cause Analysis.............................................. 10

5.3.1 General Information on Software prerequisites .......................................... 105.3.2 Software prerequisites for Wily Introscope Agents ..................................... 10

5.4 Specifi c Upgrade Installation from <=SP12 to SP13......................................... 115.4.1 Deactivation and Suppression of Previous BI Process Chain..................... 115.4.2 Upgrading End-to-End Workload Analysis to SP13 ................................... 115.4.3 Remove previous installation of Wily EP Agents ........................................ 12

5.5 Installation/Upgrade of Wily Introscope Enterprise Manager .......................... 125.6 Diagnost ics Agent Inst allation .......................................................................... 125.7 Required users for inst allation .......................................................................... 125.8 Required TCP ports ........................................................................................... 13

6 CONFIGURATION OF ROOT CAUSE ANALYSIS ....................................................... 156.1 Basic Configuration of SAP Solution Manager ................................................. 156.2 Setup of SAP Solution Manager Server ............................................................ 15

6.2.1 Change Number of Batch Processes ........................................................ 166.2.2 Activate BI source system ......................................................................... 166.2.3 Change BI Authorization Concept ............................................................. 166.2.4 Run Diagnostics Setup Wizard .................................................................. 16

6.2.5 Setup of the Help Center........................................................................... 196.2.6 Profile Generation ..................................................................................... 196.2.7 Define Landscape Solution ....................................................................... 19

6.3 Setup of Managed Systems ............................................................................... 206.3.1 Setup RFC Destinations to managed Systems .......................................... 206.3.2 Setup of ICM Logging ............................................................................... 236.3.3 Enable Flight Recorder ............................................................................. 236.3.4 Run Managed Systems Setup Wizard ....................................................... 236.3.5 Run Setup of Introscope Agents Wizard .................................................... 26

6.4 Post Configuration Activit ies ............................................................................ 296.4.1 Configuration of Remote Connection for SAP Support............................... 29

6.4.2 Planned restart of systems ........................................................................ 30



Contents May 2008

Root Cause Analysis Installation and Upgrade Guide II

6.4.3 User creation during configuration ............................................................. 306.5 Configuration Check .......................................................................................... 32



End to End Root Cause Analysis May 2008

Root Cause Analysis Installation and Upgrade Guide 1

1 SummaryThis document describes the implementation of the scenario Root Cause Analysis in SAPSolution Manager as of SP13. Its structure is follows the steps that are needed for theimplementation

Chapter 2 contains important information regarding the installation and configurationthat need to be considered before starting the implementation

Chapter 3 describes the implementation methodology.

Refer to chapter 3.1 Implementation Planning to understand which stepsneed to be planned well ahead especially with your IT department inorder to ensure a fluent installation and configuration.

To implement the root cause analysis, please follow the installation andconfiguration steps in chapter 3.2 Installation and Configuration. Fromthe two tables within this chapter, you will be linked into separate

chapters and documents. These documents are listed in chapter 2.If you are updating from a previous SP of SAP Solution Manager 7.0 toSAP Solution Manager 7.0 SP13 or higher, please follow Chapter 3.3Updating from <=SP12 to SP13.

The remaining chapters 4 and 5 are all linked from the tables in chapter 3.1, 3.2 and3.3 as just explained.





2 Important Information

2.1 SAP Notes for the Implementation

You must read the following SAP Notes before you start the installation. TheseSAP Notes contain the most recent information on the installation, as well ascorrections to the installation documentation. Please check carefully thesoftware requirements described.

Make sure that you have the up-to-date version of each SAP Note which youcan find in the SAP Service Marketplace at https://service.sap.com/notes .

SAP Notes For the

Implementation

Description

1010428 End-to-End Diagnostics (Collective note: leads to relevant notes)

2.2 Information Available on SAP Service MarketplaceMore information is available as follows on SAP Service Marketplace

Description Internet Address Document Title

General source for information

https://service.sap.com/diagnostics

Setup Description for Wily IntroscopeEnterprise Manager 7.1

https://service.sap.com/solutionmanager -> Installation Guides -> Release 7.0

Wily Introscope 7.1 -Installation Guide

Setup Guide for Diagnostics Agents


-> Installations and Configurations

Diagnostics Agent SetupGuide

Step by step check for Diagnostics Installations


-> Installations and Configurations

Installation Check Guide

Trouble Shooting Guides https://service.sap.com/diagnostics

-> Media Library

Troubleshooting Guides

End User Guide for End-to-End Applications


-> User Documentation

User Guides

Best Practice how to tailor a solution in SMSY


-> Solution Concept and Design

Solution Concept andDesign

https://service.sap.com/notes



https://service.sap.com/solutionmanager











https://service.sap.com/solutionmanager







3 Implementation MethodologyBefore starting the implementation of End-to-End Root Cause Analysis (RCA) in SAPSolution Manager Chapter 3.1 explains the process of planning the implementation. Thisincludes not only steps that need to be performed for End-to-End Root Cause Analysis, butalso steps that are needed for the whole SAP Solution Manager installation (please refer toTable 1) .

After planning the installation, chapter 3.2 structures the process of installation (see Table 2)and configuration (see Table 3) for the End-to-End Root Cause Analysis scenario in SAPSolution Manager. Parts of the installation require a direct access to the operating system,whilst the configuration is managed completely through SAP Solution Manager.

If you are not newly implementing End-to-End Root Cause Analysis and are updating from aprevious SP of SAP Solution Manager 7.0 to SAP Solution Manager 7.0 SP13 or higher,please follow Chapter 3.3 Updating from <=SP12 to SP13.

For each step in this roadmap several documents are available and linked respectively to the

steps described: Installation Guides available in the SAP Service Marketplace (https://service.sap.com )

IMG Reference Guide

Further chapters in this document

As there are different roles involved in the planning and execution it is also outlined in whichsteps the different organizations for Application Management (AP), SAP TechnicalOperations (TEC) and IT infrastructure (IT) need to be involved in the individual steps.

3.1 Implementation PlanningBefore starting the implementation, refer to the following steps for planning theimplementation:

Description Details Specificfor RCA

Aff ectedRoles

1. Plan thedistribution of SAP SolutionManager components

See 4.1 Distribution of SAPSolution Manager Components

Yes AP, TEC,IT

2. Plan Hardwareprerequisites for SAP SolutionManager 7.0 &Root Cause

AnalysisScenario

See Chapter 4.2 Hardware for SAP Solution Manager

No TEC, IT

3. Planimplementationof missingSoftwareComponents

See Chapter 5.3 Softwareprerequisites for Root Cause

Analysis

Yes TEC, IT

4. Plan User & Portavailability

See Chapter 5.7 Required usersfor installation and Chapter 5.8

Required TCP ports

Yes TEC, IT

https://service.sap.com/







& See Chapter 6.4.3 User creationduring configuration

5. Plan Executionof Root Cause

AnalysisInstallation

See Chapter 3.2 Installation andConfiguration

Yes TEC, IT

6. Plan Restart of ManagedSystems

See Chapter 6.4.2 Planned restartof systems

Yes IT

7. Plan training of SolutionManager administrators

Seehttps://service.sap.com/diagnostics-> SAP Solution Manager Starter Pack

Yes AP, TEC

8. Plan core andexpertcompetencestraining of operators andend users of Root Cause

Analysis

Seehttps://service.sap.com/diagnostics-> Training & Certification

Yes AP, TEC

Table 1: Planning the implementation of SAP Solution Manager - End-to-End Root Cause Analysis









3.2 Installation and ConfigurationThe detailed steps for the installation of SAP Solution Manager and the steps that are specificto the End-to-End Root Cause Analysis scenario are described in the following table. Pleaserefer to the documents mentioned in the details for further information how to perform thestep. For some of the steps an access to the operating system of the SAP Solution Manager System (Managing system) and the connected satellite systems (Managed systems) isneeded.

Description Runtime(h)

Details RequiresOS

Access

Specificfor RCA

Role

1 CheckHardwareprerequisitefor SAP

SolutionManager 7.0& End-to-EndScenario

2 See Chapter 4.2 Hardware for SAP Solution Manager

Yes No AP,TEC,IT

2 Installation of SAP SolutionManager 7.0incl. SPupdate or Upgrade toSolutionManager 7.0

60 See Chapter 5.1Installation/Upgrade Guides for SAP Solution Manager 7.0& See Chapter 6.1 BasicConfiguration of SAP SolutionManager

Yes No TEC,IT

3 ConfigureSLD 8 See Chapter 5.2 Configure SLD No No TEC,IT

4 Installation of WilyIntroscopeEnterpriseManager

0.3 See Chapter 5.5Installation/Upgrade of WilyIntroscope Enterprise Manager

Yes Yes TEC,IT

5 ImplementmissingSoftwarerequirementon SAPSolutionManager &ManagedSystems.

2 + 1 *systems

See Chapter 5.3 Softwareprerequisites for Root Cause

Analysis

Yes Yes AP,TEC,IT

Table 2: Installation of SAP Solution Manager 7.0 - End-to-End Root Cause Analysis

After completing the installation of the needed software components described above, theconfiguration can be done centrally (depending on your requirements) from the managingsystem (with the exception of the agent installation and post configuration activity "setup of remote connection" which both require OS access). The following table explains the stepsneeded for configuration and where to find more information about each step:






Details RequiresOS

Access

Specificfor RCA

Role

1. Configure RootCause Analysisscenario in SAPSolutionManager

1 See 6.2 Setup of SAP SolutionManager Server

No Yes AP,TEC

2. MaintainSystemLandscape

With SLD:0.5hNo SLD:1,5 * non

ABAPsystems

See Chapter 6.2.7

Define LandscapeSolution

No No AP,TEC

3. InstallDiagnostics

Agents

0,3 *systems

See Chapter 5.6Diagnostics AgentInstallation

Yes Yes TEC,IT

4. Configureconnectivity tomanagedsystem

2 See Chapter 6.3Setup of ManagedSystems

No Yes AP,TEC

5 Perform postconfigurationactivities

0,5 See Chapter 6.4Post Configuration

Activities

Yes Yes AP,TEC,IT

6. Restart SolutionManager and

ManagedSystems

0,5 See Chapter 6.4.2Planned restart of

systems

No No TEC,IT

7. Checkimplementation

1 *systems

See Chapter 6.5ConfigurationCheck

No Yes AP,TEC

Table 3: Configuration of SAP Solution Manager 7.0 - End-to-End Root Cause Analysis





3.3 Updating from <=SP12 to SP13Updating SAP Solution Manager to SP13 and implementing End to End Root Cause Analysisscenario, will request different steps depending if the a previous setup of End to End wasdone or not. The different cases are possible:

1. SAP Solution Manager 7.0 and Diagnostics configured (not End-to-End Root Cause Analysis).

2. SAP Solution Manager 7.0 and End-to-End Root Cause Analysis configured on versionSP10 to SP12.

In case of 1 & 2, Diagnostics infrastructure is already created.

In case of 2, technical improvements and architecture changes were done in the process of collecting and aggregating of the Data in the BI infrastructure

To migrate to this new data collection process, actions have to be done on SAP SolutionManager System and on the managed systems.

The upgrade process will request downtime and OS access on the managed systems thathave to be planned between all the different involved teams.

Those actions are listed in the table below:


Details RequiresOS

Acc ess

Specificfor RCA

Role Case

1. Uninstall WilyEP Agents

1 See Chapter 5.4. 3Remove previousinstallation of Wily

EP Agents

Yes Yes TEC,IT

1&2

2. Stop previousBI Process

1 See Chapter 5.4.1Deactivation andSuppression of Previous BIProcess Chain

No Yes TEC,IT

2

3. Migrate BI Data& process

0.5 See Chapter 5.4.2Upgrading End-to-End Workload

Analysis to SP13

No Yes TEC,IT

2

4. Implement

missingSoftwarerequirement onSAP SolutionManager &ManagedSystems.

2 + 1 *

systems

See Chapter 5.3

Softwareprerequisites for Root Cause

Analysis

Yes Yes AP,

TEC,IT

1&2

5. Configure RootCause Analysisscenario inSAP SolutionManager

1 See Chapter 6.2Setup of SAPSolution Manager Server

No Yes AP,TEC

1&2

6. Configure 2 See Chapter 6.3 No Yes AP, 1&2





connectivity tomanagedsystem

Setup of ManagedSystems

TEC

5. Checkimplementation

1 *systems

See Chapter 6.5Configuration

No Yes AP,TEC

1&2

Table 5: Update SAP Solution Manager 7.0 - End-to-End Root Cause Analysis

4 SAP Solution Manager Landscape Planning

4.1 Distribution of SAP Solution Manager Components

The implementation of End-Root Cause Analysis in SAP Solution Manager requires the

installation and configuration of different components across your complete landscape: SAP Solution Manager

SAP NetWeaver Business Intelligence (BI)

Solution Landscape Directory (SLD)

Wily Introscope Enterprise Manager

Diagnostics Agents

While the first four are central components, the Diagnostics Agent is deployed on themanaged systems and is responsible for extraction and collection of information andconfiguration data from the individual systems.

There are two possibilities for your landscape setup:1. Manual maintenance of the system landscape:

a. No productive SLD needed (manual maintenance in transaction SMSY required)

b. ABAP systems can provide their system information via trusted RFCconnections to SAP Solution Manager

c. BI and Wily Introscope Enterprise Manager on central SAP Solution Manager system

Attention:Manual maintenance of SMSY causes a high effort for initial data entry (approx1,5h per non ABAP system) and ongoing maintenance for each change to thenon ABAP system. Therefore this option is not recommended by SAP.

2. Automatic maintenance of the system landscape:

a. Local SLD on SAP Solution Manager system with connection and replicationfrom the productive SLD instances in your existing landscape

b. BI and Wily Introscope Enterprise Manager on central SAP Solution Manager system.





Wily Introscope Enterprise Manager It is possible for sizing reasons to install Wily Introscope Enterprise Manager on a different host.

4.2 Hardware for SAP Solution Manager Detailed sizing information can be found on http://service.sap.com/solutionmanager , pleaserefer to Order Information -> Technical Requirements.

Platform-dependent information is available in the Product Availability Matrix onhttp://service.sap.com/pam , please refer to SAP NetWeaver 07.

Minimum Hardware configuration for End-to-End Root Cause Analysis:

Disk space: 100 GBRAM: 6 GB minimum

Virtual Memory: 3 x size of physical memory

Number of CPUs: 2

5 Installation/Upgrade of SAP SolutionManager 7.0

5.1 Installation/Upgrade Guides for SAP SolutionManager 7.0

All information about new installation or upgrade may be found in the SAP servicemarketplace quick link /diagnostics -> Installation and Configuration -> Installation SAPSolution Manager 7.0 -> Installation and Upgrade Guides

As of April 2nd 2007 software downloads are done via the Solution Manager MaintenanceOptimizer. The Maintenance Optimizer will make sure that you use the correct versions of allrequired software components. You can find more information about the MaintenanceOptimizer at https://service.sap.com/solman-mopz .

Note on Unicode:End-to-End Root Cause Analysis requires a SAP Solution Manager 7.0 with aSAP double stack system (Web AS ABAP and Web AS Java in one SAPsystem). SAP recommends to run Solution Manager on Unicode (see alsocustomer letter on http://service.sap.com/Unicode ). It is required to install allnew Solution Manager Installations on Unicode. For customers that haveupgraded from previous releases of SAP Solution Manager 7.0 and are not yeton Unicode, SAP recommends to migrate to Web AS ABAP to Unicode. If thisis not possible, SAP will support End-to-End Root Cause Analysis with an

ABAP stack on non-Unicode as of SAP Solution Manager 7.0 SP13, until thecustomer has completed the Unicode conversion.

http://service.sap.com/solutionmanager


http://service.sap.com/pam


https://service.sap.com/solman-mopz


http://service.sap.com/Unicode










5.2 Configure SLDSolution Manager expects that you already run SLD(‘s) for productive usage like for WebDynpro or Process Exchange (XI). On top, Solution Manager needs an SLD (called local

SLD) itself as a complete catalog of technical systems and complete catalog of installedsoftware components as data provider for SMSY and as persistence for own WebDynproconnection data. To avoid conflicts between the availability of your productive SLD(‘s) and theavailability of the Solution Manager (like upgrade of the Solution Manager, or Root Cause

Analysis on the productive SLD in case of problems) we strongly recommends to setup thislocal SLD on the Solution Manager.

Information Setup about SLD is available in transaction IMG: SAP Solution Manager ->configuration -> Standard configuration of Basic Settings -> Solution Manager -> SystemLandscape.

Further information about SLD itself may be found on http://service.sap.com/SLD and in SAPNote 764393 .

The Landscape Fetch job of the Solution Manager SMSY should run against the local SLDand the CIM Client of the Solution Manager should store the WebDynpro data also on thelocal SLD.

5.3 Software prerequisi tes for Root Cause Analysis

5.3.1 General Information on Softwareprerequisites

SAP Note 1010428 - End-to-End DiagnosticsThis note includes detailed information about SAP notes and prerequisites for

SAP Solution Manager System & Satellite Systems running Root Cause Analysis

In SAP Note 1010428 it is also documented which managed systems are supported on whichSAP Solution Manager SP level.

SAP strongly recommends to implement End-to-End Root Cause Analysisimplementations on Solution Manager 7.0 SP13 or higher.

5.3.2 Software prerequisit es for Wily Introscope

AgentsWith SAP Solution Manager SP13, a new packaging of the Wily Introscope Agent isdelivered.

This packaging allows installing and configuring centrally new versions of Wily IS Agents fromSAP Solution Manager without any OS Actions on the managed systems.

The new software component named ISAgentSMD71 is available in SAP Servicemarketplace from SAP Service Marketplace SWDC -> Support Packages and Patches ->SAP Technology Components -> SAP SOLUTION MANAGER ->SAP SOLUTIONMANAGER 7.0 -> Entry by Component ->Agents for Satellite Systems ->ISAGENTSMD71_XX-SCA

http://service.sap.com/SLD

https://service.sap.com/sap/support/notes/764393




http://service.sap.com/SLD





Please deploy this SCA to the SAP Solution Manager Java Stack.

Managed system runs on IBM AIXThe Wily Introscope Agent supports both operating modes of the IBM hybridVM (J9 mode and classic mode), but the Introscope Agent settings are differentfor the two operating modes. Please make sure that you activate theIntroscope Agent settings for the J9 mode exactly then if the IBM hybrid VM isactually running in J9 mode. A wrong setup prevents the managed system torestart properly. Check Note 1024539 about using the IBM hybrid VM ...

5.4 Specific Upgrade Installation from <=SP12 toSP13

Specific steps are needed to implement End to End - Root Cause Analysis; they aredescribed in the following sub-chapters. Chapter 3.3 Updating from <=SP12 to SP13 explainsall overall update process.

5.4.1 Deactivation and Suppression of Previous BIProcess Chain

SAP Solution Manager SP13, implements a new mechanism to collect and aggregate datafrom the Managed Systems.

The old mechanism built on top of the BI process chain must be deactivated and removed.

The following instructions must be done on your SAP Solution Manager system.

1. Log on to your Solution Manager BI Client.

2. Run transaction RSPC.

3. Select your Process Chain under the specific tree End to End Diagnosti cs .

4. Click on the Edit icon and then on the Delete icon.

5. Press 'Yes' to the confirmation screen displayed below.

6. Press 'Continue' in the screen below to confirm the process chain termination.

7. The process is now deactivated; you can now proceed with the BI data migration.

5.4.2 Upgrading End-to-End Workload Analysis toSP13

SAP Note 1094766 contains correction instructions that have to be applied, in order toprepare the system for the upgrade procedure.

Implementation of this SAP note is mandatory prior to the execution of the rest of the upgradeprocess.





5.4.3 Remove previous installation of Wily EP Agents

If the EP Agents have been installed with the Diagnostics setup wizard, this step must be

skipped.In case of manual installation of Wily EP Agents, please refer to Wily Intro scope 7.1 -Installation Guide - Chapter 9 Additional Installation Options and especially UninstallingIntroscope -> Uninstalling Introscope Uninstalling Environment Performance Agents

This chapter explains how to uninstall and un-register the EP Agent from your System.

The guide is available under http://service.sap.com/solutionmanager -> Installation guides ->Release 7.0.

5.5 Installation/Upgrade of Wily Introscope Enterprise

Manager In addition to the standard delivery from SAP Solution Manager, the installation of WilyIntroscope Enterprise Manager 7.1 with most current patch is necessary.

The Installation Guide for Wily Introscope Enterprise Manager can be found on SAP ServiceMarketplace https://service.sap.com/instguides , please refer to SAP Components -> SAPSolution Manager -> Release 7.0 -> Wily Introscope 7.1 - Installation Guide

5.6 Diagnostics Agent InstallationThe diagnostics agent needs to be installed on the managed systems (not required anymorefor all new installations based on Web AS 7.0 SR3, as the diagnostics agent is automaticallyinstalled on this NetWeaver version). Diagnostics agent applications (such as the WilyIntroscope agents) will then be deployed from the SAP Solution Manager during theconfiguration phase. This is possible because the diagnostics data provisioning layer doesnot rely on a monolithic agent, but on a two-tier agent architecture: the diagnostics core agentallows, once deployed to the managed system, the deployment of agent applications fromSAP Solution Manager.

For detailed information on the Diagnostics Agent installation, please refer to the documentDiagnostics Agent Setup Guide on SAP Service Marketplace, quick link /diagnostics ->Installation and Configuration -> Installation

5.7 Required users for ins tallationThe following users are mandatory for the installation of Root Cause Analysis in SAP SolutionManager. The passwords for all these users will be required during the installation.

Managing system user User name example Remarks

OS system administrator Smpadm<SID>adm

Database System sap<SID>db(DB Schema Owner)

J2EE Administrator J2EE_ADMIN

http://service.sap.com/~sapdownload/011000358700006487172006E/SAPISDOC71_02.pdf




https://service.sap.com/instguides










ABAP Administrator AdminUser authorizations required(SAP_ALL, S_RFC,S_RFCACL, S_TCODE)

Wily Adminitrator Admin

Table 4: Users required for installation on the managing system

Managed system user User name example Remarks

Root OS user Root

OS system administrator eppadm<SID>adm

SMD dedicated J2EE

Administrator

SMD_ADMIN

(SMD_MANAGED_ADMIN)

it must be permanent (user

& password), changesrequires action of Diagnostics Server

ABAP Admin User AdminUser authorizations required(SAP_ALL, S_RFC,S_RFCACL, S_TCODE)

Table 5: Users required for installation on the managed system

5.8 Required TCP por tsThe following ports have to be opened up in your firewall prior to End-to-End Diagnosticsinstallation. It is recommended to place the SAP Solution Manager within the same subnet or DMZ of your managed landscape. In case you are managing systems in different subnets youhave to adapt your security settings and firewall accordingly.

Connection established “ Service” on dest.host / Protocol

Servi ce port example /Format

from host(s)Src. host

to hostDest. Host

Outside DiagnosticsServer

J2EE engine /HTTP

Ex: 50100 /5<InstanceNb>00

DMZ Diagnostics

Server

ITS / HTTP Default: 8000

Outside DiagnosticsServer

IntroscopeManager/ HTTP

Default: 8081

DiagnosticsServer

DiagnosticsServer

IGS / HTTP Ex: 41080 /4<InstanceNb>80

ALLManagedsystems(Diag. Agent)

DiagnosticsServer

J2EE engine / P4 Ex: 50104 /5<InstanceNb>04

ALL

Managed

DiagnosticsServer

Message srv. /HTTP

Ex: 8101 / 81<InstanceNb>





systems(Diag. Agent)

(not 36XX)

ALL

Managedsystems(Wily Agent)

DiagnosticsServer

IntroscopeEnterprise Manager / TCP / IP

Default: 6001

Table 6: Ports to be opened for communication to the managing system

Connection established “ Service” on dest.host (s) / Protocol

Servi ce port example /Format

from hostSrc. host

to host(s)Dest.host(s)

Outside ALLManagedSystem

J2EE engine /HTTP

Ex: 50200 5<InstanceNb>00

DiagnosticsServer

ALLManagedSystem

RFC

DiagnosticsServer *

ALLManagedSystem

Log Viewer / TCP /IP

Default: 26000

ALLManagedSystem(Diag. Agent)

ASSOCIATEDManagedSystem

J2EE engine / P4 Ex: 50204 5<InstanceNb>04

Table 7: Ports to be opened for communication with the managed system





6 Configuration of Root Cause Analysis

6.1 Basic Configuration of SAP Solution Manager

Before configuring Root Cause Analysis, the necessary IMG activities in the SAP SolutionManager system need to be completed. These activities are:

Configuration -> Basic Settings -> Wizard-based Initial Configuration of Basic Settings -> All sub activities.

Configuration -> Basic Settings >-> Standard Configuration of Basic Settings

Solution Manager

General Settings

Connection to SAP

Online Documentation

Authorization/Users

HTTP Services

System Landscape

Service Data Control Center

Specify Satellite Systems Connection (All activities)

System Configuration is done via transaction SPRO (SAP Reference IMG) within SAPSolution Manager and the according Configuration Guide.

6.2 Setup of SAP Solution Manager Server The following sections contain detailed information for installation & setup of the SMD Server.

Steps Details

1. Increase number of batch processes to atleast 3 for BI Reporting

See Chapter 6.2.1 Change Number of Batch Processes

2. Activate BI Source

System

See Chapter 6.2.2 Activate BI source system

3. Change BI Authorization Concept

See Chapter 6.2.3 Change BI Authorization Concept

4. Run Diagnostics SetupWizard

See Chapter 6.2.4 Run Diagnostics Setup Wizard

5 Setup of the SMD helpcenter

See Chapter 6.2.5 Setup of the Help Center

6 Profile Generation (onlywith SP13)

See Chapter 6.2.6 Profile Generation





6.2.1 Change Number of Batch Processes At least three batch processes are required to run the Diagnostics Wizard.

1) Start transaction rz10

2) In the profile of the ABAP instance change the background process to at least 3.

The diagnostics extractor framework manages the data extraction for End-to-End Workload Analysis, End-to-End Change Analysis and End-to-EndException Analysis. Depending on the amount of managed systems this canconsume all available Batch Work processes of the Solution Manager. Pleaseuse the simple Job selection of TA SM37 and filter for Job_Step : ABAPProgram: End-to-End_EXTRACTOR_CONTROLER to monitor the jobs for diagnostics data collection. Make sure that all these jobs are finished within anhour. If this is not possible because not enough Batch Work processes areavailable to proceed all Extractor Jobs within an hour, please increase thenumber of Work processes.

To grant the execution of other jobs like (housekeeping and transport) pleaseprioritize class A Jobs as described on SAP Help Portalhttp://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7f53505211d189550000e829fbbd/frameset.htmThe execution of the extraction Jobs creates job logs and spool requests in theTMSE. To avoid job cancellation due to spool overflow make sure that thestandard housekeeping jobs SAP_REORG_JOBSTATISTIC andSAP_REORG_SPOOL are configured according to the SAP NetWeaver SetupGuide -> Performing initial ABAP Configuration -> Schedule Background jobs

6.2.2 Act ivate BI source sys temBI Content needs to be set up. Please refer to IMG Activities for information

1. On the Logical System for BI created in the IMG activity, call transaction RSA1 .

2. Select Source system and right click to select "activate"

3. On the popup Window "Replicate Metadata?", Select 'Replicate as Well'

4. Choose "as 3.x Datasource" when asked, then confirm

6.2.3 Change BI Authorization Concept1. Start transaction rscustv23

2. Select “Obsolete Concept w ith RSR Authorization Objects ”.

3. Save the changes

6.2.4 Run Diagnostics Setup Wizard

Start the Diagnostics Setup Wizard

http://<host>:<port>/smd Diagnostics Setup --> Diagnostics System Setup Wizard

http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a7f53505211d189550000e829fbbd/frameset.htm








The Diagnostics Setup Wizard executes the followin 3 steps:

Setup: Definition of Setup paramaters.

Confirmation: Summary of setup steps.

Results: Setup Results.

Setup

In this step, you will enter all needed parameters to complete the setup. The Diagnosticssetup wizard will take care of the actions listed in the table below.

Area covered Corresponding Actions

SSO Setup Single Sign-On for Solution Manager and BI clients

User Creation of Support User in ABAP User store

Assignment of UME roles to the Support Use

Assignment of ABAP roles to the Support User

Wily IS store Wily IS connection information

BI store BI connection information

Run CCMSBISETUP routine.

Activate WEB templates services

Start BI housekeeping jobs

RFC Creation of the RFC destination on J2EE side

Creation of the RFC destinations on ABAP side

ITS store ITS connection information

SAP router Generation of SAP Router template





The following parameters must be entered in the setup wizard:

Field Description Default value

Support User Id User ID of the Diagnostics SupportUser.

If not yet existing, the User will becreated with password set inadvanced setup (default : 'init1234')

sapsupport.

Solution Manager ABAP stackconnectioninformation

Client,

Admin User ID,

Admin Password,

ITS port,

BI ABAP stackconnectioninformation

Host Name,

System number

Client,

Admin User ID,

Admin Password,

ITS port,

By default, all BI ABAP stackinformation is matched to theSolution Manager ABAPstack connection information.

J2EE administrator of the Java Stack of Solution Manager

admin User Id

admin password

Wily introscopeenterprise Managedconnect

Enterprise Manager Host,

Enterprise Manager Port,

Enterprise Manager User ID

Enterprise Manager User password

By default, EM is matched toSolution Manager host withport 6001.

Default EM user is guest

SAP Router Info The SAP router system to generateSAP Router templates

Once all information of your system is entered, press the ‘Next’ button.





Confirmation

In this step, you can select which steps are going to be executed by the setup wizard. Pressthe 'Setup' button. It will start the selected setup and configuration steps.

Remark: The CCMSBISETUP step has to be executed during the very first installation of Diagnostics. Make sure that this step is selected before starting the setup.

Results

In this step, a report of the setup wizard will be displayed. Please review this report and lookfor errors.

Press the 'Quit' button to return to the main Diagnostics screen

6.2.5 Setup of the Help Center The Help Center offers some interactive mechanisms to display help materials to diagnosticsend-user.

The Help Center content is downloaded from SAP Service Marketplace. To update thecontent of the help center:

1. Navigate to Help -> Show Help.

2. Click on Update Help Center.3. On the popup widow called " Help Center Update ", Select " File Update ".

4. Follow " Online " Instructions

6.2.6 Profile Generation1. Start transaction PFCG :

2. Select the role SAP_BI_E2E

3. Retrieve the profile name and generate the corresponding profile.

4. Depending on systems performs a user comparison for the SAPSUPPORT5. Repeat the steps for role: SAP_SATELLITE_E2E_DISP

6.2.7 Define Landscape SolutionThe maintenance of all systems that should be monitored in SAP Solution Manager isnecessary.

1. Populating technical system information into SAP Solution Manager:

a. Manual maintenance of the systems in the transaction SMSY (please refer toSAP note 987835)





b. Automatic population of system information from local SLD to SMSY. (see IMGDocumentation -> SAP Solution Manager -> Basic-Settings- StandardConfiguration of Basic Settings -> Solution manager -> System Landscape)

2. Manually complete system information according to Note 987835.

3. Define solutions in the transaction SMSY (also described in note 987835). For moreinformation on the definition of solutions see http://service.sap.com/diagnostics ->Configuration -> Solution Concept and Design)

6.3 Setup of Managed SystemsThe following table contains detailed information for setup of the managed systems

Steps Details

1. Setup RFC

Destinations tomanaged Systems

See Chapter 6.3.1 Setup RFC Destinations to managed

Systems

2. Setup of ICM Logging See Chapter 6.3.2 Setup of ICM Logging

3. Enable Flight Recorder See Chapter 6.3.3 Enable Flight Recorder

4. Run Managed SystemsSetup Wizard

See Chapter 6.3.4 Run Managed Systems Setup Wizard

5. Run Setup of Introscope AgentsWizard

See Chapter 6.3.5 Run Setup of Introscope Agents Wizard

6.3.1 Setup RFC Dest inations to managedSystems

A RFC connection from Solution manager to the managed ABAP stack needs to be created.

In Solution Manager Diagnostics start SMSY and select the solution containing the managedsystems.

Select your system in the 'landscape Components/Systems' view and go to the 'clients' panelof ABAP stack.

Enter the desired managed system client number in the “client” column, and click on the

button “Generate RFC Destinations”.This will launch the assistant which allows you to generate the READ RFC destinations (inthe managing system). As this assistant will create (remotely) the RFC connection dedicateduser on the managed systems, it will request you, during processing, to login on the managedsystem using the Solution Manager “admin user” (see the Implementation Guide intransaction SPRO ), other than DDIC and SAP*, which doesn’t allow to create the TRUSTEDRFC destination, if required.

Note that the READ RFC will then also be used to fetch the managed system data in order topopulate the “ABAP system data entries” within transaction SMSY .

Once finished the assistant has performed the following steps:

Created the user SOLMAN<Sol Man SID><Sol Man client Id> in su01 onthe managed system in the adequate client.

http://service.sap.com/diagnostics







Created the RFC destination SM_<Managed systemSID>CNLT<Managed System client Id>_READ in sm59 in SolutionManager. Therefore the current user that has triggered this assistantshould have the authorizations to perform the transaction sm59.

Here are the settings that you should use (replace NX1 / NC1 with your information):

Select the "Assign RFC Dest. For System Monitoring" option.

Select the destination named SM_<Managed system SID>CNLT<Managed System clientId>_READ in the "RFC Destination for Data Collection"





The assistant will then ask you to logon on the managed system. Logon to this managedsystem using the “admin user” that has been created there.





6.3.2 Setup of ICM LoggingTo enable the analysis of logs written by the Internet Communication Manager (ICM) by usingthe HTTP Analysis application, an additional parameter has to be maintained.

1. On the managed systems, start transaction RZ10 and add the following parameter to theinstance profile<SID>_DVEBMGS<instance no.>_<hostname> of the server where the ICM is running: icm/HTTP/logging_0: set to

PREFI X=/ , LOGFI LE=i cmht t p. l og, LOGFORMAT=SAPSMD, MAXSI ZEKB=10240,SWI TCHTF=day, FI LEWRAP=on

2. Save and activate the profile,

As this parameter value exceeds 1 line, it has to be maintained carefully.Please enter it on two lines.

6.3.3 Enable Flight Recorder On the managed system the Flight Recorder needs to be enabled by adding parameter

jstartup/recorder to the J2EE InstanceProfile. If the monitored system is of SAP NetWeaver 07 or later the parameter should already be there.

jstartup/recorder = java -classpath ../j2ee/cluster/bootstrap/launcher.jar com.sap.engine.offline.OfflineToolStart com.sap.engine.flightrecorder.core.Collector ../j2ee/cluster/bootstrap -node %nodeID% %startTime% -bz $(DIR_GLOBAL) –exitcode%exitcode%

6.3.4 Run Managed Systems Setup WizardThis Set-Up Wizard performs the configuration of systems to be managed in diagnostics.

In Diagnostics start the Managed Systems setup wizard:

http://<host>:<port>/smd Diagnostics Setup Managed Systems

Setup Wizard

The managed Systems setup wizard executes 5 steps to complete the setup for a managedsystem.

Solutions selection: Define the solutions that will be configured.

Systems selection. Define the systems that will be configured.

Setup parameters: Enter the parameters used during the configuration.

Setup steps selection: Select which steps will be executed during the setup.

Setup results: The results of the setup execution for the selected steps.





Solution selectionThis screen gives a list of all defined solutions in SMSY. For each of those solutions, a setupstatus is displayed. You can use the tooltip on Status icons to get a description of the status.

By default all "New" or "Updated solutions" are selected by default. It means that a setupaction needs to be performed for those systems

The "Next" button will display a screen will all systems defined for the selected solutions.

Systems selectionIn this screen, systems are filtered according to solution(s) selected in previous step

Select the "Show Instances" check box to display system setup status per instance. Once thesystem has been selected, press the "Next" button to continue the setup.

Only one system (SID +InstallNumber) can be selected for being setup in next step. Youshould repeat the setup procedure for all selected instances.

Setup ParametersThe following parameters must be entered in this screen

J2EE Connect ParametersJ2EE parameters are requested for a J2EE system only. In this screen, MessageServer host and port and login credentials for the J2EE administrator .

ABAP Connect Parameters ABAP parameters are requested for an ABAP system only. In this screen. ABAP user

with SAP_ALL profile has to be entered. Load Balancer info

Optional information to access the load balancer URL of the managed systems.

For each selected instances, the Agent name and the installation path must beentered, by selecting the details view:

Agent NameFor each instance of the system running on different hosts, an SMDagent should be assigned and connected. If the agent is not connected,(the field "agent" is marked as "N/A").

Installation pathThe installation path of the selected instance.

ITS dataITS server information. This is only valid for ABAP system.

Only selected instances will be setup when using the "Setup" button. Instance Setup can beselected only if corresponding agent is connected, and install path has been set.

For New Managed Systems, you should check that you select the SMD Agent correspondingto the expanded Instance. The wizard will ask for a confirmation if the IP address of the agentand the IP address from SMSY do not match.

Once assigned in the wizard, you will have to use the Agent Administration application if you

need to unbind the server name from the SMD Agent.





Right after Agent assignment (button "Set"), the selected agent is restarting. Please wait for afew minutes to wait for the restart of the agents as shown in the application.

Steps SelectionIn this step, you can choose the list of steps that should be performed during the setup. Tostart the automatic setup procedure, press the “setup” button

Setup ResultsWhen the execution of the wizard is finished, a report displays the status of the execution.

Result of Setup steps can be reviewed at any time later on, using the "Setup results" link inthe managed systems setup wizard





6.3.5 Run Setup of Introscope Agents WizardIntroscope Bytecode Agents run on the managed systems (based on J2EE engines) to reportdata to the Introscope Enterprise Manager.

Diagnostics provides an administration tool: “Introscope Agent”, which will take care of thesetup of these Introscope Bytecode Agents. The deployment and the configuration of theseBytecode Agents must be performed remotely with the assistance of Diagnostics.

RequirementsIn order to empower Diagnostics to remote-deploy and remote-configure a given IntroscopeBytecode Agent release, you will need to install (deploy) on Solution Manager the latestversion of the Java Software Component Archive (SCA), named:ISAGENTSMD7x_xxxxxx.SCA . (Make sure not to use the ISAGENTxxxxxx.SAR file)

The deployment of this SCA must be done with the Solution Manager J2EE engine’sSoftware Deployment Manager (SDM).

Before you deploy this SCA file, please double check that the Maintenance mode hasbeen activated within Diagnostics. To activate the maintenance mode, login as admin user and navigate to: Diagnostics Administration Managed Systems Agent Administrationand switch it to “on“. Finally, once the SCA has been deployed, please switch theMaintenance mode again to “off” and wait until all Diagnostics agents are reconnected.

SetupStart the Diagnostics administration tool named “Introscope Agent”:

logon as an admin user

navigate to “Diagnostics setup” “Managed systems”.

This tool will require several settings, which will be used to perform this remote-deploymentand configuration for one or several Introscope Bytecode Agents.

These settings are:

The Introscope Bytecode Agent must report to an Introscope Enterprise Manager (ISEM). Therefore provide the hostname and port number to be used by the Bytecode

Agent to connect to the dedicated Introscope Enterprise Manager.

Select the Managed system, in the dropdown list, for which you would like to remotelysetup or upgrade an Introscope Bytecode Agent. The Introscope Bytecode agents areactivated (installed) per managed system J2EE engine SERVER NODE. Be aware thatthe managed system J2EE engine’s Dispatcher node(s) is not listed, as it is not

necessarily relevant to instrument those nodes.Note: In case you do not see the system / server nodes that you defined in SMSY,please double check your system definition in SMSY and run again the Managedsystem setup wizard.

Choose the adequate profile (instrumentation) associated to the type of managedsystem. By default use the sap_IntroscopeAgent.profile. Whereas for XI systems,please select the sap_IntroscopeAgent_xi.profile.In very specific situation you may require that additional metrics are collected and willtherefore choose extended instrumentations. This could be done within the AutoprobeDirectives selection.

http://ms_getobject%28%27https//websmp130.sap-ag.de/sap/bc/bsp/spn/download_basket/download.htm?objid=012002523100009749592007D&userid=I039765&action=DL_DIRECT%27);

http://ms_getobject%28%27https//websmp130.sap-ag.de/sap/bc/bsp/spn/download_basket/download.htm?objid=012002523100009749592007D&userid=I039765&action=DL_DIRECT%27);





FOR AIX SYSTEMS ONLY: An additional setting will be required. Please make sure whether the managed systemis running within “J9 mode” (JVM parameters –Xj9 or at managed system J2EE engineOS level) before you complete this setup !!!Providing a wrong information at this level will prevent your managed system from“coming-up” again after the system restart.

Please find hereafter some more details on the various “sections” displayed by this setup tool

Introscope Agent SettingsIn the dropdown list, you can select the Solution/Landscape/SID. The corresponding J2eeServer nodes are then displayed in the table.

The third column (green flag) informs whether the SMD Agent is up and running. TheIntroscope agents settings displayed are:

ISAgent Profile

ISAgent Name

ISAgent Version: the version of the SAP Instrumentation

ISAgent state

NOTE:

The ISAgent Version is decorated with a ” ” icon to inform that the currentversion differs from the one delivered with SMD.

Please keep in mind that installing a new SMD Version preserves the previoussettings. It is necessary to perform the ISAgent setup again to switch to thenew version!

The ISAgent state informs whether the setup is already in use by the ManagedSystem. It is important to understand that the whole j2ee engine must berestarted to take the latest settings into account.

In case the J2EE engine node in the “Introscope Agents settings” is decoratedwith a red flag, please make sure that both the Managed system and theassociated DIAGNOSTICS agent are currently running.

J2ee Node Info rmation DetailsThis section will display more information details about the j2ee server nodes.

Remarks:

The JDK Location is used to generate Wily Connectors. Changing the JDK may require toperform the setup again!

EM Settings are displayed to make sure they match the one specified during the SMD Setup.





Introscope Agent SetupThis section will allow you to update or maybe even remove the Introscope Bytecode Agent(associated Java parameters within the managed system’s J2EE engine).

Pressing the Setup button opens an additional form where the admin has the ability to select:

The ISAgent Version

The ISAgent Profile

The Setup can be applied to several j2ee Server Nodes in one shot. In that case, you mustselect the relevant nodes by checking the checkbox in the table.

Last Operation ResultsYou use the last operation results tree to check each step and make sure the setup has beenproperly performed.

Advanced information

Note that this Diagnostics administration tool will indeed use the Diagnostics Agent, runningon the different managed systems, to locally “deploy” the Introscope Bytecode Agent binaries(into the Diagnostics agent’s own directory structure). The Bytecode Agents, which arerunning within the J2EE engines’ JVM process, are activated by adding some Javaparameters at the J2EE engine level of the managed system.





6.4 Post Configuration Activi ties

After completing the configuration activities, the following steps need to be performed.

6.4.1 Configuration of Remote Connection for SAPSupport

This activity will enable a remote connection for communication between SAP Support andyour Solution Manager Diagnostics and your managed systems

You can refer to SAP Notes 592085 and 962516 for connection type “SolMan Diagnostics” inorder to get more information.

Adjust the SAProuter configuration file saprouttab, using the information given by theDiagnostics Setup Wizard as described in the previous chapter.

The information returned by the setup wizard includes the following host and port:On managing system :

HTTP connection host and port to the Solution Manager ICM.

HTTP connection host and port to the Solution Manager J2EE dispatcher node.

HTTP connection host and port to the Introscope EM server (workstation or WebView)

On each of the managed sys tems:

For Web AS Java system, HTTP connection host and port to the J2EE enginedispatcher or to the loadbalancer if installed.

For Web AS ABAP system, HTTP connection host and port to managed systems ITS.

After saving saprouttab, you should import it by executing saprouter –n

Check the remote Configuration

As part of the IMG activity "SAP Solution Manager Configuration Basic Settings

Wizard Based Initial Configuration of Basic Settings Solution Manager GeneralConfiguration Schedule Background jobs", the following jobSEND_SYSTEM_RELATIONSHIP_TO_SUPPORT should have been scheduled

The job periodically sends to OSS the list of systems which are managed by SolutionManager.

This job should have the following properties:

ABAP program: AI_SC_SEND_SYSTEM_RELATIONSHIP

Start time: Immediate start

Repetition period: Daily

You can check if the list of managed systems has been transferred correctly to SAP SupportPortal by connecting to http://service.sap.com/system-data in the Solution Manager systemon tab Managed Systems.

http://dwdf215/solsup/CoE/CoE_Global/RCA/Rollout/30_Help_Center_Content/3_Other%20Documents/Install%20&%20config/SAPEVENTDOCU_LINK/DSRE.AI_SC_SEND_SYSTEM_RELATIONSHIP

http://dwdf215/solsup/CoE/CoE_Global/RCA/Rollout/30_Help_Center_Content/3_Other%20Documents/Install%20&%20config/SAPEVENTDOCU_LINK/DSRE.AI_SC_SEND_SYSTEM_RELATIONSHIP





If this tab is not visible:

Check that the product version SAP SOLUTION MANAGER 7.0 is maintained at the

system data header. Navigate to Software components

Choose Software Component Version SOLMANDIAG 7.00.

Now you should be able to select the tab Managed Systems. Here you can check thelist of systems that are connected to SMD, which has been transferred to SAP fromSAP Solution Manager via batch job SEND_SYSTEM_RELATIONSHIP_TO_SUPP.

6.4.2 Planned restart of sys tems A restart of the different systems is required during the setup of Root Cause Analysis. Therestart of the SAP Solution Manager as well as the managed systems is required due to thefollowing reasons:

SAP Solution Manager:

Restart is mandatory if application of latest patch for LMService is required. (Automaticrestart during deployment, J2EE stacks only).

ABAP profile parameters may need to be adapted in order to respect optimizationrecommendations, please see chapter 6.2.1 for background process for jobs

Managed Sys tem:

Activation of Wily Byte Agent code requires restart, only valid for Java and Duetinstallation. Restart has to be done only at the end of the setup process.

Setup of ICM Logging and Flight Recorder required restart of each ABAP stack.

6.4.3 User creation during conf igurationIf your security policy does not permit the automatic creation of generic users with the SAPSolution Manager Setup Wizard, the following users need to be created manually:

Please note that automatic creation of user is only possible if using JAVA or ABAP UME.With CUA (Central User Administration), they will need to be created manually.

Users on managing systems

Managing System User / Role or Profile Type of User / Role Remarks

SAPSUPPORT /Diagnostics End-user Dialog User

userId "SAPSUPPORT"can be customized inDiagnostics Setup ->

Advanced Setup

SAP_JAVA_SUPPORT UME

SAP_JAVA_NWADMIN_CENTRAL_READONLY UME

SAP_SOLMANDIAG_SAPSUPPORT ABAP Role User and role alsocreated/assigned in BI





client/system, if separatefrom SolMan

SAP_SOLMANDIAG_E2E ABAP Role

User and role alsocreated/assigned in BIclient/system, if separatefrom SolMan

S_AI_SMD_E2E ABAP Profile

SAP_BI_E2E ABAP Role Role assigned in BIclient/system

SMD_ADMIN Dialog User Communication user to beused by SMD Agent(specify in Installer)

SAP_J2EE_ADMIN ABAP Role

SMD_RFC Communication User Communication user set inWEBADMIN JcoRFCdestination

SAP_SOLMANDIAG_E2E ABAP Role

Table 8: Users created during configuration on managing system

Users on managed systems

Managed System User / Role or Profile Type of User / Role Remarks

SAPSUPPORT Dialog User (*) Only if User Store of Managed System = Java

SAP_JAVA_SUPPORT UME

SAP_JAVA_NWADMIN_CENTRAL_READONLY UME

SAP_JAVA_SUPPORT J2EE

<Specific roles for SystemInfo and SQL*Trace> J2EE

Only for Managed Systemwith Java stack < 640SP15, see SAP Note1042450 for details

<Specific roles for XI apps> UME and J2EEOnly for Managed Systemwith XI, see SAP Note1042450 for details

SAP_SATELLITE_E2E_DISP ABAP Role

S_E2ESATDISP ABAP Profile


SOLMAN<SID><CLIENT> Communication User "RFC Read" user createdfrom SMSY. Not createdfrom Setup Wizard

SAP_SATELLITE_E2E ABAP Role






S_BDLSM_READ ABAP Role

S_CSMREG ABAP Role

S_CUS_CMP ABAP Role

SMDAGENT_<SID> Communication User Abap Communication user for Wilyhost

SAP_IS_MONITORING ABAP Role

S_IS_MONITOR ABAP Profile

Table 9: Users created during configuration on managed system

6.5 Configuration Check After completing the configuration of Root Cause Analysis in SAP Solution Manager, check

the Configuration Check document in service.sap.com/diagnostics to verify that allconfiguration steps are done

Diagnostics provides a powerful self-check mechanism. This self-check is organized into 4categories:

Solution Manager

Solution Manager configuration

Solution Landscape configuration

Application configuration

Each Diagnostics self-check category is intended to be executed at given Diagnostics keyconfiguration steps, which are:

Solution Manager Installation:Once the setup step from the Diagnostics system setup wizard, named: “The RFC programWEBADMIN will be created and started in J2EE engine” has been successfully performed

Solution Manager confi gurationOnce ALL setup step from the Diagnostics system setup wizard have been successfullyperformed

Solution Landscape configuration

After each new additionally Managed system has been configured within Diagnostics, usingSolution Manager SMSY and the Managed system setup wizard

Appl icat ion conf igurat ion After each new additionally Managed system has been configured within Diagnostics, usingSolution Manager SMSY and the Managed system setup wizard

Please connect to Diagnostics as admin user and navigate to Diagnostics Administration – Managed system.




Then run the various self-check categories, each time you performed a Diagnostics keyconfiguration step in order to validate that this configuration step will be operational from aDiagnostics point of view.

The self-check result will provide, for each individual check item, a status and detailedinformation to guide you in order to fix the associated configuration problem

RCA Inst Upgr Guide SP13

Documents

Transcript of RCA Inst Upgr Guide SP13