Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Farm App Pools and SSPs...does this make sense?

  Asked By: Garret    Date: Mar 17    Category: Sharepoint    Views: 1377

I'm setting up our farm and wanted to see if my AppPool and SSP set up
makes sense. Please comment!

Our farm is going to host 3 web apps (along with central admin):

Teamsites.ourdomain.com
Intranet.ourdomain.com
Mysite.ourdomain.com

I'm trying to figure out how many SSPs and App Pools I should have.

For SSPs, I think I want two, as we want to segregate the intranet
search index from the teamsite search index. As such, I'll make a
SSPintranet and a SSPteamsite both running under different Domain
Accounts so each can have search running. If I do that, could I still
enable a 'search all' option for intranet users so they can search both
the intranet and team sites at the same time?

I'm not as clear on how many App pools I should have. Should there be 6?
One for each web app (including Central Admin and the 2 SSP sites)? Do
they all run under separate domain accounts? That seems like a lot.

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Alyssa Butler     Answered On: Mar 17

> I'm not as clear on how many app  pools I should have. Should there be
> 6?
> One for each web app (including Central Admin and the 2 SSP sites)? Do
> they all run under separate domain accounts? That seems like a lot.

As a follow-up to my own question...I think I have things backwards...I
likely want 6 App pools  (one for each web app) but can likely get by
with only 2 SSPs...one for our shared portal and one for the rest of the
sites which are only for internal users. Does that sound correct?

 
Answer #2    Answered By: Katy Patton     Answered On: Mar 17

Unless security is really high in your organization (and I am not
convinced you get that much security by isolating app  pools), I would
suggest using:

1 App Pool for Central Admin

1 App Pool for SSP1

1 App Pool for SSP2

1 Community App pool for everything else

Of course, if you need isolation between Web Apps to guard against 3rd
party web parts crashing the pool, then you might use more than above. I
generally don't create another app pool for every Web App - that can
affect performance, even on 64 bit boxes.

 
Answer #3    Answered By: Ana Payne     Answered On: Mar 17

I would query whether you really want more than one SSP. SharePoint
enforces security on search results, so you don't need it to protect
users from seeing links they shouldn't. You only need the separate
SSP if there is a policy issue with the use of a common index file
inside the system. Search results for users can be managed with
scopes, if you don't want results mingled.

With multiple SSPs, you lose is the ability to have a consolidated
search of all content, unless you cross-crawl which defeats the
point. You also make  the environment more complex to maintain (e.g.
two user profile databases to configure) and add to hardware
requirements (multiple index servers required).

 
Answer #4    Answered By: Hema Hegde     Answered On: Mar 17

> I would query whether you really want more than one SSP. SharePoint
> enforces security on search results, so you don't need it to protect
> users from seeing links they shouldn't. You only need the separate
> SSP if there is a policy issue with the use of a common index file
> inside the system. Search results for users can be managed with
> scopes, if you don't want results mingled.

Oh? This is a bit contrary to what our consultant suggested, but
something I should look into.

> With multiple SSPs, you lose is the ability to have a consolidated
> search of all content, unless you cross-crawl which defeats the
> point. You also make  the environment more complex to maintain (e.g.
> two user profile databases to configure) and add to hardware
> requirements (multiple index servers required).

Good points.

Yes, the way our consultant is suggesting is that we have two SSPs:

1 - for our Team Site portal that external users can access
1 - for our intranet portal, mysites portal, and all SP admin sites only
internal users can access.

We'd then have two search indexes one accessible via the intranet that
indexes everything, and one only for team site searching.

Could one index server handle both of those?

For now, we'll start slowly with one SSP and then look into this some
more before adding the second. Thanks for the advice!

 
Answer #5    Answered By: Lacey Daniels     Answered On: Mar 17

1 index can handle both (normally up to millions of documents and last time I
heard tested up to 5 million docs) so unless you are beyond that then one index
can do this if your index and search servers are capable of using such a large
index

What you are being told from both sides is correct

Results are security trimmed so with one index, if users aren't allowed to see
the content, it wont be returned in search results

If you don't want so many search results you can reduce this by using search
scopes (only search tem sites, only search file shares etc)

However, lets say that you are using MOSS for both your internal intranet AND
your internet site

You would not want any possibility that the public, accessing your internet
site, could be returned internal documents because of a security
misconfiguration (a user allowing everyone to read). In this event you would
want to use two indexes so you have the comfort of know that only certain
results will be returned to a certain set  of users. i.e. if you are in any
highly secure environment you can split the index if you want. Be aware though
that this will affect search only and doesn't stop them just typing in a url to
content !

 
Didn't find what you were looking for? Find more on Farm App Pools and SSPs...does this make sense? Or get search suggestion and latest updates.




Tagged: