Preparing System Landscape Data Router

1 - Determine amount of required SLDR

The System Landscape Data Router (SLDR) is a component enabled on the SDA, running on the Customer Management Server in the relevant Customer Networks.

What is your situation, in regards to the managed systems being now prepared in the context of Focused Run?

  • A - You plan or you operate several FRUN.
  • B - You plan or you operate SAP Solution Manager in parallel with Focused Run.
  • C - You plan or you operate SAP Solution Manager in parallel with several Focused Run.

 

Depending on your situation:

-If none of the above use cases applies: No SLDR is required.

You can skip this chapter, as the Data Suppliers, of the managed objects (including Outside Discovery), can be directly connected to LMDB through reverse proxy of the Focused Run System.

-If case A applies: One SLDR is required (per relevant customer network).

This means you plan to share managed systems among multiple Focused Run systems, but you do not need to forward Data Supplier payloads to SAP Solution Manager, SAP NetWeaver PI or other components. This SLDR is used to forward the Data Supplier payloads (including Outside Discovery) to the reverse proxies or load balancers of the relevant Focused Run systems.

Note: SLDR shall be discovered first by Focused Run following the Preparing Outside Discovery page, and then, configured following the below Configure SLDR Section.

-If case B applies: One SLDR is required (per relevant customer network).

This means you plan to share managed systems and corresponding payloads among one Focused Run system, and, in parallel, you plan to forward Data Supplier payloads to SAP Solution Manager AP, SAP NetWeaver PI or other components. This SLDR is used to forward the Data Supplier payloads (excluding Discovery) to the reverse proxies or load balancers of the relevant Focused Run systems and SAP Solution Manager. Focused Run Outside Discovery Payload Shall not be send to the SAP Solution Manager SLD, therefore it must be send directly to Focused Run (LMDB).

Note: SLDR shall be discovered first by Focused Run following the Preparing Outside Discovery page, and then, configured following the below Configure SLDR Section.

 

-If case C applies: Two SLDRs are required (per relevant customer network). This is a combination of case A and B. 

This means you plan to share managed systems and corresponding payloads among multiple Focused Run systems, and, in parallel, you plan to forward Data Supplier payloads to SAP Solution Manager AP, SAP NetWeaver PI or other components. Focused Run Outside Discovery Payload Shall not be send to the SAP Solution Manager SLD, therefore it must be send directly to Focused Run (LMDB).

Note: SLDR shall be discovered first by Focused Run following the Preparing Outside Discovery page, and then, configured following the below Configure SLDR Section.

2 - Configure SLDR

The System Landscape Data Router (SLDR) is a component enabled on the SDA, running on the Customer Management Server in the relevant Customer Networks.

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 were 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
    • In the Inbound Connection section
      Define the desired SLDR HTTP Port number
      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.
    • In the Outbound Connections section
      Press Add and specify how to access the Focused Run system :

Case A above applies:

-The <SID> of one or Multiple Focused Run systems.
-The HTTP <URL> of relevant reverse proxy or load balancer of one or Multiple Focused Run systems.
-The <USER> created during the Customer Network preparation: FRN_LDSR_<CID>.

Case B above applies:

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

Case C above applies:

-The <SID>
  of one or Multiple FRUN Systems.
  of SAP Solution Manager Central Classical SLD.
  of the Second SLDR
-The HTTP <URL>
  of relevant reverse proxy / load balancer of the FRUN system.
  of SAP Solution Manager Central Classical SLD.
-The <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 Focused RUN if several Focused Run are declared.

Note: It is recommended to test the specified Inbound and Outbound URLs, using a Web Browser (if possible). Refer to the Security Guide, chapter System Landscape Data Router Configuration, for additional details about the authentication.