IBM Support

PK86198: CUMULATIVE IFIX 12 FOR WCM V6.1.0.1 AND WCM V6.1.0.2

 

APAR status

  • Closed as program error.

Error description

  • Cumulative iFix 12 for WCM v6.1.0.1 and WCM v6.1.0.2
    

Local fix

  • Cumulative iFix 12 for WCM v6.1.0.1 and WCM v6.1.0.2
    

Problem summary

  • This is a cumulative iFix for IBM Web Content Managagement. This
    fix is applicable to WP v6.1.0.1 and WP v6.1.0.2
    
    This iFix supersedes the following (cumulative) iFixes:
    PK76129 (Cumulative iFix 1 for WCM v6.1.0.1).
    PK77042 (Cumulative iFix 2 for WCM v6.1.0.1).
    PK77299 (Cumulative iFix 3 for WCM v6.1.0.1).
    PK78855 (Cumulative iFix 4 for WCM v6.1.0.1).
    PK79704 (Cumulative iFix 5 for WCM v6.1.0.1).
    PK80482 (Cumulative iFix 6 for WCM v6.1.0.1).
    PK81490 (Cumulative iFix 7 for WCM v6.1.0.1).
    PK82453 (Cumulative iFix 8 for WCM v6.1.0.1).
    PK83500 (Cumulative iFix 9 for WCM v6.1.0.1).
    PK84399 (Cumulative iFix 10 for WCM v6.1.0.1).
    PK85196 (Cumulative iFix 11 for WCM v6.1.0.x).
    

Problem conclusion

  • A fix is available from Fix Central:
    http://www.ibm.com/eserver/support/fixes/fixcentral/swg/quickord
    er?apar=PK86198&productid=Lotus%20Web%20Content%20Management&bra
    ndid=2 (you will need to copy and paste that URL into your
    browser, or use this URL: http://tinyurl.com/PK86198 ).
    
    This cumulative iFix targets a number of problem areas in the GA
    release of WCM v6.1.0.1 and WCM v6.1.0.2. Specifically, defects
    in the following areas have been targeted:
    Syndication, Security, Rendering, Migration, Workflow.
    
    In addition, this cumulative iFix is an APAR rollup.
    
    Failing Module: WCM - Web Content Management (General)
    
    Problem Solution:
    
    The following new APARs are included in Cumulative iFix 12 for
    WCM v6.1.0.1 and WCM v6.1.0.2:
    
    PK85137 (Broken links appear for embedded images after
    syndication.)
    PK84447 (content.getId() and content.getId().getName() return
    the UUID as the content name after syndication.)
    PK85213 (Syndication not completing or taking an excessive
    amount of time to complete.)
    PK85897 (LibraryDateComponents with specified date-type don't
    render or display correctly.)
    PK85992 (Speed optimisation for content.getCategoryIds() WCM API
    method.)
    PK86076 (IllegalDocumentTypeException trying to add some content
    component types using the WCM API.)
    PK86191 (Enhance change-workflow and next-workflow-stage support
    in the WCM API.)
    PK85521 (WCM MAKES NESTED GROUP SEARCH WHEN NESTED GROUPS ARE
    DISABLED IN THE PORTAL.)
    PK85689 (WCM global context in session not scoped to Virtual
    Portals.)
    
    Affected Users: All Users
    
    Requisites:
       pre-requisite Portal Component: WCM 6.1.0.1 GA build 119.2
       pre-requisite interim fixes: PK85710 (WebSphere Portal)
    
    Platform Specific: No
    
    Fix pack: This fix will be integrated into WP v6.1.0.2
    
    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.
    -- If you have installed the updated editor you must re-deploy
    the editor after installing the cumulative fix. Please read the
    editor installation guide for instructions on the re-deployment
    process.
    
    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 {WAS_PROFILE_ROOT}/ConfigEngine/ConfigEngine.sh|bat
    update-wcm -DPortalAdminPwd=<password> -DWasPassword=<password>
    -Restart Portal
    - 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]\wcm\prereq.wcm\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
    
    Search (included in CF7 and above) a new field called
    ControllableID has been added to the seedlist attributes. After
    applying the cumulative fix, if the Search Component is
    accessing a collection crawled using the old seedlist, it will
    fail to return any results, because the ControllableID was not
    stored earlier. In such cases the Content Source will need to be
    re-created or re-crawled as follows:
     -Edit the Site and uncheck the "searchable" box.
     -Save the Site (This will remove the content source for the
    Site).
     -Edit the Site and enable the "searchable" box
     -Save the Site.
     -Go to Manage Search -> Collections -> Content Source created
    for this Site and run the crawl again.
    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 [WP_PROFILE_ROOT]\ConfigEngine\ConfigEngine.bat|sh
    update-wcm -DPortalAdminPwd=password
    
    
    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 number

    PK86198

  • Reported component name

    LOTUS WEB CONT

  • Reported component ID

    5724I2900

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-05-08

  • Closed date

    2009-05-28

  • Last modified date

    2009-06-01

  • 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

  • R61A PSY

       UP

  • R61B PSY

       UP

[{"Business Unit":{"code":null,"label":null},"Product":{"code":"DELETE","label":"DELETE CONTENT"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Edition":"","Line of Business":{"code":null,"label":null}}]

Document Information

Modified date:
10 September 2020