SLD Problem Analysis Scenario

System Landscape DirectoryProblem Analysis Scenarios

SAP NetW eaver 7 .10

System Landscape Directory 08.02.2008

Problem Analysis Scenarios 2

Copyright

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.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, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPCare trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registeredtrademarks of Adobe Systems Incorporated 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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 fortechnology 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 andservices mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of their respective companies.Data contained in this document serves informational purposes only. National productspecifications may vary.

These materials are subject to change without notice. These materials are provided by SAPAG and its affiliated companies ("SAP Group") for informational purposes only, withoutrepresentation or warranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP Group products andservices are those that are set forth in the express warranty statements accompanying suchproducts and services, if any. Nothing herein should be construed as constituting anadditional warranty.



Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types ofinformation at a glance. For more information, see Help on Help General InformationClasses and Information Classes for Business Information Warehouse on the first page of anyversion of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include fieldnames, screen titles, pushbuttons labels, menu names, menu paths,and menu options.

Cross-references to other documentation.Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names,program names, transaction codes, table names, and key concepts of aprogramming language when they are surrounded by body text, forexample, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and theirpaths, messages, names of variables and parameters, source text, andnames of installation, upgrade and database tools.

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

<Example text> Variable user entry. Angle brackets indicate that you replace thesewords and characters with appropriate entries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



System Landscape Directory Problem Analysis Scenarios.....................................................5

Access To SLD From ABAP Fails ......................................................................................5



System Landscape Directory Problem AnalysisScenariosThe following problem analysis scenarios are available for the System Landscape Directory(SLD):

Access To SLD From ABAP Fails [page 5]

For more information about SLD, see the User Manual – Configuring, Workingwith and Administering System Landscape Directory (in SAP NetWeaver 7.1) athttp://www.sdn.sap.com/irj/sdn/nw-sld.

Access To SLD From ABAP FailsTransaction SLDCHECK reports errorsA disrupted communication between an ABAP system and the System Landscape Directory(SLD) may result in various errors in ABAP applications using the SLD via the SLD ABAPAPI, for example SAP NetWeaver Process Integration or the SAP Solution Manager. Theconnectivity status can be specifically tested by executing transaction SLDCHECK.

The access to SLD from ABAP is discontinued if SLDCHECK displays red error messages inits output list. Typical situations are:

RFC ping failed.

The first call to function module LCR_LIST_BUSINESS_SYSTEMS terminated withsome exception.

The SLDCHECK section Access to the XI Profile is not covered withinthis PAS.

ScopeComponent: WAS, J2EE, SLD

Validity: J2EE: 7.10 on Windows and Unix platforms

WAS: 7.10

Used tools: SLDCHECK, SM59, SLDAPICUST, UME, SAP NetWeaverAdministrator

AnalysisThe figures on the following pages give you an overview of the analysis process. Thenumbers in parentheses refer to subsequent sections with detailed information. Start with theexecution of transaction SLDCHECK.

http://www.sdn.sap.com/irj/sdn/nw-sld.







(1) Check status of SLD server and, if required, start the SLD server...

1. Log on to http://<host>:<port>/sld Administration (the user needs anLcrAdministrator assigned, you can also use the J2EE administrator user).

2. Check the status of the server. If the server has the status SLD Stopped, choose StartSLD.

(2) Check and, if required, maintain RFC destination SAPSLDAPI via transaction SM59...

1. Within transaction SM59 TCP/IP Connections, make sure the RFC destination ismaintained. If not, create an RFC destination.



E X A M P L E

2. After creating and maintaining the RFC destination, choose Connection Test.

(3) Unicode consistence check...

1. Within transaction SM59 TCP/IP Connections MDMP & Unicode, make sure theUnicode settings of the RFC destination are consistent.

2. If the calling system is a Unicode system (see System Status SAP system dataarea), select the Unicode radio button on the MDMP & Unicode tab page.

If the calling system is a Non-Unicode system, refer to a Non-Unicode destinationprogram ID as Registered Server Program within SM59 (see (2)).



E X A M P L E

(4) Check parameters maintained in transaction SLDAPICUST...

1. Within transaction SLDAPICUST, make sure the connection parameters are maintainedcorrectly.

2. Select the lines to be checked and choose Test.

3. If host name, port, user, and password are correctly maintained, select the Primarycheckbox and re-enter the valid password.

E X A M P L E



(5) SLD interactive logon check

Log on to http://<host>:<port>/sld using the user and password maintained intransaction SLDAPICUST.

(6) Check the user maintained in the SLDAPICUST parameters within the UserManagement Engine (UME) of the J2EE engine that hosts the SLD.

Within transaction UME, check the validity of the user and password maintained inSLDAPICUST.

Does this user exist?

Is its password valid?

Is this user unlocked?

Check the validity period of this user.

Make sure the role LcrInstanceWriterLD is assigned to this user.

To start the UME, log on to http://<host>:<port>/useradmin UserManagement.

(7) Analysis in Jco RFC Provider of the SLD host J2EE Engine: Server Configuration...

1. Start the SAP NetWeaver Administrator and choose Configuration ManagementInfrastrucuture Jco RFC Provider.

E X A M P L E

2. Make sure that the relevant RFC destination is running.

3. Verify if the program ID is maintained correctly.

Be aware that the program ID is case-sensitive and must be identical to theprogram ID specified in transaction SM59.

4. On the Server Configuration tab page, make sure that the gateway parameters are setconsistently with the parameters maintained in transaction SM59.



(8) Analysis in Jco RFC Provider of the SLD host J2EE Engine: RepositoryConfiguration...

1. Start the SAP NetWeaver Administrator and choose Configuration ManagementInfrastrucuture Jco RFC Provider.

E X A M P L E

2. On the Repository Configuration tab page, check the validity of the repository logondata and verify the users’ authorization.

3. Make sure that the Unicode setting within the Repository settings is consistent with theRepository system.

If the RFC destination program ID is pointing to a Non-Unicode RFC destination intransaction SM59, deselect the Unicode checkbox within the Repository settings andadjust the Repository logon data to a Non-Unicode repository system.

Additional InformationFor more information about the SLD, see http://sdn.sap.com/irj/sdn/nw-sld.

For more information about configuring the SLD connectivity, see

Post-Installation Guide – SAP System Landscape Directory athttp://sdn.sap.com/irj/sdn/nw-sld

Installation Guides – SAP NetWeaver Process Integration 7.1 athttp://service.sap.com/installNWPI71

http://sdn.sap.com/irj/sdn/nw-sld.

http://sdn.sap.com/irj/sdn/nw-sld

http://service.sap.com/installNWPI71

Documents

SLD Problem Analysis Scenario