PK30950
=================

PK30950 Fix Description:
	Add proper close of iterators that hold open file descriptors.

Detailed Fix Description:
	When browsing URL, user iterates through categories and each iterator
	is stored in data structure in order to be closed after finish browsing.
	Closing of iterator needs for proper closing of open file descriptors.
	However, this data structure expansion causes to out of memory exception.
	The fix includes closing these iterators exactly after their using,
	so they should not be stored any more and data structure for iterators storing is removed.
	
        This fix may be applied to WebSphere Portal versions 5.1.0.1, 5.1.0.2, 5.1.0.3, and 5.1.0.4 
        with the appropriate prerequisite fix(es) installed.

Affected Users:
   All portal users.

Pre-Requisite(s):
   Portal Version:  5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4
   Portal Fixes:   PK30198

Pre-Installation:

   Export your search collections before applying the fix

   Before applying the fix all collections that need to be preserved must be exported to external files
   and deleted from the Portal. Exporting the collections would allow to import them with all their
   configurations later on after applying the fix. Any collections which would not be deleted prior to
   applying the fix would disappear from the Manage Search Collections Portlet but would not be
   deleted from the back end.

   To preserve your search collections, proceed by the following steps:

   1. Export the collections (this does not export the index, but the configurations that are used to
      collect the index).
   2. Delete the collections using the Manage Search Collections Portlet.
   3. Apply the maintenance to the PSE (install APAR).
   4. Create the collections again, no configuration is required.
   5. Import the collections (the settings to crawl the sites, and the internal list of all documents).

   Once the import process finish successfully, the documents are being fetched in the background,
   no need to activate any crawlers. You may monitor the progress of the background process by refreshing
   the search admin screen. The time it would take the import process to complete the "recrawl" depends on
   the size of the collections.


Installation:


   NOTE: Two possible configurations are available for Portal search, local and remote.
   If working in remote configuration, this fix has to be applied on both servers, local and remote.
   See that you go through the two installation phases:
   - Remote search installation instructions
   - Portal search installation instructions
   If working in local search configuration, proceed with "Portal search installation instructions".



   Remote search installation instructions:

   All the following steps are performed on the remote search server, which is the machine where remote
   search service was installed.
   1. Copy the files WebScannerSoap.ear and WebScannerEjbEar.ear to the was_profile_root/installableApps
      directory on the remote search server.These files are packaged with this ifix.
   2. Update the SOAP or EJB ear application on the remote search server, depending on what application
      is already installed.
   3. If using EJB, follow this step. If using SOAP, omit this step and proceed with the next one.
      Empty the content for the "extract" directory that was created according to infocenter instructions
      (See under 'Portal Search' section 'Preparing for remote search service').
      Extract the content of the file WebScannerEJbEar.ear into the directory "extract" which was emptied.
   4. Restart the remote search server.


   Portal search installation instructions:

   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/support/docview.wss?rs=688&uid=swg24006942

*Reminder: the version of PUI used varies based on the version of WebSphere Portal.
Ensure the correct version is in use.*

   1. Create temporary "fix" directory to store the jar file.
   2. Copy jar file to this directory.
   3. Shutdown WebSphere Portal.
   4. Follow the fix installation instructions that are packaged with
      the Portal Update Installer on how to install the fix.
   5. Restart WebSphere Portal.
   6. The temporary directory may be removed.

   Portal search uninstallation instructions:

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