Jump to: navigation, search

Deploy Digital Messaging Server with a Twitter Channel

For a Twitter channel, you need two installation packages:

  • Digital Messaging Server
  • Genesys Cloud API Driver for Twitter

The Driver adds Twitter-specific features to Digital Messaging Server and does not require its own Application object in the Configuration Server database.

You can also create a Custom Media Channel Driver.

Important
Tweets from a customer who has a protected twitter account will not enter Digital Messaging Server even if the business twitter account is authenticated to view the protected tweets from the customer’s twitter account.

Prepare the Twitter Channel

  1. Deploy Digital Messaging Server.
  2. Run the installation for Genesys Driver for Use with Twitter, selecting the desired Digital Messaging Server object.
  3. Locate the driver-for-twitter-options.cfg configuration file in the \<Digital Messaging Server application>\media-channel-drivers\channel-twitter directory.
  4. In Genesys Administrator Extension, open your Digital Messaging Server Application, go to the Options tab, and import driver-for-twitter-options.cfg, selecting No in response to Do you want to overwrite the existing data?

Configure the Options

Set the following options:

Section Option Example
channel-twitter-*anyname* driver-classname com.<your domain>.mcr.smserver.channel.twitter.cloud.TwitterCloudDriver
fetch-image true
gsa-account-name

Note: This field should be setup once and never change without first communicating with Genesys team.
CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-api-key

Note: This field should be setup once and never change without first communicating with Genesys team.
CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-batch-limit 200
gsa-batch-reserve-time 60
gsa-channel-id Note: This field should be setup once and never change without first communicating with Genesys team.

CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-channel-name Note: This field should be setup once and never change without first communicating with Genesys team.

CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-user-name Note: This field should be setup once and never change without first communicating with Genesys team.

CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-user-password Note: This field should be setup once and never change without first communicating with Genesys team.

CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

gsa-url-base Note: This field should be setup once and never change without first communicating with Genesys team.

CRITICAL: Changing this field without taking care will stop the connection between your
Social Engagement system and Twitter, and may cause a loss of data.

inbound-route 101:twitter_queue
itx-resubmit-attempts 3
itx-resubmit-delay 30
itx-submit-timeout 10
reconnection-timeout 180
sampling-period 10
x-debug-mode false
x-inbound-media Twitter
x-submit-own-all false


There is also a [log] section that holds the usual log options, which are described in the Configuration Options Reference Manual.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 15 August 2018, at 22:57.