Jump to: navigation, search

Interaction Server DAP

These options are configured on the main Interaction Server DAP.

settings Section



     


blob-chunk-size

Default Value: 1024
Valid Values: 1024-65535
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Specifies, in bytes, the amount of data to be read from a BLOB in each iteration.

connection-string

Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide.

connections

Default Value: 5
Valid Values: 1-50
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Specifies the number of concurrent connections to the database.

dbprotocol

Default Value: odbc
Valid Values: odbc
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

To enable an ODBC connection, this option must be present, with its value set to odbc. This option has no other use.

odbc-string

Default Value: No default value
Valid Values: Any valid ODBC connection string
Changes Take Effect: After restart of Interaction Server
Introduced: 8.5.100.18

Configuring a connection string is described on the ODBC Connection page of the eServices Deployment Guide. Consult the description of the connection-string option.

queue-size

Default Value: 20000
Valid Values: 50-65535
Changes Take Effect: Immediately
Introduced: 8.5.100.18

Specifies the maximum number of requests that can be stored in the queue of requests to the database.

reconnection-pause

Default Value: 5000
Valid Values: 100-300000
Changes Take Effect: Immediately
Introduced: 8.5.100.18

Specifies, in milliseconds, the time between repeated attempts to connect to the database, test database integrity, initialize database values, or reconnect to the database when a connection is lost.

This page was last edited on October 31, 2016, at 18:42.
Comments or questions about this documentation? Contact us for support!