18.11.

2020 Connect Managed Systems to SLD - SAP Solution Manager Setup - Community Wiki

Dashboard / … / Prerequisites

Connect Managed Systems to SLD

Created by Michael Kloeffer on Aug 13, 2014

Note: For detailed information, see System Landscape Directory (SLD), especially the Planning Guide - System
Landscape Directory.
After configuring a central SLD (and/or the local SAP Solution Manager SLD) and before synchronizing SLD data with
SAP Solution Manager (in 7.0: TA SMSY, in 7.1: TA LMDB), you have to think about how to get data into the SLD.
Depending on the customers system landscape, you have different opportunities on how to setup your SLD landscape:
You can use a remote SLD as central SLD and feed the SAP Solution Manager with its data (optionally via the
local SAP Solution Manager SLD), or
You can use the local SLD of SAP Solution Manager as central SLD for your landscape.
For some applications, like SAP Netweaver PI, the SLD is essential for running. During SLD downtime, no data updates
for J2EE components within your landscape are available from your SLD. To ensure that the maintenance of SAP
Solution Manager does not interfere with productive operations, we strongly recommend that you do not use the local
SLD in SAP Solution Manager as central runtime SLD if you are using SAP NetWeaver PI or WebDynpro Java
applications in your system landscape.
If you are not using SAP NetWeaver PI or WebDynpro Java applications and also do not plan to do so in the near future,
you can use the SLD running on the SAP Solution Manager system as central SLD, as no runtime dependencies to this
SLD exist.
The simplest and most reliable way is to have only one SLD for your landscape.
Data on different SLDs must not overlap, it must be strictly separated to avoid conflicts.
The cost of running an SLD infrastructure increases with the number of SLD instances, as several SLDs have to be
administrated (for example, CR Content has to be updated regularly).
Depending on your requirements, you also have to think about synchronization of SLD data stored in different SLDs: The
SLD bridge can automatically forward data received by data suppliers to additional SLDs. But data that was entered
manually into one SLD (such as PI business systems, name reservation data, products/software components, etc.) has to
be synchronized manually with export/import functions of SLD.
Altogether, it depends on the actual requirements of a landscape like what data is required in which SLD or how often is a
manual synchronization required, to decide about the optimal SLD landscape.
For details, see the Planning Guide - System Landscape Directory at System Landscape Directory (SLD.
To make a system report its data to the SLD, you have to set up the data suppliers on the AS ABAP and on the AS Java
system. For dual-stack systems, make the configuration on both stacks, the ABAP stack and the Java stack as well.

AS ABAP
To send system information of an ABAP system, proceed as follows:
1. Start transaction RZ70.
2. Enter the hostname and the gateway service of the host running the SLD. The gateway service is sapgw followed
by the instance number where the SAP system gateway port is running. Usually, it is the central instance of SAP
Solution Manager. You can check which gateway ports are available in the file etc/services on your operating
system.
3. Then schedule a job to make sure that the data in the SLD is regularly updated; the job runs twice a day. To
schedule the job, click Data Collection and Job scheduling button. Click the button with the match to activate the
current SLD configuration

https://wiki.scn.sap.com/wiki/display/SMSETUP/Connect+Managed+Systems+to+SLD 1/3
18.11.2020 Connect Managed Systems to SLD - SAP Solution Manager Setup - Community Wiki

SAP J2EE
To connect an AS Java system to the SLD, proceed as follows:
1. Start the Visual Administrator. Under /usr/sap/<SID>/<Instance>/j2ee/admin, start the go.bat or on UNIX the
go.sh) with the user sid<adm>.
2. Connect with the default connection.
3. Choose Cluster -> Server -> Services -> SLD Data Supplier -> Runtime -> HTTP Settings.
4. Enter the required data.
Under Host, enter the name of the host where the corresponding SLD runs.
Under Port , specify the HTTP standard access port of the SLD, which usually is 5<instance number>00.
Under User, specify the J2EE user SLDDSUSER, which was created automatically in the SLD configuration
step. This user must be assigned to the DataSupplierLD security role.
Under Password, enter the users password. To make sure that you know the password, you should not let it
be generated during the setup but rather provide the password during setup.
5. Use the blue flash icon on top of the page to test your settings and to trigger the data transfer

https://wiki.scn.sap.com/wiki/display/SMSETUP/Connect+Managed+Systems+to+SLD 2/3
18.11.2020 Connect Managed Systems to SLD - SAP Solution Manager Setup - Community Wiki

Setup SLD Bridging

If you decided to forward the data from another SLD to the SLD of SAP Solution Manager, setup a bridge forwarding from
the other SLD to the SAP Solution Manager SLD. Then, each time a system updates its data in the SLD this data is
automatically forwarded to all other SLDs that are maintained in the central SLD as bridge forwarding partners.
1. To add the SAP Solution Manager SLD to the central SLD, enter the SLD from which you want to send data to
SAP Solution Manager.
2. Choose administration -> data suppliers and click the Add SLD button.
3. Enter the appropriate input values:
Under URL, enter http://<solmanhost>:<solmanport>. The port is usually 5<instanzce number>00.
Under User, enter the SLDDSUSER.
Under Password, enter the password of the SLDDSUSER. As mentioned before, it is recommended to
provide the password during the setup to prevent the generation of a password nobody knows afterwards.
For details, see the Planning Guide - System Landscape Directory at System Landscape Directory (SLD.

No labels

Privacy Terms of Use Legal Disclosure Copyright

Trademark Cookie Preferences

https://wiki.scn.sap.com/wiki/display/SMSETUP/Connect+Managed+Systems+to+SLD 3/3