Show TOC

Procedure documentationCreating an RFC Destination for the SLD ABAP API on the Java Side Locate this document in the navigation structure


If you want to configure an ABAP application to access data in the SLD using the SLD ABAP API, you have to create a Jco RFC destination on the AS Java system that hosts the SLD. For more information, see SAP Java Connector.


  1. In your web browser, enter the URL of SAP NetWeaver Administrator using the following pattern:


  2. Choose   Configuration Management   Infrastructure   Jco RFC Provider  

  3. Choose Create.

  4. Enter the connection and transport parameters as required.

    Note Note



    Program ID

    We recommend that you use the following pattern: SLDAPI_<SID>, where SID is the system identifier of the J2EE Engine.

    Gateway host

    Gateway service

    Note Note

    If your AS Java is an add-on installation to an ABAP system, use the gateway of the ABAP system. You can look up the gateway parameters of an ABAP system using transaction SMGW.

    End of the note.

    Note Note

    If your AS Java is a standalone installation, we recommend using a gateway on the Central Services Instance host. As of SAP NetWeaver 7.1, usage type AS Java that comprises SLD also contains an SAP RFC Gateway.

    End of the note.

    Server Count (1..20)

    Enter 3.

    End of the note.
  5. Choose Next.

  6. Enter logon data to the ABAP repository. You can either use an existing RFC destination from   SAP NetWeaver Administrator   Configuration Management   Security   Destinations   or you specify the ABAP repository explicitly. The destination should point preferably to an AS ABAP close to SLD. If SLD is running on an AS Java standalone installation, the calling AS ABAP can be used instead. We recommend to create and use an RFC destination instead of explicitly specifying the connect parameters here. In both cases, the following parameters are required




    Server Host

    System Number





    Enter the logon data for the AS ABAP system. You must specify an existing user with appropriate authorizations for RFC.

    Note Note

    If you are running a system with both usage types AS ABAP and AS Java, use the logon data for this system.

    If your AS Java is a standalone installation, use the logon data for the calling ABAP system.

    End of the note.
  7. Choose Next.

  8. Leave the default values in the next steps.

  9. Create the Jco RFC destination by choosing Finish.


The Jco RFC destination creates a number of “Server Count” RFC server threads on your AS Java. These RFC servers register at the RFC Gateway specified. You may configure multiple ABAP systems to connect to these RFC servers. In this case, the Server Count should be increased when TIME_OUT exceptions are observed.