WSS 3.0 Architecture and Enhancements

1. WSS 3.0 Architecture and Enhancements Ashvini Shahane Member – Synergetics Research Lab

2. Agenda • WSS 3.0 Architecture • Integration with ASP.NET 2.0 • Site branding and customizations • Platform storage enhancements • Site Columns • Content Types - Defining “Types” for data stored in lists and libraries • WSS 3.0 as a platform for building solutions

3. WSS 2.0 • Site provisioning engine • Platform – Windows 2K3 • Built using ASP.NET • Integrated more at the IIS level

4. WSS 3.0 • Site provisioning engine • Platform for building solutions addressing different domains • Built on top of ASP.NET 2.0 – tight integration

5. IIS 6.0 ASP.NET STSFLTR Managed path Non .aspx/.asmx WSS ISAPI Extension WSS 2.0 Architecture Managed Path .aspx/.asmx Request Safe Direct Config Db WSS ASP.NET Handler Content Db

6. IIS 6.0 ASP.NET WSS 3.0 Architecture Request WSS ASP.NET Http Module Config Db SPVirtualPathProvider WSS ASP.NET Handler Content Db

7. WSS 3.0 Databases • Scale to Web Farm Scenario • Config database – Configuration Data • Content database – Site content and customization data

8. WSS Key Terms • Web Farm • Installation of one or more front-end web servers and back end servers • One Config Db per Web Farm • Web Application (Virtual Server) • IIS Website extended for WSS content hosting • Capable of hosting 10,000s Site Collections • Content Db associated • Site Collection (Site) • Boundary for ownership • Collection of one Top-Level Site and one or more sites under it • Site (Web) • Container for Content in WSS • Contained within a site collection • Content stored in same Db as parent Site

9. Demo Extending IIS Website

10. Site Collections and Sites • One or many Site collections per Web Application • One Top-Level Site per Site Collection • One or many Child sites per Site Collection

11. WSS 2.0 – ASP.NET 1.x WSS integrated more at the IIS level than at the ASP.NET level using ISAPI Filter ASP.NET 1.1 knows how to parse .aspx files from file system and not from database ASP.NET 1.1 does not offer Web Part infrastructure ASP.NET 1.1 offers no satisfying page template solution ASP.NET 1.1 offers no built-in navigation infrastructure WSS v3 is built on ASP.NET 2.0 WSS integration in line with best practice ASP.NET extensibility of HttpModules and HttpHandlers ASP.NET 2.0 provides parser that can use a “VirtualPathProvider” to get .aspx pages from sources other than the file system like databases ASP.NET 2.0 provides new Web Part infrastructure ASP.NET 2.0 offers Master Pages feature for page templates ASP.NET 2.0 offers rich navigation infrastructure WSS and ASP.NET Integration

12. ASP.NET Master Pages • Masters define common content and placeholders (<asp:ContentPlaceHolder>) • Content pages reference masters and fill placeholders with content (<asp:Content>) Site.master default.aspx http://.../default.aspx <%@ Master %> <asp:ContentPlaceHolder ID="Main" RunAt="server" /> <%@ Page MasterPage- File="Site.master" %> <asp:Content ContentPlaceHolderID= "Main" RunAt="server" /> </asp:Content>

13. Master Pages in WSS • WSS sites such as Team Site built using a standard master page • Quick and easy to change look and feel of entire site • Editing master page can be done with SharePoint Site Designer

14. Platform Storage Enhancements • Basic storage – Lists • More similarity between Lists and Document libraries • Versioning on lists • Folders can be created in lists • Lists can now have event handlers defined • Enhancements on lists and document libraries • New Built-In Field types, Custom Field types • RSS feeds supported on Lists and Libraries • Folders can now have Custom properties • Document Libraries now support major and minor versions

15. Management of Content • Problems with managing content • Need to share content across sites by creating lists accessible across the site collection • Often need to store documents of different types each having different meta data in a central location • Customize actions, workflow, UI menus and document policies based on the type of content or document • Many document types identified in an organization, but there is no clear way to enforce standards • WSS 3.0 Solution • Shared Site Columns • Content Types

16. Site Columns • Single column definition reused across multiple lists • Definitions stored in Site Column Gallery • Site Columns scoped at Site Collection level • Accessible across the sites in a single site collection

17. Demo Site Columns

18. Need for Content Types • Define constraints on content in lists • Define customizations and workflow in content in lists and libraries • Reusable and extendable schemas for lists and libraries content

19. Content Types • Content type can include… • Columns to represent metadata or properties • A document template on which to base documents of this type • Custom forms for New, Edit, and Display use with content type • Event handlers • Workflows available for items of this content type • Retention policies

20. Content Type Inheritance • Reuse base definition across content types and then extend and specialize further • Base type contains core properties BaseDocument CourseContent StandardCourseContent CustomizedCourseContent

21. Content Type Scoping • Content Types have templates and instances • Templates exist at the site level • Accessible in child sites • Instantiated at the list level

22. Demo Content Types

23. Collaboration ECM Search BI Portal BPM Project WSS "V3" as a Solutions Platform • WSS "V3" supplies core services • Suited for building scalable Web-enabled applications • Provides out-of-box collaboration solutions • Platform for Office servers technology Office 12 Solutions Built On WSS V3 WSS "V3" Core Workspace Services APIs Fields/Forms OM and SOAP Events Deployment Storage Repository Metadata Versioning Backup Security Rights/Roles Pluggable Auth Per Item Rights Trimming Mgmt Admin UX Delegation Provisioning Monitoring Topology Config Mgmt Farm Services Feature Policy Extranet Site Model Rendering Templates Navigation Visual Blueprint Operating System Services ASP.NET (Web Parts, Personalization, Master Pages, Provider Model for navigation, security, etc.) Database Workflow Search

24. Thank You

25. The Webcast Quiz! • Four questions, multiple choice type • More than one maybe correct • Two lucky winners will win an Orchid Music Player • If you participate in the contest and are among the 2 lucky winners, your name will be featured on http://www.microsoft.com/india/webcasts/

30. How to Participate • Please send your responses to response@erfolgcs.com • Subject = “Microsoft Webcast Contest – WSS 3.0 Architecture and Enhancements ”

31. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.