Keeping customized files

When you redeploy WAR files to a Java application server, any customizations made to the current configuration files in the unpacked folders are lost.

To keep customizations at redeployment, you can do one of the following:

•	Use the backups of the application folders related to the web applications (see Prerequisites) – after redeploying the WAR files, you can restore some of the files from the backups.

•	Use an external directory outside the portal root for the configuration files. See OpenText StreamServe Control Center User Guide > StreamServe web application configurations > Keeping customized configuration files.

Note:

Not all configuration files are stored in the external directory. See the referenced documentation above for a list of concerned files.

When you use an external directory, the configuration files in this directory are preserved when you redeploy a web application. This means that if the configuration files are updated in the hotfix, and you want these updates to be available to the web application, you must manually delete the files in the external directory before the application is started. For example, if you rename the Ad Hoc application, you must delete the webportal.properties files for the Reviewer application before the Reviewer application is re-opened in the web browser.