Setting Up RFC Communication to RFCOSCOL  

Purpose

You must set up RFC communication when you use a dedicated database server.

Process Flow

This section provides examples of the steps that are normally required to set up RFC communication. The procedure described may, however, not apply to all scenarios.

There are three main steps. Step 1 is carried out in the operating system of the system you are working in. Steps 2 and 3 are carried out in the R/3 System.

  1. Set up a remote shell access

    2. R/3 uses a remote shell to call rfcoscol via the gateway. Note that the gateway runs on a different host than rfcoscol . You must maintain the rhosts file so that the gateway can start a program on the target host without a password (you may have to create this user on the target host first). The gateway either calls the remote shell so that the user name is determined by the gateway user ID, or, if the environment variable "USER" has been preset, then this name is used.

    The user c11adm starts the gateway on the host r3c11000 , and the environment variable is not preset. When an R/3 work process needs the gateway to start the program /usr/sap/bin/rfcoscol using TCP/IP on the host c11dbsrv , then the gateway executes the following command:

    remsh c11dbsrv /usr/sap/bin/rfcoscol.....

    This is only possible if the rhosts file in the home directory of user c11adm on host c11dbsrv contains the following line:

    r3c11000 c11adm

    Using the same names as above, but where the environment variable USER has been preset as osreader , the gateway executes the following command:

    remsh c11dbsrv -l osreader /usr/sap/bin/rfcoscol

    Here, the rhosts file in the home directory of the user osreader on the host c11dbsrv must contain the following lines:

    r3c11000 osreader
  2. Set up a logical destination

    3. Create a destination with the following attributes using the RFC destination maintenance tool (Transaction SM59):

     

     

    Name:

    SAPOSCOL_<HOSTNAME> , where <HOSTNAME> is replaced by the target host name

    Type:

    T for TCP/IP

    Area:

    Explicit

    Target host:

    Target host name ( c11dbsrv in the above example)

    Program:

    /usr/sap/bin/rfcoscol

     

    Call Transaction AL15. From the menu, choose SAPOSCOL destinations. Choose New RFC destinations. This calls the RFC destination maintenance tool (Transaction SM59). From here, you can test the connection to rfcoscol .

  3. Save this logical destination as a remote saposcol .

You can use Transaction AL15 to manage existing logical destinations that call up rfcoscol . Specify a logical destination and then save it as a saposcol destination using Add Destination. This logical destination can then be used under saposcol remote.

The field Database Server specifies whether this destination leads to the R/3 System’s database server. The remote saposcol can be used for both dedicated database servers and other non-R/3 System servers.