NewsGator Activity Publisher Job
NewsGator Activity Publisher Job (1 of 2)
|
Module |
Core |
|
|
First release |
v2.1 |
|
|
Function |
Publishes social events from an asynchronous event queue to the Activity Feed. This job is intended to run continuously. It polls the activity event queue every 5 seconds and write aggregated events to the Activity Feed. Job 1 of 2. |
|
|
Consequences of stopping |
No activity events from the activity queue get published to the activity stream. Microblogs and certain events may get published. |
|
|
Data per cycle |
All (all new events since the last time one of the Publisher jobs polled the activity event queue). |
|
|
Default interval |
1 minute |
|
|
Minimum Recommended interval |
1 minute |
|
|
Maximum Recommended interval |
1 minute |
|
|
Usage notes |
The job runs for one minute, then stops. The reason for having two Publisher jobs is so that there is always at least one up and running, as one remains running as the other restarts. Setting this to a longer interval results in activity not getting posted to the stream for most of that interval - it gets posted the next time one of the Publisher jobs runs. |
|
NewsGator Activity Publisher Job (2 of 2)
|
Module |
Core |
|
|
First release |
v2.1 |
|
|
Function |
Publishes social events from an asynchronous event queue to the Activity Feed. This job is intended to run continuously. It polls the activity event queue every 5 seconds and write aggregated events to the Activity Feed. Job 2 of 2. |
|
|
Consequences of stopping |
If only job 2 of 2 is stopped, events based on the activity queue gets published slower and users may experience lag. |
|
|
Data per cycle |
All (all new events since the last time one of the Publisher jobs polled the activity event queue). |
|
|
Default interval |
1 minute |
|
|
Minimum Recommended interval |
1 minute |
|
|
Maximum Recommended interval |
1 minute |
|
|
Usage notes |
See above. |
|