Services Layer

Between the web application nodes and the database nodes are a number of services that are critical to Jive.

Caching Service

The caching service provides object caching for the web application nodes, dramatically reducing the load on the database nodes. Use "cache" when starting or enabling this service in the Jive command-line interface (CLI). For more information about how caching works in a high-availability system, be sure to read Configuring the Cache Servers for High-Availability.

Activity Engine Service

The Activity Engine nodes provide specialized functionality for attention streams, recommendations, and the personalized Inbox. Use "eae"when starting or enabling this service in the Jive CLI.

Search Service

The search nodes offload a significant amount of overhead from the web application nodes, providing personalized, contextual search results for content. Use "search" when starting or enabling this service in the Jive CLI.

Note: In an HA configuration, you'd also need two Ingress Replicator nodes for the Ingress Replicator service. Use "ingress-replicator" when starting or enabling this service in the Jive CLI. For more on this, see Required Nodes for an On-Premise HA Search Service.

Document Conversion Service

The document conversion service enables rich previews and collaboration around Microsoft Office and PDF documents without having to open up a desktop client. Use "docconverter" when starting or enabling this service in the Jive CLI.

Storage Service

The storage layer dramatically reduces the amount of load on the database nodes.

For an illustration of a basic deployment, see Jive Enterprise Architecture.