Performing two-task migration

This section details the tasks that are needed to perform two-task migration, using the export-all and import-all tasks. Refer to Migration tasks for more detailed information about the tasks.

After any migration task is completed, you can view the <wp51_root> migration/log/MigrationReportxml file for a report. This will include timestamp, names of individual tasks that were attempted, and if they were successfully completed.

Important note: The path to all export files that are created with any of the export commands is <wp_root>/migration/work.

  1. Change your working directory to the migration directory that was created when you installed WebSphere Portal V5.1. The path to this directory is dependent on your operating system. For example:

    • Windows: c:\WebSphere\PortalServer\migration

    • AIX: /usr/WebSphere/PortalServer/migration

    • Solaris: /opt/WebSphere/PortalServer/migration

  2. Make sure that any previous version of WebSphere Portal is running and operational.

  3. Make sure that the mig_core.properties and mig_wmm.properties files are updated with all required parameters as indicated in these files. You may also supply optional parameters.

  4. Note the following information before running the export task:

    • If you use an external security manager with the previously installed version and V5.1, verify it is running.
    • If you do not explicitly assign a theme to your places or pages, the previously installed version automatically uses the system default theme that you have selected in the Themes and Skins Administration. The configuration for the system default theme will not be exported by the export-all task unless a place or a page has been defined to explicitly use that theme. In this case, the configuration for the system default theme must be migrated using the export-themes-skins-configs task before running the export-all task. The export-themes-skins-configs task by default excludes themes that are supplied with previously installed version, so if you are using a WebSphere Portal supplied theme as the system default theme, specifically use the -DincludeThemes parameter when running this task. For example, if you are using the theme "WebSphere" as the system default theme, you would run the following command to export the "WebSphere" theme configuration:

      • Windows: WPmigrate.bat export-themes-skins-configs -DincludeThemes=WebSphere

      • UNIX: ./WPmigrate.sh export-themes-skins-configs -DincludeThemes=WebSphere

      The export-all task will not export portlets if they are not included on pages being exported by the export-places task. This includes clipping portlets that you have created but not included on pages. If you have such portlets, export them separately using the export-apps task, which also exports portlet settings and any access control information that is associated with the portlet while deploying the portlets. For example, to export all clipping portlets, use the following command:

      • Windows: WPmigrate.bat export-apps -DincludeApps="com.ibm.wps.portlets.clipper"

      • UNIX: ./WPmigrate.sh export-apps -DincludeApps="com.ibm.wps.portlets.clipper"

  5. Export places, pages, portlet applications, configuration for themes and skins, user customizations, portlet configuration data, and Notes and iNotes portlet settings by entering the following command on one line:

    • Windows: WPmigrate.bat export-all

    • UNIX: ./WPmigrate.sh export-all

  6. Optional: If a previous version of WebSphere Portal and WebSphere Portal V5.1 are installed on the same machine, you can now stop the previous version to minimize use of system resources.

  7. Make sure that WebSphere Portal V5.1 is running and operational.

  8. Note the following information before running the import-all task:

    • If you exported themes in step 4, first import them using the following command:

      • Windows: WPmigrate.bat import-themes-skins-configs

      • UNIX: ./WPmigrate.sh import-themes-skins-configs

    • If you exported any portlets in step 4, first import them using the following command:

      • Windows: WPmigrate.bat import-apps

      • UNIX: ./WPmigrate.sh import-apps

    • If you are using a remote Oracle database and the service name needed to access the database is different from the value specified by the WmmDbName property in the wpconfig.properties file, then enter the correct database on the command line by adding the -DWmmDbName parameter to the import-all command:

      • Windows: WPmigrate.bat import-all -DWmmDbName=<service_name>

      • UNIX: ./WPmigrate.sh import-all -DWmmDbName=<service_name>

      where: <service_name> is the service name for the remote Oracle database.

    • If you use an external security manager with WebSphere Portal V5.1, verify it is running.

  9. Enter the following command on one line to migrate WebSphere Member Services data. This command will also import all data that is exported in step 4 (including places, pages, portlet applications, configuration for themes and skins, user customizations, portlet configuration data, and Notes and iNotes portlet settings).

    • Windows: WPmigrate.bat import-all

    • UNIX: ./WPmigrate.sh import-all

    Parameters:

    • -DskipWmmMigration=<true_false>

    where:

    • <true_false> specifies whether the corresponding task for WebSphere Portal migration will be skipped. If set to true, the migrate-wmm task will be skipped.
    skipWmmMigration: In WebSphere Portal V4.x, the WebSphere Member Service database always acted as a Lookaside database. If you did not store additional attributes in a Lookaside database, you can skip Member Manager migration. For more information refer to Preparing to run the migration tasks, step 6.1. To do this, set skipWmmMigration to true. For example:

    • Windows: WPmigrate.bat migrate-all -DskipWmmMigration=true

    • UNIX: ./WPmigrate.sh migrate-all -DskipWmmMigration=true

 

Next steps

You have completed this step. 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.