Configuring the Options Tab for QIL

In Configuration Manager, configuration options are stored within section folders. The section folders and options are stored on the Options tab; you click a section to bring up its options. Options are described in detail below.

general Section

agent-place

• Default Value: ““

• Valid Values: A string representing an existing system Place (a Place that is not used by an Agent ).

• Changes Take Effect: After restart.

• Description: Used to connect to Interaction Server, to make it possible to perform ad-hoc features.

log Section

omsdk-console

• Default Value: info

• Valid Values: false, debug, info, warn, error, fatal

• Changes Take Effect: After restart.

• Description: Level and size of traces to display on the standard output.
  Non-mandatory.

omsdk-file

• Default Value: info, omsdk.log, 10, 20

• Valid Values: <level>, <filename>, <max filesize>, <max filenumber>

• <level>: false, debug, info, warn, error, fatal
  
• <file name>: correct path to a file name
  
• <max file size>

  maximum file size in MB
  

• <max file number>: number of files for the rolling logs
  

• Changes Take Effect: After restart.

• Description: Used to put OMSDK trace messages in the file. If this option is not specified, OMSDK logging to the file is not used.
  Non-mandatory.

omsdk-msgsrv

• Default Value: off

• Valid Values: off, debug, info, warn, error, fatal

• Changes Take Effect: After restart.

• Description: Specifies the level and size of OMSDK to display in the MessageServer centralized log. If this option is not specified, OMSDK logging to MessagerServer is not used.
  Non-mandatory.

log-filter Section

For Filtering Sensitive Data to Logs

default-filter-type

• Default Value: copy

• Valid Values: copy, hide, skip

• Changes Take Effect: After restart.

• Description: Specifies the default way of logging key/value information:
  • copy—copy each pair’s key and value to the log.
  • hide—copy keys to the log, but replace values with strings of asterisks.
  • skip—do not copy key/value pairs to the log.

log-filter-data Section

For Filtering Sensitive Data to Logs

<key-name>

• Default Value: copy

• Valid Values: copy, hide, skip

• Changes Take Effect: After restart.

• Description: Specifies how to log key/value pairs for the specified <key-name> key:
• copy—copy key/value pairs to the log.
• hide—copy the key to the log, but replace values with strings of asterisks.
• skip—do not copy key/value pairs to the log for the specified key.

settings Section

enable-attached-data-byte-array

• Default Value: true

• Valid Values: true, false

• Changes Take Effect: After restart.

• Description: This option specifies the conversion method for binary data in ESP requests and responses.
  • If set to true, QIL converts binary data from a request to an array of bytes (byte[]) and expects that in responses, binary data will be of the same type.
  • If set to false, QIL converts binary data to an ArrayList of objects with class Byte. Same for responses.

workflow Section

request-timeout

• Default Value: 5000

• Valid Values: <Any positive integer>

• Changes Take Effect: After restart.

• Description: Used for specifying a request timeout for the Interaction Server service. If an answer is not received from IxnServer within the specified period, a corresponding TimeoutException will be thrown. Specified in milliseconds.
  Non-mandatory.