Pre-installation requirements as root on CLI

You need to complete some pre-installation tasks before installing the Jive package. These tasks need to be completed by a root user.

The pre-installation tasks outlined in the following steps apply to all supported operating systems.
Note: Clock synchronization using NTP is required. If you are using VMware, see Timekeeping best practices for Linux guests at the VMWare Knowledge Base at http://kb.vmware.com/kb/1006427.
  1. Obtain the Jive RPM and copy it to each server and application node in your Jive network.
    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

    For more information, see Hardware requirements and Preparing to connect to Jive Hosted services.

  2. Obtain the pdfswf RPM on the PDF2SWF 0.9.1 for Jive Document Converter page at https://static.jiveon.com/docconverter.
  3. As root, modify /etc/security/limits.conf and add the following values.
    jive    soft    nofile  100000
    jive    hard    nofile  200000 
    Note: If you are using a non-root user to install Jive, then replace "jive" with that username. For more information, see Installing Jive without root access.
  4. Once you've made the change, log out and back in again as the jive user.
  5. If required, as root, modify /etc/sysctl.conf and add the following values.
    net.core.rmem_max = 16777216
    net.core.wmem_max = 16777216
    net.ipv4.tcp_wmem = 4096 65536 16777216
    net.ipv4.tcp_rmem = 4096 87380 16777216
    kernel.shmmax = 2147483648
    Note: You only need to modify these values if your existing configuration does not meet or exceed them.
  6. In /etc/sysctl.conf, increase the vm.max_map_count to fit your implementation. The Jive Setup wizard calculates a minimum required value based on how much memory is available. You may need to use a higher value than recommended depending on usage patterns or overall usage. The line in sysctl.conf should look like this:
    vm.max_map_count = 500000
  7. Run sysctl -p.