I'm testing MOSS 2007 and have as a companion, both Bill English's
Administrator Companion and Todd Bleeker's Developer Guide to WSS 3.0.
I'm not a server admin (or at least wasn't for most of my experience with
v2) so understanding what was happening at the IIS level seemed basic to me;
1 Portal per virtual server with a MSSharePointAppPool account. Increase the
number of Portals, but all used the same App Pool until max out at 15
Portals. Okay, got it.
Now, introduce MOSS with it's default setting of creating a new app pool for
each new web application, a new web application for almost any type of site
collection we want, SSP's, and the whole master page idea, and we have a
very different beast.
I'm taking the long road in my testing, trying to do due diligence to my
reading homework in the above mentioned texts (which I am very grateful for)
and an increasing amount of SharePoint blog postings. But I just can't seem
to get my head around all the new features of MOSS, and how best to utilize
them. I've read some of the recommendations on how many Web apps per app
pool (say that 5 times quickly :-) ) but there doesn't seem to be a clear
answer on why or what the implications are for choosing one architecture
over another. I have an environment that while functioning, is seriously
lacking in solid architectural design. Since I wasn't here for the intial
configuration, I want to ensure we don't make the same mistake again.
My environment has only 20 top-level areas, about 3 levels of subsites (so,
< 300 SPS sites), and a few thousand WSS sites. I have an oppotunnity here
to make a supportable architecture, and would appreciate any and all imput
to help guide me toward that goal.
As always, I'm grateful for everyone's input.