Jump to: navigation, search

iWD History Node Configuration Options

[server] Section

  • single-host-bind
  • Data Type—boolean
  • Description—Determines which address History Node listen on.
  • Valid values:
  • true—History Node will be listening only on the address specified in Server Info.
  • false—History Node will be listening on all available addresses on the machine (that is, 0.0.0.0)
  • Default value—false

[iWD] Section

  • processor-threads
  • Data Type—Integer
  • Description—Number of threads used for events processing
  • Valid values—Integer greater than 0
  • Default value—10
  • receive-timeout
  • Data Type—Integer
  • Description—Number of milliseconds since last event receive from JMS queue after which cached events will be flushed to the history DB
  • Valid values—Integer greater than 0
  • Default value—10
  • batch-size
  • Data Type—Integer
  • Description—Maximum number of events which will be saved at once in history DB. Note: one event translates to 1 or 2 rows written to the database (depends on configuration)
  • Valid values—Integer greater than 0
  • Default value—1000
  • stop-processing
  • Data Type—String
  • Description—Determines how History Node should handle stopped interactions' GTL events
  • Valid values—
  • keep—GTL events will be kept in History Node DB
  • remove—GTL events will be removed from History Node DB
  • Default value—keep
  • stop-processing-interval
  • Data Type—Integer
  • Description—Number of seconds defining frequency of the checking for stopped interactions.
  • Valid values—Integer greater than 0
  • Default value—60
  • stop-processing-delay
  • Data Type—Integer
  • Description—Number of minutes after which interactions stop processing event will be handled..
  • Valid values—Integer greater than 0
  • Default value—60
  • process-gtl
  • Data Type—Boolean
  • Description—Determines whether GTL history events should be processed and saved in history DB
  • Valid values—true, false
  • Default value—true
  • process-dm
  • Data Type—Boolean
  • Description—Determines whether DM events should be processed and saved in history DB
  • Valid values—true, false
  • Default value—true
  • migrate-schema
  • Data Type—Boolean
  • Description—Determines whether database schema should be migrated (i.e. updated) during application start
  • Valid values—true, false
  • Default value—false

[log] Section

  • level
  • Data Type—String
  • Description—Log level
  • Valid values—OFF, ERROR, WARN, INFO, DEBUG, TRACE and ALL
  • Default value—INFO
  • log-filename
  • Data Type—String
  • Description—The path to file where current events are logged
  • archive
  • Data Type—Boolean
  • Description—Determines whether to archive old events in separate files
  • Valid values—true, false
  • Default value—false
  • archived-log-filename-pattern
  • Data Type—String
  • Description—Required if archive is true. The filename pattern for archived files. If max-file-size is specified, rollover is size-based, and the pattern must contain %i for an integer index of the archived file. Otherwise rollover is date-based, and the pattern must contain %d, which is replaced with the date in yyyy-MM-dd form. If the pattern ends with .gz or .zip, files will be compressed as they are archived
  • archived-file-count
  • Data Type—Integer
  • Description—The number of archived files to keep
  • Valid values—Integer greater than or equal to 0 (zero means to keep infinite number of files)
  • Default value—5
  • max-file-size
  • Data Type—String
  • Description—The maximum size of the currently active file before a rollover is triggered
  • Valid values—The value can be expressed in bytes, kilobytes, megabytes, gigabytes, and terabytes by appending B, K, MB, GB, or TB to the numeric value. Example: 100MB, 1GB, 1TB
  • Default value— (unlimited)
  • time-zone
  • Data Type—String
  • Description—The time zone to which event timestamps will be converted
  • Valid values—The ID for a time zone, either an abbreviation such as PST, a full name such as America/Los_Angeles, or a custom ID such as GMT-8:00
  • Default value—UTC
  • log-to-console
  • Data Type—Boolean
  • Description—Determines whether to log events to the console
  • Valid values—true, false
  • Default value—false

[access-log] Section

  • log-filename
  • Data Type—String
  • Description—The path to file where current events are logged
  • archive
  • Data Type—Boolean
  • Description—Determines whether to archive old events in separate files
  • Valid values—true, false
  • Default value—false
  • archived-log-filename-pattern
  • Data Type—String
  • Description—Required if archive is true. The filename pattern for archived files. If max-file-size is specified, rollover is size-based, and the pattern must contain %i for an integer index of the archived file. Otherwise rollover is date-based, and the pattern must contain %d, which is replaced with the date in yyyy-MM-dd form. If the pattern ends with .gz or .zip, files will be compressed as they are archived.
  • archived-file-count
  • Data Type—Integer
  • Description—The number of archived files to keep
  • Valid values—Integer greater than or equal to 0 (zero means to keep infinite number of files)
  • Default value—5
  • max-file-size
  • Data Type—String
  • Description—The maximum size of the currently active file before a rollover is triggered
  • Valid values—The value can be expressed in bytes, kilobytes, megabytes, gigabytes, and terabytes by appending B, K, MB, GB, or TB to the numeric value. Example: 100MB, 1GB, 1TB
  • Default value—(unlimited)
  • time-zone
  • Data Type—String
  • Description—The time zone to which event timestamps will be converted
  • Valid values—The ID for a time zone, either an abbreviation such as PST, a full name such as America/Los_Angeles, or a custom ID such as GMT-8:00
  • Default value—UTC
  • log-to-console
  • Data Type—Boolean
  • Description—Determines whether to log events to the console
  • Valid values—true, false
  • Default value—false

Comment on this article:

blog comments powered by Disqus
This page was last modified on 14 March 2018, at 04:36.