IBM Application Runtimes Come for answers. Stay for best practices. All we’re missing is you. Join / Log in Ask a question
I have a working WebSphere Base environment (9.0.5) and I need to somehow migrate to WAS ND, with the less downtime and hassle. If possible not having to re-deploy all the running applications.
I could not find any relevant information.
Is this "migration" supported?
Is there a guide somewhere or could somebody guide me how to do it?
Backup the existing WAS installation, Install WAS ND to a new Filesystem, use Profile Migration tool to
migrate the profile to ND version. You can determine the supported and non supported configuration upgrades in this link
thanks for the reply. As I have limited knowledge of WAS administration, I need some clarification.
I could not understand much about the four tables in the document you pointed to, as they seem to have as target "stand-alone" or "base stand-alone". We are supposed to have ND as our target or am I missing something?
Anyway, the existing base installation is 9.0.5 and the ND will be the same version, so I don't think there will be any compatibility issues.
WAS is on Windows, so I will install ND to a different directory, along with DM and try to migrate the profile. After the migration the outcome will be a dmgr, a node and a server?
I also have a second WAS base edition which I also want to add to the same ND cell. Do I just federate the existing node on this second server?
Back it up - should be the first thing to do.
You can install the WAS ND binaries, create a DMGR profile (controller) to create a new cell and you can then add the existing base server to the ND cell. Run the add node command to add a stand-alone node into a cell.The addNode command does the following: Copies the base WebSphere® Application Server cell configuration to a new cell structure. You probably need to make sure there are not ports conflicts (if you are adding it to an already operating ND cell)
Hope this helps.
Thank you Joe,
I will give it a try during the weekend on a test system.
as you have a running WAS Base deployment you can federate that to a network deployment manager. So I'd setup a network deployment manager and then federate the WAS base into the DMGR cell. So you don't have to reinstall anything as this should transfer all the base WAS config to ND (assuming everything is ready to run on ND).
I know this link is from WSRR but the approach is the same (except that you don't need to check the WSRR prerequ's :) ) as this is WAS functionality. So the same approach should work for you as well (here is more info from the WAS Documentation).
Hope that helps, Hermann