(28.04) MOSSCA Invita - Bienvenidos a la casa de Sharepoint - Visión técnica

SharePoint 2007(Visión técnica)

http://www.mossca.org/openxml/[email protected]

Abril 2009

http://www.mossca.org/openxml/default.aspx�

mailto:[email protected]�

A collection of one or more servers, each performing one or more functions:

Web Server Web front endNo service or data, just serves out HTMLScale out - Network Load Balanced

Application ServerHosts ‘services’Scale out depends on services

Index server is an exception

Database ServerConfigurationContent

SharePoint Farm

WebServers

ApplicationServers

DatabaseServers

SharePoint Platform Services

Web Front EndShared Services ProviderIndex ServerQuery/SearchExcel Calculation ServerForms ServerDatabase Server

Various topologies from entry-level single machine to business critical high availability scale-out architectureInternet / Extranet / Intranet

SharePoint Farm

WebServers

ApplicationServers

DatabaseServers


Web Application

ConfigDatabase

ContentDatabases

SharedService Provider 1

SharedService Provider 2

Web Application

Web Application

SharePoint Farm

WebServers

ApplicationServers

DatabaseServers

Site Templates define Lists, Document Libraries, Web Parts, Content Types, Metadata, Workflow, etcSite is an instance of a Site Template definitionSite Collection is a group of Sites with common administrationSites / subsites are arranged in a hierarchy – typically used for navigation & security

Compliant with ASP.Net 2.0 NavigationProvider Model

Over 40 application templates and role based portals templates at http://microsoft.com/sharepointapps


Authentication – identificationWindows authenticationASP.NET Membership • ASP.NET ships with SQL Server provider• MOSS ships with LDAP provider• Extensible via custom development

Authorisation - access controls / role based

Personalisation - user profile systemAudiences - content targeting


Site CustomisationEditing assets with the site’s content database

Code DevelopmentRepeatable – reuse across multiple sitesFeatures - Develop / Deploy / Activate Package features as .WSP solution packages


Content

Traditional contentDocumentsLists Forms dataWeb ContentDigital assets

ArtifactsCSS StylesheetsMaster PagesPage Layouts

Code

Web partsWorkflowsEvent handlersFeature receiversDocument converters


Very similar to traditional developmentUse Visual Studio 2005/8 with VSeWSSProcess

1. Develop on an individual environment (normally Virtual PC 2007)

2. Check-in to Team Foundation Server3. Package into features/solutions4. Periodic deployment to shared SharePoint

Server integration environment5. Deployment to production


Use SharePoint Designer 2007Master pages, page layoutsWrite No-code workflowsModify CSS filesEdit .aspx pagesAdd script to pagesCustomise look & feel of Web PartsWrite XSLT to customise data rendering

Artifacts are not compiled into assembliesTreated as content, not code Built-in source control via SharePoint document libraries

Check-in/out; Versioning


SharePoint Farm

WebServers

ApplicationServers

DatabaseServers

Development staging server

Packaged sets of customizationsOnce installed, administrators can activate or deactivatedCan be scoped:

FarmWeb ApplicationSite CollectionWeb

Supports dependencies


To get your features and associated files deployed …You could:

Manually copy files onto the file systemAdd web.config entries for assembliesDo IIS resetRepeat, on EVERY web front end!

Alternatively – use SharePoint Solutions


SharePoint Solution Packages simplifies the distribution of solutions

Web PartsSite DefinitionsFeaturesCustom WorkflowsApplication and Site Pages…

Single file .WSP (.CAB file)

Solutions can be: added to the Solution Store of the server farmdeployed to site collectionsupgraded with new versionsretracted from site collectionsremoved from the Solution Store

Could re deployed using MSI installerSolution Installer on Codeplex

deployretract

SharePoint Farm

WebServers

ApplicationServers

DatabaseServers

WSS Config

DB

installdelete

SharePoint Solution Package Cab

.WSPFeature Manifests

Template FilesAssemblies


Page components for extending the UICan be inter-connectedCan be positioned / dragged & dropped into Web Part ZonesSerializes/stores/retrieves personalization dataHistory:

Windows SharePoint Services 2.0 (SPS 2003)Designed with its own Web Part infrastructure

ASP.NET 2.0Designed with newer universal Web Part infrastructureASP.NET 2.0 does not support WSS v2 Web Parts

Windows SharePoint Services 3.0 (MOSS 2007) Supports WSS V2 style Web PartsSupports ASP.NET 2.0 style Web Parts (preferred)


Create a new class library DLL projectCreate a class that inherits from ASP.NET Web Part classOverride methods as required (e.g. RenderContents)

Deploy Web Part DLLCompile DLL into \bin directory or GACConfigure DLL in web.config file SafeControl listWeb Parts loaded from \bin subject to security restrictions

controlled by Code Access Security settings

Import Web Part into a WSS site collectionAdd Web Part class to Web Part GalleryAdd Web Part to zone on a Web Part Page

Use the Visual Studio Extensions for SharePointor STSDEV (on codeplex)

Automates the whole process to make it simple / quick to test


Silverlight Blueprint for SharePointhttp://www.ssblueprints.net/sharepoint


Custom Site PagesFor a specific site collection

Custom Application PagesAcross all site collectionsLocated in the _layouts directoryBest practise to create a subfolder within this directory

Deploy as “SharePoint Solutions”


WSS 3.0 MOSS 2007Microsoft.SharePoint.dll Microsoft.Office.Server.dll

Microsoft.Office.Server.Publishing.dll

Microsoft.Office.Server.Policy.dll

Microsoft.Office.Server.Search.dll

Microsoft.SharePoint.Portal.dll

Microsoft.Office.Workflow.Tasks.dll

Microsoft.SharePoint.Publishing.dll

Microsoft.SharePoint.Workflow.Actions.dll

• .NET Managed APIs• Web Services

• CAML = Collaborative Application Markup Language•Definition of the Sites, Lists and Views•Querying of SharePoint content

• Get the Software Development Kits•WSSv3 SDK•MOSS 2007 SDK


• Publishing feature must be ‘Activated’

• ASP.NET 2.0 Master Pages are used to control look and feel of the website

• Page Layout defines the remainder of the page• Provides consistency for similar

types of pages• Field Controls render the

content items• Three lives : View Mode, Edit

mode & Design Time

Master Page

Page Layout

‘Pages’ Doc Lib

FileName

Welcome.aspx

PageLayout

PageLayout.aspx

Title

Welcome To News

Body

Lorem ipsum dolor sit ...

Image

/Images/Chair.jpg

Field Controls

CMS Page Rendering

2.0


Standard ASP.NET.master.aspx

Master Page ‘placeholder’ controls define where the Page Layout content is positionDelegate control – invokes a control defined by a feature

Can update master page by feature update


Standard ASP.NETPlaceholders define where the Page Layout content is positionDelegate control – invokes a control defined by a feature

Can update master page by feature update


Use SharePoint Designer to define master pages and page layoutsTreated as content - not code

SharePoint checkout/in ; approval procesesStored in the ‘masterpage catalog’ document library

Page Layout is bound to a Content TypeDesigner UI allows Field Controls for the Content Type to be dragged into the page


Field Controls render the content itemsThree lives : View Mode, Edit mode & Design Time

Standard Controls include:Rich Text Editor, Image Controls, Dates, etc

Can create you own custom Field ControlsMedia Control example in the SDK


En principio noSiempre es conveniente una taxonomía inicial

El contenido que queda fuera de la taxonomía quequede fuera de Sharepoint

Sobrevivirán aúnLas carpetas compartidasLos Zip, Rar, etc.Los ISOLos backups

Empiece por su SLAConsidere los RestoreCuando el SLA es tiered considere mapear Site Collections a DBsConsidere la performance a nivel de las Site Collections

Sí, siempre se trata de que las Site Collections funcionenadecuadamente, eso condiciona la creación de bases de datos

Un server no es una granjaTraining del AdminPoliciesDelegación de usuarios

FarmSSPSite CollectionSiteList…

Use el Sharepoint Designer en flujos sólo paradiseñar, finalmente pase a Visual Studio y genereFeatures

Menos es mejorConsidere el uso de Managed PathsDefina políticasBuenos motivos para una Web Application

SeguridadAislamiento

SÍA nivel de la Site CollectionContienen

WorkflowsTemplatesAuditingExpirationSite columns (metadata)

Si es posible 1¿Records Management? 2

Listas de discusiónFlujosCalendariosTareasMails a listas, a grupos

El Backup de SQL es imprescindibleCommand Line

Stsadm.exe –o backup –directory A nivel de granjaStsadm.exe –o backup –url Site collectionStsadm.exe –o export / import Site

(28.04) MOSSCA Invita - Bienvenidos a la casa de Sharepoint - Visión técnica

Documents

Transcript of (28.04) MOSSCA Invita - Bienvenidos a la casa de Sharepoint - Visión técnica