Show TOC

Configuring the Sender RFC AdapterLocate this document in the navigation structure

Use

You configure the sender RFC adapter to convert RFC calls from a sender to XML messages. These XML messages are then sent to the Integration Server or the PCK.

Prerequisites
  • The communication channel in which the RFC adapter is defined must be defined for a service of type Business System in the area Communication Component 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 documentation of Integration Directory (SAP NetWeaver Library Function-Oriented View under → Process Integration → Integration Directory).

  • Depending on the SAP system version, you require the following authorizations to read the metadata (authorization object: S_RFC, ACTVT: 16, FUGR):
    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.
Procedure
  1. The Transport Protocol is RFC.
  2. The Message Protocol is RFC (RFC XML).
  3. Select the Adapter Engine on the Integration Server, or select a non-centrally installed Adapter Engine.

    This selection is not available in the PCK.

Define RFC Server Parameters

The RFC server parameters identify the sender system.

  1. Select the Source tab page.
  2. Under Application Server (Gateway), specify the Gateway host name of the sender system.
  3. Under Application Server Service (Gateway), specify the Gateway service of the sender system.

    Specify the numerical description of the service port in the sender system or the alphanumerical equivalent.

    For example, enter sapgwXX where XX is the system number of the sender system.

  4. Enter the Program ID of the registered server program.

    The specified program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).

  5. If you want to use the Secure Network Connection, choose SNC.
    • Specify the SNC Name.
    • Select the Quality of Protection.
  6. Set the indicator for SNC Advanced Mode and enter the permitted SNC names ( ACL )in the table.
  7. You can also enter a value for Path to SNC Library.

    If you do not enter any details, the setting is applied to the whole RFC adapter.

  8. If the sender system is a Unicode system, choose Unicode.
  9. Specify the number of Initial Connections required between the sender system and adapter.
  10. Specify the number of Maximum Connections required between the sender system and adapter.

    This value is limited internally to a maximum of 50.

Define Parameters for Advanced Mode

  1. To specify additional parameters for the adapter configuration, select Advanced Mode.
    • Specify the Maximum Reconnection Delayin seconds between any two attempts to register new connections.

      If the channel cannot reach the specified 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).

    • If the connected system is a non-SAP system, deselect Verify Sender System.

      The sender system is then not checked using the system ID and the client.

    • Enter additional parameters and values in the table.

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

  1. The parameters vary depending on whether the system containing the Repository RFC metadata has load balancing or not.

    Defining a System with Load Balancing

    Defining a System Without Load Balancing

  2. To specify additional parameters of class JCO.Client for the adapter configuration, choose Advanced Mode.
  3. Enter the Name and Value of each parameter in the table.

Defining the Adapter Status

  1. Select the Advanced tab page.
  2. Set the Adapter Status to Active to enable messageexchange.

Defining Adapter-Specific Message Attributes

  1. To create adapter-specific message attributes, choose Set Adapter-Specific Message Attributes.
  2. If the RFC destination that is used in the SAP system is to be transferred as a message attribute in the message header, choose RFC Destination.

    The technical name of this attribute is RfcDestination.

    The attribute namespace for the adapter is http://sap.com/xi/XI/System/RFC.

Defining the Scenario Specific Timeout

  1. For scenario specific timeout, enter the time in milliseconds in the Timeout for Synchronous Communication in milliseconds field. It is the time in milliseconds for which the messaging system waits to receive a response, after which it returns a MessageExpiredException to the sender. With scenario specific timeout, it is possible to save the application from waiting for a default timeout.
    Note

    Channel Specific timeout can also be configured as a module parameter to RfcAfBean. More information: Setting a Channel-Specific Timeout