Configuring the Sender RFC Adapter
Use
You configure the sender RFC adapter so that you can use it to convert RFC calls from a sender to XML messages and send these messages to the Integration Server or the PCK.
Integration
You
configure the adapter on the Parameters tab page during the definition of a communication
channel in the
Integration Server
or in the PCK. In addition
to the adapter configuration, you can use the Module tab page to specify generic modules in the module processor,
which give the adapter additional functions.
Prerequisites
...
1. You have created a new communication channel or have opened an existing one.
2. On the Parameters tab page you have selected the adapter type RFC.
3. You have selected the Sender radio button to define the adapter as a sender adapter.
4. The communication channel in which the RFC adapter is defined must be defined for a service of type Business System in the area Service Without Party. In the PCK you must create an empty party record.
The
entries made in the communication channel must be identical to those for the
adapter-specific identifiers for the business system. For more information
about adapter-specific identifiers, see
Service in the
Integration Server or Service in the
PCK.
Activities
Transport Protocol
The transport protocol is RFC.
Message Protocol
The message protocol is RFC (RFC XML).
Adapter Engine
Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine. This selection is not available in the PCK.
Source Tab Page
RFC Server Parameters
The RFC server parameters identify the sender system.
Specify the following parameters:
Parameter |
Entry |
Application Server (Gateway) |
Gateway host name of the sender system. |
Application Server Service (Gateway) |
Gateway service of the sender system. This can be the numeric description of the service port in the sender system or the alphanumeric equivalent (for example, sapgwXX, where XX is the system number of the sender system). |
Program ID |
Program ID of the registered server program. The selected program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters). |
SNC |
If you want to use Secure Network Connection, set the SNC indicator. · Specify the SNC Name. · Select the Quality of Protection. Set the indicator for SNC Advanced Mode and enter the permitted SNC names (ACL) in the table. You can also enter a value for Path to SNC Library. If you do not enter any details here, the setting is applied to the whole RFC adapter. |
Unicode |
Select this checkbox if the sender system is a Unicode system. |
Initial Connections |
Number of initial connections required between sender system and adapter. |
Maximum Connections |
Maximum possible number of initial connections required between sender system and adapter. This value is limited internally to a maximum of 50. |
Advanced Mode |
To specify additional parameters in the adapter configuration, set the Advanced Mode indicator. · If the channel cannot reach the specified SAP gateway to register itself, it retries automatically. The time interval between registration attempts is increased exponentially from one second to an internal maximum value (3600 seconds). Enter the maximum wait time in seconds between two registration attempts by using the Maximum Reconnect Delay parameter. · If the connected sender system is a non-SAP system, you can deselect the Verify Sender System checkbox. The sender system is then not checked using the system ID and the client. · Enter additional parameters and their values in the table.
|
RFC Metadata Repository Parameters
The RFC metadata repository parameters identify the SAP system containing the repository for the RFC metadata. This does not necessarily have to be the sender system.
Load Balancing
If your SAP system works with load balancing, select the checkbox and specify the following:
System with Load Balancing
Parameter |
Entry |
Message Server |
Host name of the SAP system (message server) |
Message Server Service |
Service of the SAP system (message server). This can be the numeric description of the service port of the message server or the alphanumeric equivalent (for example, sapmsXXX, where XXX is the system ID of the SAP system). |
System ID |
System ID of the SAP system |
Logon Group |
Specify the logon group of the message server. Note that the entries are case-sensitive. |
Advanced Mode |
Select this checkbox if you want to specify additional parameters of the class JCO.Client for the adapter configuration. Enter the name and values of the parameters in the table displayed |
System Without Load Balancing
Parameter |
Entry |
Application Server |
Host name of the SAP system (application server) |
System Number |
System number of the SAP system. This is a two-digit numeric value. |
Advanced Mode |
Select this checkbox if you want to specify additional parameters of the class JCO.Client for the adapter configuration. Enter the name and values of the parameters in the table displayed |
Authentication Mode
Use Logon Data for the SAP System |
Secure Network Connection for RFC |
Specify the Logon User for logging on to the SAP system.
|
Select the required level of security under Quality of Protection. |
Specify the Logon Password for logging on to the SAP system. |
Enter the SNC Partner Name. |
|
Set the indicator for SNC Advanced Mode. · Specify the SNC Name. · Enter the SNC library and its path. If you do not enter any details here, the setting is applied to the whole RFC adapter. |
Enter the Logon Language and the Logon Client. |
Enter the Logon Language and the Logon Client. |
Authorizations to Read Metadata
Depending on the SAP system version, the following authorizations are required to read the metadata (authorization object: S_RFC, ACTVT: 16, FUGR):
Function Groups by Release
Release |
Function Groups (FUGRs) |
As of 3.1H |
RFC1, SG00, SRFC, SUNI, SYST |
As of 4.0A |
RFC1, SDIF, SG00, SRFC, SYST, SYSU, SUNI |
As of 4.6A |
RFC1, SDIF, SG00, SRFC, SYST, SYSU |
As of 4.6D |
RFC1, SDIFRUNTIME, SG00, SRFC, SYST, SYSU |
The role SAP_BC_JSF_COMMUNICATION_RO is available to SAPJSF users and contains all the required authorizations.
Advanced Tab Page
Adapter Status
Set the adapter to Active to enable messages to be exchanged.
Adapter-Specific Message Attributes
The attribute namespace for the adapter is http://sap.com/xi/XI/System/RFC.
Parameter |
Entry |
Set Adapter-Specific Message Attributes |
If you want to create adapter-specific message attributes, set this indicator. |
RFC Destination The technical name of this attribute is: RfcDestination |
If the indicator is set, the RFC destination that is used in the SAP sender system is transferred as a message attribute in the message header. |