Configuring HTTP and RFC Connections

Local RFC Connections

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

...

       1.      Specify the following parameters:

0       hostname: localhost

0       gwservice: 'sapgw$$'

0       instno: '$$'

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

RFC and HTTP Destinations on the Integration Server

ABAP Stack

...

       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:

0     LCRSAPRFC

0     SAPSLDAPI

Java Stack

...

       1.      Start the Visual Administrator.

       2.      Choose Cluster ® Server ® Services ® JCo RFC Provider.

       3.      Choose the RFC destination AI_RUNTIME_JCOSERVER.

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

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

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

0     LCRSAPRFC

0     SAPSLDAPI

       7.      Choose Cluster ® Server ® Services ® Destinations.

       8.      Choose 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.