i-fix Name: PK31226 Problem Summary: Navigator Component does not show ancestors correctly. Detailed Problem Description: f there is a Site Structure (including site and site areas) NewsSite > NewsSiteAreaLevel1 > NewsSiteAreaLevel2 > NewsContent1 NewsContent2 and following are the settings in the Navigator Component. Start type: Current Content Selected start area: None Include start: True Ancestor level: 1 Descendent level: None Preceding siblings level: all Next siblings level: all Show Site: false Show contents: true Now when it is previewed by selecting content NewsContent1 Following is displayed on the browser 1) NewsSiteAreaLevel1 NewsContent1 NewsContent2 which should be 2) NewsSiteAreaLevel2 NewsContent1 NewsContent2 Problem Analysis: The method getAncestors was returning the top level ancestor while calculating the start position for the NaviatorCmpnt. As a result the top level ancestor was being shown instead of the immedately preceding one, even when the specified ancestor level was one. Failing Module: WCM - Web Content Management (General) Problem Solution: Modified the code to calculate the start position for ancestors correctly. Affected Users: Content Authors Requisites: pre-requisite Portal Component: WCM 6.0.0.0 GA build 298.0 pre-requisite interim fixes: PK30057 Platform Specific: No Fix pack: This fix will be integrated into WP v6.0.1 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 - Create a temporary "fix" directory to store the jar file. - Copy jar file to this directory. - Shutdown WebSphere Portal. - Ensure the pre-requisite fix(es) are installed. - Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install a fix. NOTE: If a pre-requisite fix is not installed, the Portal Update Installer will fail and will list the missing pre-requisite fix(es). - Restart WebSphere Portal. - Update the deployed remote rendering portlet: - Log in to Portal as the Portal Administrator - Navigate to: Administration / Portlet Management / Web Modules - Find and select the remote rendering portlet web module - Click the Update Portlet Icon to the right of the selected portlet - Select the updated portlet WAR file located in: [PortalServer]\installableApps - Click Next and Finish - Log out of Portal for the changes to take effect. Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal. Note: If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open /profiles//config/cell//cell.xml and there will be a field indicating the cellname. (by default its called servernameCell01) For each node you are applying the ifix too, you need to: - Go into /config/ - Open up wpconfig.properties - Search for the properties Field "CellName=" - Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" 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. - Shutdown WebSphere Portal. - Follow the instructions that are packaged with the Portal Update Installer on how to uninstall a fix. - Restart WebSphere Portal. - Update the deployed remote rendering portlet: - Log in to Portal as the Portal Administrator - Navigate to: Administration / Portlet Management / Web Modules - Find and select the remote rendering portlet web module - Click the Update Portlet Icon to the right of the selected portlet - Select the portlet WAR file located in: [PortalServer]\installableApps - Click Next and Finish - Log out of Portal for the changes to take effect. Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal. Note: If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open /profiles//config/cell//cell.xml and there will be a field indicating the cellname. (by default its called servernameCell01) For each node you are applying the ifix too, you need to: - Go into /config/ - Open up wpconfig.properties - Search for the properties Field "CellName=" - Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" DISCLAIMER: This fix has received limited testing only and has not undergone IBM's complete quality assurance process. It is therefore recommended that it be tested in a testing environment before applying it to a working (authoring, production/live) system. You should always backup your data before installing a fix or fixpack.