To configure the custom properties:
1) Login to the WAS Admin Console (or Depoloyment Manager if clustered). 2) Navigate to Resources --> Resource Environment Providers --> WP StateManagerService --> Custom Properties 3) Create a new custom property if it does not exist: Name: com.ibm.wps.state.preprocessors.locale.CookieSupportedLanguagePr eProcessor.cookie.maxage Value: -1 Type: java.lang.String *Note, you may specify a different timeout value as noted above. This is an example only. 4) Create a new custom property: Name: preprocessors Value: com.ibm.wps.state.preprocessors.urlmapping.URLMappingPreProcesso r, com.ibm.wps.resolver.friendly.preprocessors.FriendlyPreProcessor , com.ibm.wps.resolver.portal.ResolvedPreprocessor, com.ibm.wps.state.preprocessors.selection.StandardPortalSelectio nImpl, com.ibm.wps.state.preprocessors.selection.FragmentSelectionImpl, com.ibm.wps.state.preprocessors.selection.ResourceSelectionImpl, com.ibm.wps.state.preprocessors.eclipse.ExtensionPreProcessor, com.ibm.wps.state.preprocessors.portlet.RequestParameterMerger, com.ibm.wps.state.preprocessors.locale.CookieSupportedLanguagePr eProcessor Type: java.lang.String *Note, the final parameter is the new property required by this APAR. The preceding properties are required and may vary from version to version of WebSphere Portal. Check the Infocenter based on your version of WebSphere Portal. 6) Save changes. If clustered, sync nodes. 7) Restart the Portal server(s).