Comments on: Upgrading WebSphere Application Servers – Update the Deployment Manager First!

By: Franch

Franch — Thu, 30 Jul 2009 07:01:27 +0000

Of course but the node agents communicates, our consultant told us that the must run the same software version same FP and same ifix to avoid problems…
After updating one node, we have to start it before stop the other, during this time (could be few seconds) our cluster members are not running the same version

By: dan

dan — Wed, 29 Jul 2009 17:14:16 +0000

Well the whole point of having a cluster is for failover and high availability (assumping an http server in there somewhere). If you have two servers in a cluster, you can take server1 down while failover will redirect traffic to server2.

By: Franch

Franch — Wed, 29 Jul 2009 16:14:28 +0000

Ok, thanks for your answer, I was wondering about this subject because all the IBM software consultants we met told us that there is no way to avoid the production interuption

By: dan

dan — Wed, 29 Jul 2009 16:10:30 +0000

Of for sure, once you have updated the deployment manager, you can then perform your upgrades by taking one node down, upgrading, starting and then taking the other node down.

There’s no issue with having different levels of WAS inside your cluster, it’s just that the DMGR always has to have the highest fixpack in the group.

By: Franch

Franch — Wed, 29 Jul 2009 15:56:28 +0000

But after updating the DMGR, could we update one node, restart it and then stop and update the second node? (In this case each node had a specific runtime)