Start of Content Area

Procedure documentation Creating an RFC Destination for the SLD ABAP API on the J2EE Side  Locate the document in its SAP Library structure

Use

If you want to configure an ABAP application to access data in the SLD using the SLD ABAP API, you have to create an RFC destination on the J2EE Engine that hosts the SLD. If the ABAP system is an add-in installation to a J2EE system, you can configure the RFC destination on the J2EE Engine, but we do not recommend it.

Procedure

in ...

       1.      In the Visual Administrator, choose Cluster ® Server ® Services ® JCo RFC Provider ® Runtime ® Bundles.

       2.      Enter the RFC destination parameters in the following fields:

Field

Description

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

If your J2EE Engine 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.

Note

If your J2EE Engine is a standalone installation, we recommend that you install a gateway on the same host.

If you cannot install a gateway on the same host, you can use the gateway of the calling ABAP system (the one that you are connecting to the SLD).

Number of processes(1..20)

Enter 3.

       3.      Enter the repository parameters in the following fields:

Field

Description

Application server host

System number

Enter the connection data for the ABAP system.

Client

Language

User

Password

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

Note

If your J2EE Engine is an add-on installation to an ABAP system, use the logon data for this system.

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

       4.      If the calling ABAP system is a Unicode system, select the Unicode indicator.

Note

If you want to connect several ABAP systems, of which some are Unicode and others are non-Unicode, you have to create two separate destinations that correspond to the two system types; for a Unicode system, select the Unicode indicator, and for a non-Unicode system, deselect the Unicode indicator.

       5.      Create the RFC destination by choosing Set.

 

 

End of Content Area