Name: PK38984
=============
 
Summary:
   PSE Crawler Scheduler is not taking DST into consideration : 
   scheduler's timer changes its run time after passing DST.
 
Problem Description:   
   Scheduler time is moved in an hour (forward or backward) when passing DST, 
   e.g. scheduler that is defined to run every day at 12:00 is moved to 13:00 after passing DST.
 
Problem Solution:
   Store information about scheduler interval type (hour/day/week/month) and calculate next run time
   according to interval type and calendar changes (like DST).

   After applying solution, user should import his/her collections.
   As a result of importing, collection schedulers for intervals of days/weeks/month 
   will be represented in hours, so user should re-define such schedulers
   with correct time interval values and types.


Failing Module(s):
   Portal Search Module
 
Affected Users:
   All users
 
Version Information:
    Portal Version(s): 6.0.0.0
     Pre-Requisite(s): PK32675
      Co-Requisite(s): ---
 
Platform Specific:
   This fix applies to all platforms.
 

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 file PseLibs.zip to the was_profile_root/installableApps directory on the remote search server.
      This file is packaged with this ifix.
   2. Empty the content of the was_profile_root/installableApps/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 PseLibs.zip into that directory 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/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. 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.
 
Un-Installation:
   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.