WebSphere

 

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

 

Prepare your previous environment for migration

 

+

Search Tips   |   Advanced Search

 

  1. Clean up your previous environment...

    • Clean up deleted portal pages

    • Clean up deleted users or groups

      If portal users or groups have been removed from the user registry, but not from the portal database, or if users have been muted, for example after too many wrong password attempts, you can identify and list these users and groups by using the cleanup-users attribute. Specify the cleanup-users attribute with the request tag of type export, and set its value to true .

      You also need to set the export-users attribute to true.

      The CleanupUsers.xml sample file shows an example of how you can export such users and groups. The resulting output file lists the affected users and groups with their action set to delete. You need to check the list and remove all users and groups that you want to keep in the portal database. For example, you might want to keep the muted users and re-enable their passwords. After you have done this, import the file into the portal. All users and groups that remain in the list are removed from the portal database.

      After deleting these entries via the modified XML script, all customization is lost for the deleted users and groups.

    • Export or remove orphaned data.

      To prepare for deleting orphaned data, use the ExportIncludingOrphanedData.xml example to perform an export that includes all orphaned data. For details about orphaned data and how to delete them refer to Deleting orphaned data.

  2. To verify that the required values are specified in the wpconfig.properties file, run the validate-database-connection-wps task on your previous environment.

  3. Do the following:

    1. Create an update directory in your previous WebSphere Portal Express directory; for example...

      C:\Program Files\WebSphere\PortalServer\update

    2. Download the WebSphere Portal Update Installer

    3. Unpack the Installer to the update directory.

  4. Set the WAS_HOME environment variable for the previous version directory where you will run the WebSphere Portal Express Update Installer:

    • Windows:

      set WAS_HOME=was_old_root

      For example:

      set WAS_HOME=C:\Program Files\WebSphere\AppServer

    • Linux:

      export WAS_HOME=was_old_root

      For example:

      export WAS_HOME=/opt/Websphere/AppServer

    • i5/OS:

      export WAS_PROD_HOME=was_old_prod_root

      For example:

      export WAS_PROD_HOME=/QIBM/ProdData/WebAS5/Base

  5. (All platforms) Apply the interim fixes, which can be found in directory...

    portal_server_root/migration/fixes

    ...of the current version.

    See Files for 'Best Practices for Migrating to IBM WebSphere Portal 6' (REDP-4227) for a list of all available migration fixes.

    For version 6.0.0.0 only, PK32308 is required before applying PK44603.

    1. For version 5.0.2.2 and 5.0.2.3:

      Enter the following command on the command line to install one or more interim fixes:

      • Windows:

        .\updatePortal.bat -install -installDir wp_old_root -fix -fixDir wp_old_root/update -fixes list of fixes

        For example:

        updatePortal.bat -install -installDir "C:\Program Files\WebSphere\PortalServer" -fix -fixDir "C:\Program Files\WebSphere\PortalServer\update" -fixes PK28269

      • Linux:

        ./updatePortal.sh -install -installDir wp_old_root -fix -fixDir wp_old_root/update -fixes list of fixes

        For example:

        ./updatePortal.sh -install -installDir /opt/WebSphere/PortalServer -fix -fixDir /opt/WebSphere/PortalServer/update -fixes PK28269

      • i5/OS:

        ./updatePortal.sh -install -installDir wp_old_user_root -fix -fixDir wp_old_prod_root/update -fixes list of fixes

        For example:

        updatePortal.sh -install -installDir "/QIBM/UserData/WebAS5/Base/instance/PortalServer5"
        -fixpackDir "/QIBM/ProdData/PortalServer5/update" -install -fixes PK28269 where instance is the name of the WebSphere Application Server instance.

  6. Apply fixes that contain database updates (technote 1200168)

 

Parent topic:

Migrating

 

Previous topic

Planning migration

 

Next topic

Migrating your customized resources