Data Interfaces

R/2 R/3 Communication (IBM)
Connection setup from R/2
Host Host (K50)
(K50)
R/2
R/2
ABAP/4 ABAP/4
Dest LU TP
T01 MP30 T01
(hs5000)
© SAP AG
LU6.2
hs5000
SNA SNA subsystem
subsystem
Progr: Progr: gwhost
gwhost
SAP SAP gateway
gateway
TCP/IP (remote)
shared memory (local)
Table XCOM (K50) Side info from gwhost
DEST = T01
LU = hs5001
TP = sapgw00
GWHOST = hs5001
GWSERV = sapgw00
Protocol = I
hs5001, sapgw00
UNIX, UNIX, NT NT (T01)
(T01)
SAP SAP gateway
gateway
R/3
R/3
ABAP/4
ABAP/4
The switching program gwhost is started on the machine where the SNA software is installed. gwhost
then looks for an entry in the side information table where the destination matches the TP specification in
the R/2 table XCOM (the program started by the SNA subsystem does not have to be called gwhost - it
can be copied beforehand or a symbolic link can be set up, e.g. ln -s gwhost T01). If you want to set up a
connection from R/2 to several R/3 Systems, each R/3 System must be defined at the SNA services level
on the one hand, and have its own intermediate program (e.g. T01, T02, ... ) on the other. There must of
course also be an entry in the side information table for each R/3 System. The symbolic destination is
identical with the name of the intermediate program (DEST=T02). To reach different destinations, e.g.
different R/3 Systems, this means that the intermediate program must be declared to the SNA subsystem
under different names.
You should ensure that the side information file can be found and read by the switching program. To do
this, you need to know the identity of the user who started the program. Of course, the authorizations of
the side information file must be set so that the user can read them.
The switching program is required for CPI-C and RFC connections.
For an RFC connection, you need to make the appropriate entry in the table RFCD.