Preparing System Landscape Data Router

How you can contact us:

Technical Assistance

Request product support from SAP
Non-Technical Assistance

Request non-product support or provide feedback on SAP Support Portal site

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 the data from the Outside Discovery and the System Landscape Directory (SLD) payload through the SDA.

The SLDR can be useful in the following scenarios:

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.

For a detailed discussion on the different scenarios, please check the page for SLD DS Payload Distribution.

Note: The SLDR relevant configuration is stored in the file: /usr/sap/hostctrl/SMDAgent/default/configuration/t-connector/<Managing SID>/custom.properties

Remind that the Simple Diagnostics Agent (SDA) is remotely deployed onto a SAP Host Agent, only if the host Outside Discovery was executed successfully.

See the Preparing Outside Discovery page.

To configure the SLDR start the Infrastructure Administration / Agent Administration, within the Launchpad:

Search and select the SLDR host
In drop down Agent Action, choose the value Open SLDR Configuration
Press Go
In the displayed SLDR Configuration pop-up provide:
- In the SLDR Activation section
  Select This Host is an SLDR
  Select Active
- It is possible to define multiple inbound ports at the SLDR. In the inbound connections section press Add and specify how to access the SLDR
  - “HTTP + Basic Authentication”
    - 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 port on this parameter, just ensure that this port is not in use in the SDA server.
    - Select “HTTP” for secure communication
    - Select “Basic Authentication”
    - Provide the SLDR User name: FRN_SLDS_<CID> (also known as SLD_DS_<CID>) and enter a Password. This user is created on the SLDR once you completed the wizard
  - “HTTPS + Basic Authentication”
    - 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 port on this parameter, just ensure that this port is not in use in the SDA server.
    - Select “HTTPS” for secure communication
    - Select “Basic Authentication”
    - Provide the SLDR User name: FRN_SLDS_<CID> (also known as SLD_DS_<CID>) and enter a Password. This user is created on the SLDR once you completed the wizard
  - “HTTPS + Certificate Based Authentication"
    - 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 port on this parameter, just ensure that this port is not in use in the SDA server.
    - Select “HTTPS” for secure communication
    - Select “Certificate-Based Authentication”
    - Provide the complete certificate subject name as SLDR User name. No password is required
- In the outbound connections section
  Press Add and specify how to access the SAP Focused Run system :

Case A:

- <SID> of one or Multiple SAP Focused Run systems.
- HTTP <URL> of relevant reverse proxy or load balancer of one or Multiple SAP Focused Run systems.
The URL should be provided in this format:
http(s)://<frun_or_sld_url>:<http_port>/sld/ds

- <USER> created during the Customer Network preparation: FRN_LDSR_<CID>.

Case B:

- <SID>
of an SAP Focused Run system OR the <SID>.
of SAP Solution Manager Central Classical SLD.
- <URL>
of relevant reverse proxy / load balancer of the SAP Focused Run system.
of SAP Solution Manager Central Classical SLD.
- <USER>
created during the Customer Network preparation: FRN_LDSR_<CID>.
of SAP Solution Manager Central Classical SLD.

Case C:

- <SID>
of one or Multiple SAP Focused Run systems.
of SAP Solution Manager Central Classical SLD.
of the Second SLDR
- HTTP <URL>
of relevant reverse proxy / load balancer of the SAP Focused Run system.
of SAP Solution Manager Central Classical SLD.
- <USER>
created during the Customer Network preparation: FRN_LDSR_<CID>.
of SAP Solution Manager Central Classical SLD.
of the second SLDR: FRN_SLDS_<CID>.

Select the primary SAP Focused Run if several SAP Focused Run systems are declared. This setting ensures that the return of the SAP Focused Run will be propagated to the data supplier.

Note: It is recommended to test the URL for your primary outbound connection e.g. the SAP Focused Run URL you have entered, by using a web browser. As a result, you should get the following information:

If you want to test the inbound connection as well, use a command line tool like cURL to do so.

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

This should result in:

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

Result

Once the configuration on the SDA is in place, you can start sending data through the SLDR on the agent, the command below should run in all servers, where the data needs to go through the SLDR:

On SAP Host Agent folder /usr/sap/hostctrl/exe/ (UNIX) or C:\Program Files\SAP\hostctrl\exe\ (Windows), run this command:

./saphostctrl -function ConfigureOutsideDiscovery -enable -sldusername FRN_SLDS_<CID> -sldpassword <Password> -sldhost <HOST_OF_SDA_CONFIGURED_AS_SLDR> -sldport <PORT_CONFIGURED_AS_INBOUND>

More details on Preparing Outside Discovery page.

Refer to the Security Guide, chapter System Landscape Data Router Configuration, for additional details about the authentication.