Possible Parameters

Type R

Registers an RFC server program at an SAP gateway and lets it wait for RFC calls by an R/2 or R/3 System.

The following parameters can be used:

In an R/3 System the program-ID and this SAP gateway must be specified in the Destination entry defined with transaction sm59: use connection type T and register mode.

To work with R/2 Systems, the entry in the sideinfo file for the gwhost program must have R instead of E as PROTOCOL parameter.

The host service names of the SAP gateway must be specified in the hosts and services files (<service name> = sapgw<R/3 system number>).

Type B

Connects to an R/3 System using load balancing (as of R/3 3.0).
The application server will be determined at runtime.

The following parameters can be used:

The host name and the service name of the message server must be defined in the ‘hosts’ and ‘service’ files (<service name> = sapms<R/3 system name>).

Type A

Connects to a specific R/3 application server.

The following parameters can be used:

The host name and the service name of the specific application server must be defined in the hosts and services files (<service name> = sapdp<R/3 system number>).

The host name and the service name of the SAP gateway must be defined in the hosts and services files. If GWHOST and GWSERV are not specified, the service name of the SAP gateway must be defined in the services file (<service name> = sapgw<R/3 system number>).

Type 2

Connects to an R/2 System.

The following parameters can be used:

The host name and the service name of the SAP gateway must be defined in the hosts and services files. (<service name> = sapgw<R/3 system number>).

Type E

Connect to another external program as RFC server program.

The host name and the service name of the SAP gateway must be defined in the hosts and services files (<service name> = sapgw<R/3 system number>).

See "Configurations" in Establishing an RFC Connection from an R/3 System for details about how to start an RFC server program by an SAP gateway.