Configuration for a TCP/IP Connection

For up-to-date information, you should read the file SAPGW.README, which is delivered with the software.

The SNI product DCAM supports TCP/IP connections as of Version 11.

A large number of computer systems are thus able to communicate with programs and applications under BS2000.

A workstation is connected via TCP/IP, and a SAP Gateway is used on UNIX or under BS2000 (depending on where the connection is set up from).

Communication with a workstation via TCP/IP is possible both for R/2 as a DCAM application and for R/2 as an UTM application.

As the R/2 software is not able to communicate directly via a TCP/IP connection, an adapter is required. The adapter is connected to R/2 (as a DCAM or UTM application) via TCP/IP on the one side, and to DCAM, on the other side.

Depending on the initiator of the communication (R/2 or partner), this function is performed under BS2000 by the gwhost communications program or in the central SAP Gateway:-

If a connection to an R/2 System is built up by a partner, which can be a non-SAP program, an R/3 System or a SAPGUI of the CUA Interface, the SAP Gateway running under BS2000 is addressed. The SAP Gateway handles the connection to the R/2 System.

In general, the SAP Gateway under BS2000 is required once only, as it can maintain connections to any number of R/2 Systems.

For every connection, a work process opens a DCAM application, which logs on to the SAP System.

A connection setup by the R/2 System to a non-SAP program or an R/3 program is made via the SAPGWHO tasks which run under BS2000. As an R/2 application is started, these tasks are started according to the number of tasks specified (SAPB2CSA, as of 5.0F in the profile).

These tasks are allocated to an R/2 System.(They run under its user name.) The number of parallel connections (built up from R/2) depends on the number of tasks started.

During connection setup by the R/2 System, the task SAPGWHO does not address the SAP Gateway under BS2000 but the SAP Gateway under UNIX, as an external program written in C can only be started from there. The side info file must contain a relevant entry.

Setting up communication with the R/2 System via TCP/IP requires a series of actions. These actions are described in the following topics:

(If R/2 is under UTM)