Upgrading

This page describes how to install a new version of the CEC. component while retaining the configuration from your previous version.

An upgrade is supplied as a new version of the WAR file containing the CEC. This new WAR replaces the old version.

First, install the WAR for the CEC in Tomcat's webapp directory, as you did in the initial installation of the CEC. Tomcat detects the change in the WAR file and reacts thus:

  1. It "undeploys" the old copy of the web application. This destroys the old WAR file and all files associated with it, except the files in the directory structure at cea.base.dir ; Tomcat does not know about these.
  2. It deploys the new WAR, putting the web application and the CEC on-line with a default configuration.

At this stage, if you are upgrading a 2008.0 release or later the CEC should start up properly, and will most likely still work properly - however, you should go through the self-test procedures to check

Upgrading from 2007.1 or earlier

After replacing the war file for a 2007.1 or earlier version of the CEC, it won't work satisfactorily as the application configuration file format is different in this release. The following section details how an existing application configuration file and registry template can be updated for this release.

If for some reason the updating does not work correctly, then some manual editing might be necessary. In all cases the configuration files should be xml schema validated as the first stage in ensuring that the

Automatic updating the application configuration files

If the war has simply been installed on top of an existing version of CEC the the environment should be pointing to the old configuration files. In this case there is a update configuration page that is capable of reading the old configuration and transforming it.

When running this page you should check that the paths to the configuration files are correct and then press the update button. This will create the correct contents for a new format app-description.xml file in the text area. This content should then be manually copied to the app-description.xml file.

Manual updating of the configuration files

If for some reason the automatic upgrade does not work, then there is an xsl script that can be used to update an existing configuration

This script can be run using an standard XSLT transformation tool such as Saxon on the app-description.xml file with the location of the registration-template.xml file as a stylesheet parameter called "regtemplate"

upgrading a HTTP or JavaClass CEC

If you are updgrading a 2007 or earlier version JavaClass or HTTP CEC then you should be aware that these specializations are now included in the universal CEC. Furthermore, if you are upgrading a HTTP CEC then the CEC is locally configured using the configuration file rather than reading its configuration from the Registry - in fact you will need to publish the local configuration to a registry just as will commandline or java class applications.