The RFC Inbound and ALE Inbound servers use the sideinfo method of connecting to R/3. This section includes the following topics:
Configuring Inbound Connections
You must configure the following environment variables for inbound connections:
Setting Environment Variables for the Inbound Connection
Listing 6-1 shows sample settings in an environment file:
Listing 6-1 Sample Environment Variable Settings for Inbound Connections
CR3_DESTINATION=SAPNODE
CR3_CLIENT=SAPCLIENT
CR3_USER=LOGINNAME
CR3_PASSWORD=LOGINPASSWORD
CR3_LANGUAGE=E
SIDE_INFO=<your eLink app directory>\sideinfo
The settings you specify depend on the configuration of your R/3 installation. See your R/3 system administrator for more information.
The RFC Inbound and ALE Inbound servers use the sideinfo method of connecting to R/3. The sideinfo file is an ASCII text file that specifies the connection point for external programs to communicate with the R/3 application server. See your SAP R/3 documentation for more information about the sideinfo file.
The sideinfo file is associated with the parameters provided to the RFC Inbound and ALE Inbound servers when they are started. A sample sideinfo file comes with BEA eLink Adapter for R/3, but you must configure this sample file for your particular R/3 environment and BEA eLink Adapter for R/3 installation. Errors in this file will prevent the RFC Inbound or ALE Inbound servers from connecting to R/3.
The following table describes the attributes in the sideinfo file:
In an R/3 environment with multiple R/3 application servers, this list of attributes is simply repeated for different node names, different instances of R/3, and possibly different gateways.
Listing 6-2 shows sample settings in a sideinfo file:
Listing 6-2 Sample Settings for sideinfo File
DEST=SAPNODE
LU=nodename
TP=sapdp00
PROTOCOL=I
GWHOST=nodename
GWSERV=sapgw00
The sideinfo file is usually located in the directory where the RFC Inbound and ALE Inbound servers are running (for example, the TUXEDO appdir). If you cannot use this location in your environment (for example, a number of other processes also connect to R/3 and use the same sideinfo information), then you can avoid duplicating the file by assigning the SIDE_INFO environment variable to a path containing the sideinfo table, as shown in the following examples:
UNIX C shell (csh):
setenv SIDE_INFO ..<your eLink app directory>\sideinfo
Windows NT:
set SIDE_INFO=<your eLink app directory>\sideinfo
The sideinfo file must have protections set so that all processes can read it.
For the RFC Inbound and ALE Inbound servers, this environment variable is defined in the server start-up script. See Setting Environment Variables for RFC Inbound in Configuring RFC Integration and Setting Environment Variables for ALE Inbound in Configuring ALE Integration for more information.
The ALE Outbound server uses the register mode method of connecting to R/3. When the ALE Outbound server is started, it connects to R/3 and registers with a specific Program ID. This Program ID is defined in the RFC destination, as defined in transaction SM59. The servers must be started and registered on the Program ID.
To register with R/3, the following information must be passed to ALE Outbound as command line parameters (which are specified in the server start-up script):
R/3 provides extensive help in isolating and testing connection problems involving the R/3 Gateway. The R/3 Gateway is sometimes called the CPIC Gateway because the CPIC protocol is the lowest-level protocol used on the TCP/IP socket when connecting to R/3.
To troubleshoot connection problems: