Skip to main content

Installing

This section includes information on how to install the pieces that make up the Jive platform.

You can use the following instructions to prepare for and complete an on-premise Jive installation. Jive production installations require multiple servers, a database, and expert knowledge of your enterprise systems; for details, refer to System requirements. Note that these instructions are a template and your requirements will be specific to your community. You should also have a plan to back up your installation, as described in Backup and storage considerations.

Note: If you want to do a quick install for evaluation or development purposes, see Quick installation for Jive evaluation.

If you are installing any of Jive's add-ons, such as Jive for Outlook, check the documentation for their separate system and installation requirements at https://docs.jivesoftware.com/.

  • CLI installer overview The Jive command-line interface (CLI) installer provides a better way to start, stop and configure an installation, and gives you more flexibility.

  • Startup property reference The following tables list the startup properties available for your Jive installation, grouped by the service they support.

  • Connecting through proxy server Certain core components and features require Jive to access information from across the firewall.

  • Preparing to connect to Jive Hosted services To ensure a successful installation, you need to make sure you can connect successfully to several component services that are hosted by Jive.

  • Managing client certificates If your corporate network uses client certificates for authentication, you need to configure Jive so it can authenticate properly.

  • Installation overview When you install the Jive platform, you perform several steps in a specific sequence.

  • CLI installation tasks Installation tasks include installing the RPM, using jive setup, and copying the configuration to other nodes in clustered environments.

  • Setting up Document Conversion To convert content from its native format into a form that can be previewed without altering the original document, you need the Document Conversion module.

  • Setting up cache server Use the same Linux package that you used to install the application servers to install a separate cache server that application servers can use in a cluster.

  • Setting up conversion machine The document conversion machine should be a dedicated machine that isn't used for any other Jive services.

  • Post-installation tasks Here you can find sample configurations and script examples common to long-term operation of a Jive installation.

  • Installing on cluster Production configuration requires you to set up a clustered environment.

  • Adding features with plugins By purchasing optional plugins offered by Jive Software, you can enhance Jive with powerful features not included by default.

  • Configuring delegated authentication In delegated authentication, Jive delegates authentication to your user identity provider.

  • Configuring binary storage provider Storing binary content data in a location outside the database is efficient and scalable. For production Jive systems, we recommend using a shared file system for storing all binary content.

  • Backup and storage considerations Here you can find considerations for reliable storage and backups for your system.

  • Configuring application with the Setup wizard From the Setup wizard, you enter information about your license, database connection, user identity system, email system, and system admin credentials.

  • Quick installation for Jive evaluation Use this quick installation procedure to set up a small instance of Jive for evaluation and testing purposes only.