Jump to: navigation, search

Configuring the Options Tab for MIL

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.

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 traces of OMSDK in 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 MessageServer 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.

esp Section

esp-response-timeout

  • Default Value: 2000
  • Valid Values: <Any positive integer>
  • Changes Take Effect: After restart.
  • Description: Used to specify response timeout for ESP service. If client’s ESP handler does not manage to handle a request during a specified period, MIL sends a fault message as a response. Specified in milliseconds.

settings Section

enable-attached-data-byte-array

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: After restart.
  • Description: Specifies how to perform TKVList to Map conversion (for attached data), namely how to convert KVTypeBinary values. The possible options are ArrayList of Byte*byte[]. By default, the option is true and KVTypeBinary is converted into ArrayList of Byte.
    This option specifies the conversion method for binary data in ESP requests and responses.
    • If set to true, MIL 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, MIL converts binary data to an ArrayList of objects with class Byte. Same for responses.

use-esp

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: After restart.
  • Description: Set to true, specifies that you use low-level ESP service in MIL.
    Non-mandatory

use-lca

  • Default Value: true
  • Valid Values: true, false
  • Changes Take Effect: After restart.
  • Description: Set to true, specifies that you use low-level LCA service in MIL.
    Non-mandatory

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

ucs Section

ucs-identify-create-contact

  • Default Value: false
  • Valid Values: true, false
  • Changes Take Effect: After restart.
  • Description: This option is used in MILUCSManager.saveInteraction(MILInteraction interaction) class. When saving interaction into UCS, this parameter shows whether to identify contact and create new one if it is not found.
    If (IdentifyCreateContact==true)
    {- Identify contact and create new contact if not found;- Interaction.ContactId = found or created Contact.Id}
    else {Interaction.ContactId = UserData.ContactId}
    


    Non-mandatory

 

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on January 7, 2014, at 08:04.