PK64821: BETTER HANDLING OF RESOURCES DURING PRE-RENDERING

APAR status

• Closed as program error.

Error description

• They are currently a number of problems with the way resources
  are dealt with during pre-rendering:
  1. The physical file name of pre-rendered resources can contain
  URL encoded characters, this is incorrect and leads to broken
  images in the browser
  2. All Pre-rendered resources for the current site are each
  stored in their own sub-directories off the
  [CACHER_DIR]\[LIBRARY]\[SITE]\resources, which can result in too
  many subdirectories under the one
  parent directory and thus missing pre-rendered resources in the
  [CACHER_DIR]
  3. If the Cacher module is the default module, then resource
  requests (for items which aren't currently pre-rendered) aren't
  passed correctly to the Resource Server Module, thus resulting
  in broken images in the browser
  4. If the Cacher module is the default module, then new objects
  from a pre-rendered site weren't correctly written out to disk,
  and thus were served dynamically from the database each item,
  until the automated pre-renderer runs
  5. If the Cacher module is the default module, then all existing
  pre-rendered resources are served via an internal cache instead
  of being streamed directly from disk, which increases the memory
  utilisation of the Cacher module and can lead to OOM errors.
  

Local fix

• For Issue 1, the workaround is to manually rename the resource
  filename in the pre-rendered directory to decode the encoded
  characters. The other issues have no workaround.
  

Problem summary

• They are currently a number of problems with the way resources a
  with during pre-rendering:
  1. The physical file name of pre-rendered resources can contain
  encoded characters, this is incorrect and leads to broken images
  browser
  2. All Pre-rendered resources for the current site are each stor
  their own sub-directories off the
  [CACHER_DIR]\[LIBRARY]\[SITE]\resources, which can result in too
  subdirectories under the one
  parent directory and thus missing pre-rendered resources in the
  [CACHER_DIR]
  3. If the Cacher module is the default module, then resource req
  (for items which aren't currently pre-rendered) aren't passed co
  to the Resource Server Module, thus resulting in broken images i
  browser
  4. If the Cacher module is the default module, then new objects
  pre-rendered site weren't correctly written out to disk, and thu
  served dynamically from the database each item, until the automa
  pre-renderer runs
  5. If the Cacher module is the default module, then all existing
  pre-rendered resources are served via an internal cache instead
  streamed directly from disk, which increases the memory utilisat
  the Cacher module and can lead to OOM errors.
  

Problem conclusion

• An interim fix is available from Fix Central at:
  
  6.0.1.3
  
  http://www.ibm.com/eserver/support/fixes/fixcentral/swgquickorde
  r?brandid=2&productid=Workplace%20Web%20Content%20Management&fix
  es=6.0.1.3-WCM-PK64821
  
  You will need to cut/paste the entire URL to resolve the above
  address.
  

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

  WRKPLC WEB CON

• Fixed component ID

  5724I2900

Applicable component levels

• R60G PSY

     UP