Apart from upgrading individual wM products(on-premise not wm.io) in an environment, what are the other (commonly employed) components that gets impacted due to the upgrade for eg. loadbalancer configuration in a cloud setup ? Specifically those components which needs to be updated along with the upgrade as the upgrade team’s responsibility.
I’m looking for real life upgrade scenarios, can someone please share from their experience on this subject? Thank you.
some things to check will be if the OS and/or Database need an upgrade as well.
Additionally you should check if the used libraries for database driver, SAP JCo API, MQSeries connectivity etc. will require newer versions.
@Holger_von_Thomsen Thank you for the response. Do you have some example for the loadbalancer configuration ?
I am sorry, but we had never needed a Loadbalancer in our project.
You don’t need to do anything to load balancer if you are installing new version on to same servers. If you configured clustering properly, you don’t really need a complex load balancer algorithm either, round robin will do. Can you tell me why you need load balancer configuration?
In my opinion load balancer should be as simple as possible. You don’t really want anything to be over-engineered there.
Only thing I remember that is important on load balancer is for MWS. It has to stick sessions to same node. In other terms once load balancer receives a traffic, it should keep sending it to the same node from the same client. It shouldn’t switch nodes when using the same session. Otherwise it will keep asking the user to login again.
I havent been involved in an upgrade lately but recalling my experience from when I did, one of the major objectives of an upgrade should be minimal impact to other components and applications. Off course, the dependencies, like the ones Holger mentioned, would have to be accounted for. But the you should try to design and upgrade plan to minimize the impact to other applications and partners. It can be tricky since most production upgrades are not done in place because of the risk involved. But one of the approaches taken is to make sure that you use URLs that can be simply rerouted to the new servers. Network admins can help with a lot of that stuff. There are sometimes challenges in scenarios even when the Integration Server or an adapter is connecting to another application. Sometimes those apps have limited access to certain IPs only. So make sure you test that from the new setup. I always like to have a new environment up, have a few transactions run through it and then switch over.