Migrate a remote rendering portlet

 

+

Search Tips   |   Advanced Search

 

After migrating your primary and secondary servers also re-configure all remote rendering portlets on any remote servers to use the migrated data.

The Web content migration tool does not need to be installed on remote servers that host the remote rendering portlets you are migrating.

You must 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. Update the file...

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

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

   • virtual.portal

     If migrating a remote 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.

   • 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 should be copied from the original server that your remote rendering portlets source their content from and where WebSphere Portal migration has taken place to the server where you are going to run the configure-remote task on. Once you have copied this directory, reference that location.

     This directory can be very large. If you do not want to copy the entire contents of this directory, you can just copy the following files:

     • <migration_backup_dir>/PortalServer/migration/work/default/importAllResults.xml

     • <migration_backup_dir>/PortalServer/migration/work/default/mappings/base32_mapping.properties

   • remote.configure.url

     Uncomment this setting and set this to the URL of the server that hosts the remote rendering portlets you are migrating. For example:

     http://[REMOTE HOST]:[REMOTE PORT]

2. Update the file...

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

   Confirm that the following parameters are uncommented and 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 your old remote rendering portlets use data from a single system you 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,

     WCM_REMOTE_HOST_BASE_PATH=http://newhostname:10040

3. Run...

   was_profile_root/PortalServer/wcm/configcm/migration/wcmmigrate configure-remote

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

   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 you will need to troubleshoot the migration.

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

6. Update the remote rendering portlets on your remote server:

   1. Login to your migrated server as an administrator.

   2. Go to...

      Administration view | Portlet Management | Web Modules | Update | Browse

   3. Select...

      portal_server_root\wcm\prereq.wcm\installableApps/ilwwcm-remoterendering-portlet.war

   4. Click Open.

   5. Click Next.

   6. Click Finish.

7. If you are using the LTPA token to authenticate between servers create and export the LTPA token:

   1. On the WAS, start the administrative console and log in.

   2. Select...

      Security | Secure administration, applications, and infrastructure | Web security | Single sign-on (SSO)

   3. Enter the fully qualified domain name and then click OK.

   4. Click Save to save the changes to the master configuration.

   5. Click Authentication mechanisms and expiration.

   6. Type the password in the Password and Confirm password fields.

   7. Type the name of your file in the Fully qualified key file name field.

   8. Click Export Keys. The key is exported to the wp_profile directory.

   9. Click OK.

   10. Click Save to save the changes to the master configuration.

   11. Log out from the console.

   12. Copy the key file that was created during the export process to the directory...

       /install_root/wp_profile

       ...on the server hosting the content that is displayed in your remote rendering portlet.

   Import the LTPA token on the server hosting the content that is displayed in your remote rendering portlet:

   1. On the WAS, start the administrative console and log in. This is the server you intend to import the LTPA token to.

   2. Select...

      Security | Secure administration, applications, and infrastructure | Authentication mechanisms and expiration

   3. Type the password in the Password and Confirm password fields.

      This must be the same password you entered on the source server.

   4. In the Fully qualified key file name field, type in the name of the key file that you copied to the wp_profile.

   5. Click Import Keys.

   6. Save any changes to the master configuration as needed and make sure your given a successful message.

 

Parent topic

Migrating version 5.1 Web content