Jump to: navigation, search

Backend Server service:wes

DevGuide2.png Purpose: Lists the options available for the service:wes section of the Genesys Web Engagement Backend Server. This section defines the server-side engagement functionality; it covers the creation of media interaction and the messages used for the transfer from the client-side application to the Genesys media servers.

Note: Some default values are filled by the Provisioning Tool.

wes.connector.chatServer.identifyCreateContact

  • Default Value: 3
  • Valid Values: 1, 2 or 3
  • Changes take effect: When the application is started or restarted.
  • 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 identify and do not create contact
    • 2 — Identify, but do no create contact
    • 3 — Identify and create contact (if absent)
The default value is applied if the option is missed or specified incorrectly.

wes.connector.chatServer.requestTimeout

  • Default Value: 5
  • Valid Values: 1 — 30
  • Changes take effect: When the application is started or restarted.
  • Description: Specifies the timeout (in seconds) for the sendRequest operation in Chat Server. The default value is used if the option is absent or specified incorrectly.

wes.connector.chatServer.queueKey

  • Default Value: 1:webme
  • Valid Values: Key defined in the section endpoints:<tenantID> of the ChatServer application.
  • Changes take effect: When the application is started or restarted.
  • Description: Specify the key of a queue used by the Chat Server. For instance, for the Environment tenant, this would be a key defined in the endpoints:1 section of the ChatServer application.

wes.connector.chatServer.queueWebengagement

  • Default Value: WebEngagement_ChatRouting.webme_chat.WebME_ChatQueue
  • Valid Values: Letters A to Z and a to z. Numbers 0 through 9. The minus, dot, underscore characters. Space characters are allowed inside the string only (not at the beginning or at the end).
  • Changes take effect: When the application is started or restarted.
  • Description: Name of the Interaction Queue object used to place chat interactions for routing with the Web Engagement Chat Routing strategy.

wes.connector.interaction.copyUserData

  • Default Value: no
  • Valid Values: all, no, <key_name1;key_name2;...key_nameN>
  • Changes take effect: When the application is started or restarted.
  • 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, underscore characters. Space characters are allowed inside the string only (not at the beginning or at the end).
  • Changes take effect: When the application is started or restarted.
  • Description: Message for the queue used to submit newwebcallback interactions. Standard for the Web API Server.
This page was last modified on November 4, 2013, at 17:19.

Feedback

Comment on this article:

blog comments powered by Disqus