Tasks in the System Landscape Directory
Use
The SAP System Landscape Directory (SLD) is the central information provider in a system landscape.
The SLD contains two types of information:
● Component Information: This is information about all available SAP products and components, including their versions. If there are any third-party products in the system landscape, they are also registered here
At design time of the integration objects, the component information is extracted from the SLD to define process integration scenarios.
More
information:
Enterprise Services
Repository
● Landscape Description: This contains all installed systems in a system landscape
When a collaborative business process is configured in the Integration Directory, the landscape descriptions are needed to determine the system information of the business partners involved.
The runtime environment of Process Integration sends the address of the Integration Server of a business system to the SLD.
Business systems are logical systems that communicate with each other by sending and receiving messages. They can be SAP or third-party systems.
○ An SAP system has one or more clients that function independently of each other as logical units at runtime. Each of these clients represents a business system in Process Integration.
○ A third-party system is also a logical unit that functions as a sender or receiver. Therefore, third-party systems are also business systems in this sense.
We recommend that you use one SLD.
If you have more than one SLD instance, you must ensure that all content is synchronized. The SLD has export and import functions for this purpose.
More information:
●
Updating the Software
Catalog
● SAP Note 764393.
More information:
System
Landscape Directory
Procedure
Configure Business Systems in the SLD
First, define and configure all business systems involved in the process in the SLD.
More information: Configuring Business Systems in the SLD
Only once you have done so can you define the business systems as communication components in the Integration Directory and address them as the senders and receivers of messages in later configuration steps.
Configure Groups and Transport Targets in the SLD
An Integration Server enables communication between business systems at runtime. It cannot execute business logic.
You can assign a group of business systems to an Integration Server. A business system group is a logical grouping of business systems that use an Integration Server to communicate with each other.
More information: Configuring Groups and Transport Targets in the SLD
Tasks for Changes in SLD
After you have made any changes in the SLD, always ensure that you clear the cache for SLD data in the Integration Directory. Only once you have done so can you access up-to-date SLD content (for example, by using input help).
More information:
Delete the
Cache for SLD Data
Example of Changes in the SLD
Change in the SLD |
Effect in Integration Directory |
Create/delete a business system |
The input help for business systems (for example, when you define a business system component) is only updated once you clear the SLD cache. |
Delete an Adapter Engine |
The input help for Adapter Engines in the communication channel is only updated once you clear the SLD cache. |
In the following cases, ensuring that a change made in the SLD has also taken effect in the Integration Directory requires manual effort.
Changes in SLD and Additional Activities in the Integration Directory
Change in the SLD |
Effect in Integration Directory |
Change a business system (registered as an SAP or Non-SAP) system More information:
|
For this change to take effect in the relevant business system service, you must compare the data with the SLD. More information: Business System (Communication Component) |
Change a business system (adapter-specific identifiers, for example, the logical system) |
For this change to take effect in the relevant business system service, you must compare the data with the SLD. More information: Communication Component |