Connecting managed systems to SLD

After configuring the local Solution Manager SLD and before reading the SLD data for Solution Manager System Landscape (transaction SMSY) you have to think about how to get data into the Solution Manager SLD. 

Depending on the customers system landscape you have different opportunities on how to setup your SLD landscape. 

You can use the SLD of SAP Solution Manager as the central SLD for your landscape or you can use another SLD as the central SLD and just feed the SLD of Solution Manager with its data.
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 this 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 way is to have only one SLD for your landscape. 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. To support this, there is a "Planning Guide for SLD" available

To make a system report its data to the SLD you have to perform some basic configuration on the ABAP and on the Java system. If your system is a dual stack system you have to make the configuration on both stacks, the ABAP stack and the Java stack as well.

ABAP

To send system information of an ABAP system you have to maintain the transaction RZ70.

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 Solution Manager. You can check which gateway ports are available in the file etc/services on your operating system.
3. Then you have to 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 on the button "Data Collection and Job scheduling". Click on the button with the match to activate the current SLD configuration.

SAP J2EE

To connect a java system to the SLD you have to maintain the SLD data supplier in the Visual Administrator.

1. Open 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
   • In the Host field, enter the name of the host where the corresponding SLD runs.
   • In the Port field, specify the HTTP standard access port of the SLD. Usually it is the port 5<instance number>00.
   • In the User field, specify the J2EE user SLDDSUSER which was created automatically in the SLD configuration step. This user must be assigned to the DataSupplierLD security role.
   • In the Password field, 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 on top of the page to test your settings and to trigger the data transfer.

Setup SLD Bridging

If you decided to forward the data from another SLD to the SLD of Solution Manager, then you have to setup a bridge forwarding from the other SLD to Solution Manager. The bridge forwarding provokes that every 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. 
To add the Solution Manager SLD to the central SLD enter the SLD from which you want to send data to Solution Manager. Choose administration --> data suppliers and click on the button „Add SLD". Enter the appropriate input values:
In the URL filed enter http://<solmanhost>:<solmanport>. The port is usually the port 5<instanzce number>00. 
In the user field enter the SLDDSUSER. 
In the password field 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.