Prepare to migrate Web content

If you plan to migrate Web content from v6.0.1.x, complete the tasks described here before you begin migration.

  1. To reduce the load on the database during migration and syndication, it is recommended that you disable JCR text search indexing on the WebSphere Portal v7.0 server before migration.

      Edit

        WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm/icm.properties

      and set jcr.textsearch.enabled to false. After the file is updated, restart server for the changes to take effect. It may take some time to rebuild the indexes when you re-enable JCR text search indexing after migration.

  2. Update the expire.blankdate.immediately property in the WCM WCMConfigService service.

      In v6.0, items that had no expire date specified would never expire. In v7.0, items with no expire date expire as soon as an expire action is triggered. If you do not configure the v7.0 server to use the earlier expiration behavior, all published content may be expired when migrated. To start using the new behavior, you can change this setting back to true after completing migration.

      1. Log in to the IBM WebSphere Application Server administration console on v7.0 server.

      2. Click Resources -> Resource Environment -> Resource Environment Providers.

      3. Edit the WCM WCMConfigService service and ensure that the expire.blankdate.immediately property is set to false.

      4. Save changes.

  3. On the source portal server, remove locks on all Web content items:

    1. Go to the Administration view.

    2. Go to Portal Content -> Web Content Libraries.

    3. Click View Locked Items.

    4. Select all items and then click Unlock.


Parent

Prepare for migration from v6.0.1.x


Related tasks


Set service configuration properties

 


+

Search Tips   |   Advanced Search