Select language:

Background documentation Properties for XPI Service: AF Core 

The following properties belong to the service XPI Service: AF Core




Default: jdbc/SAP/BC_XI_AF

This property must not be changed.


Default for AS Java: ts

JNDI name of the AS Java transaction manager.

This property must not be changed.


Value is in minutes.

Default: 1440 (i.e. once a day)

The AF Core service tries to remove persisted IDMapper entries with expired persist durations from the database at system startup and then repeatedly after the configured time interval.


Value type: Boolean

Default: true

This property can be used to disable the audit log functionality of the AF Core service.

This property must not be changed.


Possible values: cpa or registered

Default: cpa

This property specifies how the adapter monitor tries to identify the available adapters. If the value is set to cpa, it checks which adapter type metadata schemas are available in the CPA Cache service.

The list of available adapters can also be generated. This list is based on the registered adapters of the AF Core service adapter monitor.

This property must not be changed.


Value type: Value in milliseconds.

Default: 15000 (15 seconds)

It specifies the timeout value for the cluster communication in AS Java. Even though the default value of 15 seconds should be sufficient for the adapter monitoring functionality, this value may be increased in cases where you are experiencing cluster timeout exceptions of the cluster communication mechanism.


Value type: Boolean

Default: true

These properties specify for which components and adapters within the adapter framework the performance measurement (JARM) should be performed.

This property must not be changed.


Value type: Integer

Default: 5

This property specifies the maximum number of connections from the adapter framework to the central monitoring server.


Value type: Value in milliseconds

Default: 600000 (10 minutes)

This property specifies the timeout for an existing connection from the adapter framework to the central monitoring server.


Value type: Value in milliseconds

Default: 5000

This property specifies the maximum time a call waits for an available connection. After the specified time, the call fails and an exception is raised.


Value type: Boolean

Default: true

This property specifies if the information whether a channel is started or stopped is cached in memory to optimize performance.

This property must not be changed.


Value type: Integer

Default: 25

This property configures the number of process status entries kept in memory for each channel in communication channel monitoring.


Value type: Value in days

Default: 180

This property specifies how long history entries for the channel activation status should be kept in the database. Entries older than the specified number of days are deleted by a daily cleanup job.


Type: Time of day

Default: 02:30:00

This property specifies the time of day at which the daily cleanup job for history entries for the channel activation status runs.


This property specifies a list of connection definitions with the following form:

(name=global, messageListener=localejbs/AFWListener, exceptionListener= localejbs/AFWListener,, pollInterval=60000, pollAttempts=60, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=5, Rqst.maxConsumers=5)

In the SAP NetWeaver PI installation environment the message listener bean names must not be changed at any point.

The global property set defines the defaults for all adapter connections (queues). The name of the connection is retrieved from the CPA cache. You can set specific values by adding a property set for the respective adapter connection.

The pollInterval and pollAttempts parameters define how often and with which retry interval the messaging system tries to retrieve the listener beans from JNDI at system startup. This is required because the messaging system is implemented as a Java service and the message and exception listener beans are implemented as part of Java applications, which are started in a second phase during server startup. In the case of a very slow server startup, it may be necessary to increase the pollInterval or pollAttempts values in order to successfully start the four queues for sending and receiving the synchronous and asynchronous messages.

The maxConsumer parameters define the number of threads to be used to process messages in parallel for each queue type and for each connection definition.

More information: Java Service Properties that May Require Changes.


Type: Boolean

Default: false

This property enables the measurement of performance data for the Adapter Engine.


Type: Integer

Default: 500

This property specifies the maximum number of cache objects for performance data.


Type: Boolean

Default: true

This property enables the message overview function.


Type: Integer (minutes)

Default: 15

This property specifies the minutes for the periodical execution of the aggregation job for the message overview.


Was this page helpful to you?