Name

Description

XRfc.receiverChannel.normalizeService.From.toTechnicalSystem

Value type: Boolean

Default: true

If the property is set to true, the sender communication component of the XI message is changed to the adapter-specific identifier for RFC. The result is set for the From value for the RFC-XML document with envelope. If the parameter is set to false, the value of the sender communication component is used as the From value.

The internal default is set to true.

XRfc.receiverChannel.normalizeService.To.toTechnicalSystem

Value type: Boolean

Default: true

If the property is set to true, the receiver communication component of the XI message is changed to the adapter-specific identifier for RFC. The result is set for the To value for the RFC-XML document with envelope. If the parameter is set to false, the value of the receiver communication component is used as the To value.

The internal default is set to true.

XRfc.receiverChannel.normalizeService.failOnError

Value type: Boolean

Default: false

If one or both of the properties above are set to true, this property controls the system behavior in the case of a normalization step failure. If this property is set to false and the normalization step fails, the values from the XI messages are used as values for the RFC-XML with envelope document. If it set to true and the normalization step fails, the processing of this message is aborted with an error.

The internal default is set to false.

syncResponseAdaptEncoding

Value type: Boolean:

Default: true

Encoding problems may occur during synchronous communication from the SAP Business Connector to the SAP Business Connector Adapter. The SAP Business Connector sends a synchronous request with a specific encoding to the adapter. The adapter converts this request to an XI message and sends it to the Integration Server. The encoding is retained. The response from the Integration Server may arrive at the SAP Business Connector Adapter using a different encoding.

If this property is set to false, the synchronous response is sent from the adapter to the SAP Business Connector using the encoding set in the response message from the Integration Server.

If this property is set to true, the synchronous response from the Integration Server is converted to the original encoding of the request from the SAP Business Connector.

The internal default is set to true.

syncMessageDeliveryTimeoutMsec

Value type: Integer

Default: 300000 (time in msec.)

This property controls the timeout while sending synchronous messages from the SAP Business Connector Adapter to the Adapter Framework and the other way round. It is also used to set the valid until field of a synchronous response message which is sent from the adapter to the SAP Business Connector.

The internal default is the same as shown above.

idMappPersistDurationDefault

Value type: Integer

Default: 172800000 (time in msec.)

The message ID has to be retained to handle acknowledgments. The persistence time is calculated depending on the messages involved. If the calculation fails, the value of this property is used instead.

The internal default is the same as shown above.

senderChannel.TID.duplicate.Check

Value type: Boolean

Default: true

This property deals with the duplicate detection for asynchronous messages for sender channels. A duplicate check is always carried out in the Adapter Framework persistency layer. This check is only based on the XI message ID.

If this property is set to true, a duplicate check is carried out in the SAP Business Connector Adapter. A message repeatedly sent from the SAP Business Connector to the adapter has the same TID. The same message ID will be used for these duplicates. The duplicate is detected later in the Adapter Framework layer. If this property is set to false, this detection is switched off. Changing this property will affect Exactly Once (EO) handling.

The internal defaults are the same as shown above.

senderChannel.TID.duplicate.ErrorSendback

Value type: Boolean

Default: true

If this property is set to true and a duplicate is detected by the Adapter Framework persistency layer, this error is send back as a response to the sending Business Connector. This has to be done because the Business Connector always uses synchronous communication. If set to false and a duplicate is detected, this is ignored.

The internal defaults are the same as shown above.