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 post-installation 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.      Open the SLD Web UI under the URL http://<server>:<port>/sld.

       2.      Open the initial page of the SLD Web UI and log on as an administrator.

       3.      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.      On the SLD initial page, choose Administration and in the section Server ® Data Suppliers.

       2.      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.      Start the Visual Adminstrator and log on as an administrator.

       2.      Navigate to the SLD Data Supplier settings for an HTTP connection.

                            a.      Choose Cluster ® Server ®Services ® SLD Data Supplier.

                            b.      On the Runtime tab page, select HTTP Settings.

       3.      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.      On the initial screen of the SLD, choose Landscape ® Landscapes.

       2.      In the Landscapes Browser choose Landscape Type NWDI Systems.

       3.      Choose New Landscape.

A wizard appears.

       4.      In the Create New Landscape wizard, enter a name for the NWDI system and choose Create.

       5.      Create an SLD.

                            a.      In the Landscapes Browser, select the new NWDI system.

A detail view of the selected system appears.

                            b.      On the Systems tab page, choose Add System to Landscape.

A wizard appears.

                            c.      Select the Hosted System Type  ® System Landscape Directory.

                            d.      Choose New Hosted System (due to self-registration, the SLD may already exist).

                            e.      Specify the following parameters:

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

       6.      Choose Create.