Command Line Interface, Technical Documentation for Release

Document created by gialyons on Dec 11, 2013Last modified by seth.purkerson on Nov 2, 2016
Version 2Show Document
  • View in full screen mode

Product / Feature name: Jive CLI Installer

Compatible with: Jive 7.0 Custom (On-Premises Private Cloud)

Release Date: December, 2013


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


What's changed / what's new:

  • Saves time tracking down configurations
    • The site-specific configurations you've always had to make at the command line when installing the Jive platform are now in one place so you can easily view and override them.
  • Provides tools for managing the platform
    • We provide a single command-line interface for starting/stopping services and configuring the startup environment.

Technical implications:

  • Security/Authentication: Reduces the number of times root users run Jive commands, resulting in fewer users with root user permissions.
  • Permission/Access:
    • Enables separation of roles in the IT environment: Some customers expressed they'd like to separate the root administration and application administration roles in their organization. We now enable you to install the application in a custom directory location other than the default/usr/local/jive, and run commands using a different user account than the default "jive" user. Whether you use this capability or not, the root user is no longer necessary for the routine operation of the platform.
  • Storage: None
  • Performance: None
  • Other:
    • Uses port 8080 for Jive-managed Apache HTTPD service: The Jive-managed Apache HTTPD service now must run on a non-privileged port, which is port 8080 by default.

Installation notes:

  • Preparing for a new installation
    • Make sure that all the machines you will be using for the Jive platform meet the system requirements. You will also want to review the root-level configuration requirements ahead of time if possible.
    • After you install the Jive RPM, run Jive setup to see if there are any outstanding issues with root-level configuration requirements.
    • After running jive setup enable services, configure them, and start them.


  • Preparing for an upgrade
    • Move your existing startup configurations into the new unified format. The "jive setup" command provides specific suggestions for how to do this. Allow some time during your upgrade for going through these suggestions. As with all upgrades, it is best practice to test on a staging instance first.
    • Remember that the jive-managed Apache HTTPD service now must run on a non-privileged port, which is port 8080 by default. Use the following instructions to make modifications with or without a load balancer:
      Production site with a load balancer:
      Change your load balancer's configuration to point to each webapp node's port 8080 instead of port 80.
      Upgrading a single-node test instance without a load balancer:
      Modify the jiveURL in the Admin Console before you upgrade to 7.0.0 by going to Admin Console: System > Management > System Properties and modifying the jiveURL system property. For example, if your test instance's jiveURL was previously set to, set it instead to Then go ahead with your upgrade to 7.0.0.