Properties for Service SAP XI Adapter: XI

Properties Related to Connection

Name

Description

xiadapter.isconfig.url

xiadapter.isconfig.username

xiadapter.isconfig.password

xiadapter.isconfig.sapClient

xiadapter.isconfig.sapLanguage

Default: http://localhost:50080/sap/xi/engine?type=entry

Default: PIAFUSER

Default:

Default: 100

Default: de

The XI adapter as part of the Adapter Engine gets the required connection information for sending XI messages to the Integration Server (IS) from the Landscape System Directory (SLD) and the exchange profile (EP).

If the SLDAccess property of the J2EE service SAP XI AF CPACache is set to false, the connection information of the Integration Server can be explicitly set with the properties listed above.

These properties must not be changed.

xiadapter.adapterTypeNamespace

The adapter type namespace typically has the form of a URL.

Default: http://sap.com/xi/XI/System

It is used to retrieve the XI adapter metadata from the Adapter Framework CPACache Service.

This property must not be changed.

xiadapter.inbound.numberRetries.default

xiadapter.inbound.retryInterval.default

xiadapter.inbound.persistDuration.default

xiadapter.inbound.timeout.default

Default: 3

Default: 300000

Default: 2592000000

Default: 180000

All time period values are defined in milliseconds. The default retry interval is 5 minutes, the default persist duration is 30 days and the default synchronous message timeout is 3 minutes.

These properties are relevant for inbound message processing, but only in case of a central or non-central Adapter Engine.

These properties control the guaranteed delivery of XI messages between the Integration Server and the Adapter Engine.

The first three properties are only relevant for asynchronous messages.

numberRetries defines how often an asynchronous message with quality of service Exactly Once (In Order) should be resent in case of a delivery error.

retryInterval defines how long the messaging system should wait before the next retry.

persistDuration specifies how long the message should be kept in the message database of the messaging system. The value must correspond to the product of numberRetries and retryInterval. In the case of duplicate detection, the messages should be persisted for the same period of time as the message is persisted on the Integration Server. The default value is 30 days.

Only messages with an expired persist duration can be deleted from the database or archived and subsequently deleted.

It can happen that message throughput in the Adapter Engine is so high that the database volume is not able to store all asynchronous messages for the predefined period of time (30 days). In this case, the persist duration value needs to be decreased to a value that allows the messages to be kept in the database for the configured period of time, before the first messages are sent.

Timeout is only relevant for synchronous messages. It defines how long the XI adapter waits for the synchronous response message before returning a MessageExpired exception.

Properties Related to Outbound Processing

Name

Description

xiadapter.outbound.numberRetries.default

Default: 3

This, and the next two properties described below control the guaranteed delivery of XI messages between the Integration Server and the Adapter Engine.

It is only relevant for asynchronous messages.

This property defines how often an asynchronous message with quality of service Exactly Once (In Order) should be resent in the case of a delivery error.

xiadapter.outbound.retryInterval.default

Default: 300000 (5 minutes)

The property defines how long the messaging system waits between each retry.

xiadapter.outbound.persistDuration.default

Default: 2592000000 (30 days)

The property specifies how long a message should be persisted in the message database of the messaging system.

The value must be greater than the retry interval multiplied by the maximum number of configured retries.

In the case of duplicate detection, the messages should be persisted for the same period of time as the message is persisted in the Integration Server. The default value is 30 days.

Only messages with expired persist durations can be deleted from the database or archived and subsequently deleted.

It can happen that message throughput in the Adapter Engine is so high that the database volume is not able to store all asynchronous messages for the predefined period of time (30 days). In this case, the persist duration value needs to be decreased to a value that allows the messages to be kept in the database for the configured period of time, before the first messages are sent.