Properties Related to Connections and JDBC

Use

The Following Properties are Related to Connections and JDBC

Name	Description
messaging.connections	List of connection definitions with the following form: `(name=ApplicationName, messageListener=localejbs/MessagListenerBeanName, exceptionListener=localejbs/ExceptionListenerBeanName)` The application name and listener bean names must not be changed at any point. Multiple applications can send and receive messages in parallel by using a "virtual" connection for each application. The provided default connections are for the Adapter Framework, the Java Proxy Runtime, and several adapters.
messaging.connectionParams	List of parameters for each connection definition: Note This property only applies to B2B adapters (CIDX, RNIF, BC, and Marketplace) for communication with the business partner. `(name=global, pollInterval=60000, pollAttempts=10, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)` Example `messaging.connectionParams=(name=global, param1=x, param2=y, ...)(name=BCAdapter, Send.maxConsumers=7)` The `pollInterval` and `pollAttemtps` 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 `pollAttemtps` 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. If you use the default name global , changes to any of these parameters will be valid for all connection definitions. If you use the name of a specific connection definition, changes will only apply to this particular definition. More information: Java Service Properties that May Require Changes .
messaging.jdbc	Parameter: (datasource=jdbc/SAP/BC_MSG) This property must not be changed.

Name

Description

messaging.connections

List of connection definitions with the following form:

(name=ApplicationName, messageListener=localejbs/MessagListenerBeanName, exceptionListener=localejbs/ExceptionListenerBeanName)

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

Multiple applications can send and receive messages in parallel by using a "virtual" connection for each application. The provided default connections are for the Adapter Framework, the Java Proxy Runtime, and several adapters.

messaging.connectionParams

List of parameters for each connection definition:

Note

This property only applies to B2B adapters (CIDX, RNIF, BC, and Marketplace) for communication with the business partner.

(name=global, pollInterval=60000, pollAttempts=10, Send.maxConsumers=5, Recv.maxConsumers=5, Call.maxConsumers=10, Rqst.maxConsumers=10)

Example

messaging.connectionParams=(name=global, param1=x, param2=y, ...)(name=BCAdapter, Send.maxConsumers=7)

The pollInterval and pollAttemtps 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 pollAttemtps 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.

If you use the default name global , changes to any of these parameters will be valid for all connection definitions. If you use the name of a specific connection definition, changes will only apply to this particular definition.

More information: Java Service Properties that May Require Changes .

messaging.jdbc

Parameter: (datasource=jdbc/SAP/BC_MSG)

This property must not be changed.