Installing the Jive Linux 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:

Install the Package on All Nodes

You will need to install the Jive Linux package on the following nodes (installation order is irrelevant):

You should not create a jive user or a jive group (locally or in a remote authentication system) before installing because they are created for you automatically during install. If you manually create a jive user or a jive group, serious problems may occur when you administer or configure your instance later. Note that the jive user and jive group are both required for installation and normal operation and cannot be changed.

Installation Steps

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

  1. 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
  2. Copy the Jive application RPM package to the target system. 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_sbs.rpm root@targetsystem:/root
  3. Set open file limits for the Linux system(s) on which you're installing Jive. To set how many file handles the jive user can have open at a time, add the following lines to the appropriate configuration file.
    File Lines to add

    jive soft nofile 8192

    jive hard nofile 65535

    For Activity Engine and Search nodes, use the following higher limits:

    jive soft nofile 100000

    jive hard nofile 200000


    session required /lib64/security/

  4. Set options for the installation on the nodes listed below. To set these, use the Linux export command, which sets them
 as environment variables. All package-level variables are enabled by setting
 their value to a non-empty string.
    On this node Run this command(s) as root
    Activity Engine node export JIVE_APPLICATION_NOSERVICE=1
    On-Premise Search node


    Web app nodes export JIVE_APPLICATION_NOSERVICE=1
    Cache node export JIVE_APPLICATION_NOSERVICE=1
    Document Conversion node export JIVE_APPLICATION_NOSERVICE=1
    Note: If necessary, you can clear the variables with a command such as:
    Option Description Default
    JIVE_APPLICATION_NOSERVICE Prevents the RPM from starting the web application services immediately after installation. Note: We strongly recommend setting this option before you install the package on the Activity Engine, Document Conversion, Search, cache nodes, and one of the web application nodes if you're using more than one. By default, the application starts immediately after installation; so you only want one instance running after installation--the one on your primary web application node. You'll be able to navigate to that node in a web browser after installing and starting up so that you can continue with the application setup wizard. All other nodes should be stopped during that time.
    JIVE_SEARCH_SERVICE Sets one-time initialization that needs to occur for Search to work properly. Configures and starts Search service.
  5. Install the Jive application RPM using an rpm command such as the following. The i, h, and v options are provided to indicate install with hash indicators, and to be verbose during the installation. (Your copy of the Jive RPM file -- here, jive_sbs.rpm -- will have a slightly different name.)
    rpm -ivh jive_sbs.rpm

    Note: You can find out more about rpm command syntax at the Fedora web site.

    The following truncated example shows the output for a successful installation using the preceding command. In this case, the Jive RPM package was in the /root directory of the target host.

    [root@targethost ~]# rpm -ihv jive_sbs.rpm
    Preparing...                ########################################### [100%]
    Preparing clean installation.
    Pre-install tasks complete.
       1:jive_sbs               ########################################### [100%]
    Writing installation version.
    Jive post-install configuration complete.
    When it's finished, the installation program indicates that the post-install configuration is complete.
  6. 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.
  7. You're finished installing. After you have installed the Jive package on all of your nodes, you'll start the services as described in the following section.

Starting the Services

  1. Start the services on all of the nodes from root.
    On this node Run this command as root
    Activity Engine service jive-eae-service start
    Search service jive-search-service start
    Web app nodes 1 and 2

    service jive-application start

    service jive-httpd start

    Cache server(s) and cluster nodes service jive-cache start
    Document Conversion service jive-docconverter start
    If you did not enable JIVE_APPLICATION_NOSERVICE on the Activity Engine, Document Conversion, Search, and cache nodes as we strongly recommend, the Jive service will start automatically on the web application nodes.
  2. On the Activity Engine, Document Conversion, Search and cache server(s), run a chkconfig to permanently enable the service that you're running on each machine. This will ensure each node's service starts by default on a reboot. Note that on the web app node(s), run the chkconfig only if you have enabled JIVE_APPLICATION_NOSERVICE.
    On this node Run this command as root
    Activity Engine chkconfig jive-eae-service on

    service jive-system start

    Search chkconfig jive-search-service on

    service jive-system start

    Document Conversion chkconfig jive-docconverter on

    service jive-system start

    Cache server(s) and cluster nodes chkconfig jive-cache on

    service jive-system start

    Web app nodes 1 and 2

    chkconfig jive-application on

    chkconfig jive-httpd on

    service jive-system start

  3. Now you'll need to stop the services on all of the nodes except for the Activity Engine, Search, and your primary web application node, which you will use to walk through the Admin Console setup wizard in a web browser (in the next step). On the Document Conversion, cache nodes, and one of the web application nodes, run the following stop command:
    On this node Run this command as root
    Document Conversion service jive-docconverter stop
    Cache server(s) and cluster nodes service jive-cache stop
    Web app node 2

    service jive-httpd stop

    service jive-application stop

  4. 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.
  5. When you're finished with the setup wizard, you'll need to start the services, plus restart the primary web app node, as follows and in this order:
    On this node Run this command as root
    Document Conversion service jive-docconverter start
    Cache server(s) and cluster nodes service jive-cache start
    Web app node 2

    service jive-httpd start

    service jive-application start

    Web app node 1

    service jive-httpd restart

    service jive-application restart

  6. See Post-Installation Tasks for your next steps.