Creating RFC Destinations on AS ABAP and AS Java

Procedure

You need to create the following RFC destinations with both transaction SM59 (AS ABAP) and the SAP NetWeaver Administrator (AS Java):

  • AI_RUNTIME_JCOSERVER

    Points from the Integration Server to the mapping runtime. The program ID corresponds to the entry configured for the destination on AS Java (used for the mapping runtime, value mapping, and the exchange profile).

  • AI_VALIDATION_JCOSERVER

    Points from the Integration Server to the XML validation service. The program ID corresponds to the entry configured for the destination on AS Java (used for XML validation).

  • LCRSAPRFC

    The RFC destination LCRSAPRFC is required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.

  • SAPSLDAPI

    The RFC destination SAPSLDAPI is required for the connection to the SLD. It is used by the ABAP API.

Depending on your client settings, it may be necessary to log on to your Integration Server host as SAP system user with the authorization to maintain customizing tables and to release transport orders.

NOTE

User SAP* or DDIC does not have these authorizations.

Maintain the RFC Connections (ABAP)

Perform the following steps:

  1. Log on to your Integration Server host.

  2. Call transaction SM59.

  3. Choose Create.

  4. Enter at least the following:

    • RFC destination: AI_RUNTIME_JCOSERVER

    • Connection type: T

    • Description: <your description>

  5. Choose ENTER.

  6. Choose the Technical settings tab and do the following:

    1. Select Registered Server Program.

    2. In the Program ID field, enter: AI_RUNTIME_<SID>

      <SID> is the SAP system ID of your Integration Server host.

      CAUTION

      Use uppercase letters only.

    3. Select the gateway defaults.

    4. Enter Gateway host and Gateway service of your Integration Server host.

      To find out the required parameters:

      1. On the Integration Server host, call transaction SMGW.

      2. Choose   Goto   Parameters   Display   (check the entries for gateway hostname and gateway service).

    5. Choose the MDMP & Unicode tab and select the Unicodeflag in the Communication Type with Target System box.

  7. Save your settings.

  8. Repeat steps 3 to 8 for the remaining destinations:

    • AI_VALIDATION_JCOSERVER

      Program ID: AI_VALIDATION_<SID>, where <SID> is the SAP system ID of your Integration Server host.

    • LCRSAPRFC

      Program ID: LCRSAPRFC_<SID>, where <SID> is the SAP system ID of your Integration Server host.

    • SAPSLDAPI

      Program ID: SAPSLDAPI_<SID>, where <SID> is the SAP system ID of your Integration Server host.

  9. Leave transaction SM59 open to perform further tests later.

Configure the Destinations (Java)

Perform the following steps:

  1. On your Integration Server host, start the SAP NetWeaver Administrator.

  2. Choose   Configuration Management   Infrastructure   JCo RFC Provider  .

  3. Choose Create and enter exactly the same program ID and gateway options for AI_RUNTIME_JCOSERVER that you used in the step Maintain the RFC Connections (ABAP)above. Additionally, set the server count to 10 and choose Next.

  4. In the Repository Configuration section, do the following and choose Next:

    1. Deselect the Use RFC Destination flag.

    2. Enter the parameters for the Integration Server host: Application Server Host, System Number, Client, and Language.

    3. For User and Password maintain the login parameters for the user SAPJSF.

  5. Do not select anything in the Security Settings and Additional Options sections and choose Next.

  6. Choose Finish.

  7. Repeat steps 3 to 6 for the remaining destinations:

    • AI_VALIDATION_JCOSERVER

      Corresponding values from transaction SM59

      Server Count 10:

    • LCRSAPRFC

      Corresponding values from transaction SM59

      Server Count 3:

    • SAPSLDAPI

      Corresponding values from transaction SM59

      Server Count 10:

Test the RFC Destinations

After you have maintained all RFC destinations in both the ABAP and Java environments, you can check all the connections above as follows:

  1. Call transaction SM59 again.

  2. Open your RFC destination.

  3. Choose Connection Test.

    No errors should be displayed.

SAP Developer Network SAP Weblogs: SAP Process Integration (PI)