At a Glance

Released on
03/04/2013
End of Life
03/04/2014
Improvements
1
Issues Resolved
6

Cascade Server 7.2.1

Cascade Server version 7.2.1 is a maintenance release containing various bug-fixes including bug-fixes related to index block caching and also an improvement related to preserving dynamic metadata field values when a metadata set is updated. This release is recommended for all organizations running any version of Cascade Server.

  View Requirements

Improvements

  • [CSI-34] - Map dynamic metadata between Metadata Sets if identifiers are the same

Issues Resolved

  • [CSI-495] - Index Block cache not updating when asset's start date is in future
  • [CSI-520] - Outdated Index Block rendering gets cached when asset is edited during the rendering
  • [CSI-526] - Site Copy - Dynamic metadata lost during copy if asset's Content Type and Metadata Set are part of the Site being copied
  • [CSI-527] - Metadata lost for Base Folder after using Site Migration Wizard
  • [CSI-528] - Editing Format through Page region does not return user to Page
  • [CSI-529] - Recycled Pages that have a draft that has a data definition but the draft page has no structured data cannot be purged from the database

Tomcat Configuration

Some changes have been made to the context.xml file inside Tomcat which enable behavior and logging related to "abandoned" database connections.  Abandoned connections are those which are idle and held by the same process for a specific amount of time.  These connections can be detrimental to Cascade performance. 

Clients who do not use the GUI installer to perform upgrades will not receive updates to their context.xml file.  We recommend manually adding these parameters to the data source configuration in the context.xml file which can be found in the <Cascade Installation Directory>/tomcat/conf directory.

Inside this file you should see something similar the following:

<Context path="">
      <!-- Default set of monitored resources -->
      <WatchedResource>WEB-INF/web.xml</WatchedResource>
      <!-- Uncomment this to disable session persistence across Tomcat restarts -->
      <Manager pathname=""/>
      <Resource        
            auth="Container"
            name="jdbc/CascadeDS"
            type="javax.sql.DataSource"
            driverClassName="net.sourceforge.jtds.jdbc.Driver"
            username="username"
            password="password"
            maxActive="50"
            maxIdle="10"
            maxWait="3000"
            url="jdbc:jtds:sqlserver://host:port/schema_name;SelectMethod=cursor"
      />
      <ResourceLink global="cascadeSchemaName" name="schemaName" type="java.lang.String"/>
</Context>

After adding the new data source attributes, your context.xml file should look like:

<Context path="">
      <!-- Default set of monitored resources -->
      <WatchedResource>WEB-INF/web.xml</WatchedResource>
      <!-- Uncomment this to disable session persistence across Tomcat restarts -->
      <Manager pathname=""/>
      <Resource        
            auth="Container"
            name="jdbc/CascadeDS"
            type="javax.sql.DataSource"
            driverClassName="net.sourceforge.jtds.jdbc.Driver"
            username="username"
            password="password"
            maxActive="50"
            maxIdle="10"
            maxWait="3000"
            url="jdbc:jtds:sqlserver://host:port/schema_name;SelectMethod=cursor"
            removeAbandoned="true"
            removeAbandonedTimeout="300"
            logAbandoned="true"
      />
      <ResourceLink global="cascadeSchemaName" name="schemaName" type="java.lang.String"/>
</Context>

Notice the 3 attributes that have been added: removeAbandoned, removeAbandonedTimeout, and logAbandoned.

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.

Warnings:

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

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