Preparing for upgrade to or later

If you are upgrading to or later from an earlier version, you must take these steps before you start the upgrade to make sure the upgrade is successful.

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

If you are upgrading from an earlier version, see Preparing for upgrade from version earlier than 7.0. If you are upgrading to a version earlier than, see Preparing for upgrade from 7.0.x or 8.0.x.

Set the system parameters

  1. Set the system property to true or false.

    When the property is set to true, it means the cookie will only be transferred over HTTPS. When it is set to false, the cookie will be transferred even on HTTP. If this property is not set, you will not be able to login to the Admin Console after the upgrade.

  2. Delete the value for the jive.master.encryption.key.node system property. The value will be automatically repopulated after the upgrade.

    Not deleting the value of this system property may cause issues if you run the Jive upgrade on a node that was not defined as the master node previously. You should also verify that this property is deleted from all nodes.

For more information about Jive system properties, see Fine-tuning with system properties.

Back up your jiveHome directory

The jiveHome directory contains important information about your environment. The database connection information is stored there, as well as logs, cached attachments, your license file, and the local system database files (if used). You should back up this directory before upgrading.

Back up your database

You should back up your database before you upgrade. For now, the best way to manage database backups is to follow the recommendations of your DBA or the recommendations of your database software. There are a number of tools built into various databases. Here are a couple of examples:

  • MySQL: Use the mysqldump tool
  • Postgres: Use the pg_dump tool

Decide if you want historical analytics data

If you want to carry forward historical data for the User-to-User Interactions chart for Jive Analytics, then set the jive.cmr.summarize.interactions.import.history.enabled system property to true before upgrading. For more information, see System properties reference.

Remove plugins before upgrading

Before starting your upgrade, you should remove all the plugins you have installed. For those plugins that aren't compatible with the version you're upgrading to, you need to separately upgrade your plugin code (or get upgraded versions of the plugins from their developer), then install the upgraded versions after you've completed your Jive upgrade.

For more on managing plugins, see Customizing with plugins.

Allow time for search index rebuilding

We recommend that you first test the upgrade on a test instance to determine how long the search index rebuild will take. In some cases, it may take days to rebuild the index, depending on the size and activity of the community. Communities with large amounts of content and activity should allow adequate time for the search index rebuild before deploying an upgrade to production.

For more information on creating a test instance, see Creating test environment for upgrading.