Design logical architecture

Applies To: Office SharePoint Server 2007

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: 2009-01-03

Logical architecture is the manner in which logical components of a solution are organized and integrated. In Microsoft Office SharePoint Server 2007, the logical components include Shared Services Providers (SSPs), Internet Information Services (IIS) application pools, Web applications, zones, policy for Web applications, content databases, site collections, sites, host-named site collections, and My Sites.

In this chapter:

  • Logical architecture components introduces each of the logical architecture components and discusses the following considerations for each component: capacity, sharing and isolation, configurable items, administration, and planning recommendations.

  • Logical architecture model: Corporate deployment describes a practical implementation of logical architecture components to achieve a workable design, including the configuration of users, authentication, and administration sites. The accompanying model illustrates a design example of a corporate deployment of Office SharePoint Server 2007. The model illustrates how the components of the logical architecture are incorporated into the overall design. This article describes the design goals for the model and explains how the goals are achieved using the logical architecture components illustrated in the model.

  • Example Solution Architecture: Twynham School Learning Gateway describes Twynham’s virtual learning environment, the solution architecture of Twynham’s implementation, and also the solution that Coleman’s team recommends for schools that are ready to get started with Office SharePoint Server.

  • Example Solution Architecture: Blatchington Mill School describes the overall solution that Blatchington Mill School implemented and how reporting is woven into the architecture.

  • Plan SSP architecture describes Shared Services Providers (SSPs) and provides examples of how to build SSPs into the architecture of your overall solution design.

  • Design logical architecture for collaboration sites provides logical architecture design recommendations for deploying team sites within a server farm.

  • Design My Sites architecture provides logical architecture design recommendations for deploying My Sites within a server-farm.

  • Design Records Center architecture provides recommendations that can help you configure and organize the logical components of a records management solution based on Office SharePoint Server 2007 and provides guidance for configuring key features of your records management solution.

  • Plan for host-named site collections (Office SharePoint Server) describes how host-named site collections enable Office SharePoint Server 2007 to use host header names, instead of paths, to determine the site collections that users access and the content that is returned in response to user requests. Creating a host-named site collection enables you to host multiple site collections with vanity URLs for users.

  • Plan alternate access mappings (Office SharePoint Server) provides information about configuring Office SharePoint Server 2007 to map Web requests to the correct Web applications and sites. It describes how to implement alternate access mappings for common Internet deployment scenarios in which a Web application that receives a request for an internal URL, in one of the five authentication zones, returns pages that contain links to the public URL for the zone.

  • Update a Web application URL and IIS bindings (Office SharePoint Server) provides guidance for changing the URL and IIS bindings of a Web application.