Configuring the Receiver RFC Adapter (SAP Library

Configuring the Receiver RFC Adapter

Use

You configure the receiver RFC adapter so that you can use it to convert XML messages from the Integration Server or the PCK to RFC calls and send these calls to the corresponding receivers.

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, on the Module tab page in the module processor, you can specify generic modules, 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 Receiver radio button to define the adapter as a receiver 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.

5. The specifications in the communication channel must match the specifications 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.

Target Tab Page

RFC Client Parameters

The RFC client parameters identify the receiver system.

Specify the type of the RFC server.

· It can be an SAP System.

· It can be an External RFC Server. The external RFC server is a server programmed with RFC-SDK that has registered itself with an SAP gateway.

If your SAP system works with Load Balancing, choose Load Balancing.

SAP 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.

SAP System Without Load Balancing

Parameter	Entry
Application Server	Host name of the SAP system (application server)
System Number	System number of the SAP system (two-digit numeric value)

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.
	Choose Advanced SNC Mode. · Specify the SNC Name. · Enter the SNC library and the relevant path under Path to SNC Library. If you do not enter any details, 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.

Additional Parameters

Parameter	Entry
Maximum Connections	Maximum possible number of connections required between adapter and receiver system.

Specify the following parameters for the external RFC Server:

Parameter	Entry
Application Server (Gateway)	Gateway host name of the receiver system
Application Server Service (Gateway)	Gateway service of the receiver system. This can be the numeric description of the service port in the receiver system or its alphanumeric equivalent.
Program ID	Program ID of the registered server program
Maximum Connections	Maximum possible number of connections required between receiver system and adapter. Internally, this value is set to a maximum of 50 connections.

Advanced Mode

For SAP systems (with and without load balancing) and also for external RFC servers, set the Advanced Mode indicator to show additional configuration options.

Parameter	Entry
Send 'Confirm Transaction'	Only deactivate the indicator if you do not want the transaction confirmation signal (Confirm TID) to be sent after a transactional RFC call.
Commit Control for Single BAPI Calls	If you want to use this communication channel to call BAPIs as remote-enabled function modules that change the data in the database, set the indicator. If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK. The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values “”, “S”, “I”, and “W” are displayed. All other entries are evaluated as errors. To change this setting, choose BAPI Advanced Mode. Under Successful RETURN Type Values, specify the values that will lead to a successful execution.
Table	You can enter additional parameters of the class JCO.Client for the adapter configuration. Enter the names and values of the parameters in the table displayed.

RFC Metadata Repository Parameters

If an external RFC server is selected as the receiver, then an SAP system must also always be available to provide the RFC adapter with the metadata of the external RFC server. If an SAP system is selected as the receiver, you can also use this to provide metadata to the RFC adapter.

Select the Use Alternative RFC Metadata Repository checkbox if you want to use a different metadata repository to that of the receiver system.

If you select this checkbox or choose the external RFC server type, the system displays the RFC client parameters and you can enter values for the SAP system.

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.

If your SAP system works with Load Balancing, choose Load Balancing.

SAP 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.

SAP System Without Load Balancing

Parameter	Entry
Application Server	Host name of the SAP system (application server)
System Number	System number of the SAP system (two-digit numeric value)

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.
	Choose Advanced SNC Mode. · Specify the SNC Name. · Enter the SNC library and the relevant path under Path to SNC Library. If you do not enter any details, 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.

Additional Parameters

Parameter

Entry

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.

Advanced Tab Page

Adapter Status

Set the adapter to Active to enable messages to be exchanged.