APAR status
Closed as program error.
Error description
WCM CUMULATIVE IFIX 22 FOR 6.1.0.3, 6.1.5
Local fix
WCM CUMULATIVE IFIX 22 FOR 6.1.0.3, 6.1.5
Problem summary
This is a cumulative iFix for IBM Web Content Managagement. This fix is applicable to WP v6.1.0.3 and WP v6.1.5.0 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). PK86198 (Cumulative iFix 12 for WCM v6.1.0.x). PK87486 (Cumulative iFix 13 for WCM v6.1.0.x). PK88529 (Cumulative iFix 14 for WCM v6.1.0.x). PK90388 (Cumulative iFix 15 for WCM v6.1.0.x). PK91503 (Cumulative iFix 16 for WCM v6.1.0.x). PK92696 (Cumulative iFix 17 for WCM v6.1.0.x). PK94512 (Cumulative iFix 18 for WCM v6.1.0.x). PK95538 (Cumulative iFix 19 for WCM v6.1.0.x). PK96670 (Cumulative iFix 20 for WCM v6.1.0.x). PK98132 (Cumulative iFix 21 for WCM v6.1.0.x).
Problem conclusion
This cumulative iFix targets a number of problem areas in the GA release of WCM v6.1.0.3 and WCM v6.1.5.0. 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 22 for WCM v6.1.0.3 and WCM v6.1.5.0: PM01153 (ITEMNOTFOUNDEXCEPTION WHEN RENDERING CONTENT ITEMS.) PM02111 (JSR286 LRP PORTLET STATUSBAR AND ERROR ICONS MISSING WITH THE PAGE BUILDER THEME.) PM02113 (URLCMPNT TAG WITH TARGET PAGE MAPPING NOT WORKING IN SERVLET RENDERING.) PM02120 (COM.IBM.WPS.HIDDENPAGE.WCM.CONTROL.AUTHORING_PORTLET IS UNKNOWN MIGRATION FROM 60X.) PM02142 (ITEMNOTFOUNDEXCEPTION FOR DRAFT ITEMS WHEN RUNNING REFRESHALLITEMS MODULE.) PM02144 (WCM AUTHORING IS PRODUCING AN MALFORNED ANCHOR TAG WHICH CAUSES PROBLEMS FOR WEBKING.) PM02147 ("NONE" STILL VISIBLE WHEN ADDING USER/GROUP TO EMPTY USER SELECTION FIELD.) PM02151 (COM.IBM.WORKPLACE.WCM.SERVICES.VALIDATION.VALIDATIONSERVICE WAS NOT FOUND WHILE SAVING IMAGE CMPNT.) PM02154 (ZIPEXCEPTION OCCURS WHILE SYNDICATING.) PM02034 (MAXIMUM ROWS PER TABLE ATTRIBUTE BECOMES FIXED NUMBER OF ROWS.) Affected Users: All Users Requisites: pre-requisite Portal Component: WCM 6.1.0.3 GA build 19.81 pre-requisite interim fixes: None. Platform Specific: No Fix pack: This fix will be integrated into WP v6.1.0.4 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 - Update the deployed PDM Doc List 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 PDM Doc List 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. After the iFix is installed, check the status of the node you are upgrading in the Deployment Manager administrative console. If the status is Not Synchronized, ensure that the node agent is running on the node and then perform the following steps: In the Deployment Manager administrative console, click System Administration>Nodes. For the node with a status of Not Synchronized, click Synchronize. After the synchronization is complete, wait at least 30 minutes before performing the next step because the ear expander is still running. Restart the WebSphere_Portal server on the secondary node. 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. 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. - 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 - Restart WebSphere Portal. 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
PM02501
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-12-01
Closed date
2009-12-01
Last modified date
2009-12-04
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
R615 PSY
UP
[{"Business Unit":{"code":"BU051","label":"N\/A"},"Product":{"code":"SUPPORT","label":"IBM Web Content Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1.0.1","Line of Business":{"code":"LOB33","label":"N\/A"}}]
Document Information
Modified date:
21 December 2021