Creating
an RFC Destination for the SLD ABAP API on the AS Java Side
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.
More information:
SAP Java
Connector
in ...
1. In your web browser enter the URL of SAP NetWeaver Administrator using the following pattern:
http://<host>:<port>/nwa
2. Choose Configuration Management → Infrastructure → Jco RFC Provider.
3. Choose Create.
4. Enter the connection and transport parameters as required.

Field |
Description |
Program ID |
We recommend that you use the following pattern: SLDAPI_<SAPSID>, where SAPSID is the system identifier of the AS Java system. |
Gateway host Gateway service |
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.
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. |
Server Count (1..20) |
Enter 3. |
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
Field |
Description |
Application Server Host System Number Client Language User Password |
Enter the logon data for the AS ABAP system. You must specify an existing user with appropriate authorizations for RFC.
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. |
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.