For migration of WAS to higher version on same server can use the Configuration Migration Tool(I have not used it though). If migrating to a new infrastructure then follow the below steps. Yes there is no one stop documentation. Infocenter is all we have got and needs some bit of work and workarounds to get the actual things going :)
1. Take backup of configurations on all WAS servers for all profiles
• $WAS_InstallRoot/profiles/dmgr/bin/backupConfig.sh $LOCATION/WAS_Heapdumps/dmgr_backup_beforemigration.zip –nostop
• $WAS_InstallRoot/profiles/base/bin/backupConfig.sh $LOCATION/WAS_Heapdumps/node1_backup_beforemigration.zip –nostop
• $WAS_InstallRoot/profiles/base/bin/backupConfig.sh $LOCATION/WAS_Heapdumps/node2_backup_beforemigration.zip –nostop
2. The Version 8.5.5 profile nodeName and cellName must match the previous Version 7.0 or later nodeName and cellName. If the Version 8.5.5 deployment manager cellName or nodeName are different, the migration will fail.
3. Install WAS8.5.5 on new Infrastructure
4. Since we are migrating to a higher version on different servers it is necessary to generate the Remote Migration Jar file from WAS8.5.5 and copy on all WAS7 nodes and use WAS_PreUpgrade command to extract configuration from each of the nodes.
• cd $LOCATION/WAS8.5.5/AppServer /migration/bin;./createRemoteMigrJar.sh -targetDir .
Creating the remote Migration Jar File ...
BUILD SUCCESSFUL
Total time: 1 minute 50 seconds
The WebSphere Remote Migration Support jarfile has been created.
1) Send jarfile to the system where your source profile resides.
2) Unjar the file to a temp location.
3) cd to the bin directory in the temp location.
4) Run the WASPreUpgrade command against the source profile to be migrated using the -machineChange true parameter.
See the WASPreUpgrade command details in the infoCenter.
5. Perform the below activities on Old Server
Prepare for Pre Migration from Old server
• $LOCATION/WAS_Heapdumps/WAS_V85_$os.$arch_RemoteMigrSupport/bin/WASPreUpgrade.sh $LOCATION/WAS_Heapdumps/dmgr_WAS_PreUpgrade_duringmigration/ $WAS_InstallRoot -oldProfile dmgr -machineChange true
Jar the file to be copied on to respective Upgrade server
• cd $LOCATION/WAS_Heapdumps;$WAS_InstallRoot/java/bin/jar -cf dmgr_WAS_PreUpgrade_duringmigration.jar dmgr_WAS_PreUpgrade_duringmigration/
6. Perform the below activities on New Server
For Post Migration copy the Jar file created above to the given location on new server and extract the files containing source profile configurations
• mkdir $LOCATION/WAS_Heapdumps/dmgr_WAS_PostUpgrade_duringmigration
• cd $LOCATION/WAS_Heapdumps/dmgr_WAS_PostUpgrade_duringmigration
• $LOCATION/WAS/8.5.5/AppServer/java/bin/jar -xf dmgr_WAS_PreUpgrade_duringmigration.jar
Executing WAS_Post_Upgrade to configure the old profile configurations on to the new server
• $LOCATION/WAS/8.5.5/AppServer/bin/WASPostUpgrade.sh $LOCATION/WAS_Heapdumps/dmgr_WAS_PostUpgrade_duringmigration -profileName dmgr -oldProfile dmgr -replacePorts TRUE -backupConfig TRUE -scriptCompatibility TRUE -keepDmgrEnabled TRUE -username $$$ -password ###
7. Once this is completed perform the activities sequentially on all the nodes and restart nodeagents and start JVMs to see that there are no errors.
Change the SDK to 1.8 for entire cell
• $LOCATION/WAS/8.5.5/AppServer/bin/managesdk.sh -enableProfileAll -sdkname 1.8_64 -enableServers
Restart all JVMs in the cell.