Installing the Jive Package and Starting Up

Jive is compatible with a number of hardware configurations as well as network topologies. To understand the recommended deployment configuration for an on-premise installation, see Jive Enterprise Architecture.

What You'll Need

To install Jive using the RPM, you'll need the following:

At least six servers that meet the minimum specified hardware requirements described in System Requirements.
These servers should be running Linux. See the System Requirements for supported versions.
A bash shell to run the install commands.
SSH access to the servers so you can copy the RPM there for installation.
Ability to become the root user on the servers where the installation is performed, commonly via SSH, or less commonly through user interface access such as VNC.
Note: If you want to run a non-standard installation, you could separate installation tasks into root user and non-root user tasks. You'd need a root user to complete the Pre-Installation Requirements as Root on CLI, and this root user would have to create a non-root user who can run the installation. For more on how to create a non-root user see Installing Jive with Non-Root User.
Make sure you have installed the packages described in RPM Dependencies by Operating System and you complete the Pre-Installation Requirements as Root on CLI. They include copying the Jive and pdswf RPMs to the servers and modifying a few configuration files.

Install the Package on All Nodes

You will need to install the Jive Linux package on the following nodes. You can install the RPM on these nodes in any order, but use the Installation Overview for our recommended order.

Activity Engine node
Search node
Web Application nodes (2 or more, where node 1 is the primary Web Application node)
Cache server
Document Conversion node

Installation Steps Using the Jive CLI

The following installation steps are the most common approach to installing the Jive platform:

From the command line, access the target host as root. For example, the following illustrates using the ssh command to access the server at targethost as the root user.
```
joe@joesbox ~ $ ssh root@targetsystem
root@targethost's password:
Last login: Mon Feb 14 14:00:56 2011 from joesbox.example.com
```
If you haven't already copied the Jive application RPM to each server and application node in your Jive environment, then you should do it now.
Here's an example using the Linux scp command to copy the package from a computer named "joesbox" to a target system at "targetsystem":
```
scp -v joe@joesbox:/Users/joe/jive.rpm root@targetsystem:/root
```
Install the Jive application RPM on all nodes using an rpm command such as the following. The U, h, and v options are provided to indicate install/upgrade with hash indicators, and to be verbose during the installation. (Your copy of the Jive RPM file -- here, jive.rpm -- will have a slightly different name.)
```
rpm -Uvh jive.rpm
```
When the installation finishes, the Jive CLI installer asks you to become a jive user and run jive setup, which you can do by using the following command. For more on this, see Using jive setup.
```
su - jive
jive setup
```
Address any configuration issues and suggestions that jive setup provides. Re-run jive setup until you get the setup ok message.
Set up your Core application, Activity Engine, and Analytics (optional) databases using Setting Up New Databases. If you'll be using a database whose driver is not included, ensure its driver is in the application's classpath by following the steps in Database Prerequisites.
After you have installed the Jive package and run jive setup on all of your nodes, you can enable the services as described in the next section.

Enabling the Services

Enable the services on all of the nodes as a jive user.

Note: You can run jive enable --help to see what services are available to enable, or jive status -v to see all of the services and whether they're enabled or disabled.

On this node	Run this command as jive user
Activity Engine	`jive enable eae`
Search	`jive enable search`
Web application nodes	`jive enable webapp` `jive enable httpd`
Cache server(s) and cluster nodes	`jive enable cache`
Document Conversion	`jive enable docconverter`

After enabling the correct service(s), re-run jive setup. For more on this, see Using jive setup. Do this so the Jive CLI installer can detect any service-specific startup properties that need to be set:
```
jive setup
```
Once you get the setup ok message on your node, you can start the enabled services on Jive.
```
jive start
```
With a supported web browser, navigate to http://<hostname>/, where hostname is the DNS-resolvable name of the server where you installed the Jive application on your primary web application node. There, you will be prompted to finish configuring the Jive application via the Admin Console setup wizard. If you plan to populate your community with users synchronized from your LDAP implementation, the setup screens are included in this wizard.
See Post-Installation Tasks for your next steps.