Entering content frameProcess documentation Configuring the SAP Gateway Under BS2000 Locate the document in its SAP Library structure

Purpose

You can install the SAP Gateway under any user ID. It reads its parameters from the SAP profile file SAPGW.RSPARAM .

Note

Read SAPGW. README

Always read the file SAPGW. README . It normally contains important current information.

Process flow

Parameter values take effect when an SAP process is started.

These parameter values may originate from various sources:

Here, values are determined which differ from default ones.

There are definite encoded default values for most parameters. These values take effect unless you define other values.

Command line arguments are not supported in BS2000 .

Changes to parameter values only take effect when you restart the processes concerned. Changes to default values can only be made by SAP.

Profile Parameters in BS2000

The profile parameters are set in the file SAPGW.RSPARAM. Please note that a series of parameters in the BS2000 environment can only have one pre-set value. You cannot change these parameters (or parameters of this kind which have not been listed here).

The following list is sub-divided as follows:

General Profile Parameters

Default values are set for most BS2000-specific profile parameters. You can change these values.

Two-digit SAP System number <nn>

The SAP System number implicitly determines the TCP/IP service, for which the Gateway expects logon requests. The Gateway service contains the SAP System number: sapgw<nn>

Number of CPI-C requests which can be stored for a CPI-C connection.

Default value: 30

Maximum number of currently active connections.

Default value: 100

Maximum number of gateway work processes you can start.

You can start up to ten work processes in BS2000. Depending on the load, a work process is sufficient for 50 to 100 connections.

Maximum number of connections a gateway work process can accept.

Trace level (see side info parameter CPI_TRACE)

rdisp/TRACE = 0 No tracerdisp/TRACE = 1 Error tracerdisp/TRACE = 2 Complete process, short data tracerdisp/TRACE = 3 Complete process, complete data trace

The trace files are written in the respective SYSOUT protocol.

Default value: 1

BS2000-specific Profile Parameters

Default values are set for most BS2000-specific profile parameters. You can change these values.

Prefix for the DCAM applications open per session (two-digit)

Maximum number of DCAM connections per work process

This value should be identical to gw/max_conn_per_wp .

Number of buffers of the DCAM interface

This value should be at least twice as high as bs2/max_conn .

Switch for side info table.

bs2/use_sideinfo = 0 Do not use side info file.

bs2/use_sideinfo = 1 Establish target system with destination and side info file.

Default value: 0

Trace switch.

bs2/trace_to_stderr = 0 Traces not written to SYSOUT .

bs2/trace_to_stderr = 1 Traces written directly to SYSOUT.

Default value: 0

Enter command for starting the gateway reader.

Default value: /E SAPGW.LIB(E.START.READER)

Enter command for starting the gateway worker.

Default value: /E SAPGW.LIB(E.START.WORKER)

The file SAPGW.RSPARAM contains a configuration model for 100 users. Seek advice from an SAP consultant before making any changes.

Checking TCP/IP Services

The TCP/IP port accessed by the gateway read process is in the Sysout file of the gateway read process LOG.SAPGWRD.<tsn><date>.<time>.

The services file SAPGW.SERVICES is not delivered. You cannot change this file.

You can display occupied TCP/IP ports with the operator command /BCSHOW .

The host names from the BS2000 viewpoint are determined during BCAM generation (SOKHOST).

The following commands let you check whether the respective host partner can be reached via TCP/IP:

 

 

Leaving content frame