Jive's new installer,
the command-line interface (CLI), provides a time-saving way to track down configurations
and manage the platform.
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
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
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 - jivejive 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
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
Web application nodes
Cache server(s) and cluster nodes
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:
Once you get the setup ok message on your node, you can start
the enabled services on Jive.
With a supported web browser, navigate to http://<hostname>/,
where hostname is the DNS-resolvable name of the server where you installed the
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.