Migrate Web content data

 

+

Search Tips   |   Advanced Search

 

When migrating a primary system, first migrate the old Web content data from a single Web content system. This would normally be an authoring system. If you have decentralized authoring systems, aggregate all the current data onto a single system using syndication and then migrate the data from this system.

 

Pre-Migration

  • Ensure that you have completed the migration of the IBM WebSphere Portal product to the new system. Any Web content pages and rendering portlets that were present on the old system are migrated to the new system but are disabled until you complete the subsequent migration of the Web content data.

  • Before migrating Web content data, run the following tools on the old system and resolve any problems:

    Refer to the WebSphere Portal 5.1 information center for details.

  • Migrating large amounts of data will take a long time. Ensure you plan to perform migration at a time that will not conflict with peak usage.

  • Password-protected files are not supported in Web content data. If you have any resources containing password-protected files that you intend to migrate from a previous version of IWWCM, remove the password protection on the resource before you migrate. If you do not remove the password protection, the migration will fail.

  • Any Personalization components that do not reference a Personalization rule or content spot must be deleted prior to data migration.

  1. Copy the folder...

    portal_server_root/wcm/config/

    ...from the old system to a temporary migration folder on the new system. Do NOT overwrite...

    portal_server_root/wcm/config/

    ...on the new system.

  2. Depending on which data repository the old system uses, copy the following files from the old system to...

    portal_server_root/wcm/migration/exporter/lib

    ...on the new system. These will typically be:

    IBM Cloudscape db2j.jar
    IBM DB2 Universal Database Enterprise Server Edition db2jcc.jar
    db2jcc_license_cu.jar
    db2jcc_license_cisuz.jar
    Oracle Enterprise Edition classes12.jar
    Microsoft SQL Server Enterprise Edition mssqlserver.jar
    msbase.jar
    msutil.jar

  3. Update...

    portal_server_root/wcm/migration/exporter/classpath.properties

    ...by adding the names of the files copied in step 2 to the value of the property..

    exporter.classpath

  4. If migrating from a DB2 repository, edit the following files located in the temporary migration folder...

    portal_server_root/wcm/config/

    ...created in step 1...

    • aptrixjpe.properties

      Set...

      jdbc.url=jdbc:db2://<db2 host name>:<port number>/wcmdb

      ...to point to the database of the old system. Ensure that there are no spaces before or after the URL.

    • connect.cfg

      Set...

      <jdbc:db2://<db2 host name>:<port number>/wcmdb driver="com.ibm.db2.jcc.DB2Driver" />

      ...to point to the database of the new system.

      The port number for DB2 on the new system can be found under...

      %systemroot%/system32/drivers/etc/services

      ...on Windows systems or...

      /etc/services

      ...on UNIX systems.

  5. If migrating from an embedded Cloudscape repository, stop the portal server on the old system and then copy this database to the new system before migrating WCM. Edit the following files located in...

    portal_server_root/wcm/config/

    ...created in step 1

    • aptrixjpe.properties

      Set...

      jdbc.url=jdbc:db2j:path_to_database

      ...to point to the location of the Cloudscape database on the new system and ensure that there are no spaces before or after the URL.

    • connect.cfg

      Set...

      <jdbc:db2j:path_to_database driver="com.ibm.db2j.jdbc.DB2jDriver" />

  6. Update...

    portal_server_root/wcm/migration/config/migration.properties

    ...on the new system and set the following parameters...

    export.path The path on the local file system where exported data will be saved.
    import.path The directory on the local file system where transformed data is saved.
    summary.path The path on the local file system where summary configuration files will be created. These files will be used when migrating a secondary system.
    legacy.config.path The path on the local file system where the old WCM configuration is located. See step 1.
    import.servlet.url The URL of the import servlet, running on the new system. Replace localhost with the appropriate host name for the new system.
    import.library.name The name of the library created during import.
    import.library.locale The ISO locale of the library created during import.

    This must be the same as the data being migrated. It is important this is set accurately, so that the search functionality in the imported site functions correctly.

    See...

  7. Increase the total transaction lifetime timeout of the new WebSphere Portal server to 1200 seconds through the WebSphere Application Server administrative console. Go to...

    Application Servers | server | Container Services | Transaction Service

    Make a note of the current total transaction lifetime timeout so that it can be restored in step 10.

  8. Restart the portal application server.

 

Migration

  1. Go to the migration directory on the new system...

    cd portal_server_root/wcm/migration

  2. Run the wcmmigrate all-data task...

    • Windows:

      wcmmigrate.bat -user username -password password all-data

    • UNIX:

      ./wcmmigrate.sh -user username -password password all-data

    • i5/OS:

      wcmmigrate.sh -user username -password password all-data

    The user specified in the command must be a WebSphere Portal administrator.

  3. Verify the migration by reviewing the migration console. The message "command successful" is displayed after a successful migration. If the message "command failed" is displayed upon completion review the previous steps. See Troubleshooting Web Content Management migration for further information.

    The total number of items exported, transformed and imported may not be equal, as some items will be merged and other items added during the migration process.

  4. Restore the total transaction lifetime timeout setting to the original setting that was changed in step 7.

  5. Restart the portal application server.

 

Post-Migration

  1. Review the configuration of the library created when the data was migrated and make changes as required.

    For example, enable user access to this library by adding users and groups to each library role.

  2. Syndicate the migrated data to all the other servers in the new Web content system.

 

Parent Topic

Migrating a primary Web content system