Está en la página 1de 35

Setup SLD in the scope of E2E Root

Cause Analysis
Solution Manager SP17

SAP NetWeaver™ ‘04s
Document Version 1.5 – December 2008

SAP AG
Neurottstraße 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com

© Copyright 2008 SAP AG. All rights reserved.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services mentioned

No part of this publication may be reproduced or transmitted

herein as well as their respective logos are trademarks or

in any form or for any purpose without the express

registered trademarks of SAP AG in Germany and in several

permission of SAP AG. The information contained herein

other countries all over the world. All other product and

may be changed without prior notice.

service names mentioned are the trademarks of their
respective companies. Data contained in this document

Some software products marketed by SAP AG and its

serves informational purposes only. National product

distributors contain proprietary software components of other

specifications may vary.

software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.

These materials are subject to change without notice. These
materials are provided by SAP AG and its affiliated

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

companies ("SAP Group") for informational purposes

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

only, without representation or warranty of any kind, and

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

SAP Group shall not be liable for errors or omissions with

WebSphere, Netfinity, Tivoli, and Informix are trademarks

respect to the materials. The only warranties for SAP

or registered trademarks of IBM Corporation in the United

Group products and services are those that are set forth in the

States and/or other countries.

express warranty statements accompanying such products
and services, if any. Nothing herein should be construed as

Oracle is a registered trademark of Oracle Corporation.

constituting an additional warranty.

UNIX, X/Open, OSF/1, and Motif are registered trademarks
of the Open Group.

Disclaimer
Some components of this product are based on Java™. Any

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

code change in these components may cause unpredictable

VideoFrame, and MultiWin are trademarks or registered

and severe malfunctions and is therefore expressively

trademarks of Citrix Systems, Inc.

prohibited, as is any decompilation of these components.

HTML, XML, XHTML and W3C are trademarks or

Any Java™ Source Code delivered with this product is only

registered trademarks of W3C®, World Wide Web

to be used by SAP’s Support Services and may not be

Consortium, Massachusetts Institute of Technology.

modified or altered in any way.

Java is a registered trademark of Sun Microsystems, Inc.
Documentation on SAP Service Marketplace
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.

You can find this documentation at
service.sap.com/instguidesNW04

T ypographic Conventions
Type Style
Example
Text

Represents

Icons
Icon

Meaning

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

Caution

Example
text

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

Syntax

EXAMPLE
TEXT

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.

Example
text

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.

Example
text

Exact user entry. These are
words or characters that
you enter in the system
exactly as they appear in
the documentation.

<Example
text>

Variable user entry. Angle
brackets indicate that you
replace these words and
characters with appropriate
entries to make entries in
the system.

Example
Note
Recommendation

............................................................... 8 3 SOLUTION MANAGER MUST SEND ITS SYSTEM DATA TO THE PRODUCTIVE SLD 10 3.................................................................... 15 5 SMSY SHOULD FETCH THE MANAGED SYSTEMS DESCRIPTION FROM THE SOLUTION MANAGER SLD ..............3 Connect the productive SLD to the Solution Manager (local) SLD............................................................... 3 2.................. 1 1.................... 6 2...........................................................................1 Send Solution Manager ABAP system data to the productive SLD..................... 14 4 SOLUTION MANAGER J2EE APPLICATIONS (CIM CLIENT) MUST CONNECT TO THE LOCAL SLD ............. 2 2 FIRST SETUP THE SOLUTION MANAGER (LOCAL) SLD ...........................1 Kind of SLD infrastructure setup with this guide .... 10 3........2 Send Solution Manager's Java system data to a productive SLD .............Contents December 2008 Contents 1 INTRODUCTION ....................................................2 Start the Solution Manager (local) SLD. 18 6 TROUBLESHOOTING ........................................................................................ 3 2....................................................................1 Setup the Solution Manager (local) SLD ......................................... 27 Setup SLD in the scope of E2E Root Cause Analysis I ..............................

with the name: SLDSMDUSER.sdn. In particular paragraph: Special features of individual packages / Upgrade from Version 2. has introduced a guide setup procedure (transaction solman_setup). which provides very useful and important general information about SLDs. Last but not least please work-through the Diagnostics Agent Setup Guide available at: http://service. and installed CIM data models / SAP CR content versions of the involved SLDs.4 SP 08. Therefore the automatic (bridge) forwarding works independent of releases.SLD of SAP NetWeaver 7. before consider the upgrading of the CIM model version to 1. in the runtime or design-time SLD(s). It should give an overview of the steps you will have to perform and hopefully help avoiding a number of pitfalls. Moreover the SAP note 669669. a dedicated user could be created.30) on the Marketplace / SAP Support Packages. Setup SLD in the scope of E2E Root Cause Analysis 1 .5.sap.0 to Version 3.com/irj/sdn/nw-sld.Introduction 1 Introduction This guide should be used as a "cookbook" for setting up the System Landscape Directory (SLD) of a freshly installed Solution Manager system.30.System Landscape Directory. Therefore several part of this guide will no longer need to be performed manually in the scope of EhP 1. Before you start with this document please check-out the Planning Guide .5. patch levels. Finally be aware that the SLD bridge forwarding "replicates" data (provided by SLD Data Suppliers) without interpreting or changing it.0) available at: https://www. Additionally at least work-through the chapter: "Exports and Backups of CIM Instances" of the SLD setup guide (User Manual . This user will be used by the Diagnostics agents and for the Agent Candidates Management (console). IMPORTANT: The newly available Solution Manager 7. Indeed.01 SP18). which in particular includes an automated setup of the Solution Manager (local) SLD. Otherwise import first the "intermediate" SAP CIM model 1.zip contains the model version 1. Some hints relative to the update of the SLD CIM model and the SAP Component Repository data (CR) could be found in SAP note: 907897.0) will give the download location of the SAP CR and the CIM model (note that cimsap1509_*.26. this NEW feature available with Solution Manager SP15 and Diagnostics Agents SP14 will in particular need at least a CIM model version 1. In particular.0 EhP 1 (also known as Solution Manager 7. Additionally.x.4. double check that the current version used by your SLDs is at least 1.com/diagnostics for additional recommendations in particular regarding the SAP CIM data model version required (on the SLD landscape) to be able to remotely associate Diagnostics Agents to a Solution Manager system. This console allows performing a remote association of those agents with a Solution Manager system. The authorizations needed for this SLDSMDUSER user are also described in the Agent Setup guide.sap.5.

) Managing System (7. SMSY_SETUP) User: SLDDSUSER Send tech. serv. or MDM (C++). Settings – within SLD Data Suppl. etc. serv. / JCo RFC Prov. Dual stack). SLDAPICUST + tr. 2 . data (Visual Admin / HTTP Settings – within SLD Data Suppl. Agent / Sol Man system” association User: SLDBRIDGE (or standard SLDDSUSER) SLD Bridge forwarding • (If performance impacts: Remove bridge and update host used for SMSY fetch) Productive SLD 1 Web AS User: SLDAPIUSER • SMSY fetch (Visual Ad. data (tr.Introduction 1. rz70 / RFC Dest: SLD_UC) • Solution Manager Sol Man SLD (Must NOT be productive) Diagnostics • Solution Manager Dual stack Setup SLD in the scope of E2E Root Cause Analysis Managed System ABAP Web AS Managed System SLD 2 Java Web AS Web AS Managed System User: SLDDSUSER • Send tech.00) User: SLDCIMUSER Web Dynpro connection data (Using Visual Ad.1 Kind of SLD infrastructure setup with this guide User: SLDSMDUSER • Send technical Data • Periodic look-up of “Diag. Java. / CIM Client G.) Diagnostics Agent User: SLDSMDUSER Create assocation between Sol Man & Agent • ABAP Web AS Managed System Java Web AS Managed System Diagnostics Agent Managed System Managed systems (ABAP. + RFC Dest: SAPSLDAPI + tr.

0 2.) SAP_SLD_SUPPORT (Must be created. This could be done automatically. Could only be an UME group. with a build in function of the J2EE Visual Administrator.1 Setup the Solution Manager (local) SLD Please be aware that these chapters mainly applies for Solution Manager / SLD 7. which are no more relevant. Therefore run the Visual Administrator and navigate to the "SLD Data Supplier” service of your J2EE engine server node. Validate using the Solution Manager (J2EE engine) User Management Engine (UME) that at least the following UME groups (stored in the ABAP user data store as ABAP roles) exist.0 EhP1 system most of the configuration steps are first of all performed automatically and some features have been changed like for example the "Grant CIM Client Generation Permissions" settings (as described in chapter: Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD).00 systems.First setup the Solution Manager (local) SLD 2 First setup the Solution Manager (local) SLD Extract of the: Post-Installation Guide . Associate the required (SLD specific) J2EE Security roles to the UME user groups that you validated just beforehand.) 2.SLD of SAP NetWeaver 7. Setup SLD in the scope of E2E Root Cause Analysis 3 . In this service click on the button (in the top left-hand corner) named: "Assign application roles to user groups". ABAP user roles / UME user groups SAP_SLD_GUEST SAP_SLD_DEVELOPER SAP_SLD_CONFIGURATOR SAP_SLD_ORGANIZER SAP_SLD_ADMINISTRATOR SAP_SLD_DATA_SUPPLIER (Must be created. In case you setup a Solution Manager 7. 1. Could only be an UME group.

sap.First setup the Solution Manager (local) SLD 3. LcrAdministrator sap. The J2EE security roles. In this service navigate to “Runtime” -> “Policy Configurations”. Now. Note that you have two kinds of security roles: UME security roles and J2EE security roles. modify and delete UME action. the UME security roles that you will now create.lcr. LcrInstanceWriterLD.LcrSupport Read-only access to all SLD data and UI.lcr*sld” and navigate to “Security Roles”.sap.lcr. The UME roles. using the User Management Engine (J2EE UME) additionally create the following UME roles and associate them UME actions. modify and delete CIM instances of the Name Reservation subset (includes the LcrUser role). as described here after. associate these UME roles to the following UME groups. LcrInstanceWriterAll sap. modify and delete CIM instances of the Landscape Description subset (includes the LcrUser role).com_com.sap.lcr.com_com. are required for the applications based on Web Dynpro UIs. LcrInstanceWriterCR.sap. or the CIMOM Servlet. The J2EE Security Roles could be visualized using the J2EE Visual Administrator as follow.com_com. including the Administration area (used for SAP support). LcrInstanceWriterLD sap. UME Group Assigned UME role (Roles created manually) SAP_SLD_GUEST LcrUser SAP_SLD_DEVELOPER LcrInstanceWriterNR SAP_SLD_CONFIGURATOR LcrInstanceWriterNR SAP_SLD_CONFIGURATOR LcrInstanceWriterLD SAP_SLD_ORGANIZER LcrInstanceWriterAll SAP_SLD_ADMINISTRATOR LcrAdministrator Setup SLD in the scope of E2E Root Cause Analysis 4 .lcr.sap. as listed in the following table. are used by J2EE applications based on Servlets and JSPs. UME role UME Actions Actions Permissions LcrUser sap.lcr.LcrUser Read access to SLD data. which whereas already exist. also they are “distinct”.sap.com_com. Now. DataSupplierLD A UME role with no corresponding Create. CIM instances of the Landscape Description subset as a data supplier without access to the SLD UI.com_com. will have the same name as the existing J2EE security roles.sap. like the Data Supplier Servlet.com/com. Navigate to the “Security Provider” service of your J2EE engine server node. LcrSupport sap.LcrInstanceWriterLD Create.LcrInstanceWriterAll Create.LcrInstanceWriterNR Create.LcrAdministrator Administrative tasks (includes all other roles). LcrInstanceWriterNR sap. As you will see.com_com. modify and delete all types of CIM instances (includes the LcrUser. and LcrInstanceWriterNR roles). Select the Component: “sap. which you will have to create manually (hereafter) using the User Management Engine (UME).lcr.

as an ABAP Admin user and start transaction: su01 The user that are additionally need could be named: .SLDAPIUSER . SLD User on Solution Manager Assigned ABAP roles SLDAPIUSER SAP_SLD_CONFIGURATOR SLDCIMUSER SAP_SLD_ORGANIZER Setup SLD in the scope of E2E Root Cause Analysis 5 . associate the SLD users that have been created or checked in the former steps 1 & 2. and for each of them associate it with the following ABAP roles (coming from the R3 data store) or UME groups (coming from the UME data store). Finally. as an ABAP Admin user and start transaction: su01 Now take all users listed in the following table.SLDCIMUSER .First setup the Solution Manager (local) SLD SAP_SLD_DATA_SUPPLIER DataSupplierLD SAP_SLD_SUPPORT LcrSupport 4. Note that ABAP roles are visible as groups within the UME. Validate using the User Management Engine (J2EE UME) that at least the following users exist: . Therefore logon to Solution Manager (ABAP).SLDBRIDGE 6. Create additional SLD users Therefore logon.SAPJSF .SLDDSUSER 5.

please validate on the "productive” SLD. Logon to the SLD Take a user belonging to the UME group: SAP_SLD_ADMINISTRATOR.2 Start the Solution Manager (local) SLD 1. to which Solution Manager will send its Data Supplier information. 2.00) SAP_SLD_ORGANIZER (in case prod SLD is NW 6. Goto Administration Profile Setup SLD in the scope of E2E Root Cause Analysis 6 .40) Additionally. that the following user exist and that it has the relevant UME Group (or ABAP role) SLD User on "productive SLD” Assigned UME group SLDDSUSER SAP_SLD_DATA_SUPPLIER 2.First setup the Solution Manager (local) SLD SLD User on Solution Manager Assigned UME group SLDBRIDGE (or standard SLDDSUSER) SAP_SLD_DATA_SUPPLIER (in case prod SLD is NW 7.

which is in our case the Solution Manager (local) SLD itself. Note that the Gateway Service default name is: sapgw<Double stack Instance Number> 4. Edit only "Section": "datasupplier" Maintain the SLD's associated Gateway Host and Service. Start or Stop/Start the SLD Setup SLD in the scope of E2E Root Cause Analysis 7 .First setup the Solution Manager (local) SLD 3.

3 Connect the productive SLD to the Solution Manager (local) SLD The productive SLD should forward the Technical System data it receives from the Managed systems (also known as Data Suppliers) to the Solution Manager (local) SLD.First setup the Solution Manager (local) SLD 2. 2. Logon to (one) productive SLD Take a user belonging to the UME group: SAP_SLD_ADMINISTRATOR. Goto Administration Data Suppliers Setup SLD in the scope of E2E Root Cause Analysis 8 . The SLD bridge forwarding is put in place with the following steps: 1. Such a mechanism is called: SLD Bridge forwarding.

Provide Solution Manager Hostname and J2EE engine HTTP port (Web Dispatcher).First setup the Solution Manager (local) SLD 3. The user provided here should be the SLDBRIDGE user. which we created and that has the UME group: SAP_SLD_DATA_SUPPLIER on the Solution Manager system. For more information about the SLD specific users and roles please refer to the chapter dealing with users on the Solution Manager system in this document. Click on Add SLD 4. These settings will be used by the productive SLD to "replicate" the Technical System data to the Solution Manager’s (local) SLD Setup SLD in the scope of E2E Root Cause Analysis 9 .

corp:50000 sld/active not available (incoming data will be ignored). Service: enter the name of the (Productive SLD) gateway service.CIMClientException: HTTP response code: 403 Forbidden Solution The user provided for the SLD bridge forwarding. Setup SLD in the scope of E2E Root Cause Analysis 10 . named SAPSLDAPI_<SolMan_SID> and maintained in Visual Administrator (on the productive SLD).sap. #57 02/05/2008 15:40:05. Host: enter the hostname of the (standalone) gateway used by the Productive SLD. should be the SLDBRIDGE (or standard SLDDSUSER) user.lcr.ncel. An example of how to create / configure a JCO RFC Provider could be found in section: "Create JCO RFC provider SAPSLDAPI_SIZ.cimclient. 3 Solution Manager must send its system data to the productive SLD 3.sap. as they ONLY apply for setting-up the SMSY fetch infrastructure against the Solution Manager (local) SLD. please work-through the latter solution.50 [Thread-38] WARNING com.BuilderDirector: Warning: SLD target system http://nces60121833a.where you just setup the bridge to the Solution Manager's local SLD.sap. which you just created beforehand and that has the UME group: SAP_SLD_DATA_SUPPLIER on the Solution Manager system. the Productive SLD and the Solution Manager ABAP Data Supplier must use the same Gateway (the one which is "local" to the Productive SLD). In the section "SLD Bridge: Gateway Information". b. enter the following data: a.sagent.1 Send Solution Manager ABAP system data to the productive SLD Productive SLD J2EE engine Solution Manager ABAP stack Use transaction rz70 to send the ABAP system data to the SLD 1. Indeed.lcr. Note that the default name is: sapgw<Instance Number> Make sure that the entries for the gateway host and service are exactly the same as for the "JCO RFC Provider" on the productive SLD. used by the latter created RFC destination: SAPSLDAPI". In case you find the following kind of error. For more information about the SLD specific users and roles please refer to the first chapter in this document. IMPORTANT: Do NOT use the values provided in that example to configure your ABAP Data Supplier.api.Solution Manager must send its system data to the productive SLD Troubleshooting Check the SLD logs of the productive SLD . Thrown: com.

you can activate this data collection program. If you want to create additional information about RFC destinations in the SLD.Solution Manager must send its system data to the productive SLD Note: The "Data Collection Program”: _SLD_RFC is deactivated by default. Please do not deactivate other "Data Collection Programs” Setup SLD in the scope of E2E Root Cause Analysis 11 .

Solution Manager must send its system data to the productive SLD 2.without scheduling a batch job. Save these settings by choosing Activate Current Configuration. which runs the data collector . A separate screen appears with a list of the executed programs and will know whether the initial data transfer (via RFC) succeeded. For more information.only Otherwise Choose Start Data Collection and Job Scheduling. see SAP Note 584654. . Setup SLD in the scope of E2E Root Cause Analysis 12 . If you want validate that the System Technical Data (Data Supplier) is correctly sent to the Productive SLD: Choose "Start Data Collector without Job Scheduling" once . 3.

and the TCP/IP connection SLD_NUC for a non-Unicode productive SLD system. will. Validate both the hostname and service. These connections are created automatically and both should of course point to the same productive SLD. 1.Solution Manager must send its system data to the productive SLD Note: This transaction rz70 used to setup the collection of the Solution Manager ABAP technical system data. A scheduled batch job updates the data about the system in the Productive SLD twice a day (720 minutes – 12 hours). The TCP/IP connection SLD_UC is used by default for a Unicode productive SLD system. The RFC connection is chosen automatically by Solution Manager in case you left the "Automatic RFC Destination" selected in rz70 within the section "Transport Information". Setup SLD in the scope of E2E Root Cause Analysis 13 . This RFC destination will then be used to send the ABAP system data to a productive SLD Therefore please also validate in transaction sm59 that the "SAP_UC" RFC destination (TCP/IP Connection) is used by Solution Manager to send its system data to the "correct" productive SLD Gateway. You might encounter RFC connection problems In that case perform a RFC Destination connection test in transaction SM59. Result You have now setup the Solution Manager ABAP data supplier to send its technical data directly to a productive SLD by using an RFC connection. in order to send it to the productive SLD. each time you maintain the settings in the section "SLD Bridge: Gateway Information" also update: The "Gateway Options” within the TCP/IP RFC destination "SAP_UC” (for Unicode productive SLD).

the second one at each system start. please click on: Setup SLD in the scope of E2E Root Cause Analysis 14 . The first job runs periodically. This Data supplier service uses an HTTP connection. having the UME group: SAP_SLD_DATA_SUPPLIER on the productive SLD. (For more information about the SLD specific users and roles please refer to the first chapter in this document: 2.1 Setup the Solution Manager (local) SLD) In order to send and validate this connectivity. They should both be "Released".2 Send Solution Manager's Java system data to a productive SLD Now you will have to also configure the Solution Manager Java "Data Supplier" to send also the Java Technical system data to the same productive SLD. which should connect with the default user SLDDSUSER.Solution Manager must send its system data to the productive SLD 2. with transaction SM37. Background jobs Check the scheduling of SLD background jobs with the names "SAP_SLD_DATA_COLLECT" and "SAP_SLD_DATA_COLLECT_STARTUP". This keeps the system information in SLD up-to-date automatically 3.

You could find a discussion about all these subjects . as the above listed restrictions will again apply and you will moreover encounter SLD release (availability) issues.10 product. even if these are not operational. in case of planned or unplanned productive SLD(s) downtime. you would like to be able to Root Cause Analyze the productive SLD(s) themselves. you will otherwise not be able to Root Cause Analyze any other SAP product in the customer landscape. Of course.presenting the main impacts . Therefore the Java Web Dynpro applications (E2E Trace Analysis) must always be CIM clients of the Solution Manager's local SLD. (Solution Manager Java to ABAP stack JCo communication data is stored in the SLD. Indeed. Additionally note that the Solution Manager (local) SLD must never be promoted to be the productive (central) SLD. using Diagnostics. as soon as the customer landscape contains at least a SAP NW 7.) Setup SLD in the scope of E2E Root Cause Analysis 15 .Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD You should then get the following message: 4 Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD The Solution Manager RCA scenario must not reply on the availability of a productive SLD.within the SLD planning guide.

com/tc~lm~webadmin~sld~wd/webdynpro/public/lib/sap. provide the fully qualified host name of the Solution Manager system.com~tc~lm~webadmin~mainfr ame~wd.jar sap."Grant CIM Client Generation Permissions" to the following Protection Domains: sap.until EhP1 .jar Setup SLD in the scope of E2E Root Cause Analysis 16 .1 Setup the Solution Manager (local) SLD).com/com.jar sap. For more information about the SLD specific users and roles please refer to the first chapter in this document (2. Additionally .com/tc~lm~webadmin~mainframe~wd/webdynpro/public/lib/sap.Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD Therefore in the "CIM Client Generation Settings". and take the SLDCIMUSER user. which we created beforehand and that has the ABAP role: SAP_SLD_ORGANIZER (on the Solution Manager system).lcr/lcrcimom.com~tc~lm~webadmin~sld~wd.sap.

used by the Solution Manager J2EE engine applications (CIM Client).Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD Finally perform a "CIMClient Test" in order to validate that this connectivity (and user authorizations) are operational: Note that if this test fails you could read through the Troubleshooting chapter at the end of this document. via the Bridge forwarding. you should put in place a "Bridge forwarding". to be operational at the time you run it.via the Productive SLD . Now. You might simply click on the thunder strike. note that the Diagnostics system setup wizard requires.3 Connect the productive SLD to the Solution Manager (local) SLD. also into the local SLD. the Solution Manager J2EE engine applications (CIM Client) could connect to this Solution Manager (local) SLD. from the productive SLD (that you maintained in the "HTTP Settings"). to this Solution Manager local SLD Indeed. that the Solution Manager (Java) Technical System data has been pushed . Keep in mind that the Solution Manager (local) SLD.to the (local) SLD of Solution Manager itself! In case this Solution Manager Technical system data is not yet visible in the (local) SLD. will NOT be fed when you click on the thunder strike. if NO "Bridge forwarding" (from productive to local SLD) has been put in place! Setup SLD in the scope of E2E Root Cause Analysis 17 . using the SLDCIMUSER user. as shown hereafter. which will update the technical data in the Productive SLD and. As shown in chapter: 2.

Both RFC and HTTP protocols are used for connecting the SLD ABAP API and the SLD. so that the ABAP RFC calls will be forwarded to this SLD Java Client. Program ID: SAPSLDAPI_<Solution Manger SID> b. Server count : (by default) 3 Fill-in the fields from the "Repository” section as follow: e. Application server host : Fully qualified hostname of your Solution Manager system g. which should NOT be the case in the case of a Solution Manager system. used by the latter created RFC destination: SAPSLDAPI This step configures the SLD Java Client itself as well as the Solution Manager local Gateway. Some components. 1. Then only the HTTP communication could be remote. Run Visual Administrator (on the Solution Manager J2EE side) and navigate to the "JCo RFC Provider” service of your J2EE engine server node. etc. the corresponding J2EE Engine can be used alternatively as an RFC provider.). Gateway service : (by default) sapgw<Solution Manager Instance Nb> d.3 Connect the productive SLD to the Solution Manager (local) SLD. You have to configure both the RFC channel from ABAP to Java and the HTTP connection parameters (see transaction SLDAPICUST). System number : <Solution Manager Instance Nb> h. Client number: <productive ABAP client number> Setup SLD in the scope of E2E Root Cause Analysis 18 . The following figure shows the configuration of the SLD ABAP API in detail: In this situation it must be the Solution Manager local SLD Setup step 2 "SMSY fetch" Setup step 1 Setup step 3 Note: If the ABAP system is an add-in installation to a J2EE system. use the SLD Application Programming Interface for ABAP-based systems (SLD ABAP API) to read data from and write data to the SLD. Gateway host : Fully qualified hostname of your Solution Manager system c. Select "Specific Application Server” f. Fill-in the fields from the "Registered server” section as follow: a. the Solution Manager SLD will contain a "replication" of all Technical System Data (complete catalog of installed software components. In this service navigate to "Runtime” -> "Bundles”. See chapter: 2.SMSY should fetch the managed systems description from the Solution Manager SLD 5 SMSY should fetch the managed systems description from the Solution Manager SLD First of all. note that with the "SLD bridge forwarding" from the productive SLD(s) to the Solution Manager local SLD. such as XI and the Solution Manager. At this point it doesn’t mean that the Solution Manager (local) SLD will be used. Create JCO RFC provider SAPSLDAPI_SIZ.

Therefore please do not consider changing the password of this SAPJSF user (on the ABAP stack) without additionally updating the password in the UME configuration (connection to ABAP backend).) j. also used by the J2EE User Management Engine (UME). on double stack systems. whose credentials (password) are. User: SAPJSF This user is the SAPJSF user maintained in the productive ABAP client.SMSY should fetch the managed systems description from the Solution Manager SLD i. Password : <provide SAPJSF user password> CAUTION: SAPJSF is a standard communication user. as indicated in the previous field (h. In case you do not take into account this recommendation. you will encounter a system standstill after the next restart! Maintain here the Solution Manager Hostname Maintain here the Solution Manager Hostname Setup SLD in the scope of E2E Root Cause Analysis 19 .

copy the RFC destination named "SLD_UC” to create this destination "SAPSLDAPI” which should be of type (TCP/IP connections) Setup SLD in the scope of E2E Root Cause Analysis 20 . Use transaction SM59 a. Create the RFC destination "SAPSLDAPI”. Eventually.SMSY should fetch the managed systems description from the Solution Manager SLD 2.

Setup SLD in the scope of E2E Root Cause Analysis 21 . which is used by the "SAP_UC" RFC Destination). you the MUST adapt it by changing not only the Program ID to SAPSLDAPI_<SolMan_SID>. In case this RFC destination is created via a copy.SMSY should fetch the managed systems description from the Solution Manager SLD b. BUT also reference the Solution Manager Gateway host and service (instead of the productive SLD gateway.

Use transaction SLDAPICUST User SLDAPIUSER already exists. Note: The SLDAPICUST transaction indeed allows setting-up the HTTP connection to be used by the SAPSLDAPI_SIZ program (Java SLD Client) to connect to the local SLD.SMSY should fetch the managed systems description from the Solution Manager SLD 3. by default. Check that the displayed hostname is the fully qualified hostname of the Solution Manager system. to allow the Solution Manager ABAP stack program to send its requests to the (local) SLD. It must belong to the ABAP role: SAP_SLD_CONFIGURATOR. Check that the Solution Manager Hostname appears here Setup SLD in the scope of E2E Root Cause Analysis 22 .

RFC ping was successful Result of the above configuration above steps 1 & 2 b. Use transaction SLDCHECK to validate the connectivity to the SLD Here is the relationship between result of the SLDCHECK test and the various setup steps: a. please refer to the remark in chapter: 1 Introduction. please double check in transaction SLDAPICUST (on Solution Manager System) the SLDAPIUSER password! In case of warning regarding the SLD data content. Setup SLD in the scope of E2E Root Cause Analysis 23 .SMSY should fetch the managed systems description from the Solution Manager SLD 4. SLD server access settings Result of the above configuration above step 3 Check that the Solution Manager Hostname appears here IMPORTANT: When you get a message like: "Function call returned exception code 4".

Use transaction SMSY_SETUP to schedule the automatic SLD data fetch Check that the Solution Manager Hostname appears here.SMSY should fetch the managed systems description from the Solution Manager SLD Additionally a Web browser window will be displayed.) Setup SLD in the scope of E2E Root Cause Analysis 24 . Check that the Solution Manager Hostname appears here 5. (Maintain the host/port with transaction SLDAPICUST.

schedule this SMSY fetch operation.SMSY should fetch the managed systems description from the Solution Manager SLD Finally. Troubleshooting Additionally also check whether the just scheduled "SMSY Data Transfer" has already been executed without errors. by clicking on the "Schedule Data Transfert from TMS/SLD" button: Note that you can use LP01 as output device in order to prevent useless prints. using transaction: slg1 In case you get the following error: "The SLD server connection is inactive". Setup SLD in the scope of E2E Root Cause Analysis 25 .has not the correct Security roles. it is most likely related to the fact that the SLDAPIUSER (on Solution Manager) .used by this "Data Transfer" operation (see former step 3) .

as follow: Setup SLD in the scope of E2E Root Cause Analysis 26 .SMSY should fetch the managed systems description from the Solution Manager SLD Finally. Note that for a SAP internal system you could maintain the System number in SMSY. an S-user to the ABAP user. do not forget to associate. which will run this periodic SMSY "Data Transfer" job. using transaction AISUSER.

See the above chapter: 4 Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD. as described in 3. So when triggering the (Solution Manager Java stack technical) data transfer to the productive SLD. in order to generate and store (via a J2EE engine CIM Client application) the JCo Destinations: "E2E_SMD_SM_DATA" and "E2E_SMD_SM_METADATA". you will. The Solution Manager Java system data required in the local SLD. Indeed E2E Root Cause Analysis requires JCo Destinations used by the E2E tools to perform "internal" Web Dynpro connections between the Solution Manager Java stack to ABAP stack.Troubleshooting 6 Troubleshooting Issue 1: Diagnostics system setup wizard fails to perform the task: "(E2E) The JcoRFC destinations E2E_SMD_SM_DATA and E2E_SMD_SM_METADATA for WebDynpro will be created in SLD" This wizard task fails to look-up the Solution Manager system data within the local SLD.2 Send Solution Manager's Java system data to a productive SLD. Resolution: The issue comes from the fact that the Solution Manager's (local) SLD has no technical system entry yet for the Solution Manager system itself. wil be created / updated via the "Bridge forwarding" as explained in the above chapter. via the "SLD bridge forwarding" get also the following kind of entry within the Solution Manager (local) SLD: Setup SLD in the scope of E2E Root Cause Analysis 27 . These JCo Destinations will be created and associated to the Solution Manager Java stack description within the local SLD.

within the "Diagnostics system setup wizard". run again the task: "(E2E) The Jco RFC destinations E2E_SMD_SM_DATA and E2E_SMD_SM_METADATA for WebDynpro will be created in SLD". Now you will see the JCo Destinations: "E2E_SMD_SM_DATA" and "E2E_SMD_SM_METADATA" stored within the Solution Manager (local) SLD.Troubleshooting Then. Setup SLD in the scope of E2E Root Cause Analysis 28 .

Troubleshooting Issue 2: Failure of the CIM client (access) test.1 Setup the Solution Manager (local) SLD. that you created initially. you will find an error: "HTTP request processing failed (HTTP error 403)" with user SLDCIMUSER. Within the Solution Manager's J2EE engine "SAP logs" (using NW Admin). For more information about the SLD specific users and roles please refer to the first chapter: 2. Resolution: You should check whether the user SLDCIMUSER. Setup SLD in the scope of E2E Root Cause Analysis 29 . triggered within Visual Administrator. has the ABAP role: SAP_SLD_ORGANIZER on the Solution Manager system. on the "SLD Data Supplier" service of your Solution Manager J2EE engine server node under "CIM Client Generation Settings".

process_FilesystemConfiguratio n(ConfigGatherTask.sap. 10 more Setup SLD in the scope of E2E Root Cause Analysis 30 .sup. [EXCEPTION] com.webservices.jaxrpc.admin.AbstractGatherRemoteTask.task.checkTaskResult(AbstractGat herRemoteTask.sup.sap.soapbinding.java:232) […] at java.task.sap.sap.remote.remote.wsdl2java.MimeHttpBinding..exception.proxies.WarnTaskExecutionException: Thu Feb 07 11:15:33 CET 2008 | SLD:Error initializing SLD:null at com.engine.scheduler.run(Thread.sup.admin.config..sup.task.admin.scheduler.process_FilesystemConfiguratio n(ConfigGatherTask.sap.processDocum entFault(MimeHttpBinding.SLDStartException at com.services.java:534) Caused by: com.sap.remote.admin.lang.Thread.sup.Troubleshooting Issue3: The "Collect Configuration Data" task executed by Diagnostics (within "Diagnostics Administration" -> "Managed Systems" -> "Scheduler") fails with the following kind of error: [1835] The Task Collect Configuration Data (nces60128498a) has been processed with warnings.ws.ConfigGatherTask.scheduler.admin.ConfigGatherTask.scheduler.config.java:217) .java:921) […] at com.java:52) at com.

.sap. Create the namespace "sld/smd" in the Solution Manager local SLD.lcr*sld#LcrClassWriter Setup SLD in the scope of E2E Root Cause Analysis 31 . under: "Diagnostics Setup" -> "Diagnostics Systems" -> "Advanced Setup" -> "Wily & NWA" -> "NWA Information" Indeed.sap.?.com/com.sap.:5??00): sap. Populate this local SLD namespace with the technical data of the Managed systems that have been setup in E2E RCA.lcr*sld#LcrInstanceWriterLD sap.sap.com/com.lcr*sld#LcrInstanceWriterNR sap..sap. Indeed.lcr*sld#LcrAdministrator sap. 2.com/com. The following list describes the J2EE security roles required . the user maintained at this place is by default a Java administrator user of the Solution Manager System and has therefore the ABAP role: SAP_J2EE_ADMIN (and implicitly the UME / J2EE security role: LcrAdministrator). the "Collect configuration data" task requires a set of J2EE security roles in order to: 1.com/com..covered by the ABAP role: SAP_SLD_ADMINISTRATOR to perform this local SLD population (Associated description in the defaultTrace.lcr*sld#LcrSupport sap. For more information about the SLD specific users and roles please refer to the first chapter in this document.trc: [SMD_NWA_SLD_PUBLISH] Init the SLD on nwa host: http://.Troubleshooting Resolution: Find out which user is maintained within SAP Solution Manager E2E Root Cause Analysis.lcr*sld#LcrInstanceWriterCR sap.lcr*sld#LcrUser sap.com/com.com/com.sap.sap.com/com.. Note that this SLD namespace is used by some E2E RCA tools that are based on the J2EE standard NWAdmin tools.