I have downloaded the fix pack 17, both the server and client versions and the update installer
After selecting "C:\Program Files\IBM\SDP\runtimes\base_v7" as the server to be updating and the unzipped fixpack for the server the available maintenance packages screen is disabled. Is there a different way to install the fixpack 17. Do I have to install earlier fixpacks first.
1) You need to place WAS fixpack into "...IBM/WebSphere/UpdateInstaller/maintenance" directory. Then Update Installer can recognize it and propose to install.
2) You don't need to install previous fixpacks.
3) I suggest you to install WAS Java SDK fixpack 184.108.40.206 together with WAS 220.127.116.11 fixpack.
Java Platform, Enterprise Edition 6 Web Services Developer Certified Expert Exam Study Guide and Quiz Exam 1Z0-810: Upgrade to Java SE 8 Programmer Study Guide and Quiz
Joined: May 28, 2008
I suggest you to install WAS Java SDK fixpack
Thanks, sorta solved the problem.
I am able to install fix pack 13 by placing in the SDK jar file that I had got from a website into the unzipped AppServer fixpack folder.
I tried searching for an SDK jar file for fix pack 17 but could find it. Tried placing the unzipped SDK pak file in the unzipped FixPack17 folder but it didn't recognize it...
Do I have to add the SDK also as maintenance pack. Need to try that.
Besides, I am having OutOfMemory issues when I try adding library jars to my ear which is the reason why I tried the Fixpacks. Fixpack 13 didn't resolve this. Anyone else having similar issues ??
Joined: Jun 04, 2002
Please download both fixpacks (WAS AppSrv and Java SDK), put in maintenance folder and run update installer. You don't need to unpack anything manually or manually hack JARs within WAS - you may damage WAS that it won't be starting after that !
Thanks a lot MZ... I copied both files into the maintenance folder and it picked it up.
One issue that I had to work around is that in one machine(corporate VPN network) the files were downloaded as *.zip file. When I tried the download in another machine it was downloaded with the proper .pak extension. When I renamed the file to *.pak in the first machine the update installer was able to pick it up.