Options for System Landscape Directory (SLD) Scenarios

The duration for which SAP plans to provide mainstream and extended maintenance for core applications of SAP Business Suite 7 software is found in SAP Note 2881788 - End of SAP Business Suite 7 mainstream maintenance. This includes embedded SAP NetWeaver and SAP Business Warehouse components. Additional information is available on the Maintenance Strategy and the SAP NetWeaver 7.5 Maintenance Strategy page of the SAP Community.

The changes include the use of the System Landscape Directory (SLD), which is part of SAP NetWeaver AS Java. The following are affected scenarios involving an SLD.

SLD Scenarios

The System Landscape Directory plays two roles:

Gathering and distributing landscape data from technical systems sent via SLD Data Suppliers required in landscape management.
Providing data – landscape data plus data created in the SLD, e.g., software components or business systems – to its client applications.

SLD with its client applications, being part of landscape data management.

The following scenarios can involve one or more SLD systems or can use them optionally.

Options for the SLD in the Landscape Management Process

The System Landscape Directory (SLD) can act as a target for the SLD Data Suppliers of technical systems providing the data needed for the Landscape Management Process.

Note: The use of the SLD is optional for this scenario; its role can be taken over by other tools and services.

Options to replace the SLD:

Options to replace the SLD in gathering landscape data if you are not using the “direct client applications” of the SLD: System Data Upload to the SAP Support Portal via Landscape Information Services. This allows to handle data from systems in deployment models run by the customer:
- Customer Profile: System data focusing on the software maintenance with the Maintenance Planner and Cloud Integration Automation Service (CIAS).
- System Data: System data focusing on license and installation data.
The landscape handling can be based on solutions described in SAP ‘s Application Lifecycle Management. For details, see section “Landscape Data Strategy” in Get the Status of Your IT Landscape - Data in SLD, LMDB, Its Verification, and SAP for Me.
- SLD DS Payload Distribution: SAP Solution Manager and SAP Focused Run as consumers depend on up-to-date technical landscape data provided by various System Landscape Directory (SLD) data suppliers. This documentation is intended to provide background of features and functions of the different components and versions. It is focusing on the different options of distributing landscape data in different landscape scenarios. This page also lists the System Landscape Data Router (SLDR) allowing to provide data to the FRUN LMDB and all SLD systems still in use. Also see Preparing System Landscape Data Router.

You'll find two “landscape setups” focusing on the latest developments in ALM:

Customers mostly using SAP Cloud ALM (CALM): Technical systems run by the customer are registered and distributed via CALM and Landscape Information Services (LIS).
Customers using SAP Focused Run combined with CALM: Technical systems run by the customer are registered and distributed via SAP Focused Run and CALM and Landscape Information Services (LIS).

For details on the possible strategies, see section Get the Status of Your IT Landscape - Data in SLD, LMDB, Its Verification, and SAP for Me.

Options for SLD Client Application Scenarios

This section lists information regarding scenarios, where the SLD is used by client applications mentioned as "… embedded SAP NetWeaver and SAP Business Warehouse components…" in SAP Note 2881788 - End of SAP Business Suite 7 mainstream maintenance other than those in the landscape management process.

SAP Process Integration and SAP Process Orchestration

For these integration solutions, the SLD is used to provide technical systems' data and to create Business Systems. This scenario will be supported as stated in SAP Note 2881788.

Customers moving to SAP Integration Suite do not require an SLD. For more information, see:

SAP Business Technology Platform (SAP BTP) - SAP Integration Suite
SAP BTP - “Smoothly transition to the cloud from SAP Process Orchestration”
SAP Help Portal - Migration Guide for SAP Process Orchestration

SAP NetWeaver Development Infrastructure (NWDI)

In the NWDI scenario, the SLD is used to create Software Components and to define the development landscape for the teams, as well as for name reservations.

The NWDI – as the SLD – is part of SAP NetWeaver Application Server Java and, therefore, will have the same maintenance duration as stated in SAP Note 2881788.

Web Dynpro Java

This scenario will be supported as stated in SAP Note 2881788. Web Dynpro Java will, therefore, be supported as long as the SLD itself.