Microsoft Office SharePoint 2007 Technical Enablement Tour - PowerPoint PPT Presentation

View by Category
About This Presentation
Title:

Microsoft Office SharePoint 2007 Technical Enablement Tour

Description:

2006 Microsoft Corporation. Microsoft Office SharePoint 2007 Technical Enablement Tour ... Reapply all custom formatting logic e.g. adding custom CSS classes ... – PowerPoint PPT presentation

Number of Views:156
Avg rating:3.0/5.0
Slides: 37
Provided by: downloadM
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Microsoft Office SharePoint 2007 Technical Enablement Tour


1
Microsoft Office SharePoint 2007 Technical
Enablement Tour
  • Patrick Tisseghem (Managing Partner U2U)
  • patrick_at_u2u.be

2
Customizing Sites and Building SharePoint
Solutions
3
The WSS Template Architecture
  • WSS is a site provisioning engine
  • Sites are based on templates (plenty of OOB
    templates)
  • Template architecture of WSS is extensible

Save as Template in the database (.stp file)
Collection of physical files known as site
definitions
4
Site Definitions and the Global Template
  • Reside in SiteTemplates folder on every front-end
    Web server
  • Collection of XML files (following the CAML
    language) and ASPX pages acting as helper files
  • Common schema definitions and helper files are
    factored out in the Global folder
  • Site definitions are localized through resource
    files stored in the Resource folder

5
DEMO
  • Exploring Site Definitions

6
The Features Framework
  • Bring modularity to site definitions
  • Provide greater flexibility, control and
    reusability
  • Better story for making new functionality (e.g.
    new lists, menu enhancements, custom workflows,
    ...) available on existing sites

7
What is a Feature?
  • Feature.xml defines the metadata of the feature
  • Other XML files called manifest files define what
    the feature is all about
  • Event handlers
  • List and library definitions
  • Custom workflows
  • Light-up of SharePoint UI
  • Administrative operations
  • CAML and ASP.NET helper files representing the
    feature components

8
Scope of Features
  • Farm
  • Web Application
  • Site Collection
  • Site

9
OOB WSS Features
  • Team Collaboration Feature
  • Announcements List Feature
  • Content Types Feature
  • Field Types Feature
  • Administrative Links Feature

10
Making a Feature Available
  • Deploy Feature
  • Copy the all of the files making up the feature
    to the Features folder
  • Install Feature
  • Activate Feature
  • Using the browser (features admin page)
  • Using STSADM

Stsadm.exe o installfeature -force
Stsadm.exe o activatefeature url site
11
DEMO
  • Exploring and Creating Features

12
Web Content Management System What do we expect
from it?
  • An environment giving the capability to quickly
    build, deploy, and maintain highly dynamic Web
    sites
  • Branding Rich and flexible support for defining
    the look, feel, and navigation of the site
  • Decentralized Authoring Allow users to create
    and contribute content with a few simple clicks
    using tools they already know! and using
    templates that developers have created. Get
    Information Technology out of the publication
    business!
  • Workflow/Scheduling Allow supervisors to approve
    content before it is posted.
  • Data Integrity Enforce the freshness of data.
    Ensure your documents go up and come down off
    the site at the right time. Ensure mandates are
    met.
  • Policy, Procedures, and Guidelines Gentle and
    transparent enforcement of agencies content
    policies, procedures, and guidelines via templates

13
Web Content Management
Business Managers
Site Managers
Mobile Devices
Site Structure, Templates, Site
Design, Integration, Business rules, Security
Content Creation and Approval, Publishing, Schedul
ing, Archiving, Versioning
Web Services
Workflow
Web Sites
Site Designers and Web Developers
Business Users / Content Creators
14
Microsoft Content Management Server 2002
  • Low TCO/Enterprise CM - Separate content from
    design
  • Dynamically repurpose and target content for
    audiences and devices
  • Deliver fast and low-cost site updates and
    redesigns
  • Provide content versioning, scheduling and reuse
  • Enhance Biz User Productivity Empowered to
    Publish
  • Web browser-based rich authoring or direct from
    Microsoft Word
  • Out-of-the-box and extensible workflow for
    compliance and quality control
  • Powerful Abilities for IT Extensible and
    Interoperable
  • Developers rapidly create content-rich, dynamic
    Web applications
  • VS.NET integrated providing out-of-the-box server
    and user controls
  • Templates easily created by dragging and dropping
    placeholders
  • Managed API leveraging .NET framework and ASP.NET
  • Web Services extensibility
  • Integration with SharePoint Portal Server and
    Commerce Server

ASP.NET
15
Design Goals
  • Integrate CMS and SharePoint
  • Remove forced choice CMS vs. SharePoint
  • Move towards integrated ECM solution
  • Add Internet readiness to Sharepoint
  • Make creation of dynamic, produced websites
    dramatically faster and easier
  • Lower amount of costly custom code
  • Provide great OOB experience
  • Improve user experience across all features
  • Move CMS customers forward
  • Comprehensive data migration
  • Enable flexible migration plans

16
CMS vNext
  • Part of the Microsoft Office SharePoint Server
    2007
  • Delivered as a set of features
  • Option for internet/extranet/intranet
  • Towards an integrated ECM solution
  • Excellent OOB experience

17
Investments
  • Forms Authentication
  • Master Pages
  • Page Model
  • Smart Client Authoring
  • Publishing Cycle
  • Site Variations
  • WCM Web Parts

18
Demo
  • Web Content Management with MOSS 2007

19
CMS 2002 to MOSS 2007
  • Two phases of migration
  • Content migration (automatic)
  • Application migration (manual)
  • Content migration support two modes
  • Full migration
  • Incremental migration
  • Start with a full migration and then do periodic
    incremental migrations until you are ready to cut
    over
  • Incremental allows you to continue using your
    existing CMS02 installation during migration
  • CMS 2002 and MOSS 2007 can coexist on the same
    physical farm
  • This allows you complete the migration without
    having to purchase hardware for a new farm

20
CMS 2002 Content Migration
  • Content migration tool runs against CMS02
  • Generates import packages
  • What counts as content?
  • Channels, postings and all placeholder content
  • Resource galleries and resources
  • Template galleries and template gallery items
    (not the ASPX files)
  • Rights groups and users
  • Custom properties
  • What will I have after I run the automatic
    content migration tool?
  • A functioning site with all existing content
  • A set of unbranded page layouts that can be
    re-branded

21
CMS 2002 Application Migration
  • Update white master page and page layouts
    generated by the content migration tool
  • Reapply all custom formatting logic e.g. adding
    custom CSS classes
  • Should only need to touch one master page and a
    handful of page layouts

22
CMS 2002 Application Migration Custom code
23
WSS v2 vs. WSS v3 Event Handlers
  • An event handler is a .NET assembly containing
    one or more classes handling events that are
    triggered by SharePoint
  • WSS v2
  • only possible for document libraries
  • executed in an asynchronous manner
  • WSS v3 events architecture significantly improved
  • Events supported for lists, document libraries
    and content types
  • Events supported for changes to list schema as
    well as items
  • Events supported at site collection and site
    level
  • Events supported for incoming email messages
  • Support for synchronous events and asynchronous
    events
  • Synchronous events occur before the fact and are
    cancel-able

24
Steps for Creating an Event Handler
  • .NET class library
  • Reference to Microsoft.SharePoint.dll
  • Custom class inheriting a WSS receiver class

using Microsoft.SharePoint namespace Demos
public class MyEventHandler SPItemEventReceiver
public override void ItemDeleting(SPItemEve
ntProperties properties) // do something
and possibly cancel the event
properties.Cancel true
properties.ErrorMessage my message"
public override void ItemDeleted(SPItemEventPrope
rties properties) // do something

25
DEMO
  • Building a WSS v3 Event Handler

26
Deploying a WSS v3 Event Handler
  • Compile class into strong-named assembly
  • Deploy the DLL in GAC
  • Register DLL as event handler in WSS v3
  • The WSS v2 way (only for document libraries)
  • Programmatically via the object model
  • Using the new WSS feature framework

27
DEMO
  • Deploying and Registering a WSS v3 Event Handler

28
Web Part History
  • Windows SharePoint Services 2.0 (WSS)
  • Designed with its own Web Part infrastructure
  • WSS serializes/stores/retrieves personalization
    data
  • ASP.NET 2.0
  • Designed with newer universal Web Part
    infrastructure
  • Serializes/stores/retrieves personalization data
  • More flexible and more extensible than WSS
  • ASP.NET 2.0 does not support WSS v2 Web Parts
  • Windows SharePoint Services 3.0 (WSS)
  • Backward-compatible with v2 Web Parts
  • Offers a layer on top of the ASP.NET 2.0 Web Part
    infrastructure

29
Web Part Types for WSS v3
ASP.NET 2.0 Runtime
WSS v3 Runtime
WSS Web Parts
ASP Web Parts
ASP Web Parts
Hybrid Web Parts
WSS v2 Runtime
WSS Web Parts
WSS Web Parts
30
WSS v3 Web Part Page Structure
31
Developing a WSS 3.0 Web Part
  • Web Parts derive from ASP.NET 2.0 WebPart base
    class

using System using System.Web.UI using
System.Web.UI.WebControls.WebParts namespace
MyWebParts public class HelloWorldWebPart
WebPart protected override void
OnPreRender(EventArgs e) this.Title
Hello Web Part" protected override
void RenderContents(HtmlTextWriter writer)
writer.Write("Hello, world")
32
DEMO
  • Developing a WSS 3v3 Web Part

33
Deployment Steps
  • Deploy the .NET assembly
  • As private assembly in the \bin folder
  • As shared assembly in the Global Assembly Cache
    (GAC)
  • Register the Web Part as a safe control
  • Add the Web Part to the Web Part gallery
    available at the site collection level
  • Advertise the Web Part in the Add Web Part
    dialog

34
DEMO
  • Deploying a WSS v3 Web Part

35
Questions?
36
Section title here
  • Sub title here
About PowerShow.com