One or more SAProuters can be used. The following example shows
two different networks with two SAProuters and
how an RFC server program can be started by the currently running SAPGUI and how it communicates with an SAP system running on another network.
Route Permission Tables
Entry in the route permission table of SAProuter on host_r1 in Network_1:
P |
host_11 |
host_r2 |
3299 |
Entry in the route permission table of SAProuter on host_r2 in Network_2: Entry for RFC server program:
P |
host_r1 |
host_21 |
sapdp<SAP service number> |
Entry for SAPGUI:
P |
host_r1 |
host_21 |
sapgw<SAP service number> |
A destination in transaction sm59 can be defined as follows:
Connection type: |
T |
Activate type: |
Start |
Program location: |
Front-end workstation |
Program: |
/rfctest/srfcserv |
The maximum length of the gateway host (transaction sm59) is 100 bytes.
The maximum length of the host name of the application server (transaction sm59) is 100 bytes.
RFC server program and SAPGUI use the same host name of an application server
An application server runs with two network adapters, one for the network with SAP application servers and one for the network with this application server and the frontend workstation with SAPGUI. This application server has two host names in two different networks.
Problem
Starting an RFC server program via SAPGUI is not an available option, because after having been startet, the RFC server program will connect to the application server with the host name only known in the SAP network.
Solution
The RFC server program will use the same host name as the SAPGUI does.
For more information about problems and error handling, see Error Handling.