sharepoint best practices

21
www.decatec.it Best Practices Michele Adamo [email protected] http://www.decatec.it 1

Upload: decatec

Post on 28-Nov-2014

2.339 views

Category:

Technology


1 download

DESCRIPTION

Sharepoint Best Practices, evento sharepoint, , corso formazione, corsi, sharepoint training

TRANSCRIPT

Page 1: Sharepoint Best Practices

Best Practices

Michele Adamo

[email protected]://www.decatec.it

1

Page 2: Sharepoint Best Practices

www.decatec.it

Sommario

1. Estimate performance e capacity requirements2. Information Architecture3. Manage Security4. Document Management5. SharePoint Branding6. Solution Development

Page 3: Sharepoint Best Practices

www.decatec.it

Estimate performance e capacity requirements

The primary factors that affect a SharePoint Server Farm ares:

Server and Network hardware Software Configuration Customization User Load Traffic Profiles

Page 4: Sharepoint Best Practices

www.decatec.it

Estimate performance e capacity requirements

Plan for high availability Inserting at least two WFE server is sufficent to provide high

availability for thousand users in an out-of-box configuration Plan for operational excellence

64-bit hardware (for all server roles) Allocate at least 2 gigabytes (GB) of RAM per processor for front-end

Web servers and application servers. Allocate at least 4 GB of RAM per processor for database servers.

Consider Guideline for Acceptable Performance 50.000 Site Collection per content db 250.000 sub webs for Site Collection 5.000.000 Items per List 2000 Items per List View

Page 5: Sharepoint Best Practices

www.decatec.it

Information ArchitectureSite Collection vs SubSite

Home

Amministrazione Direzione

Home

Divisioni

Amministrazione Direzione

Page 6: Sharepoint Best Practices

www.decatec.it

Information ArchitectureSite Collection vs SubSite

Scalability MS recommend to limit content database size to 100GB

Backup & Restore Full fidelity backups are only possible at the site collection level If a sub-site needs to be restored then the entire site collection must be restored 3rd party solutions offer full fidelity recovery at more granular levels

Security Site Collections allow security groups and permissions to be isolated from other site collections

Search Search Scopes are defined at the site collection level Settings must be manually (or programmatically) synchronized across site collections

Page 7: Sharepoint Best Practices

www.decatec.it

Information ArchitectureSite Collection vs SubSite

Audting Policies can be created at the site collection scope No built-in mechanism for synchronizing policies across site collections

Recycle Bin Each site collection has a first and second stage recycle bin First stage counts towards the quota

Second stage does not count towards the quota. Be aware of the defaults – 30 days in the first stage and 50% of the site quota for the second stage, if there’s no quota then the second stage will grow infinitely.

Page 8: Sharepoint Best Practices

www.decatec.it

Information ArchitectureSite Collection disadvantages

Each site collection, insists to have it's own Menuyou must implement a consistent navigation between multiple site collections through CustomSiteMapProvider or XML SiteMap.

Content Type & Site Column are Site Collection levelUse must use Features to deploy Content to multiple Site Collections

Management is more complex with site collections No OOTB way to synchronize settings across site collections!

Page 9: Sharepoint Best Practices

www.decatec.it

Cross-Site Configurator

Solution Accelerator from MSFT http://www.codeplex.com/SPConfigurator

The tool automates the process of deploying site settings in all or selected sites in a server farm:

Applying Master Pages across a SharePoint server farm. Setting up Web Titles for all or selected site collections across the farm. Applying audit control settings to all or selected sites. Adding advanced settings such as “Allow content type management” to

all types of lists. Adding a new Expiration Policy at the site collection level. Adding a new Expiration Policy to content types, lists, and documents.

Page 10: Sharepoint Best Practices

www.decatec.it

Control Site Collection growths

Limit Max Versions Use versioning only if required Use Quotas Monitor Second Stage Recycle Bin

Page 11: Sharepoint Best Practices

www.decatec.it

Manage Security

Add users and domain groups to the permission level/cross site group (site collection groups)

Allow site administrators to assign permission directly

Break Permission inheritance must be an Exception!

Third-party tools:AvePointBamboo User ManagerDeliverPointSushi

Page 12: Sharepoint Best Practices

www.decatec.it

Manage Security

Add users and domain groups to the permission level/cross site group (site collection groups)

Allow site administrators to assign permission directly

Break Permission inheritance must be an Exception!

Third-party tools:AvePointBamboo User ManagerDeliverPointSushi

Page 13: Sharepoint Best Practices

www.decatec.it

Manage Security

Audiences are not security objects, they can be used for targetting content.

Can I Deny user?There is no granular or deny at a site level but you can do a deny at a web application level with a webapplication policy.

Page 14: Sharepoint Best Practices

www.decatec.it

Manage Security

SharePoint Authentication Methods: Windows Authentication Anonymous access Form Based Authentication

Extend Web Application to allow more entry Point

Page 15: Sharepoint Best Practices

www.decatec.it

SharePoint Branding

What tools should I use?o Native in-Browser

Simple Branding (Themes, Navigation, Logo)

o MS SharePoint DesignerEnd-Users adequately trained can obtain more page customization Define Content Types & Metadata

o Visual StudioMore complex customizations

There is no single best way, you should consider an appropriate mix

Page 16: Sharepoint Best Practices

www.decatec.it

SharePoint Branding

o Use Master Pages to define Look & Feel of Site

o Branding features in publishing infrastructure:o Master pages inheritance throughout site collectiono Alternate CSS URL to override Default SharePoint Core.csso Using Page Layouts, customization will be placed in a associated content

Type in the pages document library

o Do not change Master Pages & Application pages stored in Templates/Layouts Folder (Upload.aspx, Application.master)

o Use Site Definitions to globally deploying customizationso Site definition are stored in file system

Page 17: Sharepoint Best Practices

www.decatec.it

Solution Development

o Use SharePoint Solution Packageo Visual Studio 2005/2008 Extensionso STSDEVo WSPBuilder

o Take advantage of native SharePoint CapabilitiesSharePoint includes a suite of Web Parts

o Many problem solved with:o Custom Custom Content Types and custom associated list

form(Disp/edit/New)o Custom Action

o Do not use custom field typeNo support for advanced list functionality(Datasheet)

Page 18: Sharepoint Best Practices

www.decatec.it

Solution Development

o Do not insert/enable asp.net code in Content Pages o Not supported

o Create ASP.NET Virtual subdirectories in Layout folder o Developer with ASP.NET Skills

o Be aware of use ASP.NET User Controls Wrapper(SmartPart)o Not included in SharePoint Standard Deployment

Page 19: Sharepoint Best Practices

www.decatec.it

Solution Development

o Memory management for SharePoint Objecto Dispose SPSite and SPWeb o Do not dispose Context object

o Use List Event Receiver for Data Validationo Only server side

o Use caching mechanismo ASP.NET Cache Object

o Implement Async Web Part for potentially slow data source(Web Service, Legacy Databases)

Page 20: Sharepoint Best Practices

www.decatec.it

WorkFlow Development

Page 21: Sharepoint Best Practices

www.decatec.it

Document Management

SharePoint do not replace File Server File servers are usually cheaper solution than SharePoint File server are prefered for large storage(Up to 2GB)

Define Content Types & Metadata Understanding data elements in your Organization For use the same content type across site collections, you need to

develop features content types. Approval Workflow

Use AD security groups to specify approvers