IBM Support

PK85195: CUMULATIVE IFIX 17 FOR WCM V6.0.1.X

 

APAR status

  • Closed as program error.

Error description

  • Cumulative iFix 17 for WCM v6.0.1.x
    

Local fix

  • Cumulative iFix 17 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 and WP
    v6.0.1.5
    
    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).
    

Problem conclusion

  • A fix is available from Fix Central:
    http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickord
    er?apar=PK85195&productid=Lotus%20Web%20Content%20Management&bra
    ndid=2
    
    You may need to type or paste the complete address into your Web
    browser.
    
    
    This cumulative iFix targets a number of problem areas in the GA
    release of WCM v6.0.1.4 and WCM v6.0.1.5. 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)
    
    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 17 for
    WCM v6.0.1.4, WCM v6.0.1.5, in addition to the fixes already
    integrated in previous CFs:
    
    PK85109 (Remote Rendering Portlet creates too many sessions.)
    PK84447 (content.getId() and content.getId().getName() return
    the UUID as the content name after syndication.)
    PK84128 (findByName does return expected content after content
    is syndicated.)
    PK85393 (New API method to search content and be able to
    restrict search and sort results.)
    PK71590 (Menu Cache is not invalidated when content expires.
    Therefore, links to expired content are still shown in the
    menu.)
    PK85137 (Broken links appear for embedded images after
    syndication.)
    PK85213 (Syndication not completing or taking an excessive
    amount of time to complete.)
    PK84611 (SYNDICATION TRANSCATION TIMEOUT AFTER CF12.)
    
    Affected Users: All Users
    
    Requisites:
       pre-requisite Portal Component: WP v6.0.1.4, WP v6.0.1.5
       pre-requisite interim fixes: None
       co-requisite interim fixes: PK76701 (WebSphere Portal),
    PK78517 (JCR)
    
    Platform Specific: No
    
    Fix pack: This fix will be integrated into WP v6.0.1.6
    
    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
    
    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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK85195

  • Reported component name

    LOTUS WEB CONT

  • Reported component ID

    5724I2900

  • Reported release

    60H

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-04-22

  • Closed date

    2009-05-08

  • Last modified date

    2009-05-11

  • 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

  • R60H PSY

       UP

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1.4","Edition":"","Line of Business":{"code":null,"label":null}}]

Document Information

Modified date:
10 September 2020