Standalone Server--Windows 2003 Server Enterprise

Sharepoint 3.0 with SP2 installed (Basic)

 

Default Web Applications created:

http://server2003:80
http://server2003:20809

1

2

From above two graphes, we conclude that one sharepoint web application matches one IIS web site.

Multiple Web Applications

c:\windows\system32\hosts file

127.0.0.1 localhost me.com www.me.com you.com www.you.com he.com www.he.com

Create New Web Application

Create a new IIS web site

Description:SharePoint-Me
Port:80
Host Header: me.com
Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\me.com_80

Authentication provider: NTLM

Allow Anonymous: No

Use Secure Sockets Layer (SSL): No

URL:http//me.com:80

Zone:Default

Create new application pool:

Application pool name:SharePoint-me.com-80

Select a security account for this application pool

Predefined:Network Service

Database Server:Server2003\Microsoft##SSEE

Database Name:WSS_Content_me

Database Authentication: Windows authentication (recommended)

Select Windows SharePoint Services search server: Server2003

 

Click "OK"

Central Administration > Application Management > Create or Extend Web Application > Create New Web Application > Application Created

Application Created

 

The Windows SharePoint Services Web application has been created.

If this is the first time that you have used this application pool with a SharePoint Web application, you must wait until the Internet Information Services (IIS) Web site has been created on all servers. By default, no new SharePoint site collections are created with the Web application. To create a new site collection, go to the Create Site Collection page.

To finish creating the new IIS Web site, you must run "iisreset /noforce" on each Web server.

3

If a site collection is not created, accessing http://me.com will return "The webpage cannot be found".

Create Site Collection

Central Administration > Application Management > Create Site Collection

Use this page to create a new top-level Web site.

Web Application: http://me.com

Title: Me
Description:www.me.com

4

Select a template: Collaboration--Team Site

5

Click OK

 

Top-Level Site Successfully Created

The new, empty top-level site was created successfully with the specified URL. If you have permission to view the Web site, you can do so in a new browser window by clicking the URL. To return to SharePoint Central Administration, click OK.

http://me.com

Before you can log into http://me.com, you have to configure IIS authentication because the server2003 is a standalone installation (not a domain environment).

6

7

Then, both http://me.com and http://www.me.com is accessible.

After a site collection is created for a web application, a top level site (/)is automatically created and can be accessed by URL, for example, http://me.com.

Create several subsites in a web application http://me.com

They can be accessed by:

http://me.com/3D
http://me.com/VFX
http://me.com/GAD
http://me.com/DP
http://me.com/broadcast
http://me.com/web
http://me.com/acting

8

 

A Site Collection is created in SharePoint 3.0 Central Administration. A site is created within a regular SharePoint site--by default, it is the top level site.

Create another Site Collection for CDI College

9

The CDI College site collection can be accessed by http://me.com/sites/CDI.

Site Collections vs. Subsites

Create a site collection to support

Create a subsite to support

A security boundary (significantly different permissions and roles) between your sites and other sites

Shared navigation between sites

Delegation of site administration to someone different from the administrator of existing site collections

Inherited permissions from parent sites (parent sites are the higher-level sites that subsites are created within)

Search features or workflows that are scoped differently from existing site collections

Shared lists between sites

A size quota different from that of existing site collections

Shared design elements, such as themes or styles, between sites

Site collection features that are not active on other site collections (for example, the Publishing Infrastructure feature)

A small use of your SharePoint size allotment

 

Observation:

When a SharePoint site is created, there is no matching web site or virtual directory created in IIS.

Managed Path

By default, when a web application is created, two managed path (/ and sites) are defined.

10

For a managed path with Explicit inclusion type, e.g /, you cannot create more than one site collection. Because a site collection is created for web application http://me.com, you cannot create another site collection directly under the root /.

Because the managed path (sites) is defined as wildcard inclusion, you can create many site collection under it.

11

If you want to URL http://me.com/HR to be dedicated for Human Resources, you create a managed path:HR with Explicit inclusion type.

12

After you create a site collection in the Managed Path: HR, you cannot create another site collection for the Managed Path: HR. You can access the site collection by http://me.com/hr.

13

 

14

For /hr site collection,

URL--http://me.com/hr
Primary Administrator--Server2003\Liao
Database Name--WSS_Content_me

For /sites/CDI site collection,

URL--http://me.com/sites/cdi
Primary Administrator--Server2003\ming
Database Name--WSS_Content_me

For /sites/SFU site collection,

URL--http://me.com/sites/sfu
Primary Administrator--Server2003\kaiming
Database Name--WSS_Content_me