Microsoft Office Tutorials and References
In Depth Information
View All Site Collections lets you see a list of all the site collections contained in a selected web
application. You’ll learn more about self-service site creation later in this chapter.
Creating a new Web Application
Let’s move another layer up the chain and look at web applications. Suppose you want to have
more user-controlled sites with automatic deletion enabled but don’t want automatic deletion
enabled on all your other site collections or to be forced to respond to usage notifications on
your main site collections. In this case, you’ll need a new web application because site use
confirmation and deletion is applied per web application.
Web applications are what SharePoint uses to hold site collections. Every site collection has
to reside in a web application, although a web application can contain many site collections.
When SharePoint was installed earlier in the topic, two web applications were created: the first
site (in my example that’s http://spf2/) and Central Administration (in this case, http://
spf2:9876/). A web application essentially consists of two items that reside in IIS: an IIS
Web Site and an Application Pool. The default http://spf2 web application uses the IIS Web
Site SharePoint-80, while Central Administration (http://spf2:9876) uses the IIS Web Site
SharePoint Central Administration v4.
Any settings you configure in IIS on these websites affect every site collection in the
corresponding web application. IIS Web Sites host security settings such as SSL, authentication, and
anonymous access, making web applications security boundaries in the sense that their security
settings affect all the site collections they contain, while not affecting the security of other web
applications. In addition to IIS settings, SharePoint offers a lot of additional configuration that
can be done at the web application level.
DID YOU REMEMBER YOUR MANAGED ACCOUNT?
Web applications make use of their IIS Web Site application pool identity to access resources such
as their database in SQL. So if you want to give your web application its own, unique application
pool identity (good for troubleshooting because you know exactly what account is being used by
the web application but bad because each application pool does use some RAM to do its work), set
it up in SharePoint as a managed account before you create the web application. You can register an
account directly from the web page used to create the web application, but moving away from the
settings page w ill w ipe all the changes you made, and you’ll have to star t over. To set up a managed
account, just go to Configure Managed Accounts under the Security heading, and then register a
managed account. For more details, see Chapter 3.
Almost all web application administration and customization is done in Central
Administration under Application Management. Click the Manage Web Applications link,
which will take you to the Web Applications Management page, as shown in Figure 10.23.
Let’s create a new web application for user blogs—one with a main site collection for the
administration blogs and other information.
1. To create a new web application, make sure you are on the Web Applications
Management page, and click the New button.