i-fix Name: PK43726 Problem Summary: Portlets in Portlet Palette are unavailable even for wpsadmin. Also unavailable for other users even though all portlets are allowed on the page. Detailed Problem Description: SearchableManager.usePortletPreferences sets the MAX_NUMBER_RESULTS attribute to 300 when the portlet preference maxItems is null (not present). Thus it was arbitrarily truncating part of the list of portlets that are allowed on the page making the palette believe the portlets it was marking as forbidden were not allowed on the page. Problem manifests as unexpected forbidden symbols for portlets in the portlet palette. Problem Analysis: See detailed problem description. Failing Module: wp.admin.common.jar Problem Solution: Updated SearchableManager so that there would be no limit when a portlet has no maxItems set in its preferences. This results in no limit for portlets on the palette. Affected Users: All portal installations that use the portlet palette. Requisites: None Platform Specific: No Fix pack: It is anticipated that this will be integrated in WP 6.0.1.1 and later fix packs. Installation Steps: 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. Ensure the pre-requisite fix(es) are installed. 5. Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install a fix. NOTE: You must also ensure all pre-requisite fix(es) are installed. If you do not, the Portal Update Installer will fail and will list the missing pre-requisite fix(es). 6. Restart WebSphere Portal. 7. Note that the /shared/app/wp.admin.common.jar was updated. Un-Installation Steps: 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 a fix. 3. Restart WebSphere Portal.