i-fix Name: PK31802

Problem Summary: Retrieving Site or Site Area children via the WCM API can lead to OOM errors 

Detailed Problem Description:

Retrieving Site or Site Area children via the WCM API can lead to OOM errors

Problem Analysis:

An application that uses the WCM API and retrieves the children of one or more Sites and Site Areas can fail with an OOM error due to the internal JCR cache (for the current WCM API workspace) growing too large.

Failing Module: WCM - Web Content Management (General)

Problem Solution:

The internal JCR cache (for the current API workspace) is cleared prior to the API's internal 'getChildren' call to JCR.


Affected Users: All Users

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.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.


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.
- Restart WebSphere Portal.

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.