Migration prerequisites


Thoroughly review the following list of prerequisites for migration before starting the migration process.

  • install and configure all components of WebSphere Portal V5.1 before attempting migration. This includes setting up the database that you plan to use, LDAP, and so on. Verify that WebSphere Portal V5.1 is operational before you begin migration. See Install for instructions.

    Defer any major customizations to your WebSphere Portal V5.1 system until after completion of migration. It is also recommended that migration be performed on a relatively pristine WebSphere Portal V5.1 system to avoid potential conflicts.

  • configure the V5.1 LDAP suffix the same as the previously installed version of portal LDAP.

  • An operational previous version of WebSphere Portal is a prerequisite for a complete end-to-end migration. Installation of WebSphere Portal V5.1 keeps your previous version of WebSphere Portal intact. This means that if you install WebSphere Portal V5.1 on a machine that contains a previous version of WebSphere Portal, the previous version will remain unchanged. Migration tasks will simply extract data from the previous version and import it to the WebSphere Portal V5.1 system.

  • configure Lotus Collaborative Components before you begin migration. See the Enable Lotus Collaborative Components section for more information.

  • In order to run Member Manager migration, have one of the following elements installed:

  • It is strongly recommended that you apply the V5.0 migration interim fix or the V5.0.x fix pack before attempting migration to WebSphere Portal V5.1.

  • WebSphere Portal V5.1 does not support Portal Content Organizer portlets. The replacement for Portal Content Organizer portlets is the Document Manager portlet, and there is no migration path from the Portal Content Organizer portlet to the Document Manager portlet. If you have Portal Content Organizer portlets included on a page in a previous version of WebSphere Portal that you plan to migrate, remove them from the page before running migration tasks.

  • The migration of explicitly created page hierarchies from previous versions of WebSphere Portal to WebSphere Portal V5.1 does not migrate the administrative name assigned to the pages in the previous version. Therefore, all pages in the page hierarchy appear to have the same name in the Manage Pages portlet. In order to distinguish the pages, it is recommended that you access the Manage Pages portlet, open the page's properties, and select a speaking title for the pages.

  • manually migrate the LDAP database of any previous versions to the LDAP server of the WebSphere Portal V5.1 system if the two versions are not using the same LDAP server. Use the LDAP Ldif tool to export the LDAP database from the previous LDAP version and import the data using the V5.1 LDAP Ldif tool.

  • If you have WebSphere Portal V4.2.1 and are running Tivoli Access Manager, apply Tivoli Access Manager Fix Pack 2 or higher before migrating to WebSphere Portal V5.1. In order to apply the Tivoli Access Manager fix pack, also apply LDAP Fix Pack 2 to both the server and clients. After this is done, apply a patch (P411W-02D) to the LDAP server in order to start WebSphere Portal V4.2.1.

  • Java 2 security should not be enabled until you have completed all of the migration tasks.

 

Next steps

You have completed this procedure. Continue to the next step by choosing the following topic:

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

 

Tivoli is a trademark of the IBM Corporation in the United States, other countries, or both.