RE: Problem with admistrative console

> From: Urbanek, Marty
>
> Joe,
>
> I would think that should be enough. I thought they require about 400 CPW
> minimum. I'm running 4.0.2 on an LPAR with about 440 batch CPW
> and WAS comes
> up OK. Bloat yes. Mooooooooooooo!

It turned out to be a problem with the FixPack install.  After doing a lot
of research on Google, I found out that it's a "known" problem that after
you install 3.5.0 adminclient, but BEFORE you install the FixPack, you have
to manually add an empty file named in your WebSpehre application root named
<AppRoot>/properties/admin.config.

How silly of us not to know that intuitively.

Evidently, however, the bad installation hosed up EJSADMIN, so that the
WebSphere tree came up empty in Topology view (although the Types view was
fine).  More research indicated that a fresh reload of the server was now in
order.  Deleted EJSADMIN, set initial.install.config to true, and restarted
QEJBSBS.

Finally, things came up.  The first time, though, that we tried to start the
Default Server, we got a failure.  Yet more research indicated that this
particular failure was probably a timeout.  Hoping that some first time
configuration was the culprit, we tried it again, and SUCCESS!

So, while it was a long and winding road, we got there.

Thanks to all for suggestions.  By far the most helpful place, though, is
the WebSphere group on Google.  Tons of information there, from the absurd
to the arcane <grin>.

Joe