Before you upgrade your instance, take the steps described here (such as backing up important data) to help ensure that your upgrade is successful.
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.
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 in to various databases. Here are a couple of examples:
Before starting your upgrade, be sure to remove any plugins you've installed. For those plugins that aren't compatible with the version you're upgrading to, you'll 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. The latest versions of Jive-supported plugins are available from the Jive Community.
For more on managing plugins, see Adding and Removing Plugins.
The following list will help you prepare for upgrading from pre-7.0 releases.
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 on SSL Support, see Installing and Configuring SSL Support. Here's an example of how to install a certificate:
openssl s_client -connect yourserver.example.com:443 -showcerts > sam.cert
/usr/local/jive/java/jre/bin/keytool -import -alias jiveSamCert -file sam.cert -keystore /usr/local/jive/java/jre/lib/security/cacerts
Move your existing startup configurations into the new unified format. Using the "jive setup" command will provide 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.
Jive Software recommends that you first test the upgrade on a UAT 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.