Confluence Docs 3.0 : Reapplying Customisations after Confluence Upgrade This page last changed on Aug 27, 2009 by jlargman. This page is part of the Confluence Upgrade Guide.
| Hint: The steps below are for advanced Confluence users, who have applied special settings to their Confluence server and/or Confluence look and feel
After upgrading your Confluence installation to a later version of Confluence, you need to consider any customisations you have applied to your system and other special configurations: If you had previously installed Confluence/Tomcat as a Windows service, uninstall the service (to ensure that the old Confluence cannot start automatically when the server restarts) and reinstall the new one. For details please see Start Confluence automatically on Windows as a Service. If you are using a Standalone Edition of Confluence and you have previously defined a CATALINA_HOME environment variable, please check that it points to the correct path for the new Confluence Tomcat server. If you had previously connected your Confluence installation to an external database via a JNDI datasource or you implemented SSL, edit your new `web.xml` file and and copy over any relevant modifications from your old `web.xml` file, which relate to these customisations. If you were previously running Confluence on a non-standard port, edit your new `<Installation-Directory>\conf\server.xml` file as described in Change listen port for Confluence Standalone. If you had previously defined a Tomcat datasource, edit your new `<Installation-Directory>\conf\server.xml` and copy over the datasource definition from your old `server.xml`. If you were previously using any plugins, install the latest compatible version and disable any plugins that are incompatible with your new version of Confluence. The easiest way to do this is to use the Plugin Repository in the Confluence Administration Console. If you are using any customised themes, please check that they are displaying as expected. Some further customisation may be required to ensure compatibility with your new version of Confluence. If you had previously customised the default site or space layouts, you will need to reapply your changes to the new defaults as described here. If you had previously modified the Confluence source code, you will need to reapply your changes to the new version. If you were previously running Confluence over SSL, you will need to reapply your configuration as described in Adding SSL for Secure Logins and Page Security. If you had previously modified the memory flags (`Xms` and `Xmx`) in either the `<Installation-Directory>\bin\setenv.sh` or the `<Installation-Directory>\bin\setenv.bat` file, you may want to make the modifications in your new installation. The parameters are specified in the `JAVA_OPTS` variable. If you had changed the Confluence interface text, you will need to pull over the ConfluenceActionSupport.properties file. If you were using a custom SSO authenticator or the utility to Automatically Add LDAP users to the confluence-users Group, change seraph-config.xml to the correct authenticator. ##### RELATED TOPICS Upgrading Confluence

Document generated by Confluence on Nov 05, 2009 23:36