Performing multitask migration

Performing multitask migration

This section details the tasks that are needed to perform migration. Before you begin running the migration tasks, carefully review the information in this bulleted list.

Make sure that all parameters have the correct values in the mig_core.properties file. The optional parameters that are described in this section can be filled in in the properties file and can be specified on the command line. Any parameters you enter on the command line will overwrite the entries in the mig_core.properties file. If you have already specified parameters listed after the tasks in mig_core.properties, you need only enter the task itself without parameters. Refer to Migration properties for a detailed description of the properties file parameters, and to Migration tasks for more information about the migration tasks and their parameters.
Optional migration steps are provided for use during the development phase, when you might want to migrate individual artifacts and verify that they work as desired on WebSphere Portal V5.1. When migrating your production environments, it is recommended that you use one of the suitable scenarios described in the Run 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 themes, skins, portlet applications, and pages along with places, you can do so in the following step 8. If you want to migrate themes, skins, portlet applications, and pages individually, you can use the tasks in the Optional migration steps section.
Before you begin running the migration tasks, read through all the steps and develop a plan for running them.
After any migration task is completed, you can view the <wp5_root>/migration/log/MigrationReport.xml file for a report. This includes timestamp, names of individual tasks that were attempted, and if they were successfully completed.

The following steps describe how to run the migration tasks:

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

Make sure that any previously installed versions of WebSphere Portal and WebSphere Portal V5.1 are running and operational to your satisfaction.
Make sure that the mig_core.properties and mig_wmm.properties files are updated with all required parameters as indicated in the files.
Migrate users, groups, and extended user attributes from from any previously installed versions of WebSphere Portal (WebSphere Member Services) to WebSphere Portal V5.1 (Member Manager).
Skip step 4 if you did not use a Lookaside database to store additional attributes in the previous version of WebSphere Portal. If you did not use a Lookaside database, you do not need to migrate Member Manager. For more information refer to Preparing to run the migration tasks, step 6.1.

Migrate users, groups, and extended user attributes by entering the following command on one line:

Windows: WPmigrate.bat migrate-wmm
UNIX: ./WPmigrate.sh migrate-wmm

Note the following information:

Ensure that the Member Manager and WebSphere Member Services databases have the same database user ID before proceeding. If the database user IDs do not match, the migrate-wmm command will fail.

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

Windows: WPmigrate.bat migrate-wmm -DWmmDbName=<service_name>
UNIX: ./WPmigrate.sh migrate-wmm -DWmmDbName=<service_name>
where: <service_name> is the service name for the remote Oracle database.

Refer to the Verifying the migration tasks section to verify that extended user attributes were successfully migrated.

Migrate permissions that users of previously installed versions of WebSphere Portal have on user groups.

If you use an external security manager with a previous version of WebSphere Portal or WebSphere Portal V5.1, verify it is running.
On the WebSphere Portal V5.1 system, enter one of the following commands:

Windows: WPmigrate.bat migrate-user-groups-ac
UNIX: ./WPmigrate.sh migrate-user-groups-ac

Refer to the Verifying the migration tasks section to verify that access control on user groups was successfully migrated.

Permissions on All Authenticated Users and All Anonymous Users are not migrated with this step. Permissions on All Anonymous and All Authenticated Users must be migrated using the procedure described in the Migrating the remaining access control configuration section.

If you had modified default portal clients supplied with a previous version of WebSphere Portal or added custom clients, migrate them to WebSphere Portal V5.1.

Enter one of the following commands to migrate portal clients to WebSphere Portal V5.1:

Windows: WPmigrate.bat migrate-clients
UNIX: ./WPmigrate.sh migrate-clients

Optional Parameters Description
-DincludeClients=<include_names> <include_names> is a comma-separated list of case-sensitive portal client names to be included in migration. If you do not specify a value for the includeClients parameter, by default all the clients will be migrated.
-DexcludeClients=<exclude_names> <exclude_names> is a comma-separated list of case-sensitive portal client names to be excluded from migration. If you specify a value for excludeClients parameter, the clients that are specified will not be migrated.

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

Deploy Notes and iNotes portlets that are shipped with WebSphere Portal V5.1 and migrate settings from multiple Notes and iNotes Portlets from any previously installed version to WebSphere Portal V5.1. The user customization data that is associated with Notes and iNotes portlets will be migrated separately in step 10.

Enter one of the following commands to migrate Notes and iNotes portlets:

Windows: WPmigrate.bat migrate-notes-portlets
UNIX: ./WPmigrate.sh migrate-notes-portlets

Refer to the Verifying the migration tasks section to verify that Notes and iNotes portlets were successfully migrated.

Migrate places defined in any previous versions of WebSphere Portal to WebSphere Portal V5.1. Use one of the following commands to migrate places:

Windows: WPmigrate.bat migrate-places
UNIX: ./WPmigrate.sh migrate-places

Optional Parameters Description
-DincludePlaces=<include_names> <include_names> is a comma-separated list of places to be included in migration. If you do not specify a value for the includePlaces parameter, by default all the places will be migrated.
-DexcludePlaces=<exclude_names> <exclude_names> is a comma-separated list of places to be excluded from migration. If you specify a value for excludePlaces parameter, the places that are specified will not be migrated.
-DdeployPages=<true_false> <true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DdeployApps=<true_false> <true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DconfigThemesSkins=<true_false> <true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DappsPath=<your_path> <your_path> points to a location where the XML configuration interface will look for WAR files during portlet deployment (for example: file:///usr/WebSphere/PortalServer/install). The default path is file://localhost/$server_root$/installableApps, which is equivalent to <wp5_root>/installableApps at run time.

Note the following information:

If you do not explicitly assign a theme to your places or pages, the previously installed version of WebSphere Portal automatically uses the system default theme you have selected in the Themes and Skins Administration. The configuration for the system default theme is not migrated by the migrate-places 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 migrate-themes-skins-configs task before running the migrate-places task. The migrate-themes-skins-configs task by default excludes themes that are supplied with WebSphere Portal V4.x, so if you are using a WebSphere Portal-supplied theme as the system default, 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 migrate the "WebSphere" theme configuration to WebSphere Portal V5.1:

Windows: WPmigrate.bat migrate-themes-skins-configs -DincludeThemes=WebSphere
UNIX: ./WPmigrate.sh migrate-themes-skins-configs -DincludeThemes=WebSphere

The migrate-places task does not deploy portlets and does not migrate portlet settings if the portlets are not included on pages that are being migrated using the migrate-places task. This includes clipping portlets that you have created but not included on pages. If you have such portlets, deploy them separately using the migrate-apps task, which also migrates portlet settings and any access control information that is associated with the portlet while deploying the portlets.
For example, to migrate all clipping portlets, use one of the following commands:

Windows: WPmigrate.bat migrate-apps -DincludeApps="com.ibm.wps.portlets.clipper"
UNIX: ./WPmigrate.sh migrate-apps -DincludeApps="com.ibm.wps.portlets.clipper"

The configThemesSkins, deployApps, and deployPages parameters are set to true by default. This allows the migrate-places task to also migrate the corresponding pages that are used by the places, migrate the configuration of themes and skins that are used by the pages, and deploy portlet applications that are used on the pages. If you want to migrate these elements individually, verify the parameters are set to false and use the steps in the Optional migration steps section. Note that the optional tasks are provided for your use during the development phase, when you want to migrate individual artifacts and verify that they work as desired on WebSphere Portal V5.1. When migrating your production environments, it is recommended that you use the migrate-places task and use the default value of true for the parameters configThemesSkins, deployApps, and deployPages.

Refer to the Verifying the migration tasks section to verify that places were successfully migrated.
Migrate all user customizations to WebSphere Portal V5.1. User customizations are artifacts that are attributed to a user that has EDIT but not MANAGE permissions on a page. They are created when such a user changes the layout of a page or edits portlet settings. The following command also exports user customizations for all Notes and iNotes portlets.
Use one of the following commands to migrate user customizations:

Windows: WPmigrate.bat migrate-user-customizations
UNIX: ./WPmigrate.sh migrate-user-customizations

Optional Parameters Description
-DincludePages=<include_page_names> <include_page_names> is a comma-separated list of page names to be included in migration. If you do not specify a value for the includePages parameter, by default all the pages will be migrated.
-DexcludePages=<exclude_page_names> <exclude_page_names> is a comma-separated list of page names to be excluded from migration.

Refer to the Verifying the migration tasks section to verify that user customizations were successfully migrated.
Migrate Credential Vault slots and segments. Existing credential vault data must be migrated with a separate manual procedure that is described in the Migrating the remaining access control configuration section.

Use one of the following commands:

Windows: WPmigrate.bat migrate-credential-slots-segments
UNIX: ./WPmigrate.sh migrate-credential-slots-segments

Refer to the Verifying the migration tasks section to verify that Credential Vault slots were successfully migrated.

Optimize roles on the WebSphere Portal V5.1 system. This step cleans up obsolete roles and role blocks that are created on WebSphere Portal V5.1 resources during the migration process. If you use an external security manager, verify it is running before entering this command:

Enter the following command on one line to optimize roles:

Windows: WPmigrate.bat optimize-roles
UNIX: ./WPmigrate.sh optimize-roles

Refer to the Verifying the migration tasks section to verify that roles were successfully optimized.

Proceed to Migrating the remaining access control configuration.

Next steps

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

Migrating the remaining access control configuration

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.

Optional Parameters	Description
-DincludeClients=<include_names>	<include_names> is a comma-separated list of case-sensitive portal client names to be included in migration. If you do not specify a value for the includeClients parameter, by default all the clients will be migrated.
-DexcludeClients=<exclude_names>	<exclude_names> is a comma-separated list of case-sensitive portal client names to be excluded from migration. If you specify a value for excludeClients parameter, the clients that are specified will not be migrated.

Optional Parameters	Description
-DincludePlaces=<include_names>	<include_names> is a comma-separated list of places to be included in migration. If you do not specify a value for the includePlaces parameter, by default all the places will be migrated.
-DexcludePlaces=<exclude_names>	<exclude_names> is a comma-separated list of places to be excluded from migration. If you specify a value for excludePlaces parameter, the places that are specified will not be migrated.
-DdeployPages=<true_false>	<true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DdeployApps=<true_false>	<true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DconfigThemesSkins=<true_false>	<true_false> allows you the option of migrating the pages, portlet applications, themes, and skins that are associated with the places.
-DappsPath=<your_path>	<your_path> points to a location where the XML configuration interface will look for WAR files during portlet deployment (for example: file:///usr/WebSphere/PortalServer/install). The default path is file://localhost/$server_root$/installableApps, which is equivalent to <wp5_root>/installableApps at run time.

Optional Parameters	Description
-DincludePages=<include_page_names>	<include_page_names> is a comma-separated list of page names to be included in migration. If you do not specify a value for the includePages parameter, by default all the pages will be migrated.
-DexcludePages=<exclude_page_names>	<exclude_page_names> is a comma-separated list of page names to be excluded from migration.