v6.1 Web content post migration tasks

Once you have completed the WebSphere Portal migration steps, you need to perform these additional steps to complete web content migration.

Context root settings for secondary nodes in a cluster

If you are migrating a cluster, update the context root for Web Content Manager on any secondary nodes to ensure that web content is displayed properly. To update the context root...

1. On the primary node, view ...
   WP_PROFILE/ConfigEngine/properties/wkplc.properties

2. Note the value of the WpsContextRoot property.

3. On each secondary node, edit wkplc.properties, and set the value of the WpsContextRoot property to match the value on the primary node.

4. On each secondary node, run the ce-action-update-wcm-cluster-variable-map task from the WP_PROFILE/ConfigEngine}}} directory:

   • Windows: ConfigEngine.bat ce-action-update-wcm-cluster-variable-map -DWasUserId=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo

   • UNIX: ./ConfigEngine.sh ce-action-update-wcm-cluster-variable-map -DWasUserId=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo

   • i: ConfigEngine.sh ce-action-update-wcm-cluster-variable-map -DWasUserId=username -DWasPassword=foo -DPortalAdminId=username -DPortalAdminPwd=foo

JSP files and Web content plug-ins

• Any JSP files used on old system will need to be manually copied to new system.

• Any Web content plug-ins used on old system, such as custom workflows, will need to be manually copied to new system and enabled.

Search Indexes

You will need to rebuild search indexes after migrating to v7.0:

1. Stop the portal server.

2. Delete all the index directories under WP_PROFILE/PortalServer/jcr/search

3. Restart the portal server.
   The search indexes should be rebuilt the next time the index maintenance interval is reached.

4. If the index directory is not built, edit a document and save it, and try manually rebuilding the search index.

Remote rendering portlets

If you migrated the IBM API rendering portlets, update the migrated remote rendering portlets to v7.0:

1. Log in to migrated server as an administrator.

2. Go to the Administration view and then Portlet Management.

3. Select Web Modules.

4. Click Update.

5. Click Browse.

6. Select the file called ilwwcm-remoterendering-portlet.war from the $PORTAL_HOME/wcm/prereq.wcm/installableApps folder of v7.0 server. This must be a content server installation as this file is not installed on an administration server installation.

7. Click Open.

8. Click Next.

9. Click Finish.

The configuration settings of remote rendering portlets on remote servers will be unchanged after you have migrated servers. If migrated servers use the same naming conventions as old servers, then you will not have to re-configure remote rendering portlets. If you have changed the naming conventions of migrated server, such as giving migrated cluster a different name than old server cluster, then you will have to re-configure remote rendering portlets.

The migrated portal URL takes this form:

http://host_name:port_number/original-context-root_migrated/portal

For example, if original portal URL is http://www.example.com:10040/wps/portal, the URL for the migrated portal is http://www.example.com:10040/wps_migrated/portal

If you have a small number of remote rendering portlets, you can edit the configuration settings of remote rendering portlets manually. If you have a large number of remote rendering portlets, then you can use the XML configuration interface to re-configure remote rendering portlets. To do this you will have to export the pages containing remote rendering portlets:

• You can use the XML configuration interface (xmlaccess command) to export the remote rendering portlet web application and all related portal pages.

• You can also use the Export Pages portlet in the portal's administration to export the entire page hierarchy containing the remote rendering portlets.

Once exported, change the value of the WCM_REMOTE_HOST_BASE_PATH variable for all the portlets to v7.0 servers. This updated XML file can then be imported using the xmlaccess command or the Import XML portlet.

If you are migrating from version 6.0.x, a full export is also performed during a full WebSphere Portal migration, so remote rendering portlet changes can also be made to the allout.xml file before running the portal-post-upgrade task.

Parent: Migrate a V6.1.x clustered environment

Previous

Upgrading node profiles

Previous

Configure resource management and site management in a cluster

Related concepts

JSP elements

Related information

Work with xmlaccess.sh

January 11, 2012

  Corrected ConfigEngine script name. Was missing "ce-" 2011/12/15 documentation refresh Added context root info

+

Search Tips   |   Advanced Search