Show TOC

Using SLD API for AS ABAP-Based SystemsLocate this document in the navigation structure

Context

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.

To connect the SLD ABAP API with SLD, we recommend that you use an HTTP protocol. The following figure shows the configuration of the SLD ABAP API using an HTTP protocol in detail:

You can also use both RFC and HTTP protocols for connecting the SLD ABAP API and the SLD. For this purpose, you need 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 using both RFC and HTTP protocols in detail:

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

Note

As of SAP NetWeaver 7.1, usage type AS Java that comprises SLD also contains an 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


  1. Create an HTTP Destination for the SLD ABAP API.

    For more information, see Creating an HTTP Destination for the SLD ABAP API on the ABAP Side .

  2. Create an RFC Destination for the SLD ABAP API.

    For more information, see Creating an RFC Destination for the SLD ABAP API on the Java EE Side and Creating an RFC Destination for the SLD ABAP API on the ABAP Side .