Migrate a local rendering portlet

 

+

Search Tips   |   Advanced Search

 

After migrating your primary data you can re-configure all local rendering portlets to use the migrated data.

You must migrate Web content data before migrating a local rendering portlet.

If you have a small number of local rendering portlets, it may be simpler to install and configure new local rendering portlets to use the migrated data instead of migrating any existing portlets.

  1. If you are migrating one or more local rendering portlets on a primary system, go to step 2.

    If you are migrating one or more local rendering portlets on a secondary system, copy the summary configuration files created when migrating your primary system to a folder on the secondary system.

    See summary.path in the data migration topic.

  2. Update....

    was_profile_root/PortalServer/wcm/migration/config/migration.properties

    Confirm that the following parameters are set as specified and modify them if necessary:

    • summary.path

      The path on the local file system where the old IBM Lotus WCM summary configuration files were copied in step 1. This is not required on a primary server.

    • virtual.portal

      If migrating a local rendering portlet located on a virtual portal, enter the context extension for the virtual portal URL. See the URL Context description row in the Virtual Portal Manager portlet. This is not required on a primary server.

    • portal.pre.upgrade.backupDirectory

      This is the location of the backup directory where the portal-pre-upgrade task stores the data that will be exported. This is required on both primary and secondary servers.

  3. Run the wcmmigrate configure-local...

      cd was_profile_root/PortalServer/wcm/configcm/migration/
      ./wcmmigrate.sh -user username -password password configure-local

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

  4. 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 WCM migration for further information.

  5. Verify the configuration of the migrated local rendering portlet.

    Restart the portal server after completing the above steps to verify that the portlets have been configured correctly.

 

Parent topic

Migrating a primary Web content system

 

Parent topic

Migrating a secondary Web content system