Preparing for upgrade from version earlier than 7.0

If you have a version of Jive from before Jive 7.0, you need to upgrade to Jive 7.0 or Jive 8.0 first before upgrading to Jive 9.0.

You can upgrade to Jive 9.0 from Jive 7.0.x and Jive 8.0.x only. If you have a version of Jive from before Jive 7.0, you need to upgrade to Jive 7.0 or Jive 8.0 first before upgrading to Jive 9.0. For information on what's changed from 7 or 8 to 9.0, see Learn What's Changed from Jive 7 & 8 to Jive 9 on Worx at https://community.aurea.com/docs/DOC-206932.

CAUTION:
You must be upgrading from version 4.5.0 or later.

For preparations for upgrade from 7.0.x or 8.0.x instance to 9.0.x, see Preparing for upgrade from 7.0.x or 8.0.x.

For 5.0 and 6.0 upgrades, prepare for the new Jive CLI installer and interface

The following list will help you prepare for upgrading from pre-7.0 releases.

The CLI installer introduces the following changes, discussed in detail below:

  • Jive started enforcing a strict policy on HTTPS certificate checking
  • You can use jive setup to move your existing configurations into the new unified format
  • HTTPD now runs on 8080, which is a non-privileged port

For the overview of the CLI installer, see CLI installer overview.

Jive now enforces a strict policy on HTTPS certificate checking

Jive now enforces a strict policy on HTTPS certificate checking, and will not accept self-signed certificates without you adding them to the application Java keystore. If you are upgrading from Jive 6.0.3 and earlier, and you encounter communication errors between the self-signed application and the Jive server, you need to add the certificate to the Java keystore.

For more information on SSL Support, see Installing and Configuring SSL Support in the Oracle Help Center at http://docs.oracle.com/javaee/1.4/tutorial/doc/Security6.html.

Here's an example of how to install a certificate:

  1. Download the certificate from the server and save the resulting certificate to a file called sam.cert: 
    openssl s_client -connect yourserver.example.com:443 -showcerts > sam.cert
  2. Import the certificate into the local keystore on the Jive server: 
    /usr/local/jive/java/jre/bin/keytool -import -alias jiveSamCert -file sam.cert -keystore /usr/local/jive/java/jre/lib/security/cacerts

Use jive setup to move your existing configurations into new unified format

It is required to move your existing startup configurations into the new unified format. Using the jive setup command provides specific suggestions for how to do this. You should 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.

HTTPD now runs on 8080, which is a non-privileged port

Remember that the jive-managed Apache HTTPD service now must run on a non-privileged port, which is port 8080 by default. You can 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 web app node's port 8080 instead of port 80.
Note: Note that SSL is now required on a load balancer.
Upgrading a single-node test instance without a load balancer
Modify the jiveURL in the Admin Console before you upgrade 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 http://communitytest.mycompany.com, set it instead to http://communitytest.mycompany.com:8080.

After you made the necessary modifications, you can continue the upgrade.

For pre-6.0 upgrades, add a node for On-Premise Search (optional)

If you're upgrading from a version prior to 6.0 and you have chosen to implement On-Premise search instead of Cloud Search, you need to add a node for the Search service. Make sure it meets the requirements specified in Hardware requirements. For more information on available Search services, see Understanding Jive Search.

For pre-5.0 upgrades, add an Activity Engine node and database

If you're upgrading from a version prior to 5.0, you need to add a node and database for the Activity Engine. For more information, see Setting up Activity Engine and Setting up new databases before you begin upgrading.