Show TOC

Procedure documentationRFC Client Program and SAProuter Locate this document in the navigation structure

Procedure

Any RFC client program can connect to an SAP System via SAProuter. The feature SAP using SAPGUI is also possible via SAProuter. You must also allow the corresponding SAP dispatcher to work with SAProuters.

One or more SAProuters can be used. The following example shows how the client program can work with two SAProuters.

Example Example

This graphic is explained in the accompanying text.

End of the example.
Route Permission Tables

In the route permission table of SAProuter on host_r1 in Network_1 only one entry is necessary:

P host_11 host_r2 3299

The entries in the route permission table of SAProuter on host_r2 in Network_2 are dependent on the type of RFC connection which is established with the SAP system. The RFC client program must inform the RFC library about all used SAProuters for connecting to the SAP system via the parameter 'host name' in RfcOpen.

1. Using Load Balancing

The host name of the message server must contain the route string. For the example described in the last section, the RFC client must set the host name of the message server as follows: MS-Host: /H/host_r1/H/host_r2/H/host_21.

Entries in the route permission table of SAProuter on host_r2 in Network_2:

P

host_r1

host_21

sapms<SAP name>

P

host_r1

<SAP-AS host 1>

sapgw<SAP system number>

...

P

host_r1

<SAP-AS host n>

sapgw<SAP system number>

2. Specified SAP Application Server and Default SAP Gateway

The host name of the specified application server must contain the route string. For the example described in the last section, the RFC client must set the host name of the application server as follows: AS-Host: /H/host_r1/H/host_r2/H/host_22.

Entries in the route permission table of SAProuter on host_r2 in Network_2:

P

host_r1

host_22

sapgw<SAP system number>

3. Specified SAP Application Server and Specified SAP Gateway

If you are working with a specified SAP gateway, the host name of the SAP gateway must contain the route string. The host name of the application server may not contain the route string. For the example described in the last section, the RFC client must set the host name of the SAP gateway as follows: GW-Host: /H/host_r1/H/host_r2/H/host_22 AS-Host: host_23

Entries in the route permission table of SAProuter on host_r2 in Network_2:

P

host_r1

host_22

sapgw<GW service number>

4. R/2 in an IBM Environment

The host name of the SAP gateway must contain the route string. For the example described in the last section, the RFC client must set the host name of the SAP gateway as follows: GW-Host: /H/host_r1/H/host_r2/H/host_sna host-sna is a machine where a SNA LU6.2-product is running.

Entries in the route permission table of SAProuter on host_r2 in Network_2:

P

host_r1

host_sna

sapgw<GW service number>

5. R/2 in an SNI Environment (BS2000)

The host name of the SAP gateway must contain the route string. For the example described in the last section, the RFC client must set the host name of the SAP gateway as follows: GW-Host: /H/host_r1/H/host_r2/H/host_bs2 host-bs2 is a BS2000 host where the SAP R/2 is running.

Entries in the route permission table of SAProuter on host_r2 in Network_2:

P

host_r1

host_bs2

sapgw<GW service number>