To automatically start the synchronize action and retrieve tweets from a user's timeline, create a new fetch task by following these steps. The connector runs each fetch task automatically, based on the schedule that is configured in the configuration file.
To retrieve information from a user's timeline
In the [FetchTasks]
section of the configuration file, specify the number of fetch tasks using the Number
parameter. If you are configuring the first fetch task, type Number=1
. If one or more fetch tasks have already been configured, increase the value of the Number
parameter by one (1). Below the Number
parameter, specify the names of the fetch tasks, starting from zero (0). For example:
[FetchTasks] Number=1 0=MyTask
The fetch tasks that you configure are run in sequence. To run tasks in parallel, set the TaskThreads
parameter.
Below the [FetchTasks]
section, create a new TaskName section. The name of the section must match the name of the new fetch task. For example:
[FetchTasks] Number=1 0=MyTask [MyTask]
In the new section, set the following parameters:
TimelineScreenName
|
The screen name of the user from which to retrieve tweets. |
(Optional) Due to limitations of the Twitter API, the connector can only retrieve the most recent 3200 tweets made by the user. On the initial synchronize cycle, the connector retrieves the 3200 most recent tweets. On incremental synchronize cycles the connector retrieves the tweets made since the last synchronize cycle (up to a maximum of 3200). Micro Focus therefore recommends that you schedule the fetch task so that there are fewer than 3200 tweets between synchronize cycles. To specify how often the task runs, set the parameter ScheduleRepeatSecs
.
ScheduleRepeatSecs
|
The interval (in seconds) from the start of one scheduled synchronize cycle to the start of the next. |
(Optional) If the connector machine is behind a proxy server, you might need to specify the host name, port, user name, and password for your proxy server by setting the parameters ProxyHost
, ProxyPort
, ProxyUsername
, and ProxyPassword
.
|