| Administering the Community / Setting Up the Activity Engine | |
To configure the Activity Engine, you will first install the Jive package on the Activity Engine node as described in Installing the Jive Package and Starting Up. You can then configure the basic settings that control Jive's connection to the Activity Engine's core processes on the page. The table below lists the additional settings that you can adjust on the Activity Engine.
To set any of these properties, as the jive user, run the following: jive set <property> <newvalue>
| Property | Purpose | Default Value |
|---|---|---|
| eae.core.coreAddress | Address of the Activity Engine server. | localhost |
| eae.core.corePort | Port of the Activity Engine server. | 7020 |
eae.core.coreMinWorkerThreads |
Minimum number of threads to listen for incoming socket connections from the Jive web application. | 4 |
| eae.core.coreMaxWorkerThreads | Maximum number of threads to listen for incoming socket connections from the Jive web application. | 2048 |
| eae.core.user-recency-enabled | Controls whether or not only active users will have their streams populated. | true |
| eae.core.user-recency-timeout | The age in milliseconds after which a user will be considered inactive. | 2592000000 (30 days) |
| eae.core.user-recency-buffer | Update user recency time no more than once in this time period in milliseconds. | 86400000 (1 day) |
| eae.core.remove-old-entries-time-after-midnight | When to allow the tasks that remove old items from the stream to run (after midnight, in milliseconds). For example, a value of 7200000 will allow the tasks after 2 A.M. If you want the tasks to run on a set interval (not just during a time window), set this to 0 and set remove-old-entries-buffer to 24 hours (in milliseconds = 86400000). | 7200000 |
| eae.core.remove-old-entries-period | The window in milliseconds following remove-old-entries-time-after-midnight in which the old item deletion tasks will run, OR how often to run the tasks in milliseconds if remove-old-entries-buffer is set to 24 hours. For example, the default values will allow the tasks to run once between 2 A.M. and 3 A.M. | 3600000 |
| eae.core.remove-old-entries-buffer | Extra buffer time to allow the old item deletion tasks sufficient time to run. If you want the tasks to run on a set interval (not just during a time window) set this to 24 hours (in milliseconds = 86400000) and set remove-old-entries-time-after-midnight to 0, then set remove-old-entries-period to the desired interval. | 600000 |
| eae.core.log-monitor-directory | The path (absolute or relative to service configuration directory) where performance monitoring logs are saved. | var/monitoring |
| eae.core.log-monitor-period | The frequency in milliseconds that samples are written to the monitoring logs. | 60000 |
You can deploy multiple Activity Engine cores if a single Activity Engine core will not be enough to handle your volume of traffic. Do this by setting up the new Activity Engine core with the same settings as the first Activity Engine core, and adding the new address to the Activity Engine configuration in the Admin Console.
The queue depths displayed on the Activity Engine page of the Admin Console show the number of items awaiting processing by the Activity Engine node. When an activity is sent to the Activity Engine, the activity is queued and processed as quickly as possible. Each queue, or group of queues, serves a specific purpose: