Before You Upgrade

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 in to various databases. Here are a couple of examples:

MySQL — Use the mysqldump tool
Postgres — Use the pg_dump tool

Remove Plugins Before Upgrading

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.

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.

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 on SSL Support, see Installing and Configuring SSL Support. Here's an example of how to install a certificate:

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
```

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 the new unified format

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.

Note that 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. 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.
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. Then go ahead with your 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 will need to add a node for the Search service. Make sure it meets the requirements specified in Hardware Requirements.

For Pre-5.0 Upgrades, Add an Activity Engine Node and Database

If you're upgrading from a version prior to 5.0, you will need to add a node and database for the Activity Engine. Be sure to read the Setting Up the Activity Engine topics and Setting Up a New Database before you begin upgrading.

Allow Time for Search Index Rebuilding

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.