Program Start by SAPGUI (SAP Library

Program Start by SAPGUI

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 R/3 System running on another network.

Route Permission Tables

Entry in the route permission table of SAProuter on host_r1 in Network_1:

host_11

host_r2

3299

Entry in the route permission table of SAProuter on host_r2 in Network_2:
– Entry for RFC server program

host_r1

host_21

sapdp<R/3 service number>

– Entry for SAPGUI

host_r1

host_21

sapgw<R/3 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:

32 bytes for R/3 Release <= 3.0C

64 bytes for R/3 Release 3.0D

100 bytes for R/3 Release >= 3.0E.

The maximum length of the host name of the application server (transaction sm59) is:

64 bytes for R/3 Release <= 3.0D

100 bytes for R/3 Release >= 3.0E.

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 R/3 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 R/3 network.

Solution

The RFC server program will use the same host name as the SAPGUI does. This functionality is available with R/3 Release 3.0D onwards and SAPGUI 3.0D onwards.

For more information about problems and error handling, see Error Handling.