Upgrading to Cascade Server 7.0 in a standalone Tomcat instance
- Download both the ROOT.war and the cascade-7.0.zip files. You’ll need the latter to add a few dependencies to your Tomcat that are necessary for 7.0.
- Stop Cascade Server
- Create a backup of your database (this is important prior to any upgrade!)
- Unzip the file cascade-7.0.zip. We’ll refer to
the location of the unzipped folder as
CASCADE_ZIPand we’ll refer to the location of your standalone Tomcat as
TOMCATfrom here forward.
- Copy any custom plug-ins (Publish Triggers, Custom
Authentication Modules, Asset Factory Plugins, Workflow Triggers)
TOMCAT/webapps/ROOT/WEB-INF/libdirectory into a temporary location. (**NOTE:** Only perform this step if your organization has created one or more custom JAR files. DO NOT copy the entire contents of the directory. If there are no custom JAR files to be copied, this step should be skipped.)
- Copy the database drivers (*jtds-.jar*,
mysql-connector-java--bin.jar, and ojdbc.jar)
TOMCAT/libdirectory. We only support running Cascade with the versions of the database drivers that we ship. Be sure to remove any older or different versions of these drivers from your
TOMCAT/libfolder as they could cause conflicts on startup.
- Copy ehcache-core-.jar and slf4j-api-.jar
TOMCAT/libdirectory. Be sure to remove any older or different versions of these libraries from
- Copy ehcache.xml from the
CASCADE_ZIP/tomcat/confdirectory into your
TOMCAT/confdirectory. If you’re running Cascade in a Load Balanced configuration, please refer to the instructions on the KB for configuring EhCache in a Load Balanced environment.
- Remove the
- Remove the Cascade ROOT.war and exploded ROOT
folder from your
- Copy the new ROOT.war file to your
If you’re using MySQL, open your
Add the following attributes to the
<Resource>element containing your database connection information:
validationQuery="SELECT 1" testOnBorrow="true"
&autoReconnect=trueoption from the connection string in the ‘url’ attribute.
Unzip the ROOT.war file in your
TOMCAT/webappsdirectory. It should unzip to just a ROOT directory.
If there were custom JAR files in your previous installation, copy the custom plug-ins (Publish Triggers, Custom Authentication Modules, Asset Factory Plugins, Workflow Triggers) from the temporary storage location back into
Start Cascade Server.
Log in to verify that the software has been upgraded by visiting Help->About.
- Why can't my users see certain Asset Factories?
- Will setting the 'Max Asset Versions' preference retroactively remove versions from old assets?
- Can 3rd Party data be used in Cascade Server?
- Can Cascade Server automatically archive content?
- Can Cascade Server export XML for other applications?
- View all (14 more)