Personalization : migrate from 5.1 to 6.0

 

+

Search Tips   |   Advanced Search

 

This task provides detailed information used to migrate Portal Personalization to the current version of IBM WebSphere Portal. Use the following steps to migrate Personalization from a previous version of WebSphere Portal to the current version:

  1. Ensure that you completed the steps in Migrating WebSphere Portal Configurations.

  2. Configure the Document Transfer Tool on the 5.1.x WebSphere Portal :

    1. Install PK18903.

    2. Install portal_server_root/jcr/installableApps/icmjcr.ear to WebSphere Portal, or the WebSphere Portal cluster if in clustered environment, using the Administrative Console.

    3. If in clustered environment, update Web server plugin and then restart the Web server.

    4. Restart WebSphere Portal or the WebSphere Portal cluster.

  3. Update the portal_server_root/jcr/migration/conf/pzn_conf.xml file. Confirm that the following parameters are set as specified and modify them if necessary:

    • Init parameters:

      • SourceServerPort: The hostname and port where WebSphere Portal is running on the Version 5.1 machine.

      • TargetServerPort : The hostname and port where WebSphere Portal is running on the Version 6.0 machine.

      • ExportNode : The path of the node that will be exported.

      • SourceExportData : The directory on the V5.1 machine where exported data will be saved. This path must be an existing, empty directory and be shared with the V6.0 machine.

      • TargetExportData : The path on the V6.0 machine used to access the SourceExportData directory.

      • TempData : An existing, empty directory on the version 6.0 machine. This directory will be used to store temporary data.

      • SourceRepositoryUserId : The user id used to connect to the V5.1 JCR repository. If LDAP security is enabled, this needs to be fully qualified DN.

      • SourceRepositoryPassword : The password used to connect to the V5.1 JCR repository.

      • SourceWorkspace : The name of the workspace holding the V5.1 data. Unless V5.1 Personalization has been customized to use a different workspace, this should always be ROOTWORKSPACE.

      • TargetRepositoryUserId : The user id used to connect to the V6.0 JCR repository. If LDAP security is enabled, this needs to be fully qualified DN.

      • TargetRepositoryPassword : The password used to connect to the Version 6.0 JCR repository.

      • TargetWorkspace : The name of the workspace that will hold the Version 6.0 data. Unless Personalization Version 6.0 has been customized to use a different workspace, this should always be RULESWORKSPACE.

      • IncludeVersion: This specifies whether to migrate versions, if any, of Personalization.

  4. Start the 5.1.x and 6.0 WebSphere Portal servers.

    • Enter the following command:

      • UNIX:

        ./startServer.sh WebSphere_Portal

      • Windows:

        startServer.bat WebSphere_Portal

      • i5/OS:

        startServer WebSphere_Portal -profileName profile_root

        ...where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

    • For i5/OS on 5.1.x only:

      • startServer WebSphere_Portal -instance instance_name

        ...where instance_name is the name of the WebSphere Application Server instance where WebSphere Portal is installed

  5. Make sure you are in the portal_server_root/migration/ directory, then run the WPmigrate.bat/sh migrate-pzn-51x task.

 

Parent topic:

Migrating additional components