">
Subscribe

Quick guide to WWCM migration from 6.0.1.3 to 6.1.02

0

Posted on : 10-11-2009 | By : shishank | In : IBM WWCM, Migration

Scenario: WWCM migration from V6.0.1.3 to WWCM 6.1.0.2.  We have a current install of WWCM 6.0.1.3 where all the content reside and is available to end users. We have setup WWCM 6.1.0.2 and the scenario is to migrate just WCM content across from older to newer version.Here is a quick guide to the steps we followed:

  • 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 !!

Post a comment