Migrate V5.1.x personalization data stored in the JCR
When you migrate personalization data that is stored in the V5.1.x Java Content Repository (JCR) database, the migration task copies the data to the current version's JCR. After completing this procedure, manually update rules from earlier versions that use the site area property.
The steps below assume that you have completed the required tasks to prepare for migration and that you have migrated the WebSphere Portal configuration.
Use the following steps to migrate V5.1.x personalization data to the current version:
- Configure the Document Transfer Tool on the V5.1.x system:
- Shut down WebSphere Portal or the WebSphere Portal cluster.
- Install PK18903 from the WebSphere Portal Product Support Web site.
- If in standalone environment, start server1.
- Install portal_server_root/jcr/installableApps/icmjcr.ear to WebSphere Portal, or to the WebSphere Portal cluster if in clustered environment, using the administrative console.
- If in clustered environment, regenerate the Web server plug-in using the deployment manager administrative console. If you are using a remote Web server, copy the updated plug-in configuration file (plugin-cfg.xml) to the Web server's plug-in configuration directory. Stop and start the Web server.
- Restart WebSphere Portal or the WebSphere Portal cluster.
- On the V6.1 system, review the portal_server_root/jcr/prereq.jcr/migration/conf/pzn_conf.xml file, confirm that the following parameters are set as specified, and modify them if necessary:
- SourceServerPort
- The host name and port where WebSphere Portal is running on the V5.1.x system.
- TargetServerPort
- The host name and port where WebSphere Portal is running on the V6.1 system.
- ExportNode
- Path of the node that will be exported.
- SourceExportData
- Directory on the V5.1.x system where exported data will be saved. This path must be an existing, empty directory that is shared with the V6.1 system.
- TargetExportData
- Path on the V6.1 system that is used to access the SourceExportData directory.
- TempData
- An existing, empty directory on the V6.1 system. This directory will be used to store temporary data.
- SourceRepositoryUserId
- The user ID that is needed to connect to the V5.1.x Java Content Repository (JCR). If Light Directory Access Protocol (LDAP) security is enabled, this ID must be a fully qualified distinguished name (DN).
- SourceRepositoryPassword
- Password used to connect to the V5.1.x JCR.
- SourceWorkspace
- Name of the workspace that holds the V5.1.x data. Unless V5.1.x personalization has been customized to use a different workspace, this name should always be ROOTWORKSPACE.
- TargetRepositoryUserId
- The user ID that is needed to connect to the V6.1 JCR. If LDAP security is enabled, this ID must be a fully qualified DN.
- TargetRepositoryPassword
- Password used to connect to the V6.1 JCR.
- TargetWorkspace
- 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.
- IncludeVersion
- Specifies whether to migrate versions, if any, of personalization.
- Start the V5.1.x and V6.1 WebSphere Portal servers.
- Windows: startServer.bat WebSphere_Portal
- UNIX: ./startServer.sh WebSphere_Portal
- i5/OS: startServer WebSphere_Portal
- startServer WebSphere_Portal -instance instance_name where instance_name is the name of the WebSphere Application Server instance where WebSphere Portal is installed
- Make sure you are in the portal_server_root/migration directory, then run the WPmigrate.bat/sh migrate-pzn-51x task.
- Rules from previous versions that used the site area property must be manually updated. For more information, see the topic on the Web Content resource collection.
