Skip to Content

<p>The System Landscape Directory of SAP NetWeaver (SLD) serves as a central information repository for your system landscape. A system landscape consists of a number of hardware and software components that depend on each other with regard to installation, software updates, and demands on interfaces. Bear in mind that the abbreviation SLD is not intended to define a product, since the System Landscape Directory is part of SAP NetWeaver. In composite environment, SLD is used in 2 ways, the first way is in XI/PI  and NWDI, the second way is on the portal, SLD is very important for the configuration on SAP NetWeaver, the successful configuration of SLD is critical for the PI, Web Dynpro Java and portal. Specially the Jco connection is based on SLD. When I configure Jco connection and ping, I got the error message, it’s not because of something wrong on Jco connection, mainly because I confused the message server and port, and application host and port, these 2 configurations for WAS and portal are different, when we work on Web Dynpro Java, we used TCP/IP connection from Java enginee to ABAP backend system, in this case we have to get the parameter from transaction code SMGW and SCOT,  when we work on Web Dynpro ABAP, we use HTTP connection, most of the time, the company would configure system with different port, so I created a test Web Dynpro ABAP, the application would automatically generated URL with the host name and port number for me, in this case I just copy them into portal. After configuration, you can test the SLD.</p><p>In  this tutorial I’m going to show you how to configure the SLD in WAS. Logon http://<host>:<port>/sld as administrator</p><p>Technical Systems:

SLD is the central information repository for your system landscape. It contains information about technical systems, landscapes, business systems, products, and software components in your system landscape. You can view and manage this information in the SLD.


      New Technical System-> Web AS ABAP->Next


General: SAP gui logon offer the information about the Database host. Logon to the target ABAP sytem, menu System->Status, you can get the installation number and related information about the product and software component for this system.


Central Servers:  In transaction code SMGW or SCOT you can find the message server port value, it’s for the TCP/IP connection, the default instance number normally is 00


Application Servers:  is the server host name, If you want to define additional application servers, choose Add Application Server, enter the host name and instance number, and choose Next.


Clients: Enter all the client from your system, and choose Next.


Installed Products: all the products and software component can be got from the menu System->status, so different company has different configuration on this part.  On the left, select installed software products of your ABAP system by selecting the Installed indicator, On the right, all software components that are part of the selected software products appear.   Choose finish.

Web AS Java:+   New Technical System+->AS Java->



If the Web AS Java technical system is part of a dual-stack system, from the Web AS ABAP dropdownbox, select the Web AS ABAP technical system for the Web AS Java. If the Web AS Java technical system is a standalone J2EE system, select None (Standalone J2EE).  Dual-stack which means ABAP system and Java system are installed on the same server and engine, standalone means ABAP and Java system are installed on the different servers, so different company has different choices. Enter system details and choose Next.


+Instances : If you want to define new instances, choose Add New Instance and enter instance details.   If you want to define new server nodes, choose Add New Server Node and enter server node details. If you want to define new ports, choose Add New Port and enter port details.  Whether you want to add new instance or not, based on size of the company, if it’s a big company who has a lot of users, and a lot of servers, it’s better to add other instance, Choose Next.</p><p>image</p><p>Ports<em>: </em>Logon http://<host>:<port> as administrator, click system information and check the port has been used , then choose the port hasn’t been used and fill in the port, choose next.</p><p>!|height=200|alt=image|width=415|src=|border=0!</p><p>Installed Products:+ On the left, select installed software products by selecting the Installed indicator.  Next</p><p>!|height=183|alt=image|width=351|src=|border=0!</p><p>Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can have no relationship with SAP product. But if you want to set up the connection from SAP to that system, you need the logon to that system. They can also be installed as an operating system service or as a domain, here you only need to enter the domain name. </p><p><u>Third-Party</u>: New Technical System->Third-party-> Next</p><p>!|height=205|alt=image|width=351|src=|border=0!</p><p>General: +The system name and host name of Third-party technical systems contain third-party software components and products, for example peoplesoft, Oracle etc. The Third-party product is not a SAP product, but is sap partner, sap product recognize their product and their software, so you have to add the related software which SAP recognized at the end.


A landscape represents a logical, complex system, which consists of multiple, distributed components. Some of these components may be systems; others may be services, installed products, or other managed elements.

The following types of landscapes are defined in the SLD:

Administration: A system landscape, which is created for administration purposes, for example, for common monitoring.

General: A system landscape, which can contain all types of application systems.

NWDI Systems: A system landscape that contains servers of the NWDI. The NWDI consists of a local client – the Integrated Development Environment (IDE) and some logical servers for processes like source management, build tasks, transport, and name reservation. All servers work together and require a common user base together with the IDE.

Scenario: A system landscape that is created for a specific business scenario. Scenario landscapes are used in the Software Lifecycle Manager of SAP NetWeaver.

Transport: A system landscape that is created for transport purposes. For example, all SAP Web AS systems that are connected by an ABAP transport path distributing the ABAP development.

Web Service:A system landscape that is created to collect systems offering Web services and their clients. The hierarchy of these landscapes defines the Web service that is most appropriate for a given client.

Business systems:

Business systems are logical systems, which function as senders or receivers within PI. Business systems can be SAP systems or third-party systems.

Depending on the associated technical system, the following types of business systems are defined in the SLD:

Web AS ABAP: A business system, which is associated with a Web AS ABAP, can play the role either of an application system or an integration server. An integration server is the central component of PI, which provides a framework for the exchange of information among various internal and external entities of a company. The integration server facilitates the interaction between the different operating systems and applications across internal and external networks.

Web AS Java: A business system, which is associated with a Web AS Java.

Standalone: A business system, which is associated with a standalone Java application.

Third-party: A business system, which is associated with a third-party technical system.

Software Catalog:

The SLD contains a Software Catalog of all installable SAP products and software components. The Software Catalog includes information about support packages and dependencies between the products and software components. This information is the basis for the description of the system landscape.

In addition, third-party products and software components can be implemented in a system landscape. Third-party products can be standalone applications or additional modules for SAP applications. In the SLD, you have to create third-party products and software components manually.

If you want to implement E-SOA on PI or develop JAVA work on NWDI, then you have to create related product and software component also, because the work you had developed is not standard SAP product. this software component will be imported later on in design time repository of NWDI and Enterprise service builder of PI.

Creating new Products

Choose Home -> Products->new ->create a new Product and Version->next:



If  you want to create a third-party product, enter the required information about the third-party product. Enter the vendor as a URL. Choose Create, enter the same name for unit, choose next.

Instances for the Product and Product Version CIM classes, as well as the association instances are created.

On the following screen, optionally, enter a name for a software unit for the third-party product.  Choose Create.  Instances for the Software Unit CIM class are created.

Creating Software Components

Choose Home ->Software components->New->create a new software and Version->next:


Select the product which you just Created, enter the name version, change production State to started then click finish. If you want to create Web Dynpro Java, you have to choose the software component dependency specially for web dynpro java , this part would be covered in my blog about web dynpro java.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    After working several days/weeks on a particular concept, you gain a good understanding and insight
    into that, then you normally write this kind of notes for future purposes.

    Thanks for sharing your good notes with us.

    Prasad Nutalapati

  2. Former Member
    Instead of defining ABAP and Java systems manually, you might want to use RZ70 from an ABAP system and Visual Administrator from an AS Java system. By using these you make sure you get correct details of the technical pieces, such as clients etc.
  3. Jens Schwendemann

    You shouldn’t maintain types of AS ABAP or AS Java manually. Links are dead (probably because of SDN – SCN conversion) but also main goal / structure seems to be sparse


Leave a Reply