At a Glance

Released on
End of Life

Next Release: 7.12.3
Previous Release: 7.12.1

Cascade Server 7.12.2

This version adds support for selecting destinations on scheduled and on-demand Publish Set, Target, and Site publishes; support for MySQL 5.6; and a new Query API for creating targeted queries to find data in Velocity.

  View Requirements

Locator Tool Query API

A new search query API has been added to the Locator Tool which allows Velocity Format writers to load and filter assets based on a number of properties including metadata field values, asset type, site, assigned content type, and assigned metadata set.  Results can also be sorted by a particular property, limited to a maximum number, limited to only those that are publishable/indexable, and more.

This feature continues our efforts to allow Format developers to load only the assets that they need and to eliminate the use of large inefficient index blocks for page rendering.

Destinations for Scheduled Publishing

Publish Sets, Sites, and Targets can now be scheduled to publish to specific Destinations. On the edit screen, users now have the option to select all enabled Destinations or select from a list of a available Destinations. 

scheduled destinations

Additionally, the publish tab for these assets will now display a list of Destinations to select from instead of publishing to all enabled Destinations.

MySQL 5.6 Support (and End-of-Life for MySQL 5.0)

Support for MySQL 5.6 has been added.  Please take a look at the Upgrade Guide below for specific instructions about upgrading to 7.12.2 and to MySQL 5.6.

MySQL 5.0 is no longer supported beginning with version 7.12.2. If you are currently running MySQL 5.0, you must upgrade to MySQL 5.1, 5.5, or 5.6 prior to upgrading Cascade Server to 7.12.2+. 


  • [CSI-812] - Query API to Velocity


  • [CSI-811] - Support for MySQL 5.6
  • [CSI-813] - Select Destinations for Publish Sets, Target on-demand publishes; select Destinations for Publish Set, Target, and Site scheduled publishes

Upgrading MySQL 5.6

Cascade 7.12.2 is the first release that supports MySQL 5.6.  Versions prior to 7.12.2 will not run agains MySQL 5.6 so you will need to upgrade your Cascade software before pointing it to a server running MySQL 5.6.

We recommend:

  1. Stop Cascade
  2. Upgrade your database server to MySQL 5.6 or install a copy of your database to a new MySQL 5.6 server
  3. Upgrade Cascade 7.12.2
  4. Point Cascade to your MySQL 5.6 server
  5. Start Cascade

First Time Installation?

Be sure to import our default database schema prior to installing Cascade Server for the first time. Then follow our standard installation instructions.

Upgrade Steps

  1. Shut down your currently running Cascade Server instance.
  2. Before you upgrade, we strongly recommend that you back-up your production database as well as set up a test instance and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.
  3. Read the release notes and upgrade guides for all releases between your version and the latest version.
  4. If your current version of Cascade is earlier than 7.0, then you must use the full installation instructions.
  5. If your current version of Cascade is 7.0 or later, you can perform a full installation or upgrade in place using the ROOT.war installation.

MySQL 5.6 driver library updated in 7.12.2 or later

Organizations that use the ROOT.war upgrade method and are upgrading from 7.12.1 or earlier to 7.12.2 or later and use MySQL 5.6 must manually update the driver library in tomcat/lib folder from mysql-connector-java-5.1.18-bin.jar to mysql-connector-java-5.1.31-bin.jar. The file mysql-connector-java-5.1.31-bin.jar can be obtained by downloading ZIP version of Cascade Server.

EhCache library changes on upgrades to 7.10.2 or later

Organizations that use the ROOT.war upgrade method and are upgrading from 7.10.1 or earlier to 7.10.2 or later must remove the ehcache-core-*.jar and slf4j-api-*.jar from the ${CATALINA_BASE}/lib of Tomcat.

Database optimization on upgrades to 7.8.2 or later

Organizations upgrading to 7.8.2 or above for the first time may notice a delay during the initial startup accompanied by messages like these in the log file:

2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned assets...
2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned Data Definition nodes...
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Deleted 7 orhpaned Data Definition nodes
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 11:54:57,350 INFO  [OptimizeDatabaseServiceImpl] Deleted 14 more orhpaned Data Definition nodes
2014-01-01 12:02:30,529 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 12:02:58,724 INFO  [OptimizeDatabaseServiceImpl] Deleted 0 more orhpaned Data Definition nodes
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Finished clearing 224 orphaned Data Definition node record(s)
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Fixing Structured Data with missing owner entity property
2014-01-01 12:03:29,712 INFO  [OptimizeDatabaseServiceImpl] Found 211 broken Structured Data nodes
2014-01-01 12:03:32,451 INFO  [OptimizeDatabaseServiceImpl] Fixed a total of 9 assets with broken Structured Data nodes
It is important that the Cascade Server process not be stopped during this time. Once the orphaned Data Definition nodes have been removed, the application will start up normally.

Rebuild search indexes on upgrade

If you are upgrading from Cascade Server 7.4.1 or later, you should rebuild search indexes after the upgrade is complete and the application is running. To do so, navigate to System Menu -> Utilities -> Search Indexing, check the Rebuild Index? checkbox and then click Submit.


You must upgrade to at least Cascade Server 5.5 before upgrading to Cascade 6 or Cascade 7.

Contact Hannon Hill Support ( if deploying Cascade Server for the first time in a load-balanced environment as this will require a special license.