Portal, V6.1
Migrate version 5.1 Web content
You migrate your Web content data and portlets after migrating your WebSphere Portal server.
- WCM migration overview
This topic contains information about the processes involved in migrating IBM Lotus WCM data and portlets.- Migrating a primary Web content system
These tasks provide detailed information used to migrate a Web Content Management primary system. This would normally be an authoring system. If you have decentralized authoring systems, you will need to aggregate all you current data onto a single system using syndication and then migrate the data from this system. Primary migration will migrate data, rendering portlets and user profile information.- Migrating a secondary Web content system
These tasks provide detailed information used to migrate a Web Content Management secondary system. This can be a staging system, delivery system, test system or another authoring system. Only rendering portlets and
user profiles are migrated on secondary systems. Syndication is used to transfer data from the primary system to secondary systems.- Migrating a remote rendering portlet
After migrating your primary and secondary servers also re-configure all remote rendering portlets on any remote servers to use the migrated data.- Troubleshooting WCM migration
This topic details some ways to troubleshoot an unsuccessful migration.- V5.1 to 6.1 post migration steps
The IBM Lotus WCM migration process does not automatically update your Web content to use all the new features of the current release. The following steps are recommended to update your old Web content to take advantage of the new WCM features.
Parent topic
Migrating Web content