PM53203: JCR READS 200KB FROM A FILE IN JCR DB AND INDEXES

APAR status

• Closed as program error.

Error description

• JCR reads 200KB from each file stored in JCR DB, and then
  indexes those data. If file size is more than 200KB, JCR does
  not index data after 200KB. This 200KB limitation is not
  modifiable.
  
  For example, on Quickr for WebSphere Portal, uploaded files are
  stored in JCR DB, and JCR indexes those files and Quickr search
  function uses the index. Due to this limitation, large files
  uploaded on Quickr for WebSphere Portal are not fully indexed
  and Quickr users sometimes fails to find those files by search.
  

Local fix

Problem summary

• JCR reads 200KB from each file stored in JCR DB, and then
  indexes those data. If file size is more than 200KB, JCR does
  not index data after 200KB. This 200KB limitation is not
  modifiable.
  
  For example, on Quickr for WebSphere Portal, uploaded files are
  stored in JCR DB, and JCR indexes those files and Quickr search
  function uses the index. Due to this limitation, large files
  uploaded on Quickr for WebSphere Portal are not fully indexed
  and Quickr users sometimes fails to find those files by search.
  

Problem conclusion

• PM53203
  =======
  
  Problem Description:
     JCR READS 200KB FROM A FILE IN JCR DB AND INDEXES
  
  Problem Solution:
    PM53203 contains code changes.
  
  Affected Users:
     All portal users.
  
  Pre-Requisite(s):
     Portal Version: 6.1.0.6
  
  Installation Steps:
     NOTE:  YOU MUST FIRST DOWNLOAD THE UPDATE INSTALLER TOOL IN
  ORDER TO INSTALL A FIX.
            The WebSphere Portal Update Installer (PUI) 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.*
  
  Refer to the "Maintaining the cluster" topic in the 6.0
  InfoCenter
  (http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index
  .jsp?topic=/com.ibm.wp.ent.doc/wpf/clus_maint.html)
  for additional information on installing or uninstalling interim
  fixes in clustered environments
  while maintaining continuous availability of your portal.
  
  1. Stop the WebSphere Portal server
  
  2. Apply the PM53203.jar using the PUI (Portal update
  installer).
     Refer to the PUI readme for further information on using the
  PUI.
  
  3. Edit <ProfileRoot>/PortalServer/jcr/lib/com/ibm/icm/icm
  .properties and add the lines below.
  #This proerty defines the maximun length of document that can be
  indexed.
  #default value is 200KB , to increase the limit of document
  uncomment the property and set the
  #new value in KB.
  #jcr.textsearch.max.doclimit=200
  
  4. Restart the WebSphere Portal server.
  
  
  Uninstall:
  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.
  
  Use the Portal Update Installer to uninstall the fix:
  
     1. Shutdown WebSphere Portal.
     2. Follow the instructions that are packaged with the Portal
  Update Installer on how to uninstall a fix.
     3. Restart WebSphere Portal.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61A PSY

     UP

• R61B PSY

     UP

• R61C PSY

     UP

• R610 PSY

     UP