Configuring Activity Engine

To configure the Activity Engine, you first install the Jive package on the Activity Engine node as described in Installing 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 Activity Engine page. For the lists of the additional settings that you can adjust on the Activity Engine, refer to Activity Engine properties reference.

Deploying multiple Activity Engines

You can deploy multiple Activity Engine cores if a single Activity Engine core is not 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.

Queue depth settings

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:

• Command: Used when specific tasks need to be scheduled and run on the Activity Engine node, such as a user rebuild or Recommender refreshed.
• Processing: Activities sent from the application to the Activity Engine are immediately queued on the processing queue. This writes the activity to the non-user specific streams (All Stream, Profile Stream, Place Stream) and enqueues to the UserStream.
• UserRebuild: When a user rebuild task is running, this queue fills with activities that need to be processed to rebuild the user's stream.
• Upgrade: During the upgrade from a previous Jive version to 5.0, the upgrade queue fills up with activities that need to be processed, so that old content is displayed in the new stream format.
• UserStream: Activities sent from the application to the Activity Engine are enqueued on the User Stream queue after being processed by the processing queue. The processing queue builds up all the information necessary to write the activity to individual user streams or communication streams that might be following the content or person on the activity.
• Shredder: If Jive Genius is enabled, this queue fills up with items as activity comes in and needs to be shredded before being sent to Jive Genius.
• Recommender: If Jive Genius is enabled, this queue fills up with requests for recommendations bound for Jive Genius.

Expiration settings

The expiration settings control the number of days an activity remains in a given stream.