• Versioning:
  • No control of number of versions to be maintained at content type level. It’s all or none
  • No control over which content type needs versioning and which not. Its either all or none
  • No versioning at component (Image, Menu, Navigator etc.) level  
• Syndication/ Content Publish:
  • All the syndicators will be either scheduled or none of them. You cannot choose few syndicators to be automated while leaving others as manual process
  • Once the content becomes live/published it is moved across from one to other environment. There is no way to control approval of the content for specific publisher/syndicator as with other products
  • Tough to debug the cause of failure of syndicator
  • If there are some failed items with syndicator, it is tough to determine which content items failed
  • Lack of customization
  • Syndication/Publish history view is not available 
• WCM Portlets
  • Out of the Box WCM authoring and rendering portlets are legacy IBM portlets and are not JSR standards
  • Customization is painful as it uses IBM specific code and it is not exposed 
• Customizations are
  • Tough as they are IBM legacy portlets
  • Limited set of API and taglibs available which prevents customization 
• Rendition Services
  • No rendition service available out of the box 
• Workflows
  • Basic workflows can be defined
  • Parallel workflows I do not think are possible
  • Workflows available only for Authoring templates but not for components
  • Granular level privileges not possible to implement  Example: Controlling function privileges at each stage
  • No funda of voting and group approvals and rejects 
• Caching
  • No Database caching
  • If using JSP components for a functionality through Presentation Templates, there is no Out of the Box caching available 
• Rich Text Editor
  • Out of the Box RTE adds unnecessary HTML tags while creating content. Example: Adding <p> tags
  • Out of the Box RTE doesn’t provide features like copy from word which is quite common these days 
• Context upload and Extract:
  • No Out of the Box facility to import content  to WWCM. We need to write a custom module to upload
  • No Out of the Box facility to export content in readable format. Example: XML 
• Reporting:
  • Custom build is needed for any reporting. Example: Content extract between dates to a specified format, Content changes between two dates, content status between two servers etc. 
• Secured binaries (like images, documents etc. )  are stored in database than file system
• No basic WebServices available for Content Services

• Setup desktop implementation of WWCM and Portal (6.0.1.3), using DB2 and connecting to shared LDAP. Lets refer this setup as “WS6013”
• Make sure that JCR schema is separated as a database instance
• Setup syndication from source (Environment to pick content from) to WS6013
• In parallel, setup desktop implementation of WWCM and Portal (6.1.0.2) on SAME MACHINE, using DB2 and connecting to shared LDAP. Lets refer this setup as “WS6102” 

• Once syndication is completed on WS6013, apply the following iFixes: 
  • PK57970
  • PK60183
  • PK62044
  • PK63553
  • PK64160
  • PK64247
  • PK64833
• On WS6102, apply the following iFixes: 
  • 6.1.0.2-WCM-PK85196
  • Run iFix Post install tasks
    § Run {WAS_PROFILE_ROOT}/ConfigEngine.bat remove-wcm-migration -DPortalAdminPwd=<password> -DWasPassword=<password>
    § Run {WAS_PROFILE_ROOT}/ConfigEngine.bat configure-wcm-migration -DPortalAdminPwd=<password> -DWasPassword=<password>
    § Run {WAS_PROFILE_ROOT}/ConfigEngine.bat update-wcm -DPortalAdminPwd=<password> -DWasPassword==<password>
• Disable JCR text search indexing on WS6102 at location <wp_profile_root>/PortalServer/jcr/lib/com/ibm/icm/icm.properties
• Remove all subscribers & Syndicators, and disable searches on the WS6013
• Run portal-pre-upgrade task to backup WS6013 setup
  o Run from WS6102: WPmigrate.bat portal-pre-upgrade -DbackupDirectory=<Backup Directory> -DcurrentPortalDirectory=<WS6013 Portal Directory> -DcurrentPortalAdminId=<WS6013 Portal Admin Id> -DcurrentPortalAdminPwd=<WS6013 Portal Admin Password> -DbPassword==<WS6102 Database password> -DSkipAiMigration=true
• Take backup of JCR database on WS6013
• Copy WS6013 JCR database to WS6102
  o db2 “restore database JCRDB from <backup-location> taken at <timestamp>”
• Connect WS6102 to new database by running the following commands:
  o Run {WAS_PROFILE_ROOT}/ConfigEngine.bat validate-database-driver -DTransferDomainList=jcr -DPortalAdminPwd=<WS6102 Portal password> -DWasPassword=<WS6102 WAS password>
  o Run {WAS_PROFILE_ROOT}/Run {WAS_PROFILE_ROOT}/ConfigEngine.bat validate-database-connection -DTransferDomainList=jcr -DPortalAdminPwd==<WS6102 Portal password> -DWasPassword=<WS6102 WAS password>
  o Run {WAS_PROFILE_ROOT}/ConfigEngine.bat connect-database-jcr-migration -DPortalAdminPwd==<WS6102 Portal password> -DWasPassword=<WS6102 WAS password>
  o Run {WAS_PROFILE_ROOT}/ConfigEngine.bat create-wcm-persistence-tables -DPortalAdminPwd==<WS6102 Portal password> -DWasPassword=<WS6102 WAS password>
• Run task to update Node Type
  o WPmigrate.bat update-nodetypes -DPreviousPortalVersion=6013 -Dinitial.wcm.nodetype.version=2 -DbackupDirectory=<WS6013 backup directory>
• Run database tasks to re-org information of JCR database
• Run a script on WS6102 to bring it up to 6.1 level
  o Windows: WPmigrate.bat update-wcm-data -DWasUserId=username -DWasPassword=password -DbackupDirectory=directory
• Recreate subscribers and syndicators on the 6.1 server, and rebuild search indexes, enable search

All the best !!