Migrating personalization data

To migrate WebSphere Portal Express V5.0.2.2 or V5.0.2.3 personalization data, update the required parameters in the pzn_50_conf.xml file and then run the appropriate migration task. After completing this procedure, you need to manually update rules from earlier versions that use the site area property.

1. Ensure that JDBC can access the personalization database for the earlier version.
2. Review the portal_server_root/jcr/migration/conf/pzn_50_conf.xml file, confirm that the following parameters are set as specified, and modify them if necessary:

   TargetServerPort

   The host name and port where WebSphere Portal Express is running on the V6.1 system.

   TargetRepositoryUserId

   The user ID that is needed to connect to the V6.1 Java Content Repository (JCR). If Light Directory Access Protocol (LDAP) security is enabled, this ID must be a fully qualified distinguished name (DN).

   TargetRepositoryPassword

   The password used to connect to the V6.1 JCR.

   TargetWorkspace

   The name of the workspace that will hold the V6.1 data. Unless V6.1 personalization has been customized to use a different workspace, this name should always be RULESWORKSPACE.

   SourceData

   The path on the local file system where exported data will be saved. This path must be an existing, empty directory.

   ImportNode

   The name of the node where the contents of each project will be stored. If set, it must exist prior to execution. If not set, this value defaults to the name of the project being imported.

   ProjectList

   The comma-separated list of projects to be imported. If not set, all projects are imported.

   DBUserId

   The user ID used to connect to the V5.0.2.2 or V5.0.2.3 database.

   DBPassword

   The password used to connect to the V5.0.2.2 or V5.0.2.3 database.

   DBName

   The name of the V5.0.2.2 or V5.0.2.3 database.

   DBDriver

   The JDBC driver used to connect to the V5.0.2.2 or V5.0.2.3 database.

   DBHost

   The host name of the system that contains the V5.0.2.2 or V5.0.2.3 database (not used # by all drivers).

   DBPort

   The port used to connect to the V5.0.2.2 or V5.0.2.3 database server (not used by all # driver).

   IncludeVersion

   Specifies whether to migrate versions, if any, of personalization.

3. Update the portal_server_root/migration/components/jcr/jcrmig.properties file and set the jdbcClasspath parameter to the classpath needed to load the DBDriver parameter specified in the previous step.
4. Start the earlier version and current version WebSphere Portal Express servers.
   For i5/OS V5.0.2.2 and V5.0.2.3 only:

   • startServer WebSphere_Portal -instance instance_name where instance_name is the name of the WebSphere Application Server instance where WebSphere Portal Express is installed
5. Make sure that you are in the portal_server_root/migration directory, then run the WPmigrate.bat/sh migrate-pzn-50x task.
6. Rules from previous versions that used the site area property need to be manually updated. For more information, see the topic on the Web Content resource collection.