Optional migration steps

The following optional steps allow you to migrate themes, skins, portlet applications, pages, and portlet configuration data individually during the development phase. When migrating your production environments, it is recommended that you use one of the suitable scenarios described in the Running the migration tasks section. Do not use the optional tasks to migrate your production environments unless it is absolutely necessary.

If you want to migrate artifacts individually in a development environment, choose one of the following sets of steps, depending on your migration scenario:

With both WebSphere Portal versions running at the same time

With only one WebSphere Portal version running at a time

Migrating PDM

 

With both WebSphere Portal Versions running at the same time

  1. You can migrate themes and skins individually if you did not migrate them along with places. Use one of the following commands to migrate themes and skins:

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

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

    Notes:

    • In V4.x, the name of the resource must be specified in includeThemes or excludeThemes.

    • In V5.x, the objectid of the resource in the source server must be specified in includeThemes or excludeThemes. For a sample file you can use to export themes in the source server, see the migrate-themes-skins-configs section in the Migration Tasks topic.

    Optional Parameters Description
    -DincludeThemes=<include_names> <include_names> is a comma-separated list of the names of the themes and skins to be included in migration. If you do not specify a value for the includeThemes parameter, by default all the themes and skins will be migrated.
    -DexcludeThemes=<exclude_names> <exclude_names> is a comma-separated list of the names of the themes and skins to be excluded from migration. If you specify a value for excludeThemes parameter, the themes and skins that are specified will not be migrated.

    Refer to the Verifying the migration tasks section to verify that themes and skins were successfully migrated.

  2. You can deploy portlet applications individually if you did not migrate them along with places. Use one of the following commands to migrate portlet applications:

    • Windows: WPmigrate.bat migrate-apps

    • UNIX: ./WPmigrate.sh migrate-apps

    Notes:

    • In V4.x, specify the the globalid of the application in includeApps or excludeApps.

    • In V5.x, specify the Portlet Application in includeApps or excludeApps.

    For more information, see the migrate-apps section in the Migration Tasks topic.

    Optional Parameters Description
    -DincludeApps=<include_names> <include_names> is a comma-separated list of global-IDs for portlet applications to be included in migration. If you do not specify a value for the includeApps parameter, by default all the portlet applications will be migrated.
    -DexcludeApps=<exclude_names> <exclude_names> is a comma-separated list of global IDs for portlet applications to be excluded from migration. If you specify a value for excludeApps parameter, the portlet applications that are specified will not be migrated.
    -DappsPath=<your_path> <your_path> points to a URL where the WAR files could be found for custom portlet applications (for example: file:///usr/WebSphere/PortalServer/install).

    Refer to the Verifying the migration tasks section to verify that portlet applications were successfully migrated.

  3. If you did not migrate pages along with places, you can migrate pages individually. Use one of the following commands to migrate pages that are defined in previously installed versions of WebSphere Portal to WebSphere Portal V5.1:

    • Windows: WPmigrate.bat migrate-pages

    • UNIX: ./WPmigrate.sh migrate-pages

    Notes:

    • In V4.x, the name of the resource must be specified in includePages or excludePages.

    • In V5.x, a unique name must be assigned to the object in the source server and then specified in includePages or excludePages.

    For more information, see the migrate-pages section in the Migration Tasks topic.

    Optional Parameters Description
    -DincludePages=<include_names> <include_names> is a comma-separated list of case-sensitive page names to be included in migration. If you do not specify a value for the includePages parameter, by default all of the pages will be migrated.
    -DexcludePages=<exclude_names> <exclude_names> is a comma-separated list of page names to be excluded from migration. If you specify a value for excludePages parameter, the pages that are specified will not be migrated.
    -DappsPath=<your_path> <your_path> points to a URL where the WAR files could be found for custom portlet applications if -DdeployApps is set to true.
    -DconfigThemesSkins=<true_false> <true_false> allows you to specify whether to migrate themes and skins that are associated with the pages.

    Refer to the Verifying the migration tasks section to verify that pages were successfully migrated.

  4. If portlets were deployed using custom deployment scripts, you can still migrate all portlet configuration data, such as portlet titles, from previously installed versions of WebSphere Portal to WebSphere Portal V5.1. Use one of the following commands to migrate portlet configuration data if you have not already done so manually.

    • Windows: WPmigrate.bat migrate-portlets-configs

    • UNIX: ./WPmigrate.sh migrate-portlets-configs

    Optional Parameters Description
    -DincludeApps=<include_names> <include_names> is a comma-separated list of global IDs for portlet applications to be included in migration. If you do not specify a value for the includeApps parameter, by default all the portlet applications will be migrated.
    -DexcludeApps=<exclude_names> <exclude_names> is a comma-separated list of global IDs for portlet applications to be excluded from migration. If you specify a value for excludeApps parameter, the portlet applications that are specified will not be migrated.

    Refer to the Verifying the migration tasks section to verify that portlet configuration data was successfully migrated.

 

With only one WebSphere Portal version running at a time

  1. If you chose not to export and import themes and skins along with places, you can export and import them individually. Use one of the following commands to export themes and skins:

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

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

    Optional Parameters Description
    -DincludeThemes=<include_names> <include_names> is a comma-separated list of the names of themes and skins to be included in the export. If you do not specify a value for the includeThemes parameter, by default all of the themes and skins will be exported.
    -DexcludeThemes=<exclude_names> <exclude_names> is a comma-separated list of the names of themes and skins to be excluded from the export. If you specify a value for excludeThemes parameter, the themes and skins that are specified will not be exported.
    -DfilenameThemes=<filename> <filename> is the file to which themes and skins will be exported. Themes and skins are exported by default to themesout.xml.

    After you have completed all of your optional export tasks, you can import themes and skins by using one of the following commands:

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

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

    Optional Parameters Description
    -DfilenameThemesSkins=<filename> <filename> is the file from which themes and skins will be imported.

    Refer to the Verifying the migration tasks section to verify that your themes and skins were successfully migrated.

  2. If you chose not to export and import portlet applications along with places, you can export and import them individually. Use one of following commands to export portal applications:

    • Windows: WPmigrate.bat export-apps

    • UNIX: ./WPmigrate.sh export-apps

    Optional Parameters Description
    -DincludeApps=<include_names> <include_names> is a comma-separated list of global IDs for portlet applications to be included in the export. If you do not specify a value for the includeApps parameter, by default all the portlet applications will be migrated.
    -DexcludeApps=<exclude_names> <exclude_names> is a comma-separated list of global IDs for portlet applications to be excluded from the export. If you specify a value for excludeApps parameter, the portlet applications that are specified will not be exported.
    -DfilenameApps=<filename> <filename> is the file to which portlet applications will be exported. Portlet applications are by default exported to appsout.xml.
    -DpathApps=<your_path> <your_path> points to a URL where the WAR files could be found for the portlet applications.

    After you have completed all your optional export tasks, use one of the following commands to import portlet applications:

    • UNIX: ./WPmigrate.sh import-apps

    • Windows: WPmigrate.bat import-apps

    Optional Parameters Description
    -DfilenameApps=<filename> <filename> is the name of the file to which the settings will be exported.

    Refer to the Verifying the migration tasks section to verify that portlet applications were successfully migrated.

  3. If you did not export and import pages along with places, you can export and import pages individually. Use one of following commands to export pages:

    • Windows: WPmigrate.bat export-pages

    • UNIX: ./WPmigrate.sh export-pages

    Optional Parameters Description
    -DincludePages=<include_page_names> <include_page_names> is a comma-separated list of pages to be included in the export. If you do not specify a value for the includePages parameter, by default all the pages will be exported.
    -DexcludePages=<exclude_page_names> <exclude_page_names> is a comma-separated list of pages to be excluded from the export. If you specify a value for excludePages parameter, the pages that are specified will not be exported.
    -DfilenamePages=<filename> <filename> is the name of the file to which the pages will be exported. The default file name is pagesout.xml.
    -DdeployApps=<true_false> <true_false> allows you to specify whether you want to export portlet applications and themes and skins along with the pages.
    -DconfigThemesSkins=<true_false> <true_false> allows you to specify whether you want to export portlet applications and themes and skins along with the pages.
    -DpathApps=<your_path> <your_path> is a URL where the WAR files could be found for custom portlet applications.

    After you have completed all your optional export tasks, use one of the following commands to import pages:

    • Windows: WPmigrate.bat import-pages

    • UNIX: ./WPmigrate.sh import-pages

    Optional Parameters Description
    -DfilenamePages=<filename> <filename> is the name of the file to which the page data was exported.

    Refer to the Verifying the migration tasks section to verify that pages were successfully migrated.

  4. If portlets were deployed using custom deployment scripts, you can still export and import all portlet configuration data, such as the portlet title. Use one of following commands to export and import portlet configuration data.

    • UNIX: ./WPmigrate.sh export-portlets-configs

    • Windows: WPmigrate.bat export-portlets-configs

    Optional Parameters Description
    -DincludeApps=<include_names> <include_names> is a comma-separated list of global IDs for portlet applications to be included in the export. If you do not specify a value for the includeApps parameter, by default all the portlet applications will be exported.
    -DexcludeApps=<exclude_names> <exclude_names> is a comma-separated list of global IDs for portlet applications to be excluded from the export. If you specify a value for excludeApps parameter, the portlet applications that are specified will not be exported.
    -DfilenamePortletsConfig=<filename> <filename> is the file to which portlet configuration data will be exported. Portlet configuration data is exported by default to portletsconfigsout.xml.

    After you have completed all your optional export tasks, use one of the following commands to import portlet configuration data:

    • UNIX: ./WPmigrate.sh import-portlets-configs

    • Windows: WPmigrate.bat import-portlets-configs

    Optional Parameters Description
    -DfilenamePortletsConfig=<filename> <filename> is the name of the file to which the settings will be exported.

    Refer to the Verifying the migration tasks section to verify that portlet configuration data was successfully migrated.

 

Migrating PDM

Use the following procedure to migrate Document Manager from a previous 5.0x Portal Server to the 5.1 Portal Server. Make sure you migrate all users and groups before migrating PDM information. Before export, verify the admin user (default is wpsadmin) is added to the Content Contributor group on the 5.0x portal.

Before executing import-pdm, if WebSphere Portal is on UNIX, and the database is DB2, export the DB2 user profile (that you created when installing DB2) onto the administrative user. This gives that administrative user rights over DB2. It is important to complete this step before running database tasks. The profile is at this location: . /home/db2inst1/sqllib/db2profile where db2inst1 represents your database instance. The space between the . and the / is important for this to work.

  1. Add input parameters to export_pdm.properties and import_pdm.properties in the PortalServer/migration directory of the 5.1 Portal. Note that wps.rootDir points to the 5.0.x Portal location, which needs to be on a network drive if the 5.0.x Portal is on another machine.

  2. Stop the 5.0.x Portal.

  3. In the PortalServer/migration directory run WPmigrate.bat/sh export-pdm-update-server.

  4. Start the 5.0.x Portal.

  5. Run WPmigrate.bat/sh export-pdm.

  6. Stop the 5.0.x Portal.

  7. Run WPmigrate.bat/sh export-pdm-restore-server.

  8. Stop the 5.1 Portal.

  9. Run WPmigrate.bat/sh import-pdm.

See also

 

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.