Name

Description

messaging.connections

List of connection definitions with the following form:

(name=ApplicationName, messageListener=localejbs/MessagListenerBeanName, exceptionListener=localejbs/ExceptionListenerBeanName, pollInterval=60000, pollAttempts=10, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)

The application name and listener bean names must not be changed at any point.

The messaging system allows multiple applications to send and receive messages in parallel through a “virtual” connection per application. The default connections delivered with the installation are for the Adapter Framework, the Java Proxy Runtime, and several adapters.

The pollInterval and pollAttempts properties 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 J2EE service and the message and exception listener beans are implemented as part of J2EE 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 properties define the number of threads to be used to process messages in parallel for each queue type and for each connection definition.

messaging.system.defaultMaxConsumersPerQueue

Value type: Positive integer

Default: 10

This value is used when the maxConsumer values are omitted in the messaging.connections property.

messaging.jdbc.datasource

messaging.jdbc.autoConfigure

messaging.jdbc.supportsOpenSQL

messaging.jdbc.substituteEmptyString

messaging.jdbc.supportsScrollableResultSet

Default: jdbc/SAP/BC_XI_AF_MSG

Default: false

Default: true

Default: true

Default: false

These properties must not be changed.