PK79560: JSP Tag library files not updated during upgrade

6.1.0.2 Download: WebSphere Portal and Web Content Management V6.1, fix pack 2
6.1.0.3 Download: WebSphere Portal and WCM V6.1 fix pack 3, 6.1.5 feature pack
6.1.0.4 Download: WebSphere Portal and WCM V6.1.0 fix pack 4 & 6.1.5 fix pack 1
6.1.0.5 Download: WebSphere Portal and WCM V6.1.0 fix pack 5
6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6

APAR status

• Closed as program error.

Error description

• JSP Tag library files not updated during upgrade
  

Local fix

Problem summary

• Portlets that make use of new or updated JSP tags will not work.
  An example of a portlet that is broken by this behaviour is when
  the WCM rendering portlet is shipped via the Portal Catalog at
  the time of this publication.
  

Problem conclusion

• A fix is required to overcome this and is available from Fix
  Central:
  http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickord
  er?apar=PK79560&productid=WebSphere%20Portal&brandid=5
   You may need to type or paste the complete address into your
   Web browser.
  
  This is scheduled for inclusion into our next fix pack, 6.1.0.2.
  
  NOTE:  YOU MUST FIRST DOWNLOAD AND INSTALL 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
  
  Please refer to the Portal Update Installer documention for
  installation instructions of Portal Update Installer.
  
  Directions to apply Fix:
  1) Make sure the WAS adminpassword is in
  <Profile_Home>/ConfigEngine/properties/wkplc.properties file so
  that it is available for config to run.
  2) Shutdown WebSphere Portal
  3) Follow the Fix installation instructions that are packaged
  with the Portal Update Installer on how to install the Fix.
  4) Restart WebSphere Portal and synch any cluster systems
  
  Directions to remove a Fix:
  
  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.
  Example:  If your system has fix1, fix2, and fix3 applied in
  that order and fix2 is to be removed, fix3 must be removed
  first, fix2 removed, and fix3 re-applied.
  
  1) Shutdown WebSphere Portal
  2) copy
  <wp_home>/version/actions/templates/PK79560/default_cfg.xml.preP
  K7950 <config_engine_location>/config/actions/default_cfg.xml
  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:

Modules/Macros

• CONFIG
  

Fix information

• Fixed component name

  WEBSPHERE PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R61A PSY

     UP