Contact Us

Preparing System Landscape Data Router

The System Landscape Data Router (SLDR) is a component enabled on the Simple Diagnostics Agent (SDA), running on the Customer Management Server in the relevant Customer Networks, to route landscape data from a client e.g. RZ70, sapstartsrv, etc. to different destinations e.g. Landscape Management Database (LMDB) , System Landscape Directory (SLD). A SLDR is a central component and acts as data proxy also in a multi-Focused Run Scenario.

Note: In a multi-Focused Run scenario, the SLDR can only be configured from one Focused Run. As a user, you should decide upfront, which Focused Run system is the leading one. A configuration from a different SAP Focused Run system than the leading on is not allowed. Only for the leading SAP Focused Run system, the configuration will be shown in the SLDR configuration dialog. 

Operation Scenarios

The SLDR can be useful in the following scenarios. For a detailed discussion on the different scenarios, please check the page for SLD DS Payload Distribution.

Case A
You plan or you operate several SAP Focused Run.

Case B
You plan or you operate SAP Solution Manager in parallel with SAP Focused Run.

Case C
You plan or you operate SAP Solution Manager in parallel with several SAP Focused Run.

Configuration Procedure

To configure the SLDR start the Agent Administration from the Focused Run Launchpad. The SLDR configuration can be opened from the Agent Action drop down menu.


Configuration Options
 

  • In the SLDR Activation section

This Host is an SLDR: to be check, if the Simple Diagnostic Agent should enable the capability to work as a SLDR.
Active: to toggle, if the SLDR is enabled or disabled. 

 

  • Inbound Connections

It is allowed to configure multiple inbound ports. Just use a free open port number.

Port: Define the desired SLDR HTTP Port number – This is the port that will be opened on the SDA to receive the data from Outside Discovery/SLD payload. It`s possible to use any available port on this parameter.

Secure Communication: Option to select are HTTP or HTTP(S)

Authentication: The method to be used for incoming requests. Supported options:

- Basic Authentication

- Certificate-based Authentication (only works with HTTP(S))

This setting has an impact of the configuration for User/Certificate Name.

User/Certificate Name: Enter the username or the client certificate subject name which will be used in the client configuration e.g. RZ70, to connect to the SLDR.

Password: Define the password for the basic authentication use case, which will be used in the client configuration together with the username as the client credentials. There is no input necessary for the certificate-based approach.

 

  • Outbound Connections

Primary: Indicates that which destination is used propagated the result to the client in case multiple outbound destinations have been configured.

Name: Unique name of the destination. Typically, the system id of the target system is used.

URL: It is the endpoint URL. This can be either the URL to the Focused Run, a SLD or a reverse proxy. It depends on your landscape configuration. Check potential scenarios as described in SLD DS Payload Distribution. Ensure that the endpoint is valid. For any Focused Run endpoint, you are able to test the URL upfront. Check Testing SLDR Configuration > Outbound Test for this.

User: Username from the client credentials which are valid for the endpoint URL. To push the data to an Focused Run system, the username is by default FRN_LDSR_<CID> (where <CID> has to be replaced with the customer id). Refer to the Security Guide, chapter System Landscape Data Router Configuration, for additional details about the authentication.

Password: This must fit to the configured username.

Testing SLDR Configuration

Inbound Test

A connection check against the SLDR is in general possible. If you want to test the configuration, use a command line tool like cURL to do so.

curl 
curl -k -u SLD_DS_FDM 'https://<sldr host>:<inbound port>/sld/ds'


This should result in:

Result 
SLDR got response status 200 from destination <primary outbound SID>: https://<outbound URL>/sld/ds (primary: true).


curl: (18) transfer closed with 161 bytes remaining to read


Note: There is a limitation when checking the connection on an ABAP system. The connection check in transaction SM59 (which is also be used from transaction RZ70) will respond with an “Connection to partner broken.” The reason for this is that the SLDR only allows inbound requests of type HTTP-POST, while the connection check uses HTTP-GET. Any related icm-traces which showing a corresponding error can be ignored.

 

Outbound Test

It is recommended to test the URL for your outbound connections by using a web browser. For a destination to a SAP Focused Run system (also via reverse proxy), you should get the following information:


Remark: The test is only valid for connections to a SAP Focused Run system. The same will not work for testing a connection to a System Landscape Directory (SLD).

 

Result

Once the configuration on the SDA is in place, you can start sending data through the SLDR on the agent.