Contents
Open Media Service Options
This section describes the configuration options for the Open Media Interaction Service Application object. To set various configuration options for the application, use the
Options tab of the
Properties
dialog box and use the following information as a guide.
esp Section
esp-response-timeout
- Default Value: 2000
- Valid Values: Integer values from 100 to 10000
- Description: Specifies the response timeout, in milliseconds, for the External Service Property (ESP) service. If the client’s ESP handler does not handle a request within the specified period, MIL will send the fault message as a response.
general Section
agent-place
- Default Value: [none]
- Valid Values: A string representing an existing system Place (a Place that is not used by an Agent).
- Description: Used to connect to the Interaction Server to be able to perform ad-hoc features.
period
- Default Value: 60
- Valid Values: A valid integer.
- Description: Seconds to wait before a reconnection attempt. This option applies to all the QIL and MIL back-end connections after a GIS restart.
reconnectionAttempts
- Default Value: 1
- Valid Values: A valid integer.
- Description: Number of reconnections to attempt in case of connection or disconnection. This option applies to all the QIL and MIL back-end connections after a GIS restart.
log Section
omsdk-console
- Default Value: info
- Valid Values: false, debug, info, warn, error, fatal
- Description: Level and size of traces to display on the standard output.
omsdk-file
- Default Value: info, mil.log, 10, 20
-
Valid Values: <level>, <file_name_root>, <file_max_size>, <file_number> [, zip]
- <level>: false, debug, info, warn, error, fatal
- <file_name_root>: A valid path to a file name.
- <file_max_size>: Maximum file size, in MB.
- <file_number>: Number of files for the rolling logs.
- [, zip]: Specifies compressed log files (optional).
- Description: Specifies how to store traces to a file.
omsdk-msgsrv
- Default Value: off
- Valid Values: off, debug, info, warn, fatal
- Description: Specifies level and size of this server’s logging traces for the MessageServer centralized log. If this option is not specified, this server does not log to MessageServer.
server Section
type
- Default Value: openmedia
- Valid Values: openmedia
Warning
Do not change this value. Changes made to the type option of the server Section are not supported.settings Section
enable-attached-data-byte-array
- Default Value: true
- Valid Values: true, false
- Description:
Specifies the conversion method for binary data within ESP (External Service Property) requests and responses.
- If set to true, then MIL (the Media Interaction Layer) converts binary data from requests to an array of bytes (byte[]). MIL also expects that binary data in responses will be of the same type.
- If set to false, the MIL coverts binary data to an ArrayList of objects with class Byte. MIL also expects that binary data in responses will be of the same type.
use-esp
- Default Value: true
- Valid Values: true, false
- Description: When set to true , specifies that you use a low-level ESP service in MIL.
use-lca
- Default Value: false
- Valid Values: false
- Description: If set to true , specifies that you use a low-level LCA service in MIL.
Warning
Do not change this value. Changes are not supported.ucs Section
ucs-identify-create-contact
- Default Value: false
- Valid Values: true, false
- Description: Triggers the UCS (Universal Contact Server) service’s create() method. If this option is set to true , it directs UCS to create a new contact when a contact is not found, and to create a corresponding interaction.
workflow Section
request-timeout
- Default Value: 50000
- Valid Values: Integer values from 100 to 10000.
- Description: Specifies the request timeout for the Interaction Server service. If Interaction Server does not respond within the specified period (in milliseconds), then Open Media Server will throw a corresponding TimeoutException.
This page was last edited on October 14, 2014, at 13:26.
Comments or questions about this documentation? Contact us for support!