WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Personalization: migrate from 5.0 to 6.0

This task provides detailed information used to migrate the 5.0 Personalization database to Version 6.0.

Use the following steps to migrate the 5.0 Personalization database to Version 6.0:

  1. Ensure that you completed the steps in Preparing to run the migration tasks and Migrating WebSphere Portal Configurations.

  2. Ensure that JDBC can access your 5.0 Personalization database.

  3. Update 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:

    • Init parameters:

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

      • TargetRepositoryUserId: The user id used to connect to the Version 6.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 Version 6.0 Personalization has been customized to use a different workspace, this 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 defaults to the name of the project being imported.

      • ProjectList: The comma separated list of projects to be imported. If not set, all projects will be imported.

      • DBUserId: The user ID used to connect to the 5.0 database.

      • DBPassword: The password used to connect to the 5.0 database.

      • DBName: The name of the 5.0 database.

      • DBDriver: The JDBC driver used to connect to the 5.0 database.

      • DBHost: The host name of the machine containing the 5.0 database (not used # by all drivers).

      • DBPort: The port used to connect to the 5.0 database server (not used by all # driver).

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

  4. Set the jdbcClasspath parameter in the file portal_server_root/migration/components/jcr/jcrmig.properties to the classpath needed to load the DBDriver specified in the previous step.

  5. Start the 5.0.x and 6.0 WebSphere Portal Express servers.

    • Enter the following command:

      • Linux:

        ./startServer.sh WebSphere_Portal

      • Windows:

        startServer.bat WebSphere_Portal

      • i5/OS:

        startServer.sh WebSphere_Portal -profileName profile_root

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

    • For i5/OS on 5.0.x 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

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

    Rules from previous versions that made use of the site area property will need to be manually updated. See The Web Content resource collection for more information.

 

Parent topic:

Migrating additional components