Preparing the System Landscape Directory (SLD) Use The SAP NetWeaver Development Infrastructure (NWDI) uses the

System Landscape Directory (SLD) as the central information provider for system landscape data (for example, location of the CMS server). If there is not already an existing SLD server in the system landscape, an SLD server must be installed before you can use the NWDI. Although the technical entity of an SLD server is installed with every Application Server (AS) Java installation, it has to be activated explicitly on the appropriate Web Application Server which carries out the SLD functionalities in the system landscape.

This section only describes the necessary setup steps of an SLD server and clients used by the NWDI. For comprehensive information about postinstallation steps of an SLD server, read the Post-Installation Guide of SLD. (service.sap.com/sld Media Library SLD) Procedure Perform the following steps to manually configure the SLD, which is automatically performed as a configuration step. 1. Activate the SLD Server ... 1. 2. 3. Open the SLD Web UI under the URL http://<server>:<port>/sld. Open the initial page of the SLD Web UI and log on as an administrator. On the initial page, choose Administration and in the section Server Profile.

The system displays the Parameters screen. 4. ChooseSection Server Settings.

5. Enter a reserved SAP NetWeaver namespace in the input field Object Server. Keep the preset working directory in the input field Working Directory. Select the values for persistency and write protection. Save your entries.

If you only use the NWDI for testing or demo purposes, you can enter central host name (or the SID) of the AS Java as the name for the object server. More information about namespace reservation: SAP Note 710315. 6. Choose Administration and then Start Server.

The SLD server starts and in the status line, Running appears.

After the first activation of the SLD server, it is started automatically with every startup of the AS Java.

2. Import the SAP Master Component Information ... 1. On the SLD initial page, choose Administration and in the section Content Import.

2. Choose Import CR Content (this switch appears only before the content import has been executed once. By default, this is a step during installation). The SLD server starts the import of the SAP Master Component Information. This process can take some time.

For the productive use of NWDI, you must also import the current updates of the SAP Master Component Information. More information: SAP Note 669669. 3. Configure the SLD Data Supplier Bridge By default, this step is executed during installation. On ... 1. 2. On the SLD initial page, choose Administration and in the section Server Data Suppliers. On the page Configure data supplier targets, set the parameter sld/active to true.

4. Setup of the Data Suppliers (Java) The data suppliers are client-side components residing in each SAP system that are able to report actual system information of the relevant systems to the SLD server.

To fulfill the purpose of the SLD, you have to setup data suppliers for all SAP systems (this includes ABAP and Java) in the system landscape. This section only covers the configuration of the data supplier of a Java system. To activate a Java Data Supplier (executed by default during installation): ... 1. 2. Start the Visual Adminstrator and log on as an administrator. Navigate to the SLD Data Supplier settings for an HTTP connection. a. b. 3. Choose Cluster Server Services SLD Data Supplier. On the Runtime tab page, select HTTP Settings.

Specify the connection and logon data for the SLD server of your system landscape if required and save your entries.

For security reasons, do not use any user accounts that own more permissions than DataSupplierLD for the Java data supplier. Use the J2EE role DataSupplierLD to set up a dedicated user.

4.

Immediately after saving the settings, you can trigger a data transfer to your SLD server for test purposes by choosing the button

After a few seconds, the relevant Java system appears in the SLD. 5. You can check this by choosing Landscape Technical Systems and then the Technical System Type Web AS Java on the SLD initial page. 5. Register the SLD Server in the SLD The Java system that provides the SLD functionality reports itself as an SAP system using its Java Data Supplier. In order to declare this SAP system as the SLD server for the entire system landscape, it must be registered as such in the SLD. Follow the procedure below: ... 1. 2. 3. On the initial screen of the SLD, choose Landscape Landscapes. In the Landscapes Browser choose Landscape Type NWDI Systems. Choose New Landscape.

A wizard appears. 4. 5. In the Create New Landscape wizard, enter a name for the NWDI system and choose Create. Create an SLD. a. In the Landscapes Browser, select the new NWDI system.

A detail view of the selected system appears. b. A wizard appears. c. d. e. 6. Select the Hosted System Type System Landscape Directory. Choose New Hosted System (due to self-registration, the SLD may already exist). Specify the following parameters: On the Systems tab page, choose Add System to Landscape.

Hosted System Type: System Landscape Directory

Web AS Java: The <SID>of this system.

Roles: Landscape Server and, if you do not run a separate SLD system for the name reservation, Name Server.

CIM Server URL: http://<server>:<port>/sld/cimom.

Object Server: The name of the object server of this SLD server.

Description. Choose Create.

Access To SLD From ABAP Fails Problem Description Transaction SLDCHECK reports errors. A disrupted communication between an ABAP system and the System Landscape Directory (SLD) may result in various errors in the Exchange Infrastructure or in the Solution Manager. The connectivity status can be specifically tested by executing transaction SLDCHECK. The access to SLD from ABAP is discontinued if SLDCHECK displays red error messages in its output list. Typical situations are: RFC ping failed The first call to function module LCR_LIST_BUSINESS_SYSTEMS terminated with some exception

Note that the SLDCHECK section Access to the XI Profile is not covered within this PAS. Scenario Type: NetWeaver Component: Error analysis Web AS Java J2EE Engine SLD J2EE Engine >= 6.30 on Windows and Unix platforms Web AS >=6.40 SP4 Decision Roadmap Prerequisites Main Tools SLDCHECK SM59 Visual Administrator

Validity:

Analysis The figures on the following pages give you an overview of the analysis process. The numbers in brackets refer to subsequent sections with detailed information. Start with the execution of transaction SLDCHECK.

(1) Check status of SLD server and, if required, start the SLD server From the SLD main page http://<host>:<port>/sld navigate to Administration (the user needs an LcrAdministrator assigned, you can also use the J2EE administrator user).

Check the status of the server and start the server if the server has the status stopped.

(2) Check and, if required, maintain RFC destination SAPSLDAPI via transaction SM59 Within transaction SM59 TCP/IP Connections, check whether the RFC destination is maintained and, if the destination is not maintained, create the RFC destination.

After the maintenance of the RFC destination, perform a connection test by using the Test connection button. (3) Unicode consistence check Within transaction SM59 TCP/IP connections Special Options, check whether the Unicode settings of the RFC destination are consistent. If the calling system is an Unicode system (see System Status SAP system data area), set the Unicode flag in the Special Options area; if it is a Non-Unicode system refer to a Non-Unicode destination program ID as Registered Server Program within SM59 (see (2)).

(4) Check parameters maintained in transaction SLDAPICUST Within transaction SLDAPICUST, check whether the connection parameters are maintained correctly. If the correct user, password, host name and port are maintained and the primary flag is set to a valid parameter set, re-enter the valid password.

(5) SLD interactive logon check Try to log on to http://<host>:<port>/sld using the user and password maintained in transaction SLDAPICUST. (6) Check the user maintained in the SLDAPICUST parameters within transaction SU01 Within transaction SU01 check the validity of the user and password maintained in SLDAPICUST.

Does this user exist? Is its password valid? Is this user unlocked? Check the validity period of this user. Check if the role SAP_XI_APPL_SERV_USER is assigned to this user.

(7) Analysis in JCO Provider of the SLD host J2EE Engine: Destination part Start the J2EE Visual Administrator and navigate to <SYS-ID> Server<node> Services JCo RFC Provider.

Check whether the JCo RFC Provider Service is running and whether the relevant RFC destination is also running. you may need to start the service itself as well as the RFC destination. Furthermore, verify if the program ID is maintained correctly. The program ID has to be maintained case-sensitive and identical to the program ID specified in transaction SM59. Additionally, check whether the gateway parameters are set consistently with the parameters maintained in transaction SM59. (8) Analysis in JCO Provider of the SLD host J2EE Engine: Repository settings Start the J2EE Visual Administrator and navigate to <SYS-ID> Server<node> Services JCo RFC Provider.

Check the validity of the Repository logon data and verify the users authorization. Check whether the Unicode flag within the Repository settings is consistent with the Repository system. If the RFC destination program ID is pointing to a Non-Unicode RFC destination in transaction SM59, unset the Unicode flag within the Repository settings and adjust the Repository logon data to a Non-Unicode repository system. Additional Information http://service.sap.com/sld