Chapter 3 – Architecture and Capacity Planning

Wrox SP 2010 Admin – Page 59

Sharepoint versions:

Sharepoint Foundation (WSS 3.0)
Sharepoint 2010 Standard
Sharepoint Enterprise – with new service applications, business intelligence, line of business integration, reporting and office client access such as Visio.

All provided via CAL (client Access License). Only need to run one set up program, which puts all libraries in the server. Based on the licnese key entered, difference versions are made available. Required to have an appropriate CAL for each user accessing SP 2010.

Sharepoint server 2010 for Internet Site Standard (FIS). Offer smaller sites the capability to deploy on server. Will not have Enterprise Features enabled.

FIS – allow unlimited non-empooyees access to your sharepoint server.

Search server 2010 –

Search Server 2010 Express (SSX) – Sharepoint Fundation + can add content sources such as file shares, other sharepoint sites, web sites, and exchange public folders. Also with search center and other web parts. Only shortcoming – cannot be configured to be high availability. Only one server in the farm – not scalable.

Fast Search Server 2010 – an addition to the SP platform. Visual search, best bets, extreme scale (a billion), multiple language…. Two differenct license:
(1) Fast Seach server 2010 for Sharepoint – used along the CAL
(2) Fast Search server 2010 for Internet Sites – FIS for public web sites.

Sharepoint Online – (in the cloud)

Two models:

(1) Shared – a slice of the farm; server-deployed code and customization not allowed.
(2) Dedicated – run your own farm, allowed to make approved customization to the server. (changes packaged and validated by MS)

Other servers –

Sharepoint stored 99% of the content and configuration in a database.

Windows server –

Windows 2008 server supported (1) standard, (2) Enterprise and (3) Datacenter

Windows “Server Core” and “Web Edition” will not support Sharepoint 2010.

Required Additional Software –

The SP 2010 server needs to be included as a member of an AD domain. Sharepoint doesn’t support local accounts for any types of farm deployment. Never use a local account for a farm installation!!! With a local SP 2010 development server you can do this.

“Sharepoint Products and Technology Preparation Tool” will install and configure all the prerequsite package.

SQL Server –

The most common performance bottlenext for SP 2010 – SQL server!

Email servers –

The SMTP need to allow ananymous email relay from SP 2010! SP 2010 cannot be configured to provide authentication when sending emails. Need to ask email admin to add SP 2010 servers’ IP address to the list so they can send emails annonymously. If this is not possible, you need to install SMTP service in one of the Sharepoitn servers. Also, enable port 25.

Incoming Email –

SP 2010 can accept incoming emails and post the contents or attachment to a ist or library. Exchange server is NOT needed.

Steps:

1. Configure SP 2010 to run SMTP service. Set up to accept emails for the domains. E.g., …@sharepoint.mycompany.com
2. Configure corporate email server to route all ….@sharepoint.mycompany.com emails to the SP 2010 server.
3. Go to Central Admin, enable incoming email. Tell Sp 2010 to look for emails in the @sharepoint.mycompany.com domain.
4. Now someone with manage list permission can go into the list and associate an email address with the list, such as doclib1@sharepoint.mycomapny.com
5. The email address needs to be configured as a valid contact on the email server.

Text Messages (SMS) service –

set up in Central Admin, can be at farm or web application level. Need to provide the URL or a SMS sending service.

Query server –

the server responsible for responding to user search requests.

Index server –

also called Crawl server. This version is stateless, which means it doesn’t store anything locally.

SQL servers –

*.mdf and *.ldf should be placed on different disks; log files should be optomized for writing; when optimizing files, order : (1) tempdb, (2) search database and (3) content database.

Finally, when it comes to SQL Server, SharePoint doesn’t really care how you set it up. As long as SQL Server is running a supported version and can serve databases back to SharePoint, it doesn’t matter whether SQL Server is dedicated to SharePoint or is shared with other applications in the company. Nor does SharePoint care whether SQL Server is clustered or doing database mirroring or even transparent encryption. SharePoint will simply call to a SQL Server instance for a database, and if it gets data back it is happy.

Mixing and Matching servers –

One server – typeical environment for development/evaluation (Sharepoint + SQL on one machine)
Two servers – Sharepoint one server + SQL server on another
Three Servers – a network load balancing (NLB – configured for persistent sessions) device + two Sharepoint servers + SQL server

Server groups – the logocal concept of grouping similar SP service applications together on the same physical hardware.

Other Hardware notes –

Servers in the farm should be connected through gigabit connections. All servers n the farm should have identical driver letters.

Virtualization –

Virtualization is easy if there is no disk requirement.

Vocabulary:


Farm – A farms refers to all servers that are using the same configuration database.

Preventing rogue Sharepoint installation/deployment (unauthorized installation) –
HKLM\Software\policies\microsoft\SharePoint\14.0\blocksharepointinstall = 1

Registering Sharepoint in AD –

HTTP Throttling –

WFE: Web Front End

Microsoft has introduced HTTP Throttling to protect a server during peak load. By default, this feature monitors (1) the available memory in megabytes and (2) the ASP.NET requests in queue. As it monitors these counters, it generates a health score for the server on a scale from 0 to 9, with 0 being the best. The monitor checks every fi ve seconds by default. If the score is 9 for three consecutive tests, then the server will enter a throttled state. In this throttled state, SharePoint will return a 503 server busy message to all GET requests, including the crawler if you happen to be indexing. In addition, all timer jobs will be paused, which enables the server to concentrate on fi nishing existing requests and hopefully makes room for anyone doing a PUT request, like that user who just spent an hour fi lling out a form. The monitoring continues every fi ve seconds, and throttling is disabled after one occurrence of a score below 9.

This feature can be configured in Central Admin, and also with Powershell:

Get-SPWebApplicationHttpThrottlingMonitor
Set-SPWebApplicationHttpThrottlingMonitor

Large List Throttling –

SP 2010 supports list with up to 50 million items.

In Central Admin à Application Management à Manage Web App à (select Web Application) à )General settings à Resource Throttling

 

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: