Question & Answer
Question
How do I migrate the IBM WebSphere Application Server (WAS) v8.0 and later product and profile environments between IBM i partitions?
Answer
If the version of WAS changes between IBM i partitions, please refer to the following documents on how to migrate your WAS product and profiles.
IBM WebSphere Application Server v9.0 Product Migration Steps
IBM WebSphere Application Server v8.5.5 Product Migration Steps
If the version of WAS does NOT change but the IBM i VRM changes, refer to the IBM i Memo To Users (MTU) of your target IBM i VRM for special instructions regarding the WAS product.
IBM WebSphere Application Server v9.0 Product Migration Steps
IBM WebSphere Application Server v8.5.5 Product Migration Steps
If the version of WAS does NOT change but the IBM i VRM changes, refer to the IBM i Memo To Users (MTU) of your target IBM i VRM for special instructions regarding the WAS product.
IBM i 7.5 Memo To Users
IBM i 7.4 Memo To Users
IBM i 7.3 Memo To Users
IBM i 7.2 Memo To Users
IBM i 7.1 Memo To Users
NOTE: IBM WebSphere Application Server v8.5 is NOT supported on IBM i 7.5. IBM WebSphere Application Server v8.5 product users will need to upgrade to WebSphere Application Server v9.0 when upgrading to IBM i 7.5 OS.
IBM i 7.4 Memo To Users
IBM i 7.3 Memo To Users
IBM i 7.2 Memo To Users
IBM i 7.1 Memo To Users
NOTE: IBM WebSphere Application Server v8.5 is NOT supported on IBM i 7.5. IBM WebSphere Application Server v8.5 product users will need to upgrade to WebSphere Application Server v9.0 when upgrading to IBM i 7.5 OS.
IBM JDK 7.x and earlier are not supported by WebSphere Application Server v8.5. You will need to ensure 5770JV1 Option 16 and 17 LPPs are installed and your WebSphere Application Server v8.5 product and profiles are configured to use JDK 8.0.
If the version of WebSphere Application Server and the IBM i OS DO NOT change between the 2 IBM i partitions, here are the steps to move or migrate your IBM WebSphere Application Server environment between IBM i partitions:
====================================================================
====================================================================
| 1) | Identify your WebSphere Application Server installation location and library. STRQSH /QIBM/WAS/bin/queryWASinstalls The output of the command should look something like this: ---------------------------------------------------------------------------- Websphere Edition: EXPRESS Version: 8.5.5.11 Installation Location: /QIBM/ProdData/WebSphere/AppServer/V85/Express Installation Library: QWAS85A Default Profile Location: /QIBM/UserData/WebSphere/AppServer/V85/Express ---------------------------------------------------------------------------- In the example above, the Installation Location is defined as "/QIBM/ProdData/WebSphere/AppServer/V85/Express". This would be the directory you would use in place of the <INSTALL_LOCATION> variable. <INSTALL_LOCATION> = Installation Location In the example above, the Installation Library is defined as "QWAS85A". This would be the library you would use in place of the <INSTALL_LIBRARY> variable. <INSTALL_LIBRARY> = Installation Library |
| 2) | Create OR clear the save files to store your installation data. If the files do not already exist, create them. CRTSAVF QGPL/WASPRDDTA CRTSAVF QGPL/WASLIB CRTSAVF QGPL/WASPRDLIB CRTSAVF QGPL/IM If the files already exist, clear them. CLRSAVF QGPL/WASPRDDTA CLRSAVF QGPL/WASLIB CLRSAVF QGPL/WASPRDLIB CLRSAVF QGPL/IM |
| 3) | Save the IBM InstallationManager (IM) and WebSphere Application Server (WAS) installation and profile data and private authorities to save files. On the source IBM i partition, execute the following commands: SAV DEV('/QSYS.LIB/QGPL.LIB/WASPRDDTA.FILE') OBJ(('/QIBM/ProdData/WebSphere/') ('/QIBM/UserData/WebSphere') ('/QIBM/WAS')) PVTAUT(*YES) SAVLIB LIB(<INSTALL_LIBRARY>) DEV(*SAVF) SAVF(QGPL/WASLIB) PVTAUT(*YES) i.e. SAVLIB LIB(QWAS85A) DEV(*SAVF) SAVF(QGPL/WASLIB) PVTAUT(*YES) SAVLIB LIB(QWAS85) DEV(*SAVF) SAVF(QGPL/WASPRDLIB) PVTAUT(*YES) SAV DEV('/QSYS.LIB/QGPL.LIB/IM.FILE') OBJ(('/QIBM/ProdData/InstallationManager') ('/QIBM/UserData/InstallationManager') ('/QIBM/InstallationManager') ('/QIBM/UserData/IMShared')) PVTAUT(*YES) |
| 4) | FTP the save files over to the new box. On the source IBM i server, execute the following: FTP RMTSYS(<otherIBMiServer>) bin lcd QGPL cd QGPL namefmt 1 put WASPRDDTA.savf put WASLIB.savf put WASPRDLIB.savf put IM.savf |
| 5) | Restore the save files with private authorities to the new box. On the target IBM i partition, execute the following commands: RST DEV('/QSYS.LIB/QGPL.LIB/WASPRDDTA.FILE') OBJ(('/QIBM/ProdData/WebSphere/') ('/QIBM/UserData/WebSphere') ('/QIBM/WAS')) PVTAUT(*YES) RSTLIB SAVLIB(<INSTALL_LIBRARY>) DEV(*SAVF) SAVF(QGPL/WASLIB) PVTAUT(*YES) i.e. RSTLIB SAVLIB(QWAS85A) DEV(*SAVF) SAVF(QGPL/WASLIB) PVTAUT(*YES) RSTLIB SAVLIB(QWAS85) DEV(*SAVF) SAVF(QGPL/WASPRDLIB) PVTAUT(*YES) RST DEV('/QSYS.LIB/QGPL.LIB/IM.FILE') OBJ(('/QIBM/ProdData/InstallationManager') ('/QIBM/UserData/InstallationManager') ('/QIBM/InstallationManager') ('/QIBM/UserData/IMShared')) PVTAUT(*YES) |
| 6) | Update the TCP/IP host name configuration for each WebSphere Application Server profile to the host name for the new IBM i partition. How To Change The Host Name For An IBM WebSphere Application Server Full Profile |
| 7) | Start your WebSphere Application Server profiles on the new IBM i partition. STRQSH cd /QIBM/ProdData/WebSphere/AppServer/<version>/<edition>/bin startServer -profileName <profile> |
| 8) | Congratulations! You have successfully completed the WebSphere Application Server product migration. |
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHUAA2","label":"WebSphere Application Server"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
04 May 2023
UID
nas8N1020675