Plan for application pools in an EPM/Office SharePoint Server 2007 extranet environment
Updated: February 25, 2010
This article describes how to plan for application pools in an Enterprise Project Management (EPM)/ Microsoft Office SharePoint Server 2007 extranet environment. For an overview of this chapter about how to plan for EPM extranets, see Plan an EPM/Office SharePoint Server 2007 extranet environment.
Separate Internet Information Services (IIS) application pools are typically implemented to achieve process isolation between content. Application pools enable multiple sites to run on the same server computer but still have their own worker processes and identity. This reduces the effect of an exploit on one site that provides an opportunity for an attacker to inject code onto the server to attack other sites.
Practically speaking, consider using a dedicated application pool for the following scenarios:
To separate authenticated content from anonymous content.
To isolate applications that store passwords for and interact with external business applications (for example, Business Data Catalog connections).
To isolate applications where users have great liberty to create and administer sites and to collaborate on content.
The model uses application pools in the following way:
Each administration site is hosted in a dedicated application pool. This is required by Office SharePoint Server 2007.
Intranet content is divided into two application pools. Collaborative content (My Sites and team sites) is hosted in one application pool. The published intranet content is hosted in a separate application pool. This configuration provides process isolation for the published intranet content in which business data connections are more likely to be used. For example, many human resources (HR) sites use business data connections to enable employees to access their personal data.
The Partner Web application is hosted in a dedicated application pool.