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


Published on

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

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

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

  1. 1. SharePoint 2007 (Visión técnica) http://www.mossca.org/openxml/default.aspx mau@mvps.org Abril 2009
  2. 2. SharePoint Platform Services A collection of one or more servers, each performing one or more functions: Web Server Web front end No service or data, just serves out HTML Scale out - Network Load Balanced Application Server Hosts ‘services’ Scale out depends on services Index server is an exception Database Server Web Application Database Configuration Servers Servers Servers Content SharePoint Farm
  3. 3. SharePoint Platform Services Web Front End Shared Services Provider Index Server Query/Search Excel Calculation Server Forms Server Database Server Various topologies from entry-level single machine to business critical Web Application Database high availability scale-out architecture Servers Servers Servers Internet / Extranet / Intranet SharePoint Farm
  4. 4. Web Application Database Servers Servers Servers SharePoint Farm Web Web Web Application Application Application Config Database Shared Service Provider 1 Content Shared Databases Service Provider 2
  5. 5. SharePoint Platform Services Site Templates define Lists, Document Libraries, Web Parts, Content Types, Metadata, Workflow, etc Site is an instance of a Site Template definition Site Collection is a group of Sites with common administration Sites / subsites are arranged in a hierarchy – typically used for navigation & security Compliant with ASP.Net 2.0 Navigation Provider Model Over 40 application templates and role based portals templates at http://microsoft.com/sharepointapps
  6. 6. SharePoint Platform Services Authentication – identification Windows authentication ASP.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 system Audiences - content targeting
  7. 7. SharePoint Platform Services Site Customisation Editing assets with the site’s content database Code Development Repeatable – reuse across multiple sites Features - Develop / Deploy / Activate Package features as .WSP solution packages
  8. 8. SharePoint Platform Services Content Code Traditional content Web parts Documents Workflows Lists Event handlers Forms data Feature receivers Web Content Digital assets Document converters Artifacts CSS Stylesheets Master Pages Page Layouts
  9. 9. SharePoint Platform Services Very similar to traditional development Use Visual Studio 2005/8 with VSeWSS Process 1. Develop on an individual environment (normally Virtual PC 2007) 2. Check-in to Team Foundation Server 3. Package into features/solutions 4. Periodic deployment to shared SharePoint Server integration environment 5. Deployment to production
  10. 10. SharePoint Platform Services Use SharePoint Designer 2007 Master pages, page layouts Write No-code workflows Modify CSS files Edit .aspx pages Add script to pages Customise look & feel of Web Parts Write XSLT to customise data rendering Artifacts are not compiled into assemblies Treated as content, not code Built-in source control via SharePoint document libraries Check-in/out; Versioning
  11. 11. Development staging server Web Application Database Servers Servers Servers SharePoint Farm
  12. 12. SharePoint Platform Services Packaged sets of customizations Once installed, administrators can activate or deactivated Can be scoped: Farm Web Application Site Collection Web Supports dependencies
  13. 13. SharePoint Platform Services To get your features and associated files deployed … You could: Manually copy files onto the file system Add web.config entries for assemblies Do IIS reset Repeat, on EVERY web front end!  Alternatively – use SharePoint Solutions
  14. 14. SharePoint Platform Services SharePoint Solution Packages simplifies the distribution of solutions Web Parts Site Definitions Features SharePoint Solution Custom Workflows Package Cab Application and Site .WSP Pages Feature Manifests … Template Files Assemblies Single file .WSP (.CAB file) Solutions can be: added to the Solution Store of the server farm install WSS deployed to site collections delete Config DB upgraded with new versions retracted from site collections deploy removed from the Solution Store retract Web Application Database Servers Servers Servers Could re deployed using MSI installer Solution Installer on Codeplex SharePoint Farm
  15. 15. SharePoint Platform Services Page components for extending the UI Can be inter-connected Can be positioned / dragged & dropped into Web Part Zones Serializes/stores/retrieves personalization data History: Windows SharePoint Services 2.0 (SPS 2003) Designed with its own Web Part infrastructure ASP.NET 2.0 Designed with newer universal Web Part infrastructure ASP.NET 2.0 does not support WSS v2 Web Parts Windows SharePoint Services 3.0 (MOSS 2007) Supports WSS V2 style Web Parts Supports ASP.NET 2.0 style Web Parts (preferred)
  16. 16. SharePoint Platform Services Create a new class library DLL project Create a class that inherits from ASP.NET Web Part class Override methods as required (e.g. RenderContents) Deploy Web Part DLL Compile DLL into bin directory or GAC Configure DLL in web.config file SafeControl list Web Parts loaded from bin subject to security restrictions controlled by Code Access Security settings Import Web Part into a WSS site collection Add Web Part class to Web Part Gallery Add Web Part to zone on a Web Part Page Use the Visual Studio Extensions for SharePoint or STSDEV (on codeplex) Automates the whole process to make it simple / quick to test
  17. 17. SharePoint Platform Services Silverlight Blueprint for SharePoint http://www.ssblueprints.net/sharepoint
  18. 18. SharePoint Platform Services Custom Site Pages For a specific site collection Custom Application Pages Across all site collections Located in the _layouts directory Best practise to create a subfolder within this directory Deploy as “SharePoint Solutions”
  19. 19. SharePoint Platform Services WSS 3.0 MOSS 2007 Microsoft.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
  20. 20. SharePoint Platform Master Page Services • Publishing feature must be ‘Activated’ • ASP.NET 2.0 Master Pages Field Controls 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 Page Layout mode & Design Time FileName PageLayout Title Body Image Welcome.aspx PageLayout.aspx Welcome To News Lorem ipsum dolor sit ... /Images/Chair.jpg ‘Pages’ Doc Lib 2.0 CMS Page Rendering
  21. 21. SharePoint Platform Services Standard ASP.NET .master .aspx Master Page ‘placeholder’ controls define where the Page Layout content is position Delegate control – invokes a control defined by a feature Can update master page by feature update
  22. 22. SharePoint Platform Services Standard ASP.NET Placeholders define where the Page Layout content is position Delegate control – invokes a control defined by a feature Can update master page by feature update
  23. 23. SharePoint Platform Services Use SharePoint Designer to define master pages and page layouts Treated as content - not code SharePoint checkout/in ; approval proceses Stored in the ‘masterpage catalog’ document library Page Layout is bound to a Content Type Designer UI allows Field Controls for the Content Type to be dragged into the page
  24. 24. SharePoint Platform Services Field Controls render the content items Three lives : View Mode, Edit mode & Design Time Standard Controls include: Rich Text Editor, Image Controls, Dates, etc Can create you own custom Field Controls Media Control example in the SDK
  25. 25. En principio no Siempre es conveniente una taxonomía inicial El contenido que queda fuera de la taxonomía que quede fuera de Sharepoint Sobrevivirán aún Las carpetas compartidas Los Zip, Rar, etc. Los ISO Los backups
  26. 26. Empiece por su SLA Considere los Restore Cuando el SLA es tiered considere mapear Site Collections a DBs Considere la performance a nivel de las Site Collections Sí, siempre se trata de que las Site Collections funcionen adecuadamente, eso condiciona la creación de bases de datos
  27. 27. Un server no es una granja Training del Admin Policies Delegación de usuarios Farm SSP Site Collection Site List …
  28. 28. Use el Sharepoint Designer en flujos sólo para diseñar, finalmente pase a Visual Studio y genere Features
  29. 29. Menos es mejor Considere el uso de Managed Paths Defina políticas Buenos motivos para una Web Application Seguridad Aislamiento
  30. 30. SÍ A nivel de la Site Collection Contienen Workflows Templates Auditing Expiration Site columns (metadata)
  31. 31. NO
  32. 32. Si es posible 1 ¿Records Management?  2
  33. 33. Listas de discusión Flujos Calendarios Tareas Mails a listas, a grupos
  34. 34. El Backup de SQL es imprescindible Command Line Stsadm.exe –o backup –directory A nivel de granja Stsadm.exe –o backup –url Site collection Stsadm.exe –o export / import Site