Post-Upgrade Tasks

After you have upgraded, there are a few key issues to be aware of:


Your production instance is typically set up to both send email notifications (SMTP) and access an email account (Email Monitor) or server (Advanced Incoming Email). You'll definitely want to temporarily change these settings in your test production instance; otherwise, you may find that the new test instance generates email notifications that look like they're coming from your production instance. This can be very confusing to end users, and might end up unnecessarily burdening your email servers.

To make this problem less painful:

If you had customized email templates, they are not overwritten during an upgrade. We recommend testing them after an upgrade to ensure your customizations have been maintained.


You'll definitely want to change the jiveURL system property to match the URL at which you're hosting the test instance. The jiveURL is used throughout the app to render links. If you do not change this property, you will find that links to content in your test instance redirect you back to production. Additionally, this will help people recognize when they're using the test instance instead of production.


This is VERY IMPORTANT: make sure you disable the Analytics module on the test server. Otherwise, you will have two instances, production and test, writing data to the same Analytics database. This can cause data corruption and ETL task failures. Additionally, if you leave the analytics settings in place and run a major upgrade, you may break analytics functionality on the production server by upgrading the analytics database schema to the new version. You can, of course, set up a new database for analytics for your test instance. Just make sure you do one or the other.


Video keys are meant to work only with a single instance. Remove the video keys from the test instance to ensure that you do not "confuse" the video provider and break video functionality on your production instance.