Name: PK28601 ============= Summary: allow for deletion of portlet settings during WAR update Problem Description: During update of an portlet application WAR file certain portlet and application settings ar not deleted from portal datastore, since it cannot be destinguished between a user added property (that should be preserved) or a setting that was formaly provided (by the WAR developer) via portlet.xml. Therefore nothing was deleted during the update process and old or former parameters remained. The user/admin had to delete them manually via e.g. the Admin UI after the WAR update finished. Problem Solution: The update.portlet.preserves.config.settings property defined in DeploymentService.properties was extended to accept additional values. The property can now be used with the following values: update.portlet.preserves.config.settings = protect or true to protect existing values from being overwritten or deleted update.portlet.preserves.config.settings = overwrite or false to protect existing values from being deleted, but allow to overwrite them with the new values from portlet.xml update.portlet.preserves.config.settings = clean to clean existing settings, delete them and only recreate those found in the new portlet.xml Besides allowing the deletion of settings prior to update the APAR fixes another problem is fixed, where the anonymous-session property from ibm-portal-portlet-ext.xmi was not updated. The update.portlet.preserves.config.settings property defined in DeploymentService.properties was extended to accept additional values. Failing Module(s): Portlet Deplyoment Affected Users: All users Version Information: Portal Version(s): 6.0.0.0 Pre-Requisite(s): PK28928 PK27753 Co-Requisite(s): --- Platform Specific: This fix applies to all platforms. Installation: NOTE: YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX. The Portal Update Installer can be downloaded from the following link: http://www.ibm.com/software/genservers/portal/support 1. Create temporary "fix" directory to store the jar file. 2. Copy jar file to this directory. 3. Shutdown WebSphere Portal. 4. Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install the fix. 5. Restart WebSphere Portal. 6. The temporary directory may be removed. Un-Installation: NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. 1. Shutdown WebSphere Portal. 2. Follow the instructions that are packaged with the Portal Update Installer on how to uninstall the fix. 3. Restart WebSphere Portal.