As of Friday October 16th, access to restricted content on this site now requires you to log in with your Genesys account. If you don't have an account, you can request one at these locations: Request MyPartner Portal Account or Request My Support Account.
Jump to: navigation, search

[messages] Section

This section must be called messages.

db_binding

Default Value: false
Valid Values: true, false
Changes Take Effect: After restart

Specifies whether Message Server uses DB Server’s binding functionality when storing messages in the database.

db_storage

Default Value: false
Valid Values: true, false
Changes Take Effect: After restart

Specifies whether log messages are stored in a database.

Important
For the value true to take effect, you must include an appropriate Database Access Point in the Connections of the Message Server Application object.

dbthread

Default Value: true
Valid Values: true, false

true Uses internal database thread. This is the preferred method.
false Uses separate DB Server, as in releases prior to 8.5.

Changes Take Effect: After restart

Specifies how Message Server accesses the Log Database. If set to true, Message Server server attempts to launch a database client process locally that will access the Log Database using the Log DAP. This is the preferred method of accessing a database starting in 8.5.

If set to false, Message Server attempts to use a remote DB Server, as in previous releases. Genesys recommends that you use this method only with older Genesys applications.

log-queue-exp-time

Default Value: 0
Valid Values: 0—604800 (7 days)
Changes Take Effect: Immediately

Specifies for how long (in seconds) the previously received log messages will be stored in the log queue during a connection failure between Message Server and DB Server. When the timeout expires, Message Server will delete all expired messages from the queue. The default value of 0 means no expiration time.

log-queue-response

Default Value: 0
Valid Values: 0—65535
Changes Take Effect: Immediately

Specifies the maximum number of log messages that Message Server may send to DB Server from its queue in a single request when the connection between them is restored after a failure. The next portion of log messages will be sent upon confirmation response from DB Server with respect to the previous request. The default value of 0 means an unlimited number of log messages can be sent to DB Server in a single request. Setting this option to a very small value may negatively affect system performance.

log-queue-size

Default Value: 0
Valid Values: 0—4294967295
Changes Take Effect: After restart

Specifies the maximum number of log messages to be stored in a log queue during a connection failure between Message Server and DB Server. When the maximum is reached, arrival of each new log message will cause removal of the oldest message from the queue until connection to DB Server is restored.

The default value of 0 means an unlimited number of log messages can be stored in the log queue.

This page was last edited on January 31, 2020, at 14:32.

Feedback

Comment on this article:

blog comments powered by Disqus