This document will provide step-by-step instructions to migrate WebSphere Portal v6.1.x on WAS v6.1.x to WebSphere Portal v6.1.x on WAS v7.0.x.

Before You Begin

Before you begin this process, ensure you meet the following requirements.

WebSphere Application Server

The target WebSphere Application Server v7 environment must be installed on the same server as the Portal v6.1/WAS v6.1 installation, and it must be upgraded to v7.0.0.11 or higher.

WebSphere Portal Server

The WebSphere Portal Server must be upgraded to the following levels (on all nodes if in a cluster):

• Fixpack v6.1.0.4/6.1.5.1 or higher
• PM25140 applied to all nodes

Important: PM25140 is included in v6.1.0.6/6.1.5.3. However, a defect in the Portal Update Installer prevents the code for PM25140 from being installed correctly during the v6.1.0.6 fixpack installation. This has been fixed in the 01/16/2012 build of the Portal Update Installer. If you used an older Portal Update Installer to upgrade to v6.1.0.6/6.1.5.3, then you need to apply the 6.1.0.6 version of PM25140.

If you are not sure if you used the fixed Portal Update Installer or not when installing 6.1.0.6, then apply the 6.1.0.6 version of PM25140 anyway.

Standalone Instructions

For the purposes of these instructions, I will use the following terms:

v61_wp_profile == This refers to the original Portal profile on the WAS v6.1 installation.
v70_wp_profile == This refers to the new Portal profile on the WAS v7.0 installation.

1. On the WebSphere Application Server v7 installation, create a new base profile using either the Profile Management Tool (32-bit only) or the manageprofiles command line option.
   
   Important: Use the exact same cell name, node name, and hostname that you used for the Portal v6.1/WAS v6.1 installation.
   
   For example, you might run this manageprofiles command on a UNIX environment:
   
   ./manageprofiles.sh -create -defaultPorts -enableAdminSecurity false -profileName <wp_profile_name> -profilePath <profile_path> -templatePath AppServer_root/profileTemplates/default -nodeName <source_node_name> -cellName <source_cell_name> -hostName <host_name> -isDefault -omitAction samplesInstallAndConfig defaultAppDeployAndConfig
   
   where the following values are set:
   
   <wp_profile name> is the name of the new profile
   <profile_path> is the full path to the profile
   <source_node_name> is the node name on the source installation
   <source_cell_name> is the cell name on the source installation
   <host_name> is the host name of the environment.
   
   
2. Run the following ConfigEngine command from the <v61_wp_profile root>/ConfigEngine directory to install Portal-specific files into the WAS v7 installation:
   
   UNIX: ./ConfigEngine.sh install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password> Windows: ConfigEngine.bat install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password> IBM i: ConfigEngine.sh install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password>
3. Ensure OSGI cache has been cleared from the new WAS v7 installation by executing the following command from the <v70_wp_profile>/bin directory:
   
   UNIX: ./osgiCfgInit.sh -all Windows: osgiCfgInit.bat -all IBM i: osgiCfgInit.sh -all
4. If you added the property 'javax.xml.transform.TransformerFactory' the JVM properties for the WebSphere_Portal server, ensure you remove it before migrating the profile. Failure due to so could cause the WebSphere_Portal server to not start after the WAS migration completes. For details on how to remove the property, refer to this technote.
   
5. From the <WAS v7 AppServer root>/bin directory, execute the WASPreUpgrade command to back up the source profile:
   
   UNIX: ./WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer directory> Windows: WASPreUpgrade.bat <temp directory to store backup> <WAS v6.1 AppServer directory> IBM i: WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer profile directory>
   Note: If running this on IBM i, the source profile directory is used instead of the AppServer directory.
   
   For example, your command on UNIX might look like:
   
   ./WASPreUpgrade.sh /opt/IBM/wasMigrateBackup /opt/IBM/WebSphere61/AppServer
   
   For more details on the WASPreUpgrade command, refer to this link
   
6. From the <WAS v7 AppServer root>/bin directory, execute the WASPostUpgrade command to migrate the backed up source profile into the new profile
   
   UNIX: ./WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_wp_profile> -oldProfileName <v61_wp_profile> Windows: WASPostUpgrade.bat <temp directory where backup was created> -profileName <v70_wp_profile> -oldProfileName <v61_wp_profile> IBM i: WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_wp_profile>
   Note: On IBM i, do not include the -oldProfileName flag.
   
   For example, your command on UNIX might look like:
   
   ./WASPostUpgrade.sh /opt/IBM/wasMigratedBackup -profileName wp_profile -oldProfileName wp_profile
   
   For more details on the WASPostUpgrade command, refer to this link
   
   
7. From the <v70_wp_profile>/ConfigEngine directory, execute the following ConfigEngine script:
   
   UNIX: ./ConfigEngine.sh post-was-migration-update -DWasPassword=<password> Windows: ConfigEngine.bat post-was-migration-update -DWasPassword=<password> IBM i: ConfigEngine.sh post-was-migration-update -DWasPassword=<password>
   
8. IBM i only. Copy these directories from the <v61_wp_profile>/PortalServer directory to the <v70_wp_profile>/PortalServer directory:
   
   PortalServer/ap
   PortalServer/base
   PortalServer/bp
   PortalServer/cmapi
   PortalServer/doc
   PortalServer/ext
   PortalServer/installableApps
   PortalServer/installer
   PortalServer/lwo
   PortalServer/lwp04.infra
   PortalServer/pcc.api
   PortalServer/pcc.impl
   PortalServer/prereq
   PortalServer/prereq.infra
   PortalServer/pzn.ext
   PortalServer/search
   PortalServer/shared
   PortalServer/theme
   PortalServer/ui
   PortalServer/wizard
   

Cluster Instructions

Deployment Manager

For the purposes of these instructions, I will use the following terms:

v61_dmgr_profile == This refers to the original DMGR profile on the WAS v6.1 installation.
v70_dmgr_profile == This refers to the new DMGR profile on the WAS v7.0 installation.
v61_wp_profile == This refers to the original Portal profile on the WAS v6.1 installation.

1. On the WebSphere Application Server v7 installation, create a new DMGR profile using either the Profile Management Tool (32-bit only) or the manageprofiles command line option.
   
   Important: Use the exact same cell name, node name, and hostname that you used for the WAS v6.1 DMGR installation.
   
   For example, you might run this manageprofiles command on a UNIX environment:
   
   ./manageprofiles.sh -create -profileName <dmgr_profile_name> -profilePath <profile_path> -templatePath AppServer_root/profileTemplates/management -nodeName <source_node_name> -cellName <source_cell_name> -hostName <host_name> -isDefault
   
   where the following values are set:
   
   <dmgr_profile name> is the name of the new profile
   <profile_path> is the full path to the profile
   <source_node_name> is the node name on the source installation
   <source_cell_name> is the cell name on the source installation
   <host_name> is the host name of the environment.
   
   
2. Run the following ConfigEngine command from the <v61_wp_profile root>/ConfigEngine directory to gather Portal-specific files for the WAS v7 DMGR installation:
   
   UNIX: ./ConfigEngine.sh create-files-for-dmgr -DWasPassword=<password> Windows: ConfigEngine.bat create-files-for-dmgr -DWasPassword=<password> IBM i: ConfigEngine.sh create-files-for-dmgr -DWasPassword=<password>
   Note: This creates a file called 'filesForDmgr.zip' in the <PortalServer root>/filesForDmgr directory.
   
3. Copy the <PortalServer root>/filesForDmgr/filesForDmgr.zip file over to the WAS v7 DMGR server and unzip it in the into the WAS v7 <AppServer root> directory.
   
4. Ensure OSGI cache has been cleared from the new WAS v7 installation by executing the following command from the <v70_dmgr_profile>/bin directory:
   
   UNIX: ./osgiCfgInit.sh -all Windows: osgiCfgInit.bat -all IBM i: osgiCfgInit.sh -all
5. From the <WAS v7 AppServer root>/bin directory, execute the WASPreUpgrade command to back up the source profile:
   
   UNIX: ./WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer directory> Windows: WASPreUpgrade.bat <temp directory to store backup> <WAS v6.1 AppServer directory> IBM i: WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer profile directory>
   Note: If running this on IBM i, the source profile directory is used instead of the AppServer directory.
   
   For example, your command on UNIX might look like:
   
   ./WASPreUpgrade.sh /opt/IBM/wasMigrateBackup /opt/IBM/WebSphere61/AppServer
   
   For more details on the WASPreUpgrade command, refer to this link
   
6. From the <WAS v7 AppServer root>/bin directory, execute the WASPostUpgrade command to migrate the backed up source profile into the new profile
   
   UNIX: ./WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_dmgr_profile> -oldProfileName <v61_dmgr_profile> Windows: WASPostUpgrade.bat <temp directory where backup was created> -profileName <v70_dmgr_profile> -oldProfileName <v61_dmgr_profile> IBM i: WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_dmgr_profile>
   Note: On IBM i, do not include the -oldProfileName flag.
   
   For example, your command on UNIX might look like:
   
   ./WASPostUpgrade.sh /opt/IBM/wasMigratedBackup -profileName Dmgr01 -oldProfileName Dmgr01
   
   For more details on the WASPostUpgrade command, refer to this link
   
   

Portal Nodes

Repeat these steps for each Portal node you have in your cluster.

For the purposes of these instructions, I will use the following terms:

v61_wp_profile == This refers to the original Portal profile on the WAS v6.1 installation.
v70_wp_profile == This refers to the new Portal profile on the WAS v7.0 installation.

1. On the WebSphere Application Server v7 installation, create a new base profile using either the Profile Management Tool (32-bit only) or the manageprofiles command line option.
   
   Important: Use the exact same cell name, node name, and hostname that you used for the Portal v6.1/WAS v6.1 installation.
   
   For example, you might run this manageprofiles command on a UNIX environment:
   
   ./manageprofiles.sh -create -defaultPorts -enableAdminSecurity false -profileName <wp_profile_name> -profilePath <profile_path> -templatePath AppServer_root/profileTemplates/default -nodeName <source_node_name> -cellName <source_cell_name> -hostName <host_name> -isDefault -omitAction samplesInstallAndConfig defaultAppDeployAndConfig
   
   where the following values are set:
   
   <wp_profile name> is the name of the new profile
   <profile_path> is the full path to the profile
   <source_node_name> is the node name on the source installation
   <source_cell_name> is the cell name on the source installation
   <host_name> is the host name of the environment.
   
   
2. Run the following ConfigEngine command from the <v61_wp_profile root>/ConfigEngine directory to install Portal-specific files into the WAS v7 installation:
   
   UNIX: ./ConfigEngine.sh install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password> Windows: ConfigEngine.bat install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password> IBM i: ConfigEngine.sh install-wp-migration-files -DNewWasLocation=<WAS v7 install root> -DWasPassword=<password>
3. Ensure OSGI cache has been cleared from the new WAS v7 installation by executing the following command from the <v70_wp_profile>/bin directory:
   
   UNIX: ./osgiCfgInit.sh -all Windows: osgiCfgInit.bat -all IBM i: osgiCfgInit.sh -all
4. If you added the property 'javax.xml.transform.TransformerFactory' the JVM properties for the WebSphere_Portal server, ensure you remove it before migrating the profile. Failure due to so could cause the WebSphere_Portal server to not start after the WAS migration completes. For details on how to remove the property, refer to this technote.
   
5. From the <WAS v7 AppServer root>/bin directory, execute the WASPreUpgrade command to back up the source profile:
   
   UNIX: ./WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer directory> Windows: WASPreUpgrade.bat <temp directory to store backup> <WAS v6.1 AppServer directory> IBM i: WASPreUpgrade.sh <temp directory to store backup> <WAS v6.1 AppServer profile directory>
   Note: If running this on IBM i, the source profile directory is used instead of the AppServer directory.
   
   For example, your command on UNIX might look like:
   
   ./WASPreUpgrade.sh /opt/IBM/wasMigrateBackup /opt/IBM/WebSphere61/AppServer
   
   For more details on the WASPreUpgrade command, refer to this link
   
6. From the <WAS v7 AppServer root>/bin directory, execute the WASPostUpgrade command to migrate the backed up source profile into the new profile
   
   UNIX: ./WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_wp_profile> -oldProfileName <v61_wp_profile> Windows: WASPostUpgrade.bat <temp directory where backup was created> -profileName <v70_wp_profile> -oldProfileName <v61_wp_profile> IBM i: WASPostUpgrade.sh <temp directory where backup was created> -profileName <v70_wp_profile>
   Note: On IBM i, do not include the -oldProfileName flag.
   
   For example, your command on UNIX might look like:
   
   ./WASPostUpgrade.sh /opt/IBM/wasMigratedBackup -profileName wp_profile -oldProfileName wp_profile
   
   For more details on the WASPostUpgrade command, refer to this link
   
   
7. From the <v70_wp_profile>/ConfigEngine directory, execute the following ConfigEngine script:
   
   UNIX: ./ConfigEngine.sh post-was-migration-update -DWasPassword=<password> Windows: ConfigEngine.bat post-was-migration-update -DWasPassword=<password> IBM i: ConfigEngine.sh post-was-migration-update -DWasPassword=<password>
   
8. IBM i only. Copy these directories from the <v61_wp_profile>/PortalServer directory to the <v70_wp_profile>/PortalServer directory:
   
   PortalServer/ap
   PortalServer/base
   PortalServer/bp
   PortalServer/cmapi
   PortalServer/doc
   PortalServer/ext
   PortalServer/installableApps
   PortalServer/installer
   PortalServer/lwo
   PortalServer/lwp04.infra
   PortalServer/pcc.api
   PortalServer/pcc.impl
   PortalServer/prereq
   PortalServer/prereq.infra
   PortalServer/pzn.ext
   PortalServer/search
   PortalServer/shared
   PortalServer/theme
   PortalServer/ui
   PortalServer/wizard