Upgrading ViewsFlash |
Upgrading from ViewsFlash 3.5 or higher
ViewsFlash 5 requires new license keys. Before deploying it, email sales@cogix.com to request an upgraded license key. The key must be installed in the servlet parameters, usually stored in viewsflash.properties or in web.xml.
Read the release notes and if any ViewsFlash servlet parameters need to be changed, do so now. Read also Upgrading Style Templates.
ViewsFlash does not coexist simultaneously with earlier releases. If you have two or more instances of ViewsFlash sharing the same database, shut down all instances before upgrading. When you upgrade, all data is upgraded automatically. Backup the database before upgrading.
After downloading the ViewsFlash.war file, examine its WEB-INF/web.xml file and compare it to your deployed web.xml. If they are identical, you can simply redeploy the new war file. If you have made changes to your web.xml file, the easiest way to upgrade is to unpack the war file, replace the web.xml file with yours, repack the war file, and redeploy it. Alternatively, you can stop the application, save web.xml, redeploy the new war file, restore web.xml, and restart the application.
If you are not running on a database, your style templates will be upgraded automatically; you may want to backup the ViewsFlash/viewsflash/styles2 directory before upgrading if you've changed any of the standard styles. If you are running on a database, new styles are installed automatically. Existing styles that need to be upgraded automatically are listed by the ?Diagnose=1 command, which includes a link to a command that will upgrade templates.
Test your installation as described in the Installation section and troubleshoot if necessary.
If you have not made changes to the templates that need to be upgraded as listed by Diagnose=1 command, use this command to upgrade them: ?cmd=upgradestyles.
Upgrading from versions older than ViewsFlash 3.5