Plan for migration

Portal, V6.1

Plan for migration

+
Search Tips | Advanced Search

The WebSphere Portal administrator who manages migration should have appropriate skills in the components that are used for example...

Database
LDAP
IBM WAS
IBM Lotus WCM
etc...

Checkpoint Notes
Version and family Which product version and family is deployed in the existing environment?
Which product version and family do you want to migrate to?
Migration is supported between the same product families (Express, Express Plus, Enable, Extend), and from Express to Enable, Express Plus to Extend, Express to Extend, and Enable to Extend.
If you are using WebSphere Portal v6, 6.0.1, or 6.0.0.1, upgrade to either v6.1.1 or 6.0.1.3 before migrating to V6.1. For instructions on upgrading, see the WebSphere Portal Version 6.0 information center.
Migration is not supported from WebSphere Portal Express or Express Plus V5.0.2.2 or 5.0.2.3 on Linux.
Deployment scenario Do you have a standalone server environment or a clustered server environment?
Hardware What hardware does the existing portal run on?
Do you plan to migrate to the same hardware or to new hardware?
Resource limitations might prohibit running earlier and newer versions of WebSphere Portal concurrently on the same machine.
Operating system What OS and version does the existing environment run on?
Does the target version that you want to migrate to support that OS and version?
You can migrate from an older version of an operating system to a newer supported version of that OS or from a 32bit version of an OS to a supported 64bit version of that OS
Migrating between different OSs is not supported. For example, you cannot migrate from a Windows operating system to a UNIX operating system.
User registry What does the existing portal installation use to store user account information:

LDAP
WebSphere Portal database
Custom user registry

If you use LDAP, do you plan to move to a different LDAP server?
Perform maintenance cleanup on users and groups as needed before migrating. For example, clean up deleted users and their personalized pages before starting migration.
If the new version of WebSphere Portal does not support the LDAP that you used with the earlier portal server, upgrade the LDAP to a supported version.
If the earlier portal and the new portal are configured to use a standalone LDAP user registry the users and groups in the new portal installation must be the same as the directory users and groups in the earlier portal installation.
Database Does the new portal installation support the database that the earlier portal installation uses?
Can the database be upgraded if needed?
You can migrate from an older version of a database server to a newer version of that database server. Migrating between different database servers is not supported. For example, you cannot migrate from a DB2 database server to an Oracle database server. When you migrate from v6.x, WebSphere Portal reuses the database tables from the earlier version in the new version. Keep these requirements in mind:

If you used IBM Cloudscape as the default DBMS in the earlier version, transfer your data to a supported DBMS before migrating since the new version does not support Cloudscape.
If the new portal installation uses the same DBMS as the earlier portal, use the same database driver when you connect to the earlier portal's JCR and Customization database domains.

When migrating Microsoft SQL Server database tables to WebSphere Portal version 6.1, the minimum level that is supported is SQL Server 2005. If you used Microsoft SQL Server 2000 with WebSphere Portal version 6.0.1.x, install and configure SQL Server 2005 before you can migrate to WebSphere Portal version 6.1. For details, see technote 1295590 on configuring Microsoft SQL Server 2005.
If you are migrating from WebSphere Portal configured to use DB2, ensure that your source environment is running DB2 Version 9.1 with Fix Pack 1 or later version.
Web server What HTTP server does the existing installation use?
Does the new installation support this HTTP server?

External security Supported IBM and third-party security settings are migrated automatically.
Virtual portals Have multiple portals been installed?
You must manually recreate each virtual portal in the new installation before you can migrate its contents. Use the task...
ConfigEngine.sh create-virtual-portal
...to create an empty virtual portal with the corresponding name and URL context for each virtual portal that you want to migrate. Virtual portals are then migrated separately, one at a time, after you migrate the portal configuration.
If a virtual portal's admin pages are located under the node...
wps.administration
...WebSphere Portal migration automatically sets these pages to the V6.1 Portal theme. If the admin pages are located under a different page hierarchy, you will need to manually set them to the V6.1 Portal theme following migration.
If you choose to update a custom virtual portal admin page hierarchy, ensure that the virtual portal's admin page has a unique name assigned to it prior to migration.
Backup Do you have a backup plan and schedule in place for the new portal server? Back up the existing portal database before starting migration.
Cleanup and maintenance Have you deleted any users from the user registry who were registered portal users? Perform the required maintenance before migrating.
If you are migrating from V6.0, have you deleted portal pages?
Does your portal site contain orphaned data?
Perform the required maintenance before migrating.
Have you installed all required fixes that apply to the earlier WebSphere Portal installation? Install all required fixes before migrating.
Have you changed the default settings of the scheduled cleanup service? Changes to the scheduled cleanup service settings are not migrated. If you modified these settings in the earlier portal and want to continue using the same settings in the new portal, update the settings on the new portal.
Custom themes and administration Does the earlier portal installation use custom themes?
Does the earlier portal use custom administration themes? Custom administration themes cannot be migrated from V5.
Does the earlier portal use customized administration portlets or pages?
Does the earlier portal use customized global settings?
Have any portal service configurations been customized?
Custom portlets Does the earlier portal have any portlets that were developed by using Struts Framework? Custom portlets must be manually copied to the new portal installation.
Does the earlier portal have any portlets that were developed by using IBM Portlet API? The IBM Portlet API is deprecated in WebSphere Portal V6.0 and later. The recommended approach is to migrate existing custom portlets as is and then refactor them using JSR 168 Portlet API.
Does the earlier portal have custom portlets that use Click-To-Action? The pbportlet.jar file must be updated.
Are any portlets deployed as part of an Enterprise Application by using an EAR file?
Do any custom applications in the earlier portal use private IBM APIs?
Have you installed and deployed third-party portlets? Third-party portlets must be certified for use with the latest version of WebSphere Portal.
Remote portlets To migrate remote portlets (portlets that are provided as WSRP services), ensure that the WSRP Producer is available before you run the portal-post-upgrade task to import content to the new portal installation.
Private wires Do you have portlets that use private wires? Private wires cannot be migrated from V6.0.1.x because of a limitation in the earlier version.
Private wires may not migrate successfully from V5.0.1.x if the portlet, portlet instance, or page that the wire references is removed. In such cases, a warning trace message is logged and the migration process continues.
Search Do you want to migrate custom search collections? Search Web collections that were created in an earlier version of WebSphere Portal can be exported and imported into V6.1.
The pre-defined categorizer option in WebSphere Portal V5.1.x and 6.0.x is no longer available starting in V6.1. If you used this option to create search collections, you can import the search collections into the current version after enabling the required parameter. For details, see technote 1306912.
Personalization What is your migration scenario for personalized portal content?
To determine which migration procedure to use, refer to Migrating personalized portal content.
If you are migrating from V6.0.1.1 or V6.0.1.3, connect to a copy of the earlier portal's JCR database domain before running the migration tasks. See Sharing JCR domain data. Then refer to Migrating V6.0.x personalization data.
If you are migrating from V5.1.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, you can migrate the personalization data after you migrate the core portal. Follow the procedure:

Migrating V5.1.x personalization data stored in the JCR
Migrating V5.1.x exported personalization data from the file system

Composite applications Do you have composite applications to migrate?

Business process applications

Document Manager Do you have content stored in document libraries? Document Manager is not available in WebSphere Portal V6.1 and is effectively replaced with a stand-alone IBM Lotus Quickr server that is integrated with your WebSphere Portal environment.
For general guidance, refer to Migrating documents from Portal Document Manager to Quickr Document Libraries.
IBM Lotus WCM WCM requires a JCR repository of the same version. Even though you might have different version repositories stored in the same database, WCM V6.1 only works with the V6.1 repository.
If you have any WCM data that references a Portal Document Manager library, replace the Web content that was stored as a document in the document library before you begin the migration process. See Document migration.
For additional information, see Migrating Web content.
Business portlets See Deprecated business portlets.
Collaborative portlets Domino Web Access, Lotus Notes View, and Lotus Document Viewer are migrated with other portlet applications.
For information on deprecated portlets including My Lotus QuickPlaces, Inline QuickPlaces, Domino Document Manager, and Lotus Web Conferencing, see Deprecated collaborative portlets.

Parent topic
Migrating WebSphere Portal

Related concepts

Use WSRP services
Delayed cleanup of deleted portal pages

Related information

Technote 1295590
WebSphere Portal detailed system requirements
Technote 1306912

	Checkpoint	Notes
Version and family	Which product version and family is deployed in the existing environment? Which product version and family do you want to migrate to?	Migration is supported between the same product families (Express, Express Plus, Enable, Extend), and from Express to Enable, Express Plus to Extend, Express to Extend, and Enable to Extend. If you are using WebSphere Portal v6, 6.0.1, or 6.0.0.1, upgrade to either v6.1.1 or 6.0.1.3 before migrating to V6.1. For instructions on upgrading, see the WebSphere Portal Version 6.0 information center. Migration is not supported from WebSphere Portal Express or Express Plus V5.0.2.2 or 5.0.2.3 on Linux.
Deployment scenario	Do you have a standalone server environment or a clustered server environment?
Hardware	What hardware does the existing portal run on? Do you plan to migrate to the same hardware or to new hardware?	Resource limitations might prohibit running earlier and newer versions of WebSphere Portal concurrently on the same machine.
Operating system	What OS and version does the existing environment run on? Does the target version that you want to migrate to support that OS and version?	You can migrate from an older version of an operating system to a newer supported version of that OS or from a 32bit version of an OS to a supported 64bit version of that OS Migrating between different OSs is not supported. For example, you cannot migrate from a Windows operating system to a UNIX operating system.
User registry	What does the existing portal installation use to store user account information: LDAP WebSphere Portal database Custom user registry If you use LDAP, do you plan to move to a different LDAP server?	Perform maintenance cleanup on users and groups as needed before migrating. For example, clean up deleted users and their personalized pages before starting migration. If the new version of WebSphere Portal does not support the LDAP that you used with the earlier portal server, upgrade the LDAP to a supported version. If the earlier portal and the new portal are configured to use a standalone LDAP user registry the users and groups in the new portal installation must be the same as the directory users and groups in the earlier portal installation.
Database	Does the new portal installation support the database that the earlier portal installation uses? Can the database be upgraded if needed?	You can migrate from an older version of a database server to a newer version of that database server. Migrating between different database servers is not supported. For example, you cannot migrate from a DB2 database server to an Oracle database server. When you migrate from v6.x, WebSphere Portal reuses the database tables from the earlier version in the new version. Keep these requirements in mind: If you used IBM Cloudscape as the default DBMS in the earlier version, transfer your data to a supported DBMS before migrating since the new version does not support Cloudscape. If the new portal installation uses the same DBMS as the earlier portal, use the same database driver when you connect to the earlier portal's JCR and Customization database domains. When migrating Microsoft SQL Server database tables to WebSphere Portal version 6.1, the minimum level that is supported is SQL Server 2005. If you used Microsoft SQL Server 2000 with WebSphere Portal version 6.0.1.x, install and configure SQL Server 2005 before you can migrate to WebSphere Portal version 6.1. For details, see technote 1295590 on configuring Microsoft SQL Server 2005. If you are migrating from WebSphere Portal configured to use DB2, ensure that your source environment is running DB2 Version 9.1 with Fix Pack 1 or later version.
Web server	What HTTP server does the existing installation use? Does the new installation support this HTTP server?
External security		Supported IBM and third-party security settings are migrated automatically.
Virtual portals	Have multiple portals been installed?	You must manually recreate each virtual portal in the new installation before you can migrate its contents. Use the task... ConfigEngine.sh create-virtual-portal ...to create an empty virtual portal with the corresponding name and URL context for each virtual portal that you want to migrate. Virtual portals are then migrated separately, one at a time, after you migrate the portal configuration. If a virtual portal's admin pages are located under the node... wps.administration ...WebSphere Portal migration automatically sets these pages to the V6.1 Portal theme. If the admin pages are located under a different page hierarchy, you will need to manually set them to the V6.1 Portal theme following migration. If you choose to update a custom virtual portal admin page hierarchy, ensure that the virtual portal's admin page has a unique name assigned to it prior to migration.
Backup	Do you have a backup plan and schedule in place for the new portal server?	Back up the existing portal database before starting migration.
Cleanup and maintenance	Have you deleted any users from the user registry who were registered portal users?	Perform the required maintenance before migrating.
	If you are migrating from V6.0, have you deleted portal pages? Does your portal site contain orphaned data?	Perform the required maintenance before migrating.
	Have you installed all required fixes that apply to the earlier WebSphere Portal installation?	Install all required fixes before migrating.
	Have you changed the default settings of the scheduled cleanup service?	Changes to the scheduled cleanup service settings are not migrated. If you modified these settings in the earlier portal and want to continue using the same settings in the new portal, update the settings on the new portal.
Custom themes and administration	Does the earlier portal installation use custom themes?
	Does the earlier portal use custom administration themes?	Custom administration themes cannot be migrated from V5.
	Does the earlier portal use customized administration portlets or pages?
	Does the earlier portal use customized global settings?
	Have any portal service configurations been customized?
Custom portlets	Does the earlier portal have any portlets that were developed by using Struts Framework?	Custom portlets must be manually copied to the new portal installation.
	Does the earlier portal have any portlets that were developed by using IBM Portlet API?	The IBM Portlet API is deprecated in WebSphere Portal V6.0 and later. The recommended approach is to migrate existing custom portlets as is and then refactor them using JSR 168 Portlet API.
	Does the earlier portal have custom portlets that use Click-To-Action?	The pbportlet.jar file must be updated.
	Are any portlets deployed as part of an Enterprise Application by using an EAR file?
	Do any custom applications in the earlier portal use private IBM APIs?
	Have you installed and deployed third-party portlets?	Third-party portlets must be certified for use with the latest version of WebSphere Portal.
Remote portlets		To migrate remote portlets (portlets that are provided as WSRP services), ensure that the WSRP Producer is available before you run the portal-post-upgrade task to import content to the new portal installation.
Private wires	Do you have portlets that use private wires?	Private wires cannot be migrated from V6.0.1.x because of a limitation in the earlier version. Private wires may not migrate successfully from V5.0.1.x if the portlet, portlet instance, or page that the wire references is removed. In such cases, a warning trace message is logged and the migration process continues.
Search	Do you want to migrate custom search collections?	Search Web collections that were created in an earlier version of WebSphere Portal can be exported and imported into V6.1. The pre-defined categorizer option in WebSphere Portal V5.1.x and 6.0.x is no longer available starting in V6.1. If you used this option to create search collections, you can import the search collections into the current version after enabling the required parameter. For details, see technote 1306912.
Personalization	What is your migration scenario for personalized portal content?	To determine which migration procedure to use, refer to Migrating personalized portal content. If you are migrating from V6.0.1.1 or V6.0.1.3, connect to a copy of the earlier portal's JCR database domain before running the migration tasks. See Sharing JCR domain data. Then refer to Migrating V6.0.x personalization data. If you are migrating from V5.1.0, 5.1.0.1, 5.1.0.2, 5.1.0.3, 5.1.0.4, 5.1.0.5, you can migrate the personalization data after you migrate the core portal. Follow the procedure: Migrating V5.1.x personalization data stored in the JCR Migrating V5.1.x exported personalization data from the file system
Composite applications	Do you have composite applications to migrate?
Business process applications
Document Manager	Do you have content stored in document libraries?	Document Manager is not available in WebSphere Portal V6.1 and is effectively replaced with a stand-alone IBM Lotus Quickr server that is integrated with your WebSphere Portal environment. For general guidance, refer to Migrating documents from Portal Document Manager to Quickr Document Libraries.
IBM Lotus WCM		WCM requires a JCR repository of the same version. Even though you might have different version repositories stored in the same database, WCM V6.1 only works with the V6.1 repository. If you have any WCM data that references a Portal Document Manager library, replace the Web content that was stored as a document in the document library before you begin the migration process. See Document migration. For additional information, see Migrating Web content.
Business portlets		See Deprecated business portlets.
Collaborative portlets		Domino Web Access, Lotus Notes View, and Lotus Document Viewer are migrated with other portlet applications. For information on deprecated portlets including My Lotus QuickPlaces, Inline QuickPlaces, Domino Document Manager, and Lotus Web Conferencing, see Deprecated collaborative portlets.