17.08.2013 Views

Data Interfaces

Data Interfaces

Data Interfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

R/3 R/2 Communication (SNI)<br />

© SAP AG<br />

Connection setup from R/3<br />

UNIX, UNIX, NT NT (T01) (T01)<br />

BS2000 BS2000 (K50)<br />

(K50)<br />

R/3<br />

R/3<br />

ABAP/4 ABAP/4<br />

TCP/IP<br />

Table RFCDES Gateway options<br />

SAP SAP gateway<br />

gateway<br />

R/2 R/2<br />

ABAP/4<br />

ABAP/4<br />

RFC destination K50 Gateway host: BS2GW<br />

Connection type 2 Gateway service: sapgw00<br />

Table TXCOM (T01)<br />

Dest LU TP PROT Gateway host Gateway service<br />

BS2000 C BS2GW sapgw00<br />

On the external machine (BS2000), there must be an SAP gateway active (the connection must be set up<br />

from the gateway of the BS2000 host).<br />

On BS2000 machines, the SAP gateway can be accessed via TCP/IP. However, the following<br />

requirements must be satisfied:<br />

BS2000 version 11, DCAM version 11 (BCAM V.11 with TCP/IP)<br />

On BS2000 machines, the SAP gateway can communicate with an UTM application or a DCAM<br />

application.<br />

Table TXCOM of the R/3 System:<br />

Dest LU TP Prot Gateway host Gateway service<br />

S50 C host name sapgwXX<br />

The entries for LU and TP are dummy entries. For the gateway the following applies:<br />

LU=DEST and TP=X1SA<br />

host name is the name derived from the BCAM generation of the BS2000 host where the gateway is<br />

running. The gateway can function with or without side information.<br />

(Parameter: bs2/use_sideinfo [0,1]).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!