Preparing your previous environment for migration

To ensure a proper migration, you must clean up your previous environment and apply the appropriate interim fixes to the previous WebSphere Portal Express environment. Apply the fixes in the order listed to ensure a successful migration process.

1. Clean up your previous environment as follows:
   • If you deleted portal pages, use the deletion cleanup service.
   • If you deleted users or groups using your configured user registry, make sure to deregister those users and groups using either the XML configuration interface or the Manage Users and Groups portlet.
   • Export or remove orphaned data.
2. To verify that the required values are specified in the wpconfig.properties file, run the validate-database-connection-wps task on your previous environment.
3. Prepare for the update installer:
   1. Create an update directory in your previous WebSphere Portal Express directory. For example, C:\Program Files\WebSphere\PortalServer\update.
   2. Download the WebSphere Portal Update Installer from the product support site and then unpack the installer to the update directory that you created in the previous step.
   3. If you are migrating from version 5.0.2.2 or 5.0.2.3, unzip the interim fixes from the corresponding location in the current WebSphere Portal Express directory to the directory where you unpacked the Update Installer:
      • portal_server_root/migration/fixes/5022
      • portal_server_root/migration/fixes/5023

4. Enter the required command to set the WAS_HOME environment variable for the previous version directory where you will run the WebSphere Portal Express update installer:

   Operating System	Command
   Windows	set WAS_HOME=was_old_root For example: set WAS_HOME=C:\Program Files\WebSphere\AppServer
   Linux	export WAS_HOME=was_old_root For example: export WAS_HOME=/opt/Websphere/AppServer
   i5/OS	export WAS_PROD_HOME=was_old_prod_root For example: export WAS_PROD_HOME=/QIBM/ProdData/WebAS5/Base

5. Review the command that you need to enter on the command line to install one or more interim fixes:

   Operating System	Command
   Windows	.\updatePortal.bat -install -installDir wp_old_root -fix -fixDir wp_old_root/update -fixes list of fixes For example: updatePortal.bat -install -installDir "C:\Program Files\WebSphere\PortalServer" -fix -fixDir "C:\Program Files\WebSphere\PortalServer\update" -fixes PK28269
   Linux	./updatePortal.sh -install -installDir wp_old_root -fix -fixDir wp_old_root/update -fixes list of fixes For example: ./updatePortal.sh -install -installDir /opt/WebSphere/PortalServer -fix -fixDir /opt/WebSphere/PortalServer/update -fixes PK28269
   i5/OS	./updatePortal.sh -install -installDir wp_old_user_root -fix -fixDir wp_old_prod_root/update -fixes list of fixes For example: updatePortal.sh -install -installDir "/QIBM/UserData/WebAS5/Base/instance/PortalServer5" -fixpackDir "/QIBM/ProdData/PortalServer5/update" -install -fixes PK28269 where instance is the name of the WebSphere Application Server instance.

6. Use the appropriate command for your operating system to apply the appropriate interim fixes:
   • For version 5.0.2.2 and 5.0.2.3:
     • PK28269 is available from Document 4012994, PK28269 - XMLAccess export should filter invalid pages.
     • PK16482 is included in Collection of Fixes for WebSphere Portal version 5.0.2.2 and in Collection of Fixes for WebSphere Portal version 5.0.2.3, available from WebSphere Portal interim fixes.
   • For version 6.0.x: