Using SLD API for AS ABAP Based Systems 

Use

Some components, such as SAP NetWeaver PI and the SAP Solution Manager, use the SLD Application Programming Interface for ABAP-based systems (SLD ABAP API) to read data from and write data to the SLD.

The SLD ABAP API is delivered in the SLD_API package of the AS ABAP system release 6.20 and higher. 

If you run applications that read data from and write data to the SLD and the connection between the SLD ABAP API and the SLD is not configured, you have to do it manually.   

For more information about configuring the connection to an ABAP system, which is part of the SAP NetWeaver PI, see Connecting to the System Landscape Directory.

Both RFC and HTTP protocols are used for connecting the SLD ABAP API and the SLD. You have to configure both the RFC channel from ABAP to Java and the HTTP connection parameters. The following figure shows the configuration of the SLD ABAP API in detail:

We recommend that you use the same AS Java and a local gateway for the whole infrastructure.

As of SAP NetWeaver 7.1, usage type AS Java that comprises SLD also contains an SAP Gateway.

In this case, only the RFC communication is remote. If you are running a system with both usage types  - AS ABAP and AS Java, the corresponding AS Java can be used alternatively as an RFC provider. Then only the HTTP communication is remote.

Procedure

Creating an RFC Destination

More information: Creating an RFC Destination for the SLD ABAP API on the Java EE Side

More information: Creating an RFC Destination for the SLD ABAP API on the ABAP Side

Creating an HTTP Destination

More information: Creating an HTTP Destination for the SLD ABAP API on the ABAP Side