Configuration Parameters 
Use
The parameters described here specify the basic settings of the SAP Gateway - startup, execution of remote programs, tracing, etc.
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 accepted. In order to prevent misuse, you can use this parameter to prevent the trace level from being accepted within the gateway.
0: Trace level is not allowed to be accepted
1: Trace level is allowed to be accepted
Default Value |
1 |
Dynamic |
yes |
gw/rem_start
Determines how to start remote CPIC programs:
· REMOTE_SHELL : Start via remote shell
· SSH_SHELL: Start via secure shell
· REXEC : Start via rexec (UNIX only !!) )
· DISABLED : Deactivate remote activation of programs
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.
gw/start_threshold
If programs are started using rexec, blockages may occur in the gateway. To make it easier to analyze any blockages, a warning is written to the trace file once the time has exceeded by five seconds. This check is also made for remote shell calls. The value 0 deactivates this check.
Default Value |
5 (seconds) |
Dynamic |
yes |
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 |
Linux |
/usr/bin/remsh |
|
SNI |
/usr/bin/remsh |
|
AIX |
/usr/ucb/remsh |
|
OSF1 |
/usr/ucb/rsh |
|
SUN |
/bin/rsh |
|
OS/2 |
rsh |
|
Microsoft Windows |
rsh |
|
otherwise |
remsh |
|
Dynamic |
no |
|
gw/ssh
Specifies the call path of the secure shell to start programs on other hosts.
Default Value |
HP |
usr/bin/ssh |
Linux |
usr/bin/ssh |
|
AIX |
/usr/ucb/ssh |
|
OSF1 |
/usr/ucb/ssh |
|
SUN |
/bin/ssh |
|
OS/2 |
ssh |
|
Microsoft Windows |
ssh |
|
otherwise |
ssh |
|
Dynamic |
no |
|
gw/side_info
Specifies the complete path of the side-info file. Using putenv this parameter is passed to the CPIC interface, 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 directory /usr/sap/<Instanz-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 deactivated
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 are accepted
· 1: Only monitor commands from the local gateway monitor are accepted
· 2: Monitor commands from local and remote monitors are 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.
gw/logging
With this parameter you can configure gateway logging. You can specify whether the gateway writes its actions to a log file, which types of actions are logged, and how the file is renamed. You have the options to define a maximum size for the file, and to specify whether old files are overwritten.
We recommend that you make the gateway logging settings in the gateway monitor (transaction SMGW), as described in Setting Up Gateway Logging. If you want to make permanent logging settings so that it works again after the instance has been restarted, you have to set this parameter in the profile.
You must set the parameter as follows:
gw/logging = LOGFILE=<name> ACTION=[TERSMPXVCO] [MAXSIZEKB=n] [SWITCHTF=t] [FILEWRAP=on] .
The meaning of the individual elements is as follows:
● LOGFILE: File name of the log file
● ACTION: The letter sequence (subset of TERSMPXVCO) specifies the actions to be logged (more information: table in Setting Up Gateway Logging)
● MAXSIZEKB (optional): Maximum file size As soon as the file exceeds this size, a new file is opened, whereby the new file name can change if special characters are used. This happens unless a condition was specified for SWITCHTF that applies first.
● SWITCHTF (optional): Opens a new file after a specific time period, unless a condition was specified for MAXSIZEKB that applies first.
The following values can be specified:
○ year: After one year a new file is opened
○ month: After one month
○ week: After one week
○ day: After one day
○ hour: After one hour
● FILEWRAP (optional): Reuse file This parameter can only have value ON. If this value is set, no new file is written, but the one already open is reset and rewritten to. The values for parameter LOGFILE are only used the first time the file is opened.
Additional Information
Parameters for Resource Management