Jump to: navigation, search

Backend Server service:wes Section

wes.connector.chatServer.requestPoolSize

Default Value: 10

Valid Values: 1 — 99

Changes Take Effect: After start/restart

Description: Specifies the number of threads used for processing requests to Chat Server. Use the following formula to calculate the recommended value: <peak_chat_sessions_count> / (<refreshPeriod> * 5) <refreshPeriod> - The value of the wes.connector.chatServer.refreshPeriod option. <peak_chat_sessions_count> - The maximum number of simultaneous chat sessions planned for one Backend Server.

wes.connector.chatServer.queueKey

Default Value: 1:webme

Valid Values: Key defined in the endpoints:<tenantID> section of the Chat Server application.

Changes Take Effect: Immediately

Description: The key in the connected Chat Server that specifies the entry point for the Chat Routing strategy (Interaction Queue). For instance, in the Environment tenant this would be a key defined in the endpoints:1 section of the Chat Server application.

wes.connector.chatServer.queueWebengagement

Default Value: WebEngagement_Chat

Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The minus, dot, and underscore characters. Space characters are allowed inside the string only (not at the beginning or at the end).

Changes Take Effect: After restart

Description: The name of the Interaction Queue that is used as the entry point to the Chat Routing strategy. This queue must correspond to the queue specified in the key set in the wes.connector.chatServer.queueKey option.

wes.connector.chatServer.identifyCreateContact

Default Value: 3

Valid Values: 1, 2 or 3

Changes Take Effect: Immediately

Description: Controls whether a contact for a created chat interaction should be identified and/or created in the Universal Contact Server database (transferred as attached data to Chat Server, which is responsible for details of processing). The valid values have the following effect:

  • 1 — Do not try to identify this contact and do not try to create it
  • 2 — Try to identify this contact, but do not create it if absent
  • 3 — Try to identify this contact and create it if absent

The default value is applied if the option is absent or specified incorrectly.

wes.connector.chatServer.refreshPeriod

Default Value: 2

Valid Values: 1 — 5

Changes Take Effect: After start/restart

Description: Specifies how often, in seconds, to refresh the chat content in the chat widget.

wes.connector.chatServer.requestTimeout

Default Value: 5

Valid Values: 1 — 10

Changes Take Effect: After start/restart

Description: Specifies the timeout, in seconds, for requests to Chat Server. The default value is used if the option is absent or specified incorrectly.

wes.connector.chatServer.chatSessionRestoreTimeout

Default Value: 30

Valid Values: 5 — 300

Changes Take Effect: After start/restart

Description: Specifies the time, in seconds, during which the Backend Server tries to restore a broken chat session. A session can be broken, for example, if Chat Server crashes.

wes.connector.interaction.copyUserData

Default Value: rule;attempt_number

Valid Values: all, no, <key_name1;key_name2;...key_nameN>

Changes Take Effect: Immediately

Description: Specifies the mode Web Engagement uses to copy UserData from the Open Media webengagement interaction to the chat or webcallback engagement interaction. The following explains the results for each valid value:

  • all — All keys are copied.
  • <key_name1;key_name2;...key_nameN> — Only the keys in the list are copied.
  • no — No UserData is copied
  • Option is omitted, or has a blank or empty value — No UserData is copied.
Important
Trailing or leading spaces are considered part of the key name.

wes.connector.interactionServer.wcb.queueSubmit

Default Value: New

Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The minus, dot, and underscore characters. Space characters are allowed inside the string only (not at the beginning or at the end).

Changes Take Effect: Immediately

Description: Specifies the Interaction Queue that is used as the entry point to webcallback routing strategy.

This page was last modified on July 11, 2014, at 12:53.

Feedback

Comment on this article:

blog comments powered by Disqus