Siebel Connector for SAP R/3 > Installation and Configuration > Modifying SAP Configuration Files >

Modifying the saprfc.ini File

The saprfc.ini file contains information that Siebel applications use to connect with SAP. Depending upon your installation and configuration, you may have saprfc.ini files in the following folders: siebsrvr/bin, tools/bin, and seaw/bin. The siebsrvr/bin folder is used when SAP business services execute in the Siebel server. The tools/bin folder is used when SAP integration object wizards are executed in Siebel Tools. The seaw/bin folder is used when SAP business services execute from the Siebel Mobile Web Client. SAP business services execute in the client only during execution of the Workflow Simulator and EAI Business Service Simulator.

You may modify and use these files, or you may elect to use an already existing file you may have set up for your SAP R/3 installation. In any case, you must set the RFC_INI environment variable to point to your saprfc.ini file. This must be set on every Siebel installation that executes the server or Tools applications. In a test environment, you also need to set this environment variable on any machine on which you are executing the Workflow Simulator or EAI Business Service Simulator in the Siebel Mobile Web Client.

The saprfc.ini file contains a series of SAP Destination definitions. Each definition contains the connection information necessary for an external application to connect to SAP in some manner. Each entry begins with the name of the Destination: DEST=name. The name in the destination entry is important, as it is this name that must be entered in the Siebel application so that the Siebel Business Services can retrieve the connection information in this entry.

There are two types of entries in the file that are important for connection to SAP. The first is indicated by a TYPE=A entry in the saprfc.ini file destination entry. This type of destination entry indicates that the external application (Siebel Business) connects as a client to the SAP R/3 Application Server. The BAPI adapter uses this type of entry. The second destination type is indicated by a TYPE=R entry in the saprfc.ini file destination entry. This type of destination entry indicates that the external application (Siebel Business) connects as a server to the SAP R/3 Application Server. The tRFC BAPI Receiver uses this type of entry.

To create a destination entry for the BAPI adapter

1. Open the saprfc.ini file in a text editor.
2. Search for the text TYPE=A to find the sample TYPE=A entry.

   This entry has the following required lines:

   DEST=DEST_NAME
   TYPE=A
   AHOST=HOST_NAME
   SYSNR=XX

3. Edit DEST= to replace DEST_NAME with your own destination name.

   Any name can be used, but do not use spaces. You use this name as the destination in the SAPRfcConnectString component parameters for the Business Integration Manager component. For more information, see Setting Server Component Parameters.

4. Edit ASHOST= to replace HOST_NAME with your SAP application server host name.
5. Edit SYSNR= to replace XX with your SAP system number.

   For example your entry might now look something like this:

   DEST=DEV_Outbound
   TYPE=A
   ASHOST=devserver
   SYSNR=00
   RFC_TRACE=0
   ABAP_DEBUG=0
   USE_SAPGUI=0

6. Save the file and close the editor.
7. Be sure to set the RFC_INI environment variable to point to the saprfc.ini file.
8. To define connections to other SAP implementations use additional TYPE=A entries.

   For load balancing, you may use TYPE=B entries instead of TYPE=A.

   A TYPE=B entry contains the following values:
   DEST=DEST_NAME
   TYPE=B
   R3NAME=Name of the R/3 system. This is optional. The default is the destination.
   MSHOST=Host name of the message server
   GROUP=Application servers group name. This is optional. The default is PUBLIC.

See your SAP documentation for more information on this type of entry.

To create a destination entry for the tRFC BAPI receiver

1. Open the saprfc.ini file in the text editor.
2. Search for the text TYPE=R to find the sample TYPE=R entry.

   This entry has the following required lines:

   DEST=DEST_NAME
   TYPE=R
   PROGID=PROGRAM_ID
   GWHOST=HOST_NAME
   GWSERV=sapgwXX

3. Edit the DEST= line to replace the DEST_NAME with your own destination name.

   Any name can be used, but do not use spaces. You use this name as the value of the SAPRfcDestEntry component parameter for the tRFC BAPI Receiver component.

4. Edit the PROGID= line to replace PROGRAM_ID with the your program ID.

   This can be any name you decide upon, but it must be defined within SAP as part of the RFC Destination defined in SAP transaction sm59; see Creating RFC Destinations in SAP.

5. Edit the GWHOST= line to replace HOST_NAME with the SAP gateway server host name.
6. Edit the GWSERV= line to replace the sapgwXX with your SAP gateway server name.

   Usually it is in this form: sapgw followed by the two-digit system number. For example, your entry might now look something like this:

   DEST=DEV_Inbound
   TYPE=R
   PROGID=myprogramid
   GWHOST=devserver
   GWSERV=sapgw00
   RFC_TRACE=0

   For debugging purposes you may want to set the values of RFC_TRACE or ABAP_DEBUG. For more information, see Troubleshooting SAP Connection Problems.