i-fix Name: PK30057 Problem Summary: cumulative iFix 1 for wcm600 Detailed Problem Description: This cumulative iFix targets a number of problem areas in the GA release of wcm600. Specifically, defects in the following areas have been targeted: Syndication, Migration, Versioning, Prerendering and Performance. Problem Analysis: A number of defects have been rolled up into this iFix. Failing Module: WCM - Web Content Management (General) Problem Solution: 10831 Portlet unavailable after AccessDeniedException as a result of RTE embedded image permissions. 05081 WCM authoring fails after 3.5 hours (iSeries System) 05095 Migration: Import fails Authorization Data Exception 10496 summary file encoding causes broken portlet configurations 10409 Apostrophe no rendered correctly in RTE in IE 10340 API: Content created and saved without calling setTitle leaves title blank 10325 Users task for migration failing with Class Cast exception 05034 Unable to syndicate 48k content items 10117 Unable to save object in repository if workflow is changed from 3 to 1 stage on draft content 09956 Restore all: Restore all leaves undefined references on actions 10793 Migration fails if exported data contains a versioned site or site area 10383 WCM Authoring Form can be submitted early which can lead to data loss 10364 ArrayCmpnts are slow saving for large amounts of HTML 10285 Migration: Import fails with node does not exist 10235 MemberFixer : OOM during update mode, does not log out of jcr 05004 PERF: authoring PVT scenario performance is very poor compared with 5103 09201 Migration Performance: Import takes over 12 hours on 9k items 05094 Migration : IllegalStateException while rendering inline Array Cmpnt 05098 java.lang.NullPointerException occurring during authoring on save 10513 SiteAreas and Templates aren't displayed using DisplayNames in menus 10508 Search is not working on image picker of rich text component. 10494 Index OOB exception during migration data transform 05064 EventLogService needs to use PagingIterator for Content queries on initialize 10379 Text Element should be broken into 4k chunks, not 256 bytes. 10377 Saving with the API does not update Authoring cache 10347 Infocenter: Navigator Type Examples page needs to be updated 05042 update record not getting deleted during syndication 05040 Unrecognized reference for workflow reject stage and for image references from link cmpnts. 10242 API: ContentLinks can't be copied with workspace.copySiteFrameworkDocument 10168 Migration: Links not working due to no library path 10151 Error occurs within portlet if restoring or reading workflow stage with a deleted action 10129 Restoring content not retaining current workflow if version with different workflow is restored 10124 pre-rendered object/library name with space can't be found via webserver access 10062 Syndication/Library: Subscriber/Library not showing on horizontal cluster after you create it 10019 Migration: IDComponent field attribute needs to change to title if it was name 09923 Restarting workflow entering first stage twice. 09835 Versions of Deleted Items don't show sitepath 09834 Get incorrect error message when trying to Restore deleted items that are same name siblings 03629 Advanced Search - Cant add items when searching in Recent items 01359 API javadoc description for the ContentComponents should make clear these are content elements 00108 5.1.0.1: Regression-SaveAs doesn't work correctly with Scheduled Action 10172 Items restored by label & date got locks and ticks even when the restore all is finished. 10100 API: Saving an edited LibraryLinkComponent sometimes throws a NPE 09979 The name field must consist error shown even when nothing is entered in name field. 09890 GVT regression: restore all by label can't work for Chinese label 09806 Autodata conversion not working for Link and JSP element. 09799 API: Immediate second API method callafter update doesn't reflect changes 09795 Library: reason should be given as to why a library can not be deleted. 09761 API: Saving an edited DateComponent sometimes throws a NPE 09586 An error occurred within the portlet when edit a restored version of authoring template 08480 Editor of the library and owner of the item don't see Unlock button. 04179 Cannot see "Versions" button in a newly authoring template in read mode if i havent closed & reopened the AT 03871 Default workflow can't be removed completely after choosing none on the workflow selection pane. 09649 Rendering Inline Component class : NPE will continue render 09864 Migration: Fails on Import when DB is restarted and resume occurs with DB lock Affected Users: All Users Requisites: pre-requisite Portal Component: WCM 6.0.0.0 GA build 298.0 pre-requisite interim fixes: None optional recommended fixes: PK30516 (JCR) Platform Specific: No Fix pack: This fix will be integrated into WP v6.0.0.1 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/software/genservers/portal/support Preparation: If you have changed the CellName from the default values during the installation of Portal, you would need to also update this change in the [WPS_ROOT]\config\wpconfig.properties file. If you have not changed the default CellName value during the Portal installation, you can skip this step, and continue. - Go to [WPS_ROOT]\config\wpconfig.properties - Search for the "CellName=" field - Change the CellName to point to what you have changed it too, during the installation. 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). - Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm - Stop and Restart the WebSphere Portal Server. - Update the deployed remote rendering portlet: - 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 portlet WAR file located in: [PortalServer]\wcm\installableApps - Click Next and Finish - Log out of Portal for the changes to take effect. - Please note, the following configuration setting is optional and may be appended to your [WPS_ROOT]\wcm\shared\app\config\wcmservices\WCMConfigService.properties <-- begin --> # enable to only drop the rendering caches at the end of syndication for a performance improvement render.cache.delaysyndicationflush = false - Please note, that if you are using Oracle as your DB Persistency, then you will need to download and install Oracle Database 10g Release 2 (10.2.0.2) JDBC Driver for use with WCM and Portal. This is the latest driver at the Oracle site. Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal. Note: If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open /profiles//config/cell//cell.xml and there will be a field indicating the cellname. (by default its called servernameCell01) For each node you are applying the ifix too, you need to: - Go into /config/ - Open up wpconfig.properties - Search for the properties Field "CellName=" - Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" 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. - Run [WPS_ROOT]\config\WPSconfig.bat|sh update-wcm - Stop and Restart the WebSphere Portal Server. - Update the deployed remote rendering portlet: - 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 portlet WAR file located in: [PortalServer]\wcm\installableApps - Click Next and Finish - Log out of Portal for the changes to take effect. Refer to the "Maintaining the cluster" section of the Portal Information Center for information on installing fixes in clustered environments while maintaining continuous availability of your Portal. Note: If you are tryng to deploy the ifix on a horizontal cluster, Before you run the portal update installer, please take note of the cell name of your deployment manager. You can get the cell nameby going to the deployment manager machine, open /profiles//config/cell//cell.xml and there will be a field indicating the cellname. (by default its called servernameCell01) For each node you are applying the ifix too, you need to: - Go into /config/ - Open up wpconfig.properties - Search for the properties Field "CellName=" - Change it to point to the deployment manager's cellname. i.e. "CellName=DeploymentManagerCell" 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.