Re: WAS 7.0 Express Install hangs at 30 percent

[Pete Helgren <Pete@xxxxxxxxxx>]

In this particular case, and it was the part that I wasn't 
understanding, is that you must apply the WAS group *before* installing 
WAS, which was counter intuitive.  I had downloaded the group and was 
waiting to install it (using the special instructions you noted) AFTER I 
had installed WAS 7 express.  That approach was *wrong*.  I had to apply 
the group *first*, which had fixes for SS1, JV1, QU1 and some other LP's 
that I don't recall at the moment and then install WAS.  After the 
installation I had to reapply the group, following the instructions you 
indicated.  But my fatal mistake that took two weeks to resolve was to 
understand that the group had to be applied first, using option 8 on the 
PTF menu.  After that, WAS 7 express finally DID install and then I 
could proceed.

Again the install was the issue.  Applying the group after install was a 
cake walk.....

Pete


On 6/2/2010 6:31 AM, rob@xxxxxxxxx wrote:
> Pete,
>
> There are special considerations with WAS and it's group ptf's.  If you go
> to
> http://youri:2001/HTTPAdmin
> log in and select Manage, All Servers, All Application Servers, it will
> show you the current version of WAS.  A sample might be V6.0.2.35.  Just
> putting on the group ptf will not upgrade your WAS.  You must follow the
> special instructions.  For example,
> http://tinyurl.com/SF99352
> or
> http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/ad2a5c5706e1a1d18625743a00160c80?OpenDocument
> which points to
> http://www-03.ibm.com/systems/i/software/websphere/services/fixpack60.html
>
> See the cover letter for the WAS group you are trying to install.
>
> Rob Berendt
>