Regarding RFC adapter

[Former Member]

Hi

Why we need Programme ID and RFC destination of Type T for configuring RFC adapter

S V

[Former Member · Accepted solution]

Hi,

TCP/IP Connections (Type T)

Type T destinations are connections to external programs that use the RFC API to receive RFCs. The activation type can be either Start or Registration.

If it is Start, you must specify the host name and the pathname of the program to be started.

Activation Type Start

The communication method depends on how you select the program location:

¡ Explicit host

In this case, the program is started either by the default gateway for the system or by the explicitly specified gateway (gwrd) via remote shell.

Ensure that the computer with the gateway process can access the specified computer by entering /etc/ping must be the same as in SM59. (If you call an RFC server program without any parameters, the RfcAccept call always returns an error code (RFC_HANDLE_NULL) and the program terminates at once.)

¡ Application server

On choosing Application server and specifying your program, you can start the program from the SAP application server.

First, ensure that the program can be accessed from the SAP application server and that the SAP application server has the authorization to start the program.

To check this, logon with the user ID of the SAP application server (e.g. c11adm). If possible, change to the working directory of the SAP application server (/usr/sap/.../D.../work) and try to start the RFC server program manually from there. (If you call an RFC server program without any parameters, the RfcAccept call always returns an error code (RFC_HANDLE_NULL) and the program terminates at once.)

¡ Front-end workstation

On choosing Front-end workstation and specifying your program, you can start the program from the SAPGUI.

Ensure that you can access the program with SAPGUI.

Ensure that SAPGUI has the authorization to start the program.

To check this, simply call the RFC server program in your environment.

The function call can also be transactional (CALL FUNCTION... IN BACKGROUND TASK DESTINATION...).

Activation Type Registration

If the activation type is Registration, you have to identify a registered RFC program. With an SAP gateway, an RFC server program can be registered under this ID and then wait for RFC calls from different SAP Systems.

Example entry name: SERVER_EXEC

Thanks

Vikranth

[Former Member]

Why we need program ID

The selected program ID uniquely describes the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).That is why you choose the registration type Registered Server Program and in the Program ID field you enter the corresponding program ID from the configuration of the sender RFC adapter.

Q: Where can I find the program id ?

Ans: Well, the program id can be anything, even your name. But the catch here is that you should have the same in both the RFC destination and your RFC adapter.

Note: If you have read the above mentioned blog by Mike, he has used sdnweblog as the program id and the same is used in the RFC destination and also the RFC adapter

Interesting read - Question 22 of SAP note 730870

An extract of the same is

"To identify a XI RfcAdapter sender channel within the SAP Gateway it is important that its Program ID is unique within this Gateway. So try to avoid using common phrases as Program ID like 'rfcadapter' or 'rfcToXmb'.

To check which Program IDs are registered at the SAP Gateway the gateway-monitor can be used via transaction SMGW. Select Goto -> Logged on Clients. Registered RFC-Servers have a System-Type of 'REGISTER_TP'. The Program ID of the registered RFC-Servrer can be found in column 'TP name'. Unfortunately the list within SMGW only shows the truncated version of the Program ID (column 'TP name'). To get the full name, the details of an entry have to be selected. As an alternative the report RSGETALL_REG_SERVERS can be executed in transaction SE38. The output of this report will show the full names of the Program ID in column 'Registered PROGID'. This functionality is also available in the function module GWY_READ_CONNECTED_SYSTEMS which can be executed in transaction SE37."

tHANKS

Vikranth

[Former Member]

Hi,

A RfcAdapter sender channel registers itself with this Program ID as a RFC-Server at the SAP Gateway. The sending system uses the same Program ID to identify the RFC-Server at the SAP Gateway. If the sending system is a SAP system, this Program ID has to be maintained in the RFC destination (transaction SM59).During the sending system sends some RFC calls, the SAP Gateway will search its registration list for the Program ID supplied by the sending system. If there are more than one RFC-Server registered with the same Program ID, it will automaticaly schedule the RFC calles to each of the RFC-Servers using the round robin approach. This is done to distribute the load over all RFC-Servers equally.

Check this link...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1093c7a4-369f-2910-dfb2-afd07f21...

Regards,

Vivek LR

[GabrielSagaya]

1. The Program ID

*********************

The program id can be anything But the catch here is that you should have the same in both the RFC destination and your RFC adapter.

To identify a XI RfcAdapter sender channel within the SAP Gateway it is important that its Program ID is unique within this Gateway. So try to avoid using common phrases as Program ID like 'rfcadapter' or 'rfcToXmb'.

To check which Program IDs are registered at the SAP Gateway the gateway-monitor can be used via transaction SMGW. Select Goto -> Logged on Clients. Registered RFC-Servers have a System-Type of 'REGISTER_TP'.

The Program ID of the registered RFC-Servrer can be found in column 'TP name'. Unfortunately the list within SMGW only shows the truncated version of the Program ID (column 'TP name'). To get the full name, the details of an entry have to be selected. As an alternative the report RSGETALL_REG_SERVERS can be executed in transaction SE38. The output of this report will show the full names of the Program ID in column 'Registered PROGID'. This functionality is also available in the function module GWY_READ_CONNECTED_SYSTEMS which can be executed in transaction SE37."

The RFC destination

**************************

Make sure that the RFC destination is to be created in the R3 systems and not XI.

If in your adapter monitoring you find a message as 'Could not start server: Connect to SAP gateway failed' then try to replace the GWHost (gateway host) with the IP of the R3 system.

Configuring the Sender RFC Adapter - step by step

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step