Item Minimum Requirement MS Recommends

yompmulligrubsInternet and Web Development

Oct 31, 2013 (3 years and 11 months ago)

94 views


Servers

Estimated Price

Office SharePoint Server 2007 (CALs also required)

$4,451

Office SharePoint Server 2007 for Internet Sites (no CALs required)

$41,134

Microsoft Search Server 2008 (no CALs required)

$14,420

Microsoft Search Server 2008 Express

(no CALs required)

Free Download


Client Access Licenses

Estimated Price

Office SharePoint Server 2007 Standard CAL

$94

Office SharePoint Server 2007
Enterprise CAL
1

$75


Open table as
spreadsheet
Item

Minimum Requirement

MS Recommends

Operating system

Any edition of Microsoft Windows
Server 2003

Any edition of Microsoft
Windows Server 2003

CPU

1 CPU running at 2.5 GHz

2 CPUs running at least 3 GHz

RAM

1 GB

2 GB or more

Disk space

Minimum 3 GB of free disk space

Minimum 10 GB of free disk
space

File system

NTFS

NTFS

IIS version

6.0 with ASP.NET (in Worker Process
Isolation Mode)

6.0 with ASP.NET (in Worker
Process Isolation Mode)

Database engine

SQL Server 2005 Express or SQL
Server 2000 with Service Pack 3a

A separate SQL Server 2005 and
its latest service pack

Internet browser

IE 6.0 with the latest service pack

IE 7 with the latest service pack








Open table as spreadsheet
Feature

SQL
Server Express

MS SQL
2000/2005

Limited database size

Yes (4 GB max
-

but see comment in the text
below)

No

Can run on a separate server

No

Yes

Includes management tools

No

Yes

License type

Free

Per CPU or per
user




Open table as spreadsheet
Question

People to Ask

Comment

Do you need an intranet for the
whole organization?

Top management,
people responsible for
managing organization
-
wide information

For a small company with fewer than
50 users, WSS may be sufficient.
But if there is a lot of
information,
MOSS will better suit your needs.

Do you need a local intranet for
your department or team?

Middle management,
team leaders

WSS is a good choice if the
department or team is working with
the same type of information.

Do you want to be able
to search
for information across sites or
external to SharePoint?

All types of users

Only MOSS offers global search
functionality.

Is searching inside a specific
SharePoint site enough for your
needs?

All types of users

This is a complementary question to

the previous one; if the answer is
yes, you could fulfill this need by
using WSS and MS SQL Server
together.

Do groups of users need to share
and update different types of
information?

All types of users

If the answer is yes, this need is
fulfilled by W
SS.

Do you need a way of presenting
more information than just the e
-
mail addresses and phone
numbers for some or all of your
users?

Middle management,
team leaders, project
leaders

MOSS has the My Site feature,
which presents much more
information about
users than the
typical Employee List.

Do you need a way to display
MS Excel spreadsheets and
charts to users without requiring
them to have MS Excel?

Information
management, middle
management, team
leaders, project leaders

MOSS alone supports this with th
e
Excel Service.

Do your users need to display
Information
MOSS alone supports this with the
Open table as spreadsheet
Question

People to Ask

Comment

and fill out forms with a web
browser?

management, middle
management, team
leaders, project leaders

Forms Service.

Do you need to display and
update data in exte
rnal data
sources, such as SAP and Oracle
databases?

Information
management, middle
management, team
leaders, project leaders

MOSS alone supports this with the
Business Data Catalog (BDC)
feature.



Comparing SharePoint Server and Windows SharePoint
Services 3.0


MOSS Versions


While WSS is a free component, MOSS must be licensed separately. MOSS comes in several

different versions that target different deployment scenarios and have different licensing

requirements. Regardless of your scenario,
however, every organization using MOSS must

purchase the base MOSS 2007 server license. Along with the server license, you must also

purchase the appropriate client access licenses (CAL) to meet your needs.

For general use,
MOSS comes in a Standard and an
Enterprise edition. The Standard

edition gives you access
to the basic set of MOSS functionality, including content management,

workflow, and
collaboration. The Enterprise edition includes the functionality of the

Standard edition but
adds the BDC, Excel S
ervices, Office Forms Server, and more. Additional

versions allow you
to use MOSS solely for deploying Internet sites or separate features

such as the Office
Forms Server. In this book, I always assume that you have the MOSS 2007

Enterprise
edition availab
le.



Storage Capacity Planning


Storage capacity is a major planning point in any SharePoint deployment. Since all of the
pages,

lists, and documents are stored in SQL Server 2005, you must adequately size the
disk space to

support not only your initial n
eeds, but also to allow for growth over a period
of years. Start by

considering any existing documents that you want to migrate to
SharePoint. For these documents,

plan on having disk storage equal to one and a half times
the total size of the documents

to

be migrated. Additionally, you’ll need another 30% for
indexing the new content, and an

additional 60% for the search server. Finally, you’ll need
to consider growth, including the number

of versions that will be created. This is calculated
by assuming an

average document size

multiplied by an average number of versions. Table
2
-
1 details the planning formulas and

shows an example based on migrating 100GB of
existing documents with an average file size

of 1MB and planning for five years of growth.

Table 2
-
1.
Calculating Storage Requirements








Limitations


SharePoint has several limitations that you should keep in mind as you are planning your

deployment. Generally, the limits presented here are not hard limits, but exceeding them
can

cause performance

degradation. The limits are typically quite large and you’re unlikely
to run

into most of them, but it is possible. For example, you could easily exceed the
recommended

2,000 documents per folder unless you plan your document migration
accordingly.

When e
xamining the SharePoint limits, you’ll see references to several terms
that are

specific to SharePoint. In SharePoint, a web application refers to an Internet
Information

Server site that has been extended with SharePoint. Each web application may
contain
one

or more site collection. A site collection is typically a complete intranet,
extranet, or Internet

implementation. A site collection is made up of one or more sites. A
site is a dedicated section

of the site collection for team collaboration, business
intelligence
reporting, records

management, or the like. Sites contain lists and documents and may
have subsites underneath

them. Table 2
-
2 lists the SharePoint limits associated with these
terms.





Deployment Architectures


SharePoint may be deployed
in several different architectural configurations from a single

server utilizing SQL Server Express to a multiserver farm with an active
-
passive SQL
cluster.

The exact deployment architecture will be based on the number of users, storage
requirements,

and
availability requirements. Small team
-
based installations may be able to
use a

single server while large Internet presence sites will need a farm. Table 2
-
3 lists the
various

configurations and their specifications based on an average corporate user with a
n
average

amount of activity.


Table 2
-
3.
Deployment Architectures


Single
-
Server Configuration

A single
-
server deployment of WSS or MOSS can be created on a server that has a 2.8GHz

processor with 2GB of RAM and a 100GB hard drive. In this scenario, you
would utilize SQL

Server Express to create the required databases directly on the server without the need for

a separate installation of SQL Server 2005. This deployment is remarkably easy to set up by

simply running the WSS or MOSS installation and follow
ing the steps. However, this is the

least reliable configuration because everything obviously relies on the availability of a
single

machine.


Small Farm Configuration

System performance can be improved by moving the database off of the single server and
onto

its own server. This requires a separate installation of SQL Server, but improves
performance

significantly because all database operations can happen on the separate
server. However, this

configuration is really no more reliable than the single
-
serve
r
configuration because it is still

vulnerable to a single failure.


Medium Farm Configuration

True enterprise reliability begins with the medium farm configuration. In this
configuration,

the web front
-
end servers, application server, and database servers

are
separate. A typical

configuration would have two front
-
end web servers, a single
application server, and an activepassive

SQL Server cluster. Generally, these servers are
dual
-
processor machines with at least

4GB of RAM and upward of 200GB hard drives
.
Performance and reliability in this configuration

are greatly enhanced by separating the
required functions across machines.



Large Farm Configuration

The large farmconfiguration is a scaled
-
out version of the medium farm configuration. In
the

large far
m, upward of four front
-
end web servers are used to handle hundreds of
thousands ofusers. An application server and active
-
passive SQL Server cluster are
employed in the same

way as the medium farm configuration. This configuration is typical
for a large I
nternet presence

site.














http://technet.microsoft.com/en
-
us/library/cc262787.aspx












Default Web Parts

WSS 3.0

MOSS Enterprise

Content Editor Web Part

Yes

Yes

Form Web Part

Yes

Yes

Image Web Part

Yes

Yes

Page Viewer Web
Part

Yes

Yes

Relevant Documents

Yes

Yes

Site Users

Yes

Yes

User Tasks

Yes

Yes

XML Web Part

Yes

Yes

Contact Details

No

Yes

Business Data Actions

No

Yes

Business Data Item

No

Yes

Business Data Item Builder

No

Yes

Business Data List

No

Yes

Business

Data Related List

No

Yes

Excel Web Access

No

Yes

IView Web Part

No

Yes

WSRP Consumer Web Part

No

Yes

Default Web Parts

WSS 3.0

MOSS Enterprise

Site Aggregator

No

Yes

Key Performance Indicators

No

Yes

KPI Details

No

Yes

Content Query Web Parts

No

Yes

I need to…

No

Yes

RSS Viewer

No

Yes

Summary Link Web Part

No

Yes

Table of Contents Web Part

No

Yes

This Week in Pictures

No

Yes

Business Data Catalog Filter

No

Yes

Choice Filter

No

Yes

Current User Filter

No

Yes

Date Filter

No

Yes

Filter Actions

No

Yes

Page Field Filter

No

Yes

Query

String (URL) Filter

No

Yes

SharePoint List Filter

No

Yes

SQL Server 2005 Analysis Services Filter

No

Yes

Text Filter

No

Yes

My Calendar

No

Yes

My Contacts

No

Yes

My Inbox

No

Yes

My Mail Folder

No

Yes

My Tasks

No

Yes

Advanced Search Box

No

Yes

People Search Box

No

Yes

People Search Core Results

No

Yes

Search Action Links

No

Yes

Search Best Bets

No

Yes

Search Box

No

Yes

Search Core Results

No

Yes

Search High Confidence Results

No

Yes

Search Paging

No

Yes

Search Statistics

No

Yes

Default Web Parts

WSS 3.0

MOSS Enterprise

Search
Summary

No

Yes

Categories

No

Yes

Sites in Categories

No

Yes

Top Sites

No

Yes


SharePoint's Folder Tree

SharePoint keeps a number of files in these folders, most commonly ASP.NET files (
.aspx
) and
XML files (
.xml
). These files describe exactly how a given web page will look, including its
icons, links, and lists. For example, if you wanted to move the logo on the Home page to the far
right instead of its current left position, you would modify the
.aspx

file for t
hat particular page.
Most of these files can be modified with an editor, such as Notepad, but you should think twice
before changing them. Some of them can be replaced when you apply the next service pack, and
improper modifications may corrupt the portal
site. In the following table is an explanation of the
most interesting folders under the Template folder for the U.S. English version of SharePoint
(1033) and what is inside them. Note that for all site templates listed below the Template ID is
also listed
; this ID is used when SharePoint code and applications need to refer to a specific site
template.

Important


Note that customizing the Master Page used by this site is the preferred way of
customizing the logo, as described later in this chapter. The des
cription here is just
to help you understand how the files work in this folder structure.

Open table
as spreadsheet
ID

\
Template Folders

Comments

0

\
Global


The global template

1

\
Site Templates
\
STS


Team Site, Blank Site, Document Workspace

2

\
Site
Templates
\
MPS


Basic Meeting Workspace, Blank Meeting
Workspace, Decision Meeting Workspace,
Social Meeting Workspace, Multipage Meeting
Workspace

3

\
Site
Templates
\
CENTRALADMIN


SharePoint Central Administration

4

\
Site Templates
\
Wiki


Wiki site

7

\
Sit
e Templates
\
BDR


Document Center

9

\
Site Templates
\
Blog


Blog site

20

\
Site Templates
\
SPS


(Obsolete) The Home page of the SharePoint
Portal Server site, including its lists and
configuration settings.

Open table
as spreadsheet
ID

\
Template Folders

Comments

21

\
Site Templates
\
SPSPERS


My Site

22

\
Site
Templates
\
SPSMSITE


Personalization Site

30

\
Site Templates
\
SPSTOC


(OBSOLETE)
-

Contents area Template

31

\
Site Templates
\
SPSTOPIC


(OBSOLETE)
-

Topic area template

32

\
Site Templates
\
SPSNEWS


(OBSOLETE)
-

News area template

33

\
Site
Templates
\
SPSNHOME


(SubWebOnly)
-

News Home template

34

\
Site Templates
\
SPSSITES


Site Directory area template

36

\
Site Templates
\
SPSCOMMU


(OBSOLETE)
-

Community area template

38

\
Site
Templates
\
SPSREPORTCENTER


Report Center Site

39

\
Site
Templates
\
PUBLISHING


Publishing and Team Collaboration Site

40

\
Site Templates
\
OSRV


Shared Services Administration Site

50

\
Site Templates
\
SRCHCEN


Search Center

51

\
Site Templates
\
PROFILES


Profiles

53

\
Site
Templates
\
BLANKINTERNET


Publishing Site,

Press Releases Site

54

\
Site
Templates
\
SPSMSITEHOST


My Site Host

90

\
Site
Templates
\
SRCHCENTERLITE


Search Center Lite

14483

\
Site Templates
\
offile


Records Repository



\
ADMIN


Contains all
.aspx

files used by SharePoint
Central Administration. Avoid modifying these
pages.



\
IMAGES


Contains all icons and images used by
SharePoint for its portal site and team sites.
Create a sub
-

folder under Images if you want
to add your own pictures. Avoid
modifying
this folder.



\
LAYOUTS
\
1033


Contains all pages required for standard site
administration. Do not modify these files.



\
LAYOUTS
\
1033
\
STYLES


Contains Cascading Style Sheets (CSS) that
control how the portal area pages will look.



\
LAYOUTS
\
1
033
\
IMAGES


Contains the images used by MOSS and WSS
in the administration pages.



\
SQL


Contains SQL scripts that are used when
creating configuration and content databases.
Open table
as spreadsheet
ID

\
Template Folders

Comments

Do not change these files.



\
XML


Contains configuration files. The
DOCICON.XML

file is used when you need to map icons to new
document file types.


Content placeholder

Description

PlaceHolderBodyAreaClass

Additional body styles in the page header

PlaceHolderBodyLeftBorder

Border element for the main page body

PlaceHolderBodyRightMargin

Right margin of the main page body

PlaceHolderCalendarNavigator

Shows a date
-
picker for navigating in a calendar when a calendar is visible on the page

PlaceHolderFormDigest

The "form digest" security control

PlaceHolderGlo
balNavigation

The global navigation breadcrumb

PlaceHolderHorizontalNav

Top navigation menu for the page

PlaceHolderLeftActions

Bottom of the left navigation area

PlaceHolderLeftNavBar

Left navigation area

PlaceHolderLeftNavBarBorder

Border
element on the left navigation bar

PlaceHolderLeftNavBarDataSource

Data source for the left navigation menu

PlaceHolderLeftNavBarTop

Top of the left navigation area

PlaceHolderMain

Main content of the page

PlaceHolderMiniConsole

A place to show
page
-
level commands, for example, WIKI commands such as Edit Page, History, and Incoming Links

PlaceHolderNavSpacer

The width of the left navigation area

PlaceHolderPageDescription

Description of the page contents

PlaceHolderPageImage

Page icon in th
e upper
-
left area of the page

PlaceHolderSearchArea

Search box area

PlaceHolderSiteName

Site name

PlaceHolderTitleAreaClass

Additional styles in the page header

PlaceHolderTitleAreaSeparator

Shows shadows for the title area

PlaceHolderTitleBreadcrumb

Main content breadcrumb area

PlaceHolderPageTitleInTitleArea

Page title shown immediately below the breadcrumbs

PlaceHolderTitleLeftBorder

Left border of the title area

PlaceHolderTitleRightMargin

Right margin of the title

area

PlaceHolderTopNavBar

Top navigation area

PlaceHolderUtilityContent

Extra content at the bottom of the page

SPNavigation

Empty by default in Windows SharePoint Services 3.0. Can be used for additional page editing controls.

WSSDesignConsole

The page editing controls when the page is in Edit Page mode (in the browser, click Site Actions, and then click Edit Page)



Creating a New Web Application and Site Collection

Once WSS is properly configured, you can finally create your first site. In th
is section, you

will create a site collection based on the team site template. Follow these steps to create

your first site:

1.
On the SharePoint Central Administration page, click the Application Management

tab.

2.
On the Application Management page, clic
k the link titled Create or Extend Web

Application.

CHAPTER 2
n
SHAREPOINT OVERVIEW, PLANNING, AND INSTALLATION
53

3.
On the Create or Extend Web Application page, click the link titled Create a New Web

Application.

4.
On the Create a New Web Application
page, select the option Use an Existing IIS

Web Site.

5.
Choose Default Web Site in the drop
-
down list.

6.
Under the Authentication Provider, choose either Negotiate (Kerberos) or NTLM,

depending upon the choice you made earlier.

7.
In the Application Pool

section, select Create a New Application Pool.

8.
Enter
WSS_Pool
as the pool name.

9.
Select the Configurable option for the application pool security account.

10.
In the User Name field, enter
DOMAIN
\
SPContentPool
.

11.
In the Password field, enter the ac
count password.

12.
In the Reset Internet Information Services section, select the option to Restart IIS

Automatically.

13.
In the Search Server section, select VSWSS from the drop
-
down list.

14.
Click the OK button.

15.
On the Application Created page, cl
ick the link titled Create Site Collection.

16.
On the Create Site Collection page, enter
Home Site
in the Title field.

17.
Use the drop
-
down list in the Web Site Address section and verify that just the single

forward slash is selected. This will create t
he site at the root for the server.

18.
Under the Primary Site Collection Administrator section, enter
DOMAIN
\
Administrator

in the User Name field.

19.
Click the OK button to create the new site collection.

20.
Once the Site Collection is created, return
to the Application Management tab.

21.
Click the link titled Policy for Web Application under the Application Security section.

22.
On the Policy for Web Application page, click the Add Users button.

23.
On the Add Users page, click the Next button.

24.
Un
der the Choose Users section, enter any accounts that should have administrative

control over the Site Collection. Be sure to include the DOMAIN
\
Administrator and

VSWSS
\
Administrator accounts.

25.
In the Choose Permissions section, check the box labeled
Full Control.

26.
Click the Finish button. You should now have full access to the new Site Collection.



Starting the Search Service

The WSS Search Service is not running initially. In order to use search functions, you must

configure the service with an
appropriate account for searching and one for crawling. In
this

section, you will use the accounts you created earlier to configure the Search Service.

Follow these steps to configure the Search Service:

1.
On the SharePoint Central Administration page, cl
ick the Operations tab.

2.
In the Topology and Services section, click the link titled Services on Server.

3.
On the Services on Server page, click the Start link next to the Windows SharePoint

Services Search.

4.
In the Service Account section, enter
DOMA
IN
\
SPSearchAcct
in the User Name field.

5.
Enter the account password in the Password field.

6.
In the Content Access Account section, enter
DOMAIN
\
SPCrawlAcct
in the User Name

field.

7.
Enter the account password in the Password field.

8.
Click the Start
button.

Configuring Outgoing E
-
Mail

WSS uses an SMTP server to send alerts and messages to users. In this section, you will
enter

the e
-
mail settings for WSS. Follow these steps to configure the e
-
mail settings:

1.
On the SharePoint Central Administration
page, click the Operations tab.

2.
In the Topology and Services section, click the link titled Outgoing E
-
mail Settings.

3.
On the Outgoing E
-
Mail Settings page, enter
VSPDC
in the Outbound SMTP Server

field.

4.
Enter
administrator@domain.local
in the From

Address field.

5.
Enter
administrator@domain.local
in the Reply To field.

6.
Click the OK button.


Adding MOSS to the List of Trusted Sites

You may find that when you access SharePoint sites that you are prompted for a username

and password. You can elimi
nate this behavior by adding the VSMOSS server to the list of

trusted sites or the Local Intranet zone. In either case, you should also ensure that the
browser

settings are configured to automatically log the user on to the site.

CHAPTER 2
n
SHAREPOINT OVERVIEW, PLANNING, AND INSTALLATION
57

Follow these steps to add VSMOSS to the list of trusted sites:

1.
In the Internet Explorer, select Tools
ä
Internet Options.

2.
On the Security tab, click the Trusted Sites icon.

3.
Click the Sites button.

4.
Clear the box titled Require Server Verification (https) for All Sites in This Zone.

5.
Verify that
http://vsmoss
is in the Websites list. If not, add it.

6.
Click the Close button.

7.
Click the Custom Level button.

8.
In the Settings list, under User
Authentication, select Automatic Logon with Current

Username and Password.

9.
Click the OK button.

10.
Click the OK button to close the options dialog.

Configuring Outgoing E
-
Mail

Once the Shared Services are set up, you may return to the Central
Administration pages to

continue configuring additional components. In this exercise, you will configure an SMTP

server for MOSS. MOSS uses an SMTP server to send alerts and messages to users. Follow

these steps to configure the e
-
mail settings:

1.
Click
the Operations tab in SharePoint 3.0 Central Administration.

2.
Click the link titled Outgoing E
-
Mail Settings under the Topology and Services section.

3.
On the Outgoing E
-
Mail Settings page, enter
VSPDC
in the Outbound SMTP Server

field.

4.
Enter
adminis
trator@domain.local
in the From Address field.

5.
Enter
administrator@domain.local
in the Reply To field.

6.
Click the OK button.


Configuring Anonymous Access

Before you can configure a site to allow anonymous access, the associated web application

must f
irst have anonymous access enabled through Central Administration. If the web
application

is set through Central Administration to allow anonymous access, you can control what

parts of your site are visible to anonymous users. If the central administrator
has not
enabled

anonymous access for the web application, the functionality will not be visible.

Follow these steps to enable anonymous access for the web application:

1.
Open the Central Administration site by selecting Start
ä
Administrative Tools
ä

Shar
ePoint 3.0 Central Administration.

2.
In the Central Administration site, click the Application Management tab.

3.
Under the Application Security section, click the link titled Authentication Providers.

4.
On the Authentication Providers page, make sure th
at the correct web application is

selected. If not, drop the menu and select Change Web Application.

5.
On the Authentication Providers page, click the Default Zone link.

6.
On the Edit Authentication page, check the box labeled Enable Anonymous Access.

7.

Click the Save button.


Once the web application is configured for anonymous access, you can return to the

Permissions page. From the Permissions page, you can select Settings
ä
Anonymous Access

to open the Anonymous Access Settings page. On this page,
you may select to expose the

entire site, all lists and libraries, or nothing at all. Additionally, you can control the visibility
of

an individual list or library through its permission settings. This combination of site
-
level
and

list
-
level configuration

gives you a good deal of control over what parts of the site can be

accessed anonymously.



Object Model

hierarchy




Object Model

Physical hierarchy











Because Windows SharePoint Services V3.0 uses .NET Framework 2.0, WSS web parts can also
use the ASP.NET 2.0 web parts control set. When you are creating web parts for WSS V3.0, you
have the option of inheriting from the System.Web.UI.WebControls.WebParts.
WebPart
(ASP.NET 2.0 web part) or Windows SharePoint Services web part class. The Windows
SharePoint Services web part class was part of Windows SharePoint Services V2.0, before the
ASP.NET web parts were introduced, where they supported web part developme
nt.

Developers can now easily apply their .NET development experience and use Visual Studio 2005
to create new ASP.NET 2.0 web parts for Windows SharePoint Services V3.0 sites.

ASP.NET 2.0 web parts will run on both ASP.NET web pages and WSS site pages. You can
build a web part for WSS V3.0 site that drives from:



System.Web.UI.WebControls.WebParts.WebPart



Microsoft.SharePoint.WebPartPages.WebPart

When to Use Windows SharePoint Services Web Part Class

There are a few cases when you will have to use Windows SharePoint Services web parts instead
of ASP.NET web parts. Windows SharePoint Services web parts support additional Windows
SharePoint Services

features that are not supported through an ASP.NET web part. Following is
a list of features that are only supported through Windows SharePoint Services web parts:



Connections between web parts that are outside of a Web Part zone



Cross page connections



A

data caching infrastructure that allows caching to the content database



Client
-
side connections (Web Part Page Services Component)

Another reason for using Windows SharePoint Services web parts is when you want to upgrade
your Windows SharePoint Services
V2.0 web parts to the V3.0 environment. The new version of
the web part should be driven from the SharePoint web part class. SharePoint web parts can only
be hosted in Windows SharePoint Services site pages.






Web part page

Web Part Zone

Web part Ma
nager

Provider

Consumer