Properties Related to RFC Clients (Receiver Channels)

The Following Properties are Related to RFC Clients (Receiver Channels)

Name

Description

writeXmlPreambleToPayload

Value type: Boolean

Default: true

The RFC adapter creates an RFC-XML document from an RFC response (RFC receiver channel in the case of synchronous processing).

If this property is set to true, the RFC-XML document will contain an XML preamble.

If this property is set to false, the RFC-XML document will not contain an XML preamble.

pathToSNCLibraryDefault

Value type: String

Default: not set

This is the setting for the default name (with absolute path) of the SNC library you have to use for RFC communication over SNC. It can be overridden by the channel configuration setting in the Integration Directory (SNC advanced mode).

Even if you do not specify anything neither for this property nor in the channel configuration, the RFC layer will be able to find the SNC library, for example, by using settings in the process environment. This depends on the used platform.

monitorHistoryLength

Value type: Integer

Default: 5

The number of entries to be displayed in the channel history of RFC channels in the adapter monitor.

A value of 0 will turn off the channel history.

initialRfcClientConnectCheck

Value type: Boolean

Default: true

The connection parameters provided by the adapter configuration are checked if

A channel is created/updated in the Integration Directory

The RFC adapter is restarted

A dependent service like the SAP XI AF CPA Cache or SAP XI AF Core is restarted

The J2EE Engine is restarted

The parameter check is done by connecting/disconnecting to the remote system. If the check fails, the channel is marked as failed and the channel cannot be used for message exchange. To enable the channel or force a recheck, the channel has to be activated from outside once again. This can be done by updating this channel in the Integration Directory or by restarting the RFC adapter or the J2EE Engine.

If this property is set to false, the check is disabled. Messages sent through a channel with a configuration error and a disabled check produce a runtime error.

clientMode

Value type: Fixed text: reset/none

Default: reset

Each receiver channel has a pool of RFC clients associated with it. If a message is sent through a channel, an RFC client is retrieved from this pool and then the message is processed by using this client. The client is released to the client pool afterwards and it can be used for another message which is sent through the same channel. After the client has been used, a state is assigned to the client in the receiver system.

The default value of this property is reset, which will issue a reset of the client context in the receiver system after each usage of a client. This leads to SAP systems with versions lower than 4.0A being disconnected/connected.

If this value is set to none, nothing will be done after the client has been used.

RfcClient.confirmTID

Value type: Boolean

Default: true

If set to true, the current TID is directly confirmed after each tRFC call to the remote target system. If set to false, no confirmation of the TID is sent.

You can override this setting by selecting Confirm TID in each channel configuration (advanced section).

RfcClient.supportEOIO

Value type: Boolean

Default: true

If set to true, receiver channels of the type RFC send a message with quality of service (QoS) Exactly Once In Order (EOIO) as a tRFC to the remote target system. This system must guarantee the direct execution of this tRFC call in the same way that SAP systems do. If set to false, a runtime error occurs if a message with QoS EOIO is sent to a receiver channel of type RFC.

ignoreJrfcJdsrError

Value type: Boolean

Default: true

Internal flag to prevent errors in certain releases in the JDSR layer. This property will be removed in a future release. This property must not be changed.

RfcClient.message.exceptionNameFromMessage

Value type: Boolean

Default: false

When a synchronous RFC call is sent to an SAP system, an ABAP exception is thrown that results in a synchronous fault response message. An error header is created along with this message that contains the fields ApplicationFaultMessage and ApplicationFaultMessageNamespace. This property controls how these fields are filled.

If this property is set to false, the content of field ApplicationFaultMessage is the name of the called function module, followed by the text .Exception, and the content of field ApplicationFaultMessageNamespace is the name of the RFC namespace urn:sap-com:document:sap:rfc:functions.

If this property is set to true, the content of field ApplicationFaultMessage is the interface name of the request message followed by the text .Exception, and the content of field ApplicationFaultMessageNamespace is the interface namespace of the request message.

See also SAP Note 832258.