Upgrading Fix pack on websphere application server

--------------------------------

We are planning to decide on a policy on WebSphere Application Server Upgrade. Have to decide on a policy to apply patches to WebSphere. There are two questions that need to be answered. When and why to upgrade fix packs on websphere. Say for instance we are rnning WAS 6.1.0.17 . we need to set up a policy so in order to upgrade WebSphere to a new fix pack level and set it as a standard enterpise wide. Can someone help. All I need is What and Why.

--------------------------------

Posted By: killerweed1 at Jun 7 2009 3:13AM

You need to stay up to date on fixpacks because there are usually security updates and other issues that are addressed. It just makes good policy to keep up to date.

I always start in Dev, then immediately apply to Test. After two weeks I'll enter a change control request to update Production.

--------------------------------

Posted By: brewdude at Jun 8 2009 3:16PM

Agreed. We did intend to patch WebSphere in dev as soon as the newest patch was realeased, meaning that it would take about 3 months to hit production. However the biggest problem we have is trying to convince /"the business/" to commit to the man hours to deploy the code. Currently in production we are only running WAS 6.0.2.19 so we are beginning to get behind...

--------------------------------

Posted By: frankstar123 at Jun 9 2009 10:26AM

Wow...sounds like you need a Champion!

--------------------------------

Posted By: brewdude at Jun 9 2009 1:20PM

Generally once in 4 to 6 months cycle is good for patching given that no security patches are released in between or you don't run into a showstopper bug which you have to do it right away.
Regression testing of Apps would be part of the patching if it touches main components like the web or ejb container or jdk fixes to make sure nothing is broken after the patch.

--------------------------------

Posted By: sphere41 at Jun 9 2009 9:51PM