PK98642: CUMULATIVE IFIX 28 FOR WCM V6.0.1.X

APAR status

• Closed as program error.

Error description

• CUMULATIVE IFIX 28 FOR WCM V6.0.1.X
  

Local fix

• CUMULATIVE IFIX 28 FOR WCM V6.0.1.X
  

Problem summary

• This is a cumulative iFix for IBM Web Content Managagement, for
  version 6.0.1.x. This fix is applicable to WP v6.0.1.4, WP
  v6.0.1.5 and WP v6.0.1.6
  
  This iFix supersedes the following (cumulative) iFixes:
  PK71419 (Cumulative iFix 1 for WCM v6.0.1.4).
  PK71679 (Cumulative iFix 2 for WCM v6.0.1.4).
  PK72731 (Cumulative iFix 3 for WCM v6.0.1.4).
  PK73644 (Cumulative iFix 4 for WCM v6.0.1.4).
  PK74395 (Cumulative iFix 5 for WCM v6.0.1.4).
  PK75099 (Cumulative iFix 6 for WCM v6.0.1.4).
  PK76127 (Cumulative iFix 7 for WCM v6.0.1.x).
  PK77047 (Cumulative iFix 8 for WCM v6.0.1.x).
  PK77670 (Cumulative iFix 9 for WCM v6.0.1.x).
  PK78690 (Cumulative iFix 10 for WCM v6.0.1.x).
  PK79697 (Cumulative iFix 11 for WCM v6.0.1.x).
  PK80490 (Cumulative iFix 12 for WCM v6.0.1.x).
  PK81489 (Cumulative iFix 13 for WCM v6.0.1.x).
  PK82452 (Cumulative iFix 14 for WCM v6.0.1.x).
  PK83474 (Cumulative iFix 15 for WCM v6.0.1.x).
  PK84398 (Cumulative iFix 16 for WCM v6.0.1.x).
  PK85195 (Cumulative iFix 17 for WCM v6.0.1.x).
  PK86197 (Cumulative iFix 18 for WCM v6.0.1.x).
  PK87485 (Cumulative iFix 19 for WCM v6.0.1.x).
  PK88528 (Cumulative iFix 20 for WCM v6.0.1.x).
  PK90387 (Cumulative iFix 21 for WCM v6.0.1.x).
  PK91502 (Cumulative iFix 22 for WCM v6.0.1.x).
  PK92695 (Cumulative iFix 23 for WCM v6.0.1.x).
  PK93880 (Cumulative iFix 24 for WCM v6.0.1.x).
  PK94834 (Cumulative iFix 25 for WCM v6.0.1.x).
  PK95807 (Cumulative iFix 26 for WCM v6.0.1.x).
  PK97018 (Cumulative iFix 27 for WCM v6.0.1.x).
  

Problem conclusion

• A fix is available from Fix Central:
  http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickord
  er?apar=PK98642&productid=Lotus%20Web%20Content%20Management&bra
  ndid=2
  
  This cumulative iFix targets a number of problem areas in the GA
  release of WCM v6.0.1.4 , WCM v6.0.1.5 and WCM v6.0.1.6.
  Specifically,
  defects in the following areas have been targeted:
  Migration, API, Versioning, Syndication, Rendering, Authoring
  
  This fix has a co-requisite dependency on PK76701 (WebSphere
  Portal) , PK89284 (JCR. For WCM v6.0.1.4 , WCM v6.0.1.5),
  PK99291 (JCR for
  WCM v6.0.1.4, WCM v6.0.1.5, WCM v6.0.1.6)
  
  The migration tool now finds all orphan site areas and migrates
  these to a site called orphans. Previously it was necessary to
  run the
  Site Checker before migration to ensure that all orphan site
  areas were accounted for. One side effect of this feature is
  that all orphans
  are aggregated into the same site, even those which were
  previously found by the Site Checker.
  
  Failing Module: WCM - Web Content Management (General)
  
  Problem Solution:
  
  The following new APARs are included in Cumulative iFix 28 for
  WCM v6.0.1.4, WCM v6.0.1.5 WCM v6.0.1.6, in addition to the
  fixes already
  integrated in previous CFs:
  
  PK97326 (FILERESOURCE DELETIONS ARE NOT SYNDICATED TO THE
  SUBSCRIBER.)
  PK97988 (../JCR/STRONGWORKSPACESTATE OUT OF MEMORY OOM AFTER
  CF22-27.)
  PK98329 (FUNCTION ADDED TO CONTENTSEARCH GIVING THE ABILITY NOT
  TO RETURNCATEGORY DESCENDANTS.)
  PK97228 (LIBRARYRICHTEXTCOMPONENT AND LIBRARYTEXTCOMPONENT
  CLASSES ADDED TO API.)
  PK98474 (STYLESHEET (OR OTHER RESOURCE) COMPONENTS WITH NO FILES
  ATTACHEDMAY FAIL TO SYNDICATE CORRECTLY.)
  PK98507 (ZIPEXCEPTION FOR RENDEIRNG IMAGES SAVED IN AN EARLIER
  RELEASE)
  
  Affected Users: All Users
  
  Requisites:
     pre-requisite Portal Component: WP v6.0.1.4, WP v6.0.1.5, WP
  v6.0.1.6
     pre-requisite interim fixes: None
     co-requisite interim fixes: PK76701 (WebSphere Portal),
  PK89284 (JCR. For WCM v6.0.1.4 , WCM v6.0.1.5)
  
  Platform Specific: No
  
  Fix pack: This fix will be integrated into WP v6.0.1.7
  
  Installation Steps:
  
  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?uid=swg24006942
  
  -- Do not apply this cumulative fix at the same time as another
  cumulative fix.
  -- Do not apply this cumulative fix at the same time as any
  interim fixes.  Apply interim fixes after the installation of a
  cumulative
  fix.
  -- Only apply this cumulative fix on a system which does not
  have a newer cumulative fix installed.
  Install:- Create a temporary "fix" directory to store the jar
  file.- Copy jar file to this directory.- Shutdown WebSphere
  Portal.- Ensure
  the pre-requisite fix(es) are installed.- Follow the fix
  installation instructions that are packaged with the Portal
  Update Installer on
  how to install a fix.  NOTE: If a pre-requisite fix is not
  installed, the Portal Update Installer will fail and will list
  the missing pre
  -requisite fix(es).- Restart WebSphere Portal.- Backup any files
  (e.g. custom JSPs) which have been copied to the deployed WCM
  EAR or
  portlet WAR directories
  - Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm
  -DPortalAdminPwd=password
  - Update the deployed remote rendering portlet:
     - Backup any files (e.g. custom JSPs) which have been copied
  to the deployed remote rendering portlet WAR directory
     - Log in to Portal as the Portal Administrator
     - Navigate to: Administration / Portlet Management / Web
  Modules
     - Find and select the remote rendering portlet web module
     - Click the Update Portlet Icon to the right of the selected
  portlet
     - Select the updated portlet WAR file located in:
  [PortalServer]\installableApps
     - Click Next and Finish
  - Log out of Portal for the changes to take effect.
  
  
  Refer to the clustering section of the Portal Information Center
  (typically 'Clustering -> Performing Upgrades in a 24x7
  cluster') for
  additional information on installing interim fixes in clustered
  environments while maintaining continuous availability of your
  Portal.
  
  APAR configuration:
  PK74353 (Add utility to allow bulk removal of drafts)
  
  A new DraftDetectionModule with optional 'remove' mode
  (remove=true) has been developed to automate removing drafts.
  The module must first be configured in the WCM configuration
  file (like similar modules such as the
  MemberFixer/LibraryDelete)
  before it can be used. To configure the new module, perform the
  following steps:
  1) Edit the
  \wcm\shared\app\config\wcmservices\WCMConfigService.properties
  file
  1a) Add the following three lines underneath the
  'connect.businesslogic.module' property:
  connect.businesslogic.module.draftdetection.class=com.aptrix.plu
  to.workflow.DraftDetectionModule
  connect.businesslogic.module.draftdetection.remoteaccess=true
  connect.businesslogic.module.draftdetection.autoload=false
  1b) Add 'draftdetection' to the end of the
  'connect.businesslogic.module' property
  connect.businesslogic.module=<existing entries>,draftdetection
  2) Restart the server To run the new module in report mode,
  hit the following URL in the browser:
  http://[HOST]:[PORT]/wps/wcm/connect/?MOD=draftdetection&library
  =[LIBRARY]
  To run the new module in remove mode, hit the following URL in
  the browser:
  http://[HOST]:[PORT]/wps/wcm/connect/?MOD=draftdetection&library
  =[LIBRARY]&remove=true
  
  PK88848 (TASK REQUIRED TO RESET THE EVENT LOG DATABASE WHILE THE
  SYSTEM IS RUNNING.)
  
  This fix provides a module to reset the event log database while
  the system is running. The module is enabled by performing the
  following
  in the WCMConfigServices.properties file:
  
  1) Add 'reseteventlog
  ' to end of the 'connect.businesslogic.module' property.
  
  2) Adding the following lines:
  
  connect.businesslogic.module.reseteventlog.class=com.ibm.workpla
  ce.wcm.services.eventlog.ResetEventLogModule
  connect.businesslogic.module.reseteventlog.remoteaccess=true
  connect.businesslogic.module.reseteventlog.autoload=false
  
  3) Restart the server
  
  The module can then be accessed by entering the following in
  your browser's address bar:
  
  http://[HOST]:[PORT]/wps/wcm/myconnect?MOD=reseteventlog&library
  =[NAME OF LIBRARY TO RESET]
  
  To start the reset task append &fix=true to the above URL.
  
  This module will take a short time to run and respond to the
  browser. A background task started by the module will continue
  to run on the
  server after the module has responded and can take up to several
  hours or days to complete. Any items modified between the last
  successful
  syndication and the time you get a response from this module in
  your browser will not be syndicated until the background task
  has
  completed. To avoid this limitation you should follow these
  steps:
  
  1. Stop all authoring activity on the server
  2. Run a syndication update to ensure the subscriber is up to
  date with all the current items in the event log
  3. Run this module in fix mode
  4. Wait for the module to respond to the browser (this should
  only take a few minutes)
  5. Continue authoring
  6. The background task will populate the event log with all
  historical entries
  7. Any authoring activity will add new entries
  8. Syndication updates will continue to send any new entries
  added to the event log
  9. When the background task is complete you can perform a
  syndication full rebuild to check all historical entries
  
  To see the status of the background task, run this module again
  IN REPORT MODE.
  
  Un-Installation Steps:
  
  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.
  
  - Shutdown WebSphere Portal.- Follow the instructions that are
  packaged with the Portal Update Installer on how to uninstall a
  fix.-
  Restart WebSphere Portal.- Backup any files (e.g. custom JSPs)
  which have been copied to the deployed WCM EAR or portlet WAR
  directories
  - Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm
  -DPortalAdminPwd=password
  - Update the deployed remote rendering portlet:
     - Backup any files (e.g. custom JSPs) which have been copied
  to the deployed remote rendering portlet WAR directory
     - Log in to Portal as the Portal Administrator
     - Navigate to: Administration / Portlet Management / Web
  Modules
     - Find and select the remote rendering portlet web module
     - Click the Update Portlet Icon to the right of the selected
  portlet
     - Select the updated portlet WAR file located in:
  [PortalServer]\installableApps
     - Click Next and Finish
  - Log out of Portal for the changes to take effect.
  
  
  Refer to the clustering section of the Portal Information Center
  (typically 'Clustering -> Performing Upgrades in a 24x7
  cluster') for
  additional information on uninstalling interim fixes in
  clustered environments while maintaining continuous availability
  of your Portal.
  
  DISCLAIMER:
  
  This fix has received limited testing only and has not undergone
  IBM's complete quality assurance process. It is therefore
  recommended
  that it be tested in a testing environment before applying it to
  a working (authoring, production/live) system. You should always
  backup
  your data before installing a fix or fixpack.
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R60G PSY

     UP