Skip to main content

Software  >  Lotus  >  

Recommended fixes for Web Content Management (WCM) versions 6.0.1 and 6.0.0.3
 Flash (Alert)
 
Abstract
After upgrading to IBM® Web Content Management (WCM) 6.0.1 or 6.0.0.3, there are several important fixes (interim fixes or iFixes) that should be applied on top of the cumulative fixes for each respective version. These fixes are the most critical to maintaining a successful Web Content Management solution.
 
Content
Not applying the following fixes will leave IBM Web Content Management (WCM) customers exposed to some critical known issues.
A download package containing all of these fixes is available:

To simplify the process of locating and downloading these fixes, refer to Document #4016049, "Recommended Fixes for IBM Workplace Web Content Management v6.0.1 and 6.0.0.3" for more information.



We strongly recommend upgrading to the following fixpack levels where applicable. Many of the iFixes below are included in the latest fixpacks. Please note that we have released fixpacks v6.0.0.4 & v6.0.1.1. To get these either of these releases, click the following link:
Understanding Web Content Management (WCM) 6.0.1.1 vs. 6.0.0.4 and the recommended upgrade path

In the event you cannot upgrade, then we recommend the iFixes listed below. You must follow the ReadMe instructions for these iFixes to perform a correct installation. A correct installation can include updating portlets and/or adding configuration values as necessary to the properties files.

For 6.0.1 ONLY:

1. PK42760 -- Cumulative iFix 1 for WCM 6.0.1
    This is a WPS performance fix that greatly improves the performance of WCM anonymous content viewing.

2. PK56304 - ANONYMOUS ENTITLEMENTS NOT CACHED FOR WCM CONTENT
For 6.0.0.3 ONLY:
PK42760 -- Cumulative iFix 1 for WCM 6.0.0.3

Critical iFixes for both 6.0.1 & 6.0.0.3
1. PK43246 Internet Explorer browser not caching images
2. PK44315 Simultaneous transactions involving drafts result in database deadlocks.
3. PK44317 Simultaneous transactions involving drafts result in database deadlocks.
4. PK44323 Simultaneous transactions involving drafts result in database deadlocks.
5. PK44348 Simultaneous transactions involving drafts result in database deadlocks.
6. PK44671 Changing the workflow of a published item after a failure to change the workflow, will result in both draft and published content in the repository.
7. PK44917 (After applying PK44317 on Portal using Oracle, the system will throw XA exceptions on startup.) This fix only applies to Oracle.
8. PK44516 WCM Rendering performance slow on initial load of data after the Portal server is restarted.
9. PK44775 Clicking the Save and Approve button gives the error, 'This value is required (Categories)', even if a category has been selected.
10. PK45654 -- HTML components cannot be accessed in the WCM Authoring portlet.
11. PK45987 -- Library delete module is required to delete all items under a library.
12. PK46081 -- Users able to see workflows for which they have no access.
13. PK46866 -- Deadlocks occur in DB2 when multiple users create drafts simultaneously.
14. PK47108 -- Public images rendered by WCM are not cacheable by a caching proxy server.
15. PK47111 -- Menu Cache is not cleared when a content item expires.
16. PK47120 -- Content created under new site areas not updated in menu cache.
17. PK47193 -- Publish event does not flush the menu caches.
18. PK47750 -- Draft content from published has wrong permissions.
19. PK47970 -- Menu cache fails to rebuild properly when a render request is done simultaneously as a content create or update.
20. PK48740 -- HTML Components with links fails to save.

Recommended Syndication iFixes (for both 6.0.1 & 6.0.0.3)
1. PK43267 -- Make use of JCR API to simplify syndication by creating versions directly instead of replaying them on the subscriber.
2. PK43634 -- An extra version of the deleted item appears at the subscriber when the versioning strategy is manual.
3. PK44162 -- Make use of JCR API to simplify syndication by creating versions directly instead of replaying them on the subscriber.
4. PK44395 -- Automatic syndication doesn't work after moving a content item from one site area to another site area.
5. PK44570 -- Duplicate path exception on subscriber during syndication.
6. PK44964 -- Content copied to a library does not syndicate.
7. PK45133 -- Referential Integrity Exception for delete of Default Content and Site/SiteArea in same Syndication Update.
8. PK45144 -- DuplicatePathException for items in "Deleted Items" folder.
9. PK45527 -- NonSerializableException PrincipalInformationDecorator.
10. PK45543 -- NonSerializableException PrincipalInformationDecorator.
11. PK45544 -- NonSerializableException PrincipalInformationDecorator.
12. PK45545 -- NonSerializableException PrincipalInformationDecorator.
13. PK46028 -- EventLogException prevents syndication of versions.
14. PK46368 -- DuplicatePathException for renamed and moved item that matches existing item.
15. PK46930 -- Documents with self references will not get syndicated.
16. PK46931 -- NullPointerException when syndicating document deletion summary without owner.
17. PK47379 -- NullPointerException in ResourceCmpntTransformer.
18. PK47659 -- Connection exceptions when rebuilding the event log on startup
19. PK47923 -- ContentLink moves do not get syndicated.
20. PK48275 -- Draft content links are not syndicated.
21. PK48340 -- Cached images at the subscriber do not get invalidated from the internal WCM caches after syndication.

Recommended JCR iFixes for syndication and performance (version 6.0.0.3 only):
JCR cumulative iFix for WebSphere Portal version 6.0.0.1. This iFix for Portal applies to WCM fixpacks v6.0.0.1, v6.0.0.3 and v6.0.0.4:
    NOTE: This cumulative iFix is part of the iFix download .zip files.

Recommended JCR iFixes for syndication and performance (for version 6.0.1 only):
JCR cumulative iFix for WebSphere Portal version 6.0.1 & 6.0.1.1 found at
http://www-1.ibm.com/support/docview.wss?rs=688&uid=swg24016395.

Additional WCM performance information:
Web Content Management 6.0 Tuning Guide at http://www.ibm.com/support/docview.wss?rs=688&uid=swg27008780.

Web Content Management 6.0 Best Practices Guide:
This guide also contains tuning recommendations. All tuning steps should be performed taking note of the DB2 collation settings (if using DB2), and recommended caching and optimization steps.
Best practices for using IBM Workplace Web Content Management V6

Achieving optimal Authoring performance in v6 of Web Content Management:
Achieving optimal Authoring performance in v6 of Web Content Management
 
 
 

Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
This material provides me with the information I need.




This material is clear and easy to understand.




Did the information help you to achieve your goal?
What updates, improvements, or related information would you like to see in this document?
Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
Input the verification number to submit feedback:
Document information
 Product categories:
 Software
 Enterprise Content Management
 Content Management
 Workplace Web Content Management
 General
 Operating system(s):
  AIX, HP-UX, Linux, Solaris, Windows, i5/OS
 Software version:
  6.0.0.3, 6.0.1
 Software edition:
  Java edition
 Reference #:
  1260790
 IBM Group:
 Software Group
 Modified date:
 2009-09-14

Translate My Page
 
 

Rate this page

Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.