i-fix Name: PK31685

Problem Summary: Error in the LRP when the WCM_GLOBAL_CONTEXT value is url encoded

Detailed Problem Description:

Passing in an url encoded string that includes forward slashes as the context to the local rendering portlet will cause the portlet not be able to find the specified content.

Problem Analysis:

When a WCM_GLOBAL_CONTEXT string is passed into the local rendering portlet only the names of the site, sitearea and content is being decoded. This means when the / is passed in, in an encoded form, the attempt to tokenised the whole context path will be inccorect and therefore the content will be be found.

Failing Module: WCM - Web Content Management (General)

Problem Solution:

Encode the whole parameter string to ensure that strings that are passed in are completely encoded as oppose to potentially be partially encoded. This means decoding the string once will ensure the presence of the / and therefore tokenisation of the context path will be correct.

Affected Users: All Users

Requisites:
   pre-requisite Portal Component: WCM 6.0.0.0 GA build 298.0
   pre-requisite interim fixes: PK29339, PK29843 (these also pre-req: PK31448, 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).
- Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm -DPortalAdminPwd=password
- Stop and Restart the WebSphere Portal Server.


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 <AppServerRoot>/profiles/<DeploymentManagerProfile>/config/cell/<CellName>/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 <PortalInstallRoot>/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.
- Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm -DPortalAdminPwd=password
- Stop and Restart the WebSphere Portal Server. 

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 <AppServerRoot>/profiles/<DeploymentManagerProfile>/config/cell/<CellName>/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 <PortalInstallRoot>/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.