There is a side info table called TXCOM in the database of each SAP system. It contains the following column headings:
Dest
Destination
Symbolic name of the target system
(up to 8 characters)
LU
Logical unit
(up to 8 characters)
TP
Transaction
program
(up to 8 characters)
Prot
Protocol type (1 character)
The following protocol types are possible:
Protocol type |
Meaning |
C |
The partner program is an ABAP program in R/2. |
I |
The partner program is an SAP NetWeaver ABAP program that can be accessed via TCP/IP. |
E |
The partner program is a C program, which can be accessed via TCP/IP and started by means of fork/exec, remote shell or rexec. |
F |
The partner program is a C program, which can be accessed via TCP/IP and started externally (for example, by the R/3 Frontend or an R/3 Server). |
R |
The partner program is a C program, which can be accessed via TCP/IP and has registered at the SAP-Gateway. |
Gateway host
Host
computer of the SAP Gateway
(up to 20 characters)
If the computer name is longer, you must define a symbolic computer name in
the THOST table.
Gateway service
SAP Gateway
service
(up to 20 characters)
The table txcom must be configured according to the target system:
Two ABAP programs on two SAP servers (BIN and B20), located on the same computer, communicate with one another.
The connection parameters must be defined in the TXCOM side info table. If the target system is an SAP system Release 2.1 or higher, you can also specify sapgw<nr> under TP.
The following table has examples of values.
DEST
LU
TP
Prot
Gateway-Host
Gateway-Service
---------------------------------------------------------------
bin hs0001 sapdp53 I is0001
sapgw00
b20 hs0001 sapdp21 I is0001
sapgw00
DEST21 hw0002 sapgw53 I
-
-
An ABAP program of an SAP system communicates with a program written in C of an external system.
The protocol type for this type of communication must be E, as the partner program is located outside the SAP system and can be accessed via TCP/IP.
In the following side info example, the SAP Gateway and the target system are on different computers. The SAP Gateway starts the program written in C using Remote Shell.
For this the following requirements must be met:
· The SAP Gateway ID must be available on the target computer.
· The file .rhosts must be available in the home directory of the SAP Gateway ID on the target computer. The gateway computer must be registered in the file .rhosts. The program written in C or a Softlink must also be available in the home directory.
· The connection parameters must be defined in the TXCOM side info table. The following table has examples of values.
/* C Program: rcvcpic */
DEST
LU
TP
Prot Gateway-Host Gateway-Service
---------------------------------------------------------------
rcvcpic iw10004 rcvcpic
E
is0001
sapgw00