Jump to: navigation, search

Deploy Social Messaging Server with a Twitter Channel

Overview

For a Twitter channel, you need two installation packages: Social Messaging Server and Genesys Driver for Use with Twitter. The Driver adds Twitter-specific features to Social 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
Unlike some other eServices components, Social Messaging Server does not require Java Environment and Libraries for eServices and UCS.
If you have primary and backup Social Messaging Servers, you should not use the same Twitter Application for both. Instead, create a Twitter Application for each Social Messaging Server
.

  1. Deploy Social Messaging Server.
  2. Run the installation for Genesys Driver for Use with Twitter, selecting the desired Social Messaging Server object:
    Select a Social Messaging Server object
  3. Locate the driver-for-twitter-options.cfg configuration file in the \<Social Messaging Server application>\media-channel-drivers\channel-twitter directory.
  4. In Configuration Manager, open your Social 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?

Set the following options:

Section Option Example
channel-<any name>

driver-classname

com.genesyslab.mcr.smserver.channel.twitter.TwitterDriver

inbound-route

101:twitter_queue

reconnection-timeout

20

ucs-in-use

false

ucs-request-timeout

60

x-access-token

167466696-lksFBUeqs0WmybyhkbpCUWmiE28fEboIjjU91if1

x-access-token-secret

RGB2LlWD0UkZl7eKvO2fvIsiEQtEX6CAVmlZ7s1w

x-inbound-media

twitter

x-consumer-key

PBevSLoxNVkpBtPGx5NfsA

x-consumer-secret

8wZKKOSA5dtBqnMj3vcbdsUnpNZCcEwKJEBRyYFpxs

x-debug-mode

false

x-registered-app-name
Release 8.1.0 and earlier only

MyApp

x-source-nick-name
Release 8.1.1 and later

false

x-submit-own-all

Twitter-Channel

x-ucs-relations-chunk

200

x-user-id
Release 8.1.0 and earlier only

197203329

channel-<any name>-monitor-<any name>

cleanup-relations

7

control-str-public

off

control-str-user

off

get-direct-messages

false

get-home-timeline

true

get-mentions

false

itx-submit-timeout
Release 8.1.1 and later

false

itx-resubmit-attempts
Release 8.1.1 and later

4

itx-resubmit-delay
Release 8.1.1 and later

65

refresh-period-channel-account

30

refresh-period-followers

10

refresh-period-friends

20

sampling-history

216000

sampling-period

9000

str-follow-<any name>

49028817

str-language

en es

str-track-<any name>

fail,disappointed,frustrated

endpoints:*tenant_dbid*

endpoints:*tenant_dbid*

Twitter Inbound Queue
This is the name of the queue in the sample Twitter Business Process that is supplied with Genesys Social Messaging Management.

settings

hide-attached-data

10

media-accounts-monitoring

true

subject-size

40

workspace-location

c:\smserv-workspace\



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

Next Steps

Review the sample queries supplied with the Driver for Use with Twitter.

This page was last modified on November 20, 2018, at 10:25.

Feedback

Comment on this article:

blog comments powered by Disqus