Setup Solution Manage Diagnostics Sld

SAP NetWeaver 04s

Document Version 1.5 December 2008

Setup SLD in the scope of E2E RootCause Analysis

Solution Manager SP17

Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmittedin any form or for any purpose without the expresspermission of SAP AG. The information contained hereinmay be changed without prior notice.

Some software products marketed by SAP AG and itsdistributors contain proprietary software components of othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks 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 trademarksor registered trademarks of IBM Corporation in the UnitedStates and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks orregistered trademarks of W3C, World Wide WebConsortium, 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 andimplemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAPNetWeaver, and other SAP products and services mentionedherein as well as their respective logos are trademarks orregistered trademarks of SAP AG in Germany and in severalother countries all over the world. All other product andservice names mentioned are the trademarks of theirrespective companies. Data contained in this documentserves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. Thesematerials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposesonly, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions withrespect to the materials. The only warranties for SAPGroup products and services are those that are set forth in theexpress warranty statements accompanying such productsand services, if any. Nothing herein should be construed asconstituting an additional warranty.

DisclaimerSome components of this product are based on Java. Anycode change in these components may cause unpredictableand severe malfunctions and is therefore expressivelyprohibited, as is any decompilation of these components.

Any Java Source Code delivered with this product is onlyto be used by SAPs Support Services and may not bemodified or altered in any way.

Documentation on SAP Service MarketplaceYou can find this documentation atservice.sap.com/instguidesNW04

SAP AG

Neurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

T yp 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 charactersquoted from the screen.These include field names,screen titles, pushbuttonslabels, menu names, menupaths, and menu options.Cross-references to otherdocumentation

Exampletext

Emphasized words orphrases in body text,graphic titles, and tabletitles.

EXAMPLETEXT

Technical names of systemobjects. These includereport names, programnames, transaction codes,table names, and keyconcepts of a programminglanguage when they aresurrounded by body text,for example, SELECT andINCLUDE.

Exampletext

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

Exampletext

Exact user entry. These arewords or characters thatyou enter in the systemexactly as they appear inthe documentation.

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

I c o n s

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents December 2008

Setup SLD in the scope of E2E Root Cause Analysis I

Contents

1 INTRODUCTION ............................................................................................................ 11.1 Kind of SLD infrastructure setup with this guide ............................................... 2

2 FIRST SETUP THE SOLUTION MANAGER (LOCAL) SLD ........................................... 32.1 Setup the Solution Manager (local) SLD............................................................. 32.2 Start the Solution Manager (local) SLD............................................................... 62.3 Connect the productive SLD to the Solution Manager (local) SLD.................... 8

3 SOLUTION MANAGER MUST SEND ITS SYSTEM DATA TO THE PRODUCTIVE SLD 10

3.1 Send Solution Manager ABAP system data to the productive SLD................. 103.2 Send Solution Manager's Java system data to a productive SLD ................... 14

4 SOLUTION MANAGER J2EE APPLICATIONS (CIM CLIENT) MUST CONNECT TOTHE LOCAL SLD ............................................................................................................... 155 SMSY SHOULD FETCH THE MANAGED SYSTEMS DESCRIPTION FROM THESOLUTION MANAGER SLD .............................................................................................. 186 TROUBLESHOOTING ................................................................................................. 27

Introduction

Setup SLD in the scope of E2E Root Cause Analysis 1

1 IntroductionThis guide should be used as a "cookbook" for setting up the System Landscape Directory (SLD) of afreshly installed Solution Manager system. It should give an overview of the steps you will have toperform and hopefully help avoiding a number of pitfalls.

Before you start with this document please check-out the Planning Guide - System LandscapeDirectory, which provides very useful and important general information about SLDs. Additionally atleast work-through the chapter: "Exports and Backups of CIM Instances" of the SLD setup guide(User Manual - SLD of SAP NetWeaver 7.0) available at: https://www.sdn.sap.com/irj/sdn/nw-sld.

IMPORTANT: The newly available Solution Manager 7.0 EhP 1 (also known as Solution Manager7.01 SP18), has introduced a guide setup procedure (transaction solman_setup), which in particularincludes an automated setup of the Solution Manager (local) SLD. Therefore several part of this guidewill no longer need to be performed manually in the scope of EhP 1.

Last but not least please work-through the Diagnostics Agent Setup Guide available at:http://service.sap.com/diagnostics for additional recommendations in particular regarding the SAPCIM data model version required (on the SLD landscape) to be able to remotely associateDiagnostics Agents to a Solution Manager system. Indeed, this NEW feature available with SolutionManager SP15 and Diagnostics Agents SP14 will in particular need at least a CIM model version1.5.26. Additionally, a dedicated user could be created, in the runtime or design-time SLD(s), with thename: SLDSMDUSER. This user will be used by the Diagnostics agents and for the AgentCandidates Management (console). This console allows performing a remote association of thoseagents with a Solution Manager system. The authorizations needed for this SLDSMDUSER user arealso described in the Agent Setup guide.

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. In particular, before consider the upgrading of the CIMmodel version to 1.5.x, double check that the current version used by your SLDs is at least 1.4.30.Otherwise import first the "intermediate" SAP CIM model 1.4 SP 08. Moreover the SAP note 669669.In particular paragraph: Special features of individual packages / Upgrade from Version 2.0 toVersion 3.0) will give the download location of the SAP CR and the CIM model (note thatcimsap1509_*.zip contains the model version 1.5.30) on the Marketplace / SAP Support Packages.

Finally be aware that the SLD bridge forwarding "replicates" data (provided by SLD Data Suppliers)without interpreting or changing it. Therefore the automatic (bridge) forwarding works independent ofreleases, patch levels, and installed CIM data models / SAP CR content versions of the involvedSLDs.

Introduction


1.1 Kind of SLD infrastructure setup with this guide

SLD 2Web AS

Solution Manager

DiagnosticsManaging System (7.00)

Web Dynpro connection data(Using Visual Ad. /CIM Client G. Settings withinSLD Data Suppl. serv.)

Solution ManagerDual stack

Productive SLD 1Web AS

Send tech. data(tr. rz70 /

RFC Dest: SLD_UC) Send tech. data(Visual Admin /HTTP Settings within SLD DataSuppl. serv.)

User: SLDDSUSERUser: SLDDSUSER

User: SLDCIMUSER

Managed System

Managed System

JavaWeb AS

Managed System

Create assocationbetween Sol Man & Agent

User: SLDSMDUSER

User: SLDBRIDGE (or standard SLDDSUSER) SLD Bridge forwarding(If performance impacts: Remove bridge and update host used for SMSY fetch)

User: SLDSMDUSER

Send technical Data Periodic look-up ofDiag. Agent / Sol Mansystem association

SMSY fetch(Visual Ad. / JCo RFC Prov.+ RFC Dest: SAPSLDAPI+ tr. SLDAPICUST+ tr. SMSY_SETUP)

User: SLDAPIUSER

Managed systems(ABAP, Java, Dual stack),

or MDM (C++), etc.

Managed System

Managed System

JavaWeb AS

Managed System

ABAPWeb AS

ABAPWeb AS

DiagnosticsAgent

DiagnosticsAgent

Sol Man SLD(Must NOT be productive)

First setup the Solution Manager (local) SLD


2 First setup the Solution Manager (local) SLDExtract of the: Post-Installation Guide - SLD of SAP NetWeaver 7.0

2.1 Setup the Solution Manager (local) SLDPlease be aware that these chapters mainly applies for Solution Manager / SLD 7.00 systems.In case you setup a Solution Manager 7.0 EhP1 system most of the configuration steps arefirst 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 ManagerJ2EE applications (CIM client) must connect to the LOCAL SLD), which are no more relevant.

1. Validate using the Solution Manager (J2EE engine) User Management Engine (UME) that atleast the following UME groups (stored in the ABAP user data store as ABAP roles) exist.

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. Could only be an UME group.)

SAP_SLD_SUPPORT (Must be created. Could only be an UME group.)

2. Associate the required (SLD specific) J2EE Security roles to the UME user groups that youvalidated just beforehand.

This could be done automatically, with a build in function of the J2EE Visual Administrator.

Therefore run the Visual Administrator and navigate to the "SLD Data Supplier service of yourJ2EE engine server node. In this service click on the button (in the top left-hand corner) named:"Assign application roles to user groups".



3. Now, using the User Management Engine (J2EE UME) additionally create the following UMEroles and associate them UME actions, as listed in the following table.

Note that you have two kinds of security roles: UME security roles and J2EE security roles. TheUME roles, which you will have to create manually (hereafter) using the User ManagementEngine (UME), are required for the applications based on Web Dynpro UIs. The J2EE securityroles, which whereas already exist, are used by J2EE applications based on Servlets andJSPs, like the Data Supplier Servlet, or the CIMOM Servlet. The J2EE Security Roles could bevisualized using the J2EE Visual Administrator as follow. Navigate to the Security Providerservice of your J2EE engine server node. In this service navigate to Runtime -> PolicyConfigurations. Select the Component: sap.com/com.sap.lcr*sld and navigate to SecurityRoles. As you will see, the UME security roles that you will now create, will have the samename as the existing J2EE security roles, also they are distinct.

UME role UME Actions Actions Permissions

LcrUser sap.com_com.sap.lcr.LcrUser Read access to SLD data.

LcrSupport sap.com_com.sap.lcr.LcrSupport Read-only access to all SLD data and

UI, including the Administration area

(used for SAP support).

LcrInstanceWriterLD sap.com_com.sap.lcr.LcrInstanceWriterLD Create, modify and delete CIM

instances of the Landscape

Description subset (includes the

LcrUser role).

DataSupplierLD A UME role with no corresponding Create, modify and delete

UME action. CIM instances of the Landscape

Description subset as a data supplier

without access to the SLD UI.

LcrInstanceWriterNR sap.com_com.sap.lcr.LcrInstanceWriterNR Create, modify and delete CIM

instances of the Name Reservation

subset (includes the LcrUser role).

LcrInstanceWriterAll sap.com_com.sap.lcr.LcrInstanceWriterAll Create, modify and delete all types of

CIM instances (includes the LcrUser,

LcrInstanceWriterCR,

LcrInstanceWriterLD, and

LcrInstanceWriterNR roles).

LcrAdministrator sap.com_com.sap.lcr.LcrAdministrator Administrative tasks (includes all other

roles).

Now, associate these UME roles to the following UME groups, as described here after.

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



SAP_SLD_DATA_SUPPLIER DataSupplierLD

SAP_SLD_SUPPORT LcrSupport

4. Validate using the User Management Engine (J2EE UME) that at least the following users exist:

- SAPJSF

- SLDAPIUSER

- SLDDSUSER

5. Create additional SLD users

Therefore logon, as an ABAP Admin user and start transaction: su01

The user that are additionally need could be named:

- SLDCIMUSER

- SLDBRIDGE

6. Finally, associate the SLD users that have been created or checked in the former steps 1 & 2.

Therefore logon to Solution Manager (ABAP), as an ABAP Admin user and start transaction:su01

Now take all users listed in the following table, and for each of them associate it with thefollowing ABAP roles (coming from the R3 data store) or UME groups (coming from the UMEdata store). Note that ABAP roles are visible as groups within the UME.

SLD User on Solution Manager Assigned ABAP roles

SLDAPIUSER SAP_SLD_CONFIGURATOR

SLDCIMUSER SAP_SLD_ORGANIZER



SLD User on Solution Manager Assigned UME group

SLDBRIDGE (or standard SLDDSUSER) SAP_SLD_DATA_SUPPLIER (in case prod SLD is NW 7.00)

SAP_SLD_ORGANIZER (in case prod SLD is NW 6.40)

Additionally, please validate on the "productive SLD, to which Solution Manager will send itsData Supplier information, 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.2 Start the Solution Manager (local) SLD1. Logon to the SLD

Take a user belonging to the UME group: SAP_SLD_ADMINISTRATOR.

2. Goto Administration? Profile



3. Edit only "Section": "datasupplier"

Maintain the SLD's associated Gateway Host and Service, which is in our case the Solution Manager(local) SLD itself.

Note that the Gateway Service default name is: sapgw

4. Start or Stop/Start the SLD



2.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. Such a mechanism is called:SLD Bridge forwarding.

The SLD bridge forwarding is put in place with the following steps:

1. Logon to (one) productive SLD

Take a user belonging to the UME group: SAP_SLD_ADMINISTRATOR.

2. Goto Administration? Data Suppliers



3. Click on Add SLD

4. Provide Solution Manager Hostname and J2EE engine HTTP port (Web Dispatcher).

The user provided here should be the SLDBRIDGE user, which we created and that has the UMEgroup: SAP_SLD_DATA_SUPPLIER on the Solution Manager system. For more information aboutthe SLD specific users and roles please refer to the chapter dealing with users on the SolutionManager system in this document.

These settings will be used by the productive SLD to "replicate" the Technical System data to theSolution Managers (local) SLD

Solution Manager must send its system data to the productive SLD


Troubleshooting

Check the SLD logs of the productive SLD - where you just setup the bridge to the Solution Manager'slocal SLD.

In case you find the following kind of error, please work-through the latter solution.

#57 02/05/2008 15:40:05.50 [Thread-38] WARNING com.sap.lcr.sagent.BuilderDirector: Warning:SLD target system http://nces60121833a.ncel.sap.corp:50000 sld/active not available (incoming datawill be ignored).

Thrown: com.sap.lcr.api.cimclient.CIMClientException: HTTP response code: 403 Forbidden

Solution

The user provided for the SLD bridge forwarding, should be the SLDBRIDGE (or standardSLDDSUSER) user, which you just created beforehand and that has the UME group:SAP_SLD_DATA_SUPPLIER on the Solution Manager system. For more information about the SLDspecific users and roles please refer to the first chapter in this document.

3 Solution Manager must send its system data tothe productive SLD

3.1 Send Solution Manager ABAP system data to theproductive SLD

Use transaction rz70 to send the ABAP system data to the SLD

1. In the section "SLD Bridge: Gateway Information", enter the following data:

a. Host: enter the hostname of the (standalone) gateway used by the Productive SLD.

b. Service: enter the name of the (Productive SLD) gateway service. Note that the defaultname is: sapgw

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, named SAPSLDAPI_ andmaintained in Visual Administrator (on the productive SLD). Indeed, the Productive SLD andthe Solution Manager ABAP Data Supplier must use the same Gateway (the one which is"local" to the Productive SLD).

An example of how to create / configure a JCO RFC Provider could be found in section:"Create JCO RFC provider SAPSLDAPI_SIZ, used by the latter created RFC destination:SAPSLDAPI". IMPORTANT: Do NOT use the values provided in that example to configure yourABAP Data Supplier, as they ONLY apply for setting-up the SMSY fetch infrastructure againstthe Solution Manager (local) SLD.

Productive SLDJ2EE engine

Solution ManagerABAP stack



Note: The "Data Collection Program: _SLD_RFC is deactivated by default.

If you want to create additional information about RFC destinations in the SLD, you can activatethis data collection program. Please do not deactivate other "Data Collection Programs



2. Save these settings by choosing Activate Current Configuration.

3. If you want validate that the System Technical Data (Data Supplier) is correctly sent to theProductive SLD:

Choose "Start Data Collector without Job Scheduling" , which runs the data collector - onlyonce - without scheduling a batch job.

Otherwise Choose Start Data Collection and Job Scheduling.

A separate screen appears with a list of the executed programs and will know whether the initialdata transfer (via RFC) succeeded. For more information, see SAP Note 584654.



Note: This transaction rz70 used to setup the collection of the Solution Manager ABAP technicalsystem data, in order to send it to the productive SLD, will, each time you maintain the settings in thesection "SLD Bridge: Gateway Information" also update:

The "Gateway Options within the TCP/IP RFC destination "SAP_UC (for Unicode productiveSLD).

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/IPConnection) is used by Solution Manager to send its system data to the "correct" productive SLDGateway. Validate both the hostname and service.

ResultYou have now setup the Solution Manager ABAP data supplier to send its technical data directly to aproductive SLD by using an RFC connection. A scheduled batch job updates the data about thesystem in the Productive SLD twice a day (720 minutes 12 hours).

1. You might encounter RFC connection problems

In that case perform a RFC Destination connection test in transaction SM59. The TCP/IP connectionSLD_UC is used by default for a Unicode productive SLD system, and the TCP/IP connectionSLD_NUC for a non-Unicode productive SLD system. These connections are created automaticallyand both should of course point to the same productive SLD. The RFC connection is chosenautomatically by Solution Manager in case you left the "Automatic RFC Destination" selected in rz70within the section "Transport Information".



2. Background jobs

Check the scheduling of SLD background jobs with the names "SAP_SLD_DATA_COLLECT" and"SAP_SLD_DATA_COLLECT_STARTUP", with transaction SM37. They should both be "Released".The first job runs periodically, the second one at each system start. This keeps the system informationin SLD up-to-date automatically

3.2 Send Solution Manager's Java system data to aproductive SLD

Now you will have to also configure the Solution Manager Java "Data Supplier" to send also the JavaTechnical system data to the same productive SLD. This Data supplier service uses an HTTPconnection, which should connect with the default user SLDDSUSER, having the UME group:SAP_SLD_DATA_SUPPLIER on the productive SLD. (For more information about the SLD specificusers 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, please click on:

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. Indeed, incase of planned or unplanned productive SLD(s) downtime, you will otherwise not be able to RootCause Analyze any other SAP product in the customer landscape. Of course, you would like to beable to Root Cause Analyze the productive SLD(s) themselves, using Diagnostics, even if these arenot operational. Additionally note that the Solution Manager (local) SLD must never be promoted to bethe productive (central) SLD, as the above listed restrictions will again apply and you will moreoverencounter SLD release (availability) issues, as soon as the customer landscape contains at least aSAP NW 7.10 product. You could find a discussion about all these subjects - presenting the mainimpacts - within the SLD planning guide.

Therefore the Java Web Dynpro applications (E2E Trace Analysis) must always be CIM clients of theSolution Manager's local SLD. (Solution Manager Java to ABAP stack JCo communication data isstored in the SLD.)



Therefore in the "CIM Client Generation Settings", provide the fully qualified host name of the SolutionManager system, and take the SLDCIMUSER user, which we created beforehand and that has theABAP role: SAP_SLD_ORGANIZER (on the Solution Manager system). For more information aboutthe SLD specific users and roles please refer to the first chapter in this document (2.1 Setup theSolution Manager (local) SLD).

Additionally - until EhP1 - "Grant CIM Client Generation Permissions" to the following ProtectionDomains:

sap.com/com.sap.lcr/lcrcimom.jar

sap.com/tc~lm~webadmin~mainframe~wd/webdynpro/public/lib/sap.com~tc~lm~webadmin~mainframe~wd.jar

sap.com/tc~lm~webadmin~sld~wd/webdynpro/public/lib/sap.com~tc~lm~webadmin~sld~wd.jar



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 thisdocument.

Now, the Solution Manager J2EE engine applications (CIM Client) could connect to this SolutionManager (local) SLD, using the SLDCIMUSER user.

As shown in chapter: 2.3 Connect the productive SLD to the Solution Manager (local) SLD, youshould put in place a "Bridge forwarding", from the productive SLD (that you maintained in the "HTTPSettings"), to this Solution Manager local SLD

Indeed, note that the Diagnostics system setup wizard requires, to be operational at the time you runit, that the Solution Manager (Java) Technical System data has been pushed - via the Productive 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. You mightsimply click on the thunder strike, as shown hereafter, which will update the technical data in theProductive SLD and, via the Bridge forwarding, also into the local SLD.

Keep in mind that the Solution Manager (local) SLD, used by the Solution Manager J2EE engineapplications (CIM Client), will NOT be fed when you click on the thunder strike, if NO "Bridgeforwarding" (from productive to local SLD) has been put in place!

SMSY should fetch the managed systems description from the Solution Manager SLD


5 SMSY should fetch the managed systemsdescription from the Solution Manager SLD

First of all, note that with the "SLD bridge forwarding" from the productive SLD(s) to the SolutionManager local SLD, the Solution Manager SLD will contain a "replication" of all Technical SystemData (complete catalog of installed software components, etc.). See chapter: 2.3 Connect theproductive SLD to the Solution Manager (local) SLD.

Some components, such as XI and the Solution Manager, use the SLD Application ProgrammingInterface for ABAP-based systems (SLD ABAP API) to read data from and write data to the SLD.

Both RFC and HTTP protocols are used for connecting the SLD ABAP API and the SLD. You have toconfigure both the RFC channel from ABAP to Java and the HTTP connection parameters (seetransaction SLDAPICUST). The following figure shows the configuration of the SLD ABAP API indetail:

Note: If the ABAP system is an add-in installation to a J2EE system, the corresponding J2EE Enginecan be used alternatively as an RFC provider. Then only the HTTP communication could be remote,which should NOT be the case in the case of a Solution Manager system.

1. Create JCO RFC provider SAPSLDAPI_SIZ, used by the latter created RFC destination:SAPSLDAPI

This step configures the SLD Java Client itself as well as the Solution Manager local Gateway,so that the ABAP RFC calls will be forwarded to this SLD Java Client. At this point it doesntmean that the Solution Manager (local) SLD will be used.

Run Visual Administrator (on the Solution Manager J2EE side) and navigate to the "JCo RFCProvider service of your J2EE engine server node. In this service navigate to "Runtime ->"Bundles.

Fill-in the fields from the "Registered server section as follow:

a. Program ID: SAPSLDAPI_

b. Gateway host : Fully qualified hostname of your Solution Manager system

c. Gateway service : (by default) sapgw

d. Server count : (by default) 3

Fill-in the fields from the "Repository section as follow:

e. Select "Specific Application Server

f. Application server host : Fully qualified hostname of your Solution Manager system

g. System number :

h. Client number:

In this situation itmust be the SolutionManager local SLD

Setup step 1

Setup step 2

Setup step 3"SMSY fetch"



i. User: SAPJSF

This user is the SAPJSF user maintained in the productive ABAP client, as indicated inthe previous field (h.)

j. Password :

CAUTION: SAPJSF is a standard communication user, whose credentials (password) are, ondouble stack systems, also used by the J2EE User Management Engine (UME). Thereforeplease 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 ABAPbackend).

In case you do not take into account this recommendation, you will encounter a systemstandstill after the next restart!

Maintain here theSolution ManagerHostname

Maintain here theSolution ManagerHostname



2. Use transaction SM59

a. Create the RFC destination "SAPSLDAPI. Eventually, copy the RFC destination named"SLD_UC to create this destination "SAPSLDAPI which should be of type (TCP/IPconnections)



b. In case this RFC destination is created via a copy, you the MUST adapt it by changingnot only the Program ID to SAPSLDAPI_, BUT also reference theSolution Manager Gateway host and service (instead of the productive SLD gateway,which is used by the "SAP_UC" RFC Destination).



3. Use transaction SLDAPICUST

User SLDAPIUSER already exists, by default. It must belong to the ABAP role:SAP_SLD_CONFIGURATOR, to allow the Solution Manager ABAP stack program to send itsrequests to the (local) SLD. Check that the displayed hostname is the fully qualified hostnameof the Solution Manager system.

Note: The SLDAPICUST transaction indeed allows setting-up the HTTP connection to be usedby the SAPSLDAPI_SIZ program (Java SLD Client) to connect to the local SLD.

Check that the SolutionManager Hostnameappears here



4. 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. RFC ping was successful

Result of the above configuration above steps 1 & 2

b. SLD server access settings

Result of the above configuration above step 3


IMPORTANT: When you get a messagelike: "Function call returned exception code4", please double check in transactionSLDAPICUST (on Solution ManagerSystem) the SLDAPIUSER password!

In case of warning regarding the SLDdata content, please refer to the remarkin chapter: 1 Introduction.



Additionally a Web browser window will be displayed.

5. Use transaction SMSY_SETUP to schedule the automatic SLD data fetch


Check that the SolutionManager Hostname appearshere. (Maintain the host/portwith transaction SLDAPICUST.)



Finally, schedule this SMSY fetch operation, 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.

Troubleshooting

Additionally also check whether the just scheduled "SMSY Data Transfer" has already been executedwithout errors, using transaction: slg1

In case you get the following error: "The SLD server connection is inactive", it is most likely related tothe fact that the SLDAPIUSER (on Solution Manager) - used by this "Data Transfer" operation (seeformer step 3) - has not the correct Security roles.



Finally, do not forget to associate, using transaction AISUSER, an S-user to the ABAP user, which willrun this periodic SMSY "Data Transfer" job.

Note that for a SAP internal system you could maintain the System number in SMSY, as follow:

Troubleshooting


6 TroubleshootingIssue 1: Diagnostics system setup wizard fails to perform the task: "(E2E) The JcoRFC destinationsE2E_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, in order togenerate and store (via a J2EE engine CIM Client application) the JCo Destinations:"E2E_SMD_SM_DATA" and "E2E_SMD_SM_METADATA".

Resolution: The issue comes from the fact that the Solution Manager's (local) SLD has no technicalsystem entry yet for the Solution Manager system itself. Indeed E2E Root Cause Analysis requiresJCo Destinations used by the E2E tools to perform "internal" Web Dynpro connections between theSolution Manager Java stack to ABAP stack. These JCo Destinations will be created and associatedto the Solution Manager Java stack description within the local SLD. See the above chapter: 4Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD.

The Solution Manager Java system data required in the local SLD, wil be created / updated via the"Bridge forwarding" as explained in the above chapter.

So when triggering the (Solution Manager Java stack technical) data transfer to the productive SLD,as described in 3.2 Send Solution Manager's Java system data to a productive SLD, you will, via the"SLD bridge forwarding" get also the following kind of entry within the Solution Manager (local) SLD:

Troubleshooting


Then, run again the task: "(E2E) The Jco RFC destinations E2E_SMD_SM_DATA andE2E_SMD_SM_METADATA for WebDynpro will be created in SLD", within the "Diagnostics systemsetup wizard".

Now you will see the JCo Destinations: "E2E_SMD_SM_DATA" and "E2E_SMD_SM_METADATA"stored within the Solution Manager (local) SLD.

Troubleshooting


Issue 2: Failure of the CIM client (access) test, triggered within Visual Administrator, on the "SLDData Supplier" service of your Solution Manager J2EE engine server node under "CIM ClientGeneration Settings".

Within the Solution Manager's J2EE engine "SAP logs" (using NW Admin), you will find an error:"HTTP request processing failed (HTTP error 403)" with user SLDCIMUSER.

Resolution: You should check whether the user SLDCIMUSER, that you created initially, has theABAP role: SAP_SLD_ORGANIZER on the Solution Manager system. For more information about theSLD specific users and roles please refer to the first chapter: 2.1 Setup the Solution Manager (local)SLD.

Troubleshooting


Issue3: The "Collect Configuration Data" task executed by Diagnostics (within "DiagnosticsAdministration" -> "Managed Systems" -> "Scheduler") fails with the following kind of error:

[1835] The Task Collect Configuration Data (nces60128498a) has been processed with warnings.[EXCEPTION] com.sap.sup.admin.scheduler.exception.WarnTaskExecutionException: Thu Feb 07 11:15:33 CET2008 | SLD:Error initializing SLD:nullatcom.sap.sup.admin.scheduler.task.remote.AbstractGatherRemoteTask.checkTaskResult(AbstractGatherRemoteTask.java:52)atcom.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_FilesystemConfiguration(ConfigGatherTask.java:232)[]

at java.lang.Thread.run(Thread.java:534)Caused by: com.sap.sup.admin.ws.proxies.SLDStartExceptionatcom.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.processDocumentFault(MimeHttpBinding.java:921)[]

atcom.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_FilesystemConfiguration(ConfigGatherTask.java:217)... 10 more

Troubleshooting


Resolution: Find out which user is maintained within SAP Solution Manager E2E Root CauseAnalysis, under: "Diagnostics Setup" -> "Diagnostics Systems" -> "Advanced Setup" -> "Wily & NWA"-> "NWA Information"

Indeed, the user maintained at this place is by default a Java administrator user of the SolutionManager System and has therefore the ABAP role: SAP_J2EE_ADMIN (and implicitly the UME/ J2EE security role: LcrAdministrator). For more information about the SLD specific users androles please refer to the first chapter in this document.

Indeed, the "Collect configuration data" task requires a set of J2EE security roles in order to:

1. Create the namespace "sld/smd" in the Solution Manager local SLD.

2. Populate this local SLD namespace with the technical data of the Managed systems that havebeen setup in E2E RCA.

Note that this SLD namespace is used by some E2E RCA tools that are based on the J2EE standardNWAdmin tools.

The following list describes the J2EE security roles required - covered by the ABAP role:SAP_SLD_ADMINISTRATOR to perform this local SLD population (Associated description in thedefaultTrace.?.trc: [SMD_NWA_SLD_PUBLISH] Init the SLD on nwa host: http://.....:5??00):

sap.com/com.sap.lcr*sld#LcrUser

sap.com/com.sap.lcr*sld#LcrSupport

sap.com/com.sap.lcr*sld#LcrInstanceWriterCR

sap.com/com.sap.lcr*sld#LcrInstanceWriterLD

sap.com/com.sap.lcr*sld#LcrInstanceWriterNR

sap.com/com.sap.lcr*sld#LcrAdministrator

sap.com/com.sap.lcr*sld#LcrClassWriter

1 Introduction1.1 Kind of SLD infrastructure setup with this guide

2 First setup the Solution Manager (local) SLD2.1 Setup the Solution Manager (local) SLD2.2 Start the Solution Manager (local) SLD2.3 Connect the productive SLD to the Solution Manager (local) SLD

3 Solution Manager must send its system data to the productive SLD3.1 Send Solution Manager ABAP system data to the productive SLD3.1 Send Solution Manager ABAP system data to the productive SLDResult

3.2 Send Solution Manager's Java system data to a productive SLD

4 Solution Manager J2EE applications (CIM client) must connect to the LOCAL SLD5 SMSY should fetch the managed systems description from the Solution Manager SLD6 Troubleshooting

Documents

Setup Solution Manage Diagnostics Sld