Creating Destinations on the ABAP Server

Use

On AS ABAP, you need to create the following RFC destinations:

  1. JCo RFC Providers

  2. INTEGRATION_DIRECTORY_HMI used for the cache update

  3. SAPXICACHE<sy-client> used for the ABAP cache update

  4. SAPXIPP<client> used for principal propagation

Procedure

1. Create the JCo RFC Providers

Create the following JCo RFC providers on the ABAP Server. Each JCo RFC provider points from the ABAB Server to the Java Server.

JCo RFC Provider

Description

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

Required for the connection to the System Landscape Directory (SLD). It is used to read the exchange profile.

SAPSLDAPI

Required for the connection to the SLD. It is used by the ABAP API.

To create the JCo RFC Providers, 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.

    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 Start of the navigation pathGoto Next navigation step Parameters Next navigation step DisplayEnd of the navigation path(check the entries for gateway hostname and gateway service ).

    5. Choose the MDMP & Unicode tab and select the Unicode flag 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.

2. Create INTEGRATION_DIRECTORY_HMI

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: INTEGRATION_DIRECTORY_HMI

    • Connection Type: H

    • Description: <your description>

  5. Choose Enter .

  6. Choose the following tabs and enter the required data:

    • Technical Settings

      • Target Host: host name of AS Java

      • Service No.: HTTP port number

        The following naming convention applies: 5<AS_Java_instance_number>00 50000 , if your AS Java instance is 00)

      • Path Prefix: /dir/CacheRefresh

    • Logon & Security

      • Select Basic Authentication , confirm the dialog box, and ignore the warning.

      • Enter the client of your Integration Server and the user PIIS<SID> with a valid password. The following roles need to be assignet to the he user PIIS<SID>upon its creation:

        • SAP_XI_IS_SERV_USER_MAIN

        • SAP_XI_IS_SERV_USER
        • SAP_SLD_CONFIGURATOR
        For more information, see: Standard Users (Dual-Stack).

    • The user PIIS<SID> must be created with following roles accordingly

    • Special Options

      • Timeout : 30000

      • HTTP Settings : HTTP Version : HTTP 1.0, Compression : inactive , Compressed Response : No

      • HTTP Cookies : Accept Cookies : Yes (All)

    • Save your settings.

3. Create SAPXICACHE<sy-client>

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: SAPXICACHE<sy-client>

    • Connection Type: 3 (Connection to ABAP System)

  5. Choose Enter .

  6. Choose the Logon & Security tab and enter the following logon data:

    • The client of your Integration Server

    • The user PICACHEUSER with the password.

  7. Save your settings.

4. Create SAPXIPP<client>

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: SAPXIPP<client>

      Specify the client of your Integration Server.

    • Connection Type: 3

  5. Choose Enter .

  6. Choose the Logon & Security tab and enter the following logon data:

    • The client of your Integration Server

    • The user PIPPUSER with the password.

  7. Save your settings.

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 ConnectionTest .

    No errors should be displayed. The test has been executed successfully if the response status code is 500 and you find REQID not found in the response body.