Implementing Technical Systems in the SLD

Objectives

After completing this lesson, you will be able to:
  • Implement technical systems in the System Landscape Directory (SLD)
  • Maintain the SAP NetWeaver Application Server for Java in the SLD
  • Create Third-Party Technical Systems in the SLD

System Types

In addition to information about products and software components, you can also enter technical and business systems in the SLD. There are various types of technical systems. The type of technical system determines the attributes you must enter. From the SLD initial screen, follow the Technical Systems link to access the definition of the technical systems. The system navigates to a screen where you can select a system type. The system then displays a list of technical systems for the selected system type.

SAP NetWeaver Application Server (AS) for ABAP SLD Registration

A prerequisite for registering systems as technical systems in the SLD is that you activate the data supplier bridge in the SLD. When you configure the data supplier bridge, specify the Remote Function Call (RFC) gateway on which you register.

Data Supplier for SAP Systems (ABAP)

You must activate a data supplier in the back-end system. In ABAP-based SAP systems, you can configure and start this data supplier by calling transaction RZ70. The selection of data collection programs allows you to control which data is collected and transferred. An RFC destination SLD_UC or SLD_NUC is automatically created for transfers. The data collected is transferred by the RFC connection through the gateway to the data supplier bridge and is then imported into the SLD.

Configuring of the Data Supplier (ABAP) – Transaction RZ70

The figure, Configuring of the Data Supplier (ABAP) – Transaction RZ70, illustrates the required settings in transaction RZ70 for configuring a data supplier.

Hint

With SAP ERP 6.04 and later, transaction RZ70 also collects information about the product version of the system.

How to Register an SAP ABAP System to the SLD

DemoStart Demo

In this demonstration, explain transaction RZ70, but do not execute it. The registration was done already.

Steps

  1. Log on to the SLD, http://nwktdc00.wdf.sap.corp:50000/sld, with your BIT500-00 user ID and password.

  2. Go to Administration → Details.

  3. Go to the Data Supplier tab and show the Gateway Host and the Gateway Port.

  4. Using the SAP Logon, log on to ZME client 800 with your BIT500-00 user ID and password

  5. Explain that this is a system that we will use as back end for some of the exercises and needs to be registered in our NWK SLD.

  6. Call transaction RZ70.

  7. Explain that the Gateway Host set to nwktdc00 and Gateway Service set to sapgw00 has to match the ones in the Administration of the SLD. Explain that there is a Background job that has been configured to check every 720 minutes for new updates. The SLD needs to be informed of such updates as a new support package or a new client.

  8. The system has been already registered. Do not execute the Data Collection. Just explain the transaction.

  9. Explain that a destination called SLD_UC is used to connect to the SLD.

  10. Show the Technical System in the SLD.

SAP NetWeaver Application Server (AS) for Java SLD Registration

The Java component SLD data supplier is deployed and started for the data suppliers for SAP NetWeaver AS for Java Systems server (formerly known as the SAP Java 2 Platform, Enterprise Edition SAP J2EE engine). The necessary parameters are passed to this Java service using the SAP NetWeaver Administrator (NWA) tool.

Refreshing the data of the Java server (such as host, installed software components, and so on) is done each time the machine restarts, and the data is imported into the SLD using the data supplier bridge.

To Register a Java Server in the SLD

Perform the following steps to register a Java server in the SLD:

Steps

  1. Log on to the Java server with NWA system (http://<server>.<domain>:<port>/nwa).

  2. Choose Configuration → Infrastructure → Destinations.

  3. Choose SLD DATA Supplier Service and maintain the following data on the HTTP Settings tab page:

    1. Set the appropriate URL to http://host:port.

    2. Set the authentication to basic.

    3. Set the appropriate user name and password.

      Note

      The specified user must have the user role SAP_SLD_DATA_SUPPLIER or higher on the target SLD Server.

    4. Save the data.

  4. In the menu, choose Go To → Configuration → Infrastructure → SLD Data Supplier Configuration.

  5. Choose the Collect and Send Data pushbutton.

Result

A successful data transfer message displays and you see the system in SLD.

How to Maintain SLD HTTP Settings in the SAP NetWeaver Application

DemoStart Demo

Steps

  1. Maintain SLD HTTP Settings in the SAP NetWeaver Application

    1. Log on to the SAP NetWeaver Application with your BIT500-## user credentials. http://nwktdc00.wdf.sap.corp:50000/nwa

    2. Navigate to Configuration → Infrastructure → SLD Data Supplier Configuration. This is used to define how the AS Java registers in the SLD and provides access to SLD for other JAVA Applications.

    3. Explain that an initial configuration of the data supplier for AS Java-based systems is automatically performed by the SAP installation tool during the AS Java system installation. However, if you want to change the default settings, or if you have installed the AS Java in a different way, you can use the SAP NetWeaver Administrator to configure the data supplier manually.

    4. Show the Collect and Send data button used to collect and send data to the SLD Server.

    5. Navigate to Configuration → Infrastructure → Destinations.

    6. Show the SLD_DataSupplier destination.

    7. Explain that each AS Java system has a built-in mechanism for reporting data to the central SLD that you can configure using this destination. In addition, other applications that run on the AS Java system can find out where the central SLD is located and use this information to connect.

    8. Also show the SLD_Client destination. The SLD service provides every Java application with the option to generate an SLD client for accessing an SLD server.

      Note

      Do NOT change anything, just talk about the configuration.

Example of a Technical System Landscape

The figure, Technical System Landscape of the Example Scenario, shows the system landscape for the Create Technical Systems in the SLD exercise.

The system landscape consists of two third-party type application systems and client 800 of the SAP Process Integration system, which is configured as the Integration Server. The system exchanges data using SAP Process Integration. Therefore, the network connections and communication channels are configured at the same time as the system landscape.

Create Technical Systems in the SLD

Business Scenario

Mapping the server landscape provides a basis for integrating two systems in a system landscape.

Create two technical systems TS_BIT500_##_A and TS_BIT500_##_B, both of the Third-Party type, in the SLD.

Caution

Note that the system names are case-sensitive and must be entered as they appear in the exercise.

Exercise Information

Note

In this exercise, when the values include ##, replace the character with a two-digit number (01–30).

Exercise Options

You can perform this exercise in two ways:

  1. Live Environment: choose Start Exercise, and from the entry page choose Open PDF Document. Follow the steps described in this pdf in your own system landscape.
  2. Simulation: choose Start Exercise, and from the entry page choose Start Tutorial. Watch the step-by-step instructions within the simulation.

Note

We recommend running the simulation first.
ExerciseStart Exercise

Task 1: Create Two Technical Systems

Steps

  1. Open the SLD. Log on with your user ID and password. Then navigate to Landscape → Technical Systems.

    1. Open -for example- the Internet Explorer Browser and enter the URL http://nwktdc00.wdf.sap.corp:50000/dir and choose System Landscape Directory.

    2. If required, log on with your BIT500-## credentials.

    3. Navigate to Landscape → Technical Systems.

  2. Create two new third party Technical Systems as shown in the table.

    TypeSystem NameHost NameProduct InstalledSoftware Components Installed
    Third-PartyTS_BIT500_##_Abit500host##aP_BIT500_##SC_BIT500_##_A
    Third-PartyTS_BIT500_##_Bbit500host##bP_BIT500_##SC_BIT500_##_B

    1. Choose the New Technical System button.

    2. Select the Third-Party radio button.

    3. Choose Next.

    4. In the System Name field, enter TS_BIT500_##_A. In the Host Name field, enter bit500host##a.

    5. In the filter row, enter P_BIT500_## to find your product. Then select the Installed checkbox.

    6. Choose the software component according to the table and select the Installed checkbox.

    7. Choose Finish.

    8. Repeat steps a to g and create a second technical system called TS_BIT500_##_B.

  3. Review your newly created Technical Systems.

    1. In the Technical Systems Type field, select Third Party.

    2. Choose each of your Technical Systems.

    3. Review each of the tabs. Make sure that the Installed Software is correct.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn