Required External Components

In addition to the required servers on which you'll install the Jive RPM, you'll need to set up several external components.

The following external components are required in a production installation of Jive.

At a minimum, you'll need set up a database server for the core web application, Activity Engine, and Analytics. For detailed information about requirements and setup, see Database Configuration.
Load Balancer
Because you need multiple application nodes to run Jive in production, you'll need to set up a load balancer to manage incoming traffic.
Shared Storage

For non-trivial deployments, we recommend that you provision a unit of shared storage on a SAN/NAS to store binary content. This single unit of storage must be mountable on all the web application nodes in your installation, and should be easy to expand because the amount of content in Jive grows over time. This shared storage will be used both for storing binary content such as uploaded documents, and for storing the output after the Search server has indexed the text content. For more information on binary storage see Configuring a Binary Storage Provider. To estimate the amount of disk space you will need for this component, see Sizing Binary Storage.

Content Delivery Network (Recommended)

If you are deploying a large, globally-dispersed public community (typically one used for customers, vendors, and employees), Jive Software strongly recommends using a third-party content delivery network (CDN) tool. A CDN service can help your Jive pages load faster for globally-dispersed community users.

If you are deploying a large, globally-dispersed internal community (typically one used for employees only), you may also be able to use a CDN to help Jive pages load faster for remote users.

For assistance with deploying a CDN and selecting an appropriate vendor, please contact Support.