Plan for Web applications in an EPM/Office SharePoint Server 2007 extranet environment

  • Article

This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2010-02-24

This article describes how to plan for Web applications 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.

Web applications

A Web application is an IIS Web site that is created and used by SharePoint Products and Technologies. Each Web application is represented by a different Web site in IIS. You assign each Web application a unique domain name, which helps prevent cross-site scripting attacks.

Generally speaking, use dedicated Web applications in the following ways:

  • Separate anonymous content from authenticated content   In the model, the company Internet site is hosted in a dedicated Web application and application pool.

  • Isolate users   In the model, Partner Web is hosted in a dedicated Web application and application pool to ensure that partners do not have access to the intranet content.

  • Enforce permissions   A dedicated Web application provides the opportunity to enforce permissions by policies by using the Policy for Web Application page in Central Administration. For example, you can create a policy on the company Internet site to explicitly deny write access to one or more groups of users. Policies for a Web application are enforced regardless of permissions configured on individual sites or documents within the Web application.

  • Optimize performance   Applications achieve better performance if they are put in Web applications together with other applications of similar data characteristics. For example, the data characteristics of My Sites include many sites that are small. In contrast, team sites typically consist of a smaller number of very large sites. By putting these different kinds of sites in separate Web applications, the resulting databases are composed of data with similar characteristics, which optimizes database performance. In the model, My Sites and team sites do not have unique data isolation requirements — they share the same application pool. Nonetheless, My Sites and team sites are put in separate Web applications to optimize performance.

  • Optimize manageability   Because creating separate Web applications results in separate sites and databases, you can implement different site limits (recycle bin, expiration, and size) and negotiate different service-level agreements. For example, you might allow more time to restore My Site content if this is not the most important kind of content within your organization. This lets you restore more important content before you restore My Site content. In the model, My Sites are put in a separate Web application to enable administrators to more aggressively manage growth compared to other applications.