Group 65Go to Hannon Hill
All Collections
Installation & Upgrades
Upgrading with the Full Installer

Upgrading with the Full Installer

The following steps can be used to upgrade your Cascade CMS installation using a full installer.
Ryan Griffith avatar
Written by Ryan Griffith
Updated over a week ago

Before Upgrading

Some upgrades require full installations in order to take advantage of updated technologies used by the application (Tomcat, JVM). Please verify what type of installation is required for the version you are upgrading to by referring to the Cascade CMS Release Notes.

Download

Download the appropriate installer for your operating system. Note: Linux/*nix users should download the ZIP file.

Upgrading

The following steps should be taken when performing an upgrade via the full installer:

  • Leave the current installation directory as is (you will need to reference files from the existing installation).
  • For Windows installations: remove any previous Windows Service prior to running the full installer.
  • Follow the full installation instructions for the appropriate operating system (Windows,  Mac OS X). Note: There is no GUI installer for Linux/*nix environments; instead please follow the instructions for Installation using the ZIP File.
  • When the installer prompts for the installation directory, be sure to select a new location on the hard drive. When prompted to enter database connection information, configure the application to point to the existing Cascade CMS database. Previous database connection information can be referenced from the old/existing tomcat/conf/context.xml file.

At this point, you'll need to manually apply any further customization you've made to Cascade including:

  • Customizations to the tomcat/conf/context.xml file not including the database configuration (which is set by the installer).
  • Customizations to the tomcat/conf/server.xml file not including the HTTP port (which is set by the installer).
  • Customizations to the tomcat/conf/web.xml file.
  • Copying custom Asset Factory plugins, Publish Triggers, custom authentication modules from the old/existing tomcat/webapps/ROOT/WEB-INF/lib directory to the new installation folder's tomcat/webapps/ROOT/WEB-INF/lib directory. Note: The tomcat/webapps/ROOT/WEB-INF/lib directory will not exist in the new installation until the application has been deployed at least one time. For this reason, the application will need to be started (make sure you can log in) and then shut down before copying custom JAR files.

IMPORTANT: The following files should not be copied from the old installation into the new installation as they can cause compatibility problems:

  • tomcat/conf/context.xml
  • tomcat/conf/server.xml
  • tomcat/conf/web.xml

Instead, they should be used only as a reference for updating the corresponding files in the new installation.

Did this answer your question?