Prepare the previous environment for migration

 

+

Search Tips   |   Advanced Search

 

To ensure a proper migration, clean up the old environment and apply the appropriate interim fixes to the previous WebSphere Portal environment.

You must apply the fixes in the order provided below to ensure a proper migration process.

1. Clean up the old environment as follows:
   • If you deleted portal pages
   • If you deleted resources, you may have orphaned data
   • If you deleted users or groups using the configured user registry

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

3. Create an update directory in the old WebSphere Portal directory. For example,...

   C:\Program Files\WebSphere\PortalServer\update

4. Download the WebSphere Portal Update Installer

5. Unpack the Installer to the update directory.

6. Unzip the interim fixes from the appropriate directory of the current WebSphere Portal directory to the update directory created in the previous step:
   • portal_server_root/migration/fixes/5022
   • portal_server_root/migration/fixes/5023
   • portal_server_root/migration/fixes/510
   • portal_server_root/migration/fixes/5101
   • portal_server_root/migration/fixes/5102
   • portal_server_root/migration/fixes/5103

7. Set WAS_HOME to previous version directory where you will run the WebSphere Portal Update Installer:

   export WAS_HOME=was_old_root

   For example:

   export WAS_HOME=/opt/Websphere/AppServer

8. Install one or more interim fixes:

   ./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 PK07258 PK07872

9. (All platforms) Apply the following interim fixes:

   1. For version 5.0.2.2 and 5.0.2.3:
      • PK28269 - XMLAccess export should filter invalid pages

   2. For version 5.1.0:
      • PQ96317
      • PQ98046
      • PQ97287
      • PQ95975
      • PQ97656
      • PQ99439
      • PQ99519
      • PK01286
      • PK00826
      • PK03737
      • PK01695
      • PK07872
      • PK14100
      • PK15013
      • PK19790
      • PK23171
      • PK20467

   3. For version 5.1.0.1:
      • PK07872
      • PK14100
      • PK14103
      • PK15013
      • PK19790
      • PK23171
      • PK20467
      • PK16371
      • PK16597
      • PK18538
      • PK21688
      • PK07258
      • PK17690
      • PK21136
      • PK23901

   4. For version 5.1.0.2:
      • PK14100
      • PK14103
      • PK15013
      • PK19790
      • PK23171
      • PK20467
      • PK16371
      • PK16597
      • PK18538
      • PK21688
      • PK17690
      • PK21136
      • PK22244
      • PK23901

   5. For version 5.1.0.3:
      • PK23171
      • PK20467
      • PK18538
      • PK21688
      • PK21136
      • PK22244
      • PK23901

10. (System i5 only) Apply the following interim fixes:
    1. For 510:
       • PK01639
       • PK08409
       • PK11536

    2. For 5101:
       • PK08409
       • PK11536

    3. For 5102:
       • PK11536

11. For instructions on applying fixes that contain database updates, see technote 1200168: WebSphere Portal database check and update tool wpdbupdate.

 

Parent Topic

Migrating

 

Previous topic

Planning migration

 

Next topic

Migrating the customized resources

 

---