Show TOC

Procedure documentationConfiguring HTTP and RFC Connections Locate this document in the navigation structure

Procedure

Local RFC Connections

For local RFC connections between AS ABAP and AS Java (that is, for RFC connections within the same instance), the variable $$ is used for local addressing.

  1. Specify the following parameters:

    • hostname: localhost

    • gwservice: 'sapgw$$'

    • instno: '$$'

    At runtime, rfcengine substitutes '$$' with the local instance number.

RFC and HTTP Destinations on the Integration Server
AS ABAP

  1. Call transaction SM59.

  2. Choose the HTTP destination INTEGRATION_DIRECTORY_HMI.

  3. Set the HTTP connect data to <virtual host>:<httpport>.

  4. Choose the RFC destination AI_RUNTIME_JCOSERVER.

  5. Delete the gateway settings.

  6. Repeat step 5 for the following RFC destinations:

    • LCRSAPRFC

    • SAPSLDAPI

AS Java

  1. Start the SAP NetWeaver Administrator.

  2. Choose   Configuration Management   Infrastructure Management   Jco RFC Destinations  .

  3. Select the RFC destination AI_RUNTIME_JCOSERVER.

  4. Change the gateway connection data to localhost, sapgw$$.

  5. Change the repository connection data to localhost, $$.

  6. Repeat steps 4 and 5 for the following RFC destinations:

    • LCRSAPRFC

    • SAPSLDAPI

  7. Choose   Configuration Management   Security Management   Destinations  .

  8. Select the HTTP destination pmistore.

  9. Set the HTTP connect data to <virtual host>:<httpport>.

External RFC and HTTP Destinations

RFC and HTTP destinations to the Integration Server should address the load balanced components Message Server and Web Dispatcher.