Configuration Parameters

Use

The following parameters define basic settings for the SAP gateway – startup behavior, execution type of remote programs, tracing, and so on.

Features

gw/startup

File containing statements to start programs when the gateway starts. This is useful if CPIC/RFC server programs are always to run. When the gateway is restarted, these programs are thus started as well.

Default value

-

Dynamic

No

File syntax:

Local start of a program
local program [parameter ...]

Remote start of a program (using Remote Shell, or value of parameter gw/remsh)
hostname program [parameter ...]

";*!" can be used as comment characters. The individual parameters in the file must be separated by tabs.

 Example of a file

; Syntax : local program [parameter...] or

;          hostname program [parameter ...]

;

; Under Windows the options ( starting with '-' )

; or strings containing a '/' must be placed in

; in quotation marks, for example

; hw1439 "/priv/cpict2" "-tp" cpict2 "-gwhost" p29290 "-gwserv" sapgw53

;

; start program locally ( registers using ID cpicsrc on gateway

; running locally and responds to service sapgw53 )

local /usr/sap/BIN/SYS/exe/run/cpicserver -tp cpicsrv -gwhost uw1033 -gwserv sapgw53

; start program remotely

hw1439 /usr/sap/BIN/SYS/exe/run/rfcserver -tp rfcsrv -gwhost uw1033 -gwserv sapgw53

gw/accept_remote_trace_level

Specifies whether the trace level of a CPIC or RFC connection should be transferred. In order to prevent misuse, you can use this parameter to prevent the trace level from being transferred within the gateway.

0:Transfer of trace level allowed

1: Transfer of trace level allowed

Default value

1

Dynamic

Yes

gw/export_trace_level

Determines whether the trace level of a CPIC or RFC connection to an external client or to a remote gateway is transferred.

0: Trace level not transferred

1: Trace level not transferred

Default value

0

Dynamic

Yes

gw/external_trace_level

Determines the trace level with which an external program is started. Argument CPIC_TRACE=<n> is generated for this and the program to be started is specified in the argument. For more information about the trace level see rdisp/TRACE*-Parameter.

Afterwards the trace files can be found in the user’s start directory, in which the external program was started (SIDadm).

Default value

0

Dynamic

Yes

gw/rem_start

Determines how to start remote CPIC programs:

·         REMOTE_SHELL : Start using remote shell

·         Start using rexec (UNIX only !!) )

·         DISABLED : Remote start not permitted

Remote programs to be started via remote shell always run under the “gateway” identification. If remote programs are started using rexec, they run under the identification defined by the parameters SAPUSERNAME and SAPPASSWORD.

Default value

REMOTE_SHELL

Dynamic

Yes(*)

(*) but only if changing the parameter affords increased security, thus REMOTE_SHELL -> DISABLED or REXEC -> DISABLED is allowed, whereas DISABLED -> REMOTE_SHELL or DIABLED -> REXEC is not.

SAPUSERNAME

Identification for starting remote CPIC programs using rexec.

Default value

-

Dynamic

No

SAPPASSWORD

Identification for starting remote CPIC programs using rexec.

Default value

-

Dynamic

No

gw/remsh

Specifies the call path of the remote shell to start programs on other hosts. If the variable USER is defined in the environment, the value of this variable is transferred to the remote shell with the option -l <value>.

Default value

HP

/usr/bin/remsh

AIX

/usr/ucb/remsh

SUN

/bin/rsh

Windows

rsh

otherwise

remsh

Dynamic

No

gw/side_info

Specifies the complete path of the side-info file. This parameter is passed on to the CPIC interface via putenv and defines the shell variable SIDE-INFO. The side-info file should be created in the Data Directory of the gateway instance, that is in /usr/sap/<instance name>/data.

Default value

<Data Directory>sideinfo

Dynamic

No

gw/stat

Determines the status of the gateway statistics after starting the gateway. The gateway statistics can be evaluated using the gateway monitor (gwmon or transaction SMGW), and can be changed dynamically.

0:Statistics not active
1: Statistics active

Default value

0

Dynamic

Yes

gw/monitor

This parameter determines whether the gateway should communicate with the monitor locally or remotely.

·         0 : No monitor commands allowed

·         1: Only monitor commands from the local monitors accepted

·         2: Commands from local and remote monitors accepted.

Default value

2

Dynamic

Yes(*)

 (*) but only if changing the parameter affords increased security, thus 2 -> 1 is allowed, 1 -> 2 is not allowed.