- This topic has 0 replies, 1 voice, and was last updated 14 years, 2 months ago by
.
-
Posts
-
With early versions of WebSphere 7.0 and 6.1 we’ve seen that simple changes to an application will can take a considerable amount of time to become available within the server once sync’d. This problem is caused by using a version of WAS 7.0 that has not been patched through update #11 or 6.1 that has not been patched up to #31. Updating WAS to the most recent version will fix this problem
For WAS 7.0, please apply at least Fix Pack 11, which you can find on this page:
http://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver70For WAS 6.1, please apply at least Fix Pack 31, which you can find on this page:
http://www-01.ibm.com/support/docview.wss?uid=swg27004980#ver61To install either fix pack you’ll also need to have IBM’s update installer already installed. If you need a copy that works with either WAS 7.0 or 6.1 you can get it here: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020448
If you’d like to see what version you’re running prior to applying the update, you can open a shell window and navigate to the AppServer/bin folder and run the VersionInfo.bat program. This will give you the exact version of WAS you are currently on. When you apply the fix pack 11, the version should say 7.0.0.11.
For the interested, the following two issues are likely be the reason why earlier versions of WAS are problematic when partial application updates are applied. Please note that WAS uses the wsadmin tool for deployment.
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK79287
http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg1PK78563
