Adam409
asked on
Should four different divisions (with overlapping associates and security permissions) have diff. web applications
I have multi part question in regards to setting up the topology for my company and am curious about best practices.
We are creating a Sharepoint farm that will be used by different divisions in the company and we require isolation between the divisions.
We have let's call them Division1, Division2 and Division3 all to setup each needing to be separated from each other. Here are some of the questions and concerns i have:
** I should note my sharepoint farm is on the same domain as all the different divisions.
I have done some research and am getting conflicting information on these points which is why i thought i would ask these questions here.
We are creating a Sharepoint farm that will be used by different divisions in the company and we require isolation between the divisions.
We have let's call them Division1, Division2 and Division3 all to setup each needing to be separated from each other. Here are some of the questions and concerns i have:
What i was wondering about is do i setup a different web application for each? or do i setup more generic web application and separate them with site collections? for example internet.domain.com, intranet.domain.com, my.domain.com or do i setup division1.domain.com, division2.domain.com to reach the isolation we require?
If i do use the more generic web applications approach what is the best practice for separating search and metadata? Is setting up partitioning for each service the better way to go in this scenario?
Do i setup a different application pool for each web application? Do i setup a different service application per service? or used a shared app / service pool? What are the advantages of each?
** I should note my sharepoint farm is on the same domain as all the different divisions.
I have done some research and am getting conflicting information on these points which is why i thought i would ask these questions here.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm still a little torn as too which way to go for my SharePoint Farm. The scenario is that each division has multiple departments and I would need Search and Metadata to be shared within each department but not between divisions. Couple things I’m still unsure on are
1. Should I have separate Application pools for each Web App?
2. Should I have separate domain accounts for each Web App?
3. Should I have separate service pools for each Service?
4. Should I have separate service accounts for each Service?
Here are the 2 scenarios that I see possibly working and I hope I can get an opinion as too best case:
1. Setup each division as its own separate web app. -> http://division1, http://division2
-- Setup each department as its own site collections -> http://division1/hr, http://division1/finance
-- Have 1 common mysites Web app for the entire parent company?
2. or Setup each division as a separate site collection all within 1 Web Application -> http://intranet/
-- Setup each division as its own site collection -> http://intranet/division1, http://intranet/division2
--- In this scenario it might be beneficial to create seperate content db's per site collection possibly?
-- Setup each department at its own site -> http://intranet/division1/hr, http://intranet/division1/finance
-- Have 1 common mysites Web app for entire company?
Are there any real advantages / disadvantages in terms of Isolation of Search / Metadata, security or anything else I’m not thinking of for each scenario?
Hopefully I'm not over thinking this but i want to get it right in the beginning.
Thanks again Mathew and Colby for all help!