Microsoft Sharepoint Products and Technologies Resource Kit eBook

Chapter 17: Configuring SharePoint Portal Server 2003 479
Note Each portal site still has the db_owner database role on the configuration
database and can affect other portal sites in the server farm by writing
to the configuration database.
Remember and be careful to switch all components of the Web server to the
new application pool, including the virtual directories (for example, _vti_bin,
_layouts, and so on). If this is not done, the portal site will become inaccessible.
Also, do not forget to assign the appropriate user account to the application pool.
Figure 17-14 shows the Identity tab of the properties page for an application pool
where this is done.
F17XR14.bmp
Figure 17-14 Creating an additional application pool
Creating Portal Sites
It is important to realize that more than one portal site can be hosted by a Microsoft
SharePoint Portal 2003 server. This section will describe the overall steps required to
create additional portal sites beyond the first one in a multi-front-end server farm.
From what we’ve learned so far, we know that for each portal site we need an
additional virtual server to be created in IIS. We also know that even though we do
not extend portal virtual servers directly, the portal site creation process, displayed
in Figure 17-15, extends them for us. Extending a virtual server involves associating
the Windows SharePoint Services ISAPI filter to it, as well as entering folder references
for Managed path exclusions or inclusions.