Migrate a remote rendering portlet

 

+

Search Tips   |   Advanced Search

 

After migrating the primary data re-configure all remote rendering portlets to use the migrated data.

Migrate Web content data on the system that the remote rendering portlet is configured to use before migrating a remote rendering portlet.

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

  1. If you are migrating one or more remote rendering portlets on a primary system, go to step 3. If you are migrating one or more remote rendering portlets on a secondary system, copy the summary configuration files created when migrating the primary system to a folder on the secondary system. See summary.path in the data migration topic.

  2. Update...

    portal_server_root/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 IWWCM summary configuration files were copied in step 1.

    • virtual.portal:

      If migrating a remote rendering portlet located on a virtual portal, enter the name of the virtual portal.

  3. Update...

    portal_server_root/wcm/migration/config/remote_rendering.properties

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

    • remote.host.base.path.list:

      Enter the remote host base path of old remote rendering portlet. This is the "Web Content Management Server Host" specified in the old remote rendering portlet configuration. For example, 

          remote.host.base.path.list=http://oldhostname:9081

      If all the old remote rendering portlets use data from a single system we can specify remote.host.base.path.list=all.

    • WCM_REMOTE_HOST_BASE_PATH:

      Enter the remote host base path of the server the remote rendering portlet is being migrated to. For example, 

          remote.host.base.path.list=http://newhostname:9081

  4. Run the wcmmigrate configure-remote task from the directory...

    portal_server_root/wcm/migration

    ...where portal_server_root is the install directory path of the current version of IBM WebSphere Portal.

    • Windows:

      wcmmigrate.bat -user username -password password configure-remote

    • UNIX:

      ./wcmmigrate.sh -user username -password password configure-remote

    • i5/OS:

      wcmmigrate.sh -user username -password password configure-remote

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

  5. 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.

  6. Verify the configuration of the migrated remote 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