i-fix Name: PK34912 Problem Summary: In hierarchal resource types such as pages, drilling down into the children results in the table of child resources displayed, but it does not contain the Externalize/Internalize (optional) or Unique Name column headers or values. Non-heirarchal resource types such as portlets will not see this error Detailed Problem Description: Missing columns when drilling down into hierarchical resources in the permissions portlet. Problem Analysis: Permissions portlet has incorrect child list state and incorrect JSP pages. Failing Module: ResourceView.war Problem Solution: Corrected JSP and errors in child list state. Affected Users: All Requisites: None Platform Specific: No Fix pack: This fix will be integrated into WPv5.1.0.5 and WPv6.0 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/admin.jar was updated. And note that this iFix provided new war file(s): /installableApps/ResourceView.war 8. To install the admin portlets listed above, -- start portal server -- logon as wpsadmin -- click on Administration -- click on Portlets -- click on Manage Applications -- update the existing ResourceView.war with the new one in the installableApps directory Refer to Clustering->”Performing Upgrades in a 24x7 cluster” section for additional information on applying interim fixes in clustered environments while maintaining continuous availability of your Portal.} 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. Refer to Clustering->”Performing Upgrades in a 24x7 cluster” section for additional information on applying interim fixes in clustered environments while maintaining continuous availability of your Portal.}