Steps for migrating WCM data from 6.0 to 6.1

To migrate from IBM WebSphere Portal V6.0 or later, you must connect to a copy of the earlier portal's JCR database domain before running the migration tasks.

Important: If the new portal installation uses the same DBMS as the earlier portal, you must use the same database driver to connect to the copy of the earlier portal's JCR database domain. For example, if you configured the new portal's release domain to use DB2 with a DB2 Type 4 driver, and the earlier portal's JCR database domain also uses DB2, you must use a DB2 Type 4 driver to connect to the copy of the earlier portal's JCR database domain. If the new portal uses Oracle for the release domain and the earlier portal's JCR database domain uses a different DBMS such as DB2, you do not need to use the same database driver to connect to the copy of the earlier portal's JCR domain.

Follow these steps for migrating data

1. Create a separate copy of the earlier WebSphere Portal JCR domain.


2. On the new portal, locate and update the properties files listed below to reflect a connection to the JCR domain copy that you created in the previous step:
   * wp_profile_root/ConfigEngine/properties/wkplc.properties
   * wp_profile_root/ConfigEngine/properties/wkplc_comp.properties
   * wp_profile_root/ConfigEngine/properties/wkplc_dbtype.properties
   Note: The value of the parameter jcr.DbSchema in the wkplc_comp.properties file must be specified in uppercase (for example, jcr.DbSchema=JCR).


3. Change to the wp_profile_root/ConfigEngine directory, and then enter the following commands to validate the configuration properties:
   
   ConfigEngine.bat validate-database-driver -DTransferDomainList=jcr
   ConfigEngine.bat validate-database-connection -DTransferDomainList=jcr
   


4. Stop the WebSphere_Portal server.


5. Connect WebSphere Portal Version 6.1 to the copy of the earlier JCR domain:
   ConfigEngine.bat connect-database-jcr-migration
   Note: The portal-post-upgrade task uses database catalog functions during execution. These catalog functions need to be correctly bound to the database for the portal-post-upgrade task to work. Refer to the documentation for your DBMS to determine how to do this.
   


6. If you used IBM Lotus Web Content Management in the earlier portal, delete any V6.0.1.x syndicators or subscribers that were copied with the JCR database domain. See Setting up a syndication relationship.


7. If you are migrating Web Content Management you must also run the following task:
   ConfigEngine.bat create-wcm-persistence-tables


8. Verify that the new portal server starts.