Jump to: navigation, search

iWD Section



     


allow-listed-attributes

Default Value: No default value
Valid Values: Valid attribute name(s), or _ALL_
Changes Take Effect: Immediately
Introduced: 9.0.016.09

Specifies the (comma-separated) list of attributes to be shown in global task list history. For example, specific desired system-generated or strategy-generated attributes. You can specify _ALL_ to allow all attributes.

batch-size

Default Value: 1000
Valid Values: Valid number of events
Changes Take Effect: After restart


Maximum number of events which will be saved at once in history DB. Note: one event may translate to multiple rows in the database.

block-listed-attributes

Default Value: No default value
Valid Values: Valid attribute name(s), or _ALL_
Changes Take Effect: Immediately
Introduced: 9.0.016.09

Specifies the (comma-separated) list of attributes to be filtered out of global task list history. For example, unwanted system-generated or strategy-generated attributes. You can specify _ALL_ to block all attributes except those listed in the allow-listed-attributes list.

migrate-schema

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


Determines whether database schema should be migrated (i.e. updated) during application start.

process-dm

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


Determines whether datamart events should be processed and saved in history DB.

process-gtl

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


Determines whether GTL history events should be processed and saved in history DB.

processor-threads

Default Value: 10
Valid Values: Valid number of processor threads
Changes Take Effect: After restart


Number of processor threads used for events processing.

receive-timeout

Default Value: 10
Valid Values: Valid number of miliseconds
Changes Take Effect: After restart


Number of miliseconds since last event received from JMS queue after which cached events will be flushed to the history DB.

stop-processing

Default Value: remove
Valid Values: Keep or remove
Changes Take Effect: After restart


History Node behavior after receiving "Stop processing" event from Interaction Server. If "keep", interaction history will be preserved; if "remove", interaction history will be purged after specified timeout.

stop-processing-delay

Default Value: 60
Valid Values: Valid number of minutes
Changes Take Effect: After restart


Number of minutes since the stop processing event received from JMS queue after which interaction history will be purged from database.

stop-processing-interval

Default Value: 60
Valid Values: Valid number of seconds
Changes Take Effect: After restart


Frequency of history purge in seconds.

taskEventLimit

Default Value:
Valid Values: Any positive integer
Changes Take Effect: After restart
Introduced: 9.0.013.11

The maximum number of events that will be migrated from the Events Log database. If the parameter is not defined or it is set to 0 (zero) the migration process will try to process all existing events of Events Log database.

This page was last edited on January 26, 2018, at 08:53.
blog comments powered by Disqus