Overview

This article provides an overview of the point upgrade (also known as a minor upgrade) process. It also outlines the essential considerations you need to make before deciding to upgrade as well as the scheduling considerations.

Information

IMPORTANT! Jive Hosting is unable to perform a rollback to an earlier version, should you encounter issues with a new version after an upgrade. For this reason, testing any customizations against the new version in your Internal Development instance before moving forward with a UAT (User Acceptance Testing) upgrade is critical. This will limit the amount of time your UAT and Production sites are out of sync due to issues encountered on UAT.

Scheduling the Upgrade

• You need to reach out to your Account Manager/Executive for scheduling the upgrades as per Planning a Jive Hosted Instance Upgrade. They will then help you in coordinating the upgrade efforts with the Professional Services team who will perform the upgrade.
• Upgrades are generally first performed for the UAT instance before moving to the Production instance. This can be different based on your requirements that you can discuss with your Account Manager/Executive.
• It typically takes 2-4 week's notice to secure a preferred time slot for the Production upgrade/Go-Live after the initial UAT instance upgrade, however, the actual timelines may differ based on your instance's needs and will be communicated by your Account Manager/Executive or the Professional Services team.

Hosting Process Overview

1. The site is put into Maintenance Mode.
   • During this time users visiting the site will see a simple message stating the site is currently undergoing maintenance.
   • If desired, you can set a custom maintenance page by using the Jive Cloud Admin Tool. You can view the instructions in the article Customizing the Maintenance Page Message.
2. Hosting performs a database backup.
3. RPM files on the instance are upgraded. This is required.
   • If your RPM files are not upgraded, the core functionality of your site will not work until they are.
4. WAR files are installed.
   • This pertains to stock WARs or custom WARs provided by our Professional Services team.
   • A series of upgrade tasks are performed, and the database is usually backed up automatically by the WAR deploy process.
5. The instance is restarted.
   • Any plugins which need to be updated to be compatible with the new version are also installed during this step.
6. The site is taken out of Maintenance Mode.
7. Hosting notifies you that the process is complete and invites you to test and validate the instance.

Note! The Production upgrade follows an identical process to the UAT upgrade and depending on how consistent the two instances are, you should see similar timings. If you are in doubt, please request a "Prod to UAT Data Refresh" through a support case before moving forward with the upgrade process.