1. SharePoint Deployment Mirjam van Olst Technology Consultant Information Worker Solutions

2. Introduction: Deployment in MOSS 2007

3. Agenda Content Deployment Content Migration API Site Definitions Features Feature Stapling Solution Deployment Forms Deployment 3

4. Content Deployment

5. Internet Production Farm Authoring Farm Content Deployment Content Deployment Requests

6. Content Deployment Paths and jobs –Paths connect source and destination site collections –Jobs control what content is copied when –One direction (source → destination) Incremental by default –Incremental takes changes since last successful deployment Configured by central administrator –Can delegate to authors using the Quick Deploy job Content fix-up –Links are fixed-up and are relative to the production site –All security trimming happens on the destination Latest major, minor version items copied to production

7. Content Deployment MOSS 2007 necessary for content deployment features Source and destination systems must be connected

8. Content Deployment

9. Content Migration API New in SharePoint 2007 Part of Wss3 Surfaced in STSADM: export and import cmds Basis for MOSS 2007 Content Deployment –Content Deployment paths and jobs (Central Admin) –Used especially in WCM for content deployment

10. Content Migration API Powerful API, but… –Version 1.0 (has some glitches) –Was poorly documented, more info is surfacing in docs and blogs Exports to file system –Content migration package (.cmp = renamed CAB) file well defined schema –All XML +.dat files for actual data files (pages, pictures, documents, …) –Deployment between disconnected systems

11. Content Migration API STSADM export/import can handle only complete sites Use custom code for: “cherry picking”: –Site Collection, Site, List, Folder, Item –Include/exclude dependencies: content types, masterpages, css files, images, attachments Exported content retaining object identity –To identify objects to update in selective migration scenario’s –Supports export of complex web part configurations with list id’s Incremental exports, based on change token

12. Content Migration API Scenario’s Application deployment Content deployment Reparenting objects Some restrictions No deployment of file system based objects like features No deployment of workflows Content types can’t be “cherry-picked” Content Migration objects SPImport, SPImportSettings, SPExport, SPExportSettings

13. Content Migration API

14. 14 Site Definitions

15. What is a Site Definition? Defines a unique type of SharePoint site views forms fields editform.aspx allitems.aspx SCHEMA.XML (per list) navigation bars modules list instances standard views default.aspx feature references ONET.XML configurations WEBTEMP.XML Example Configurations: Basic Meeting Workspace Blank Meeting Workspace Decision Meeting Workspace Social Meeting Workspace Located: 12\Template\1033\XML Located: 12\Template\SiteTemplates\ HelpDesk\XML Located: 12\Template\Features\ AnnouncementsList\Announce 12\Template\Features\ HelpDeskList\HelpDesk views forms fields editform.aspx allitems.aspx views forms fields editform.aspx allitems.aspx views forms fields editform.aspx allitems.aspx views forms fields editform.aspx allitems.aspx

16. Site Definitions Opgeslagen in SiteTemplates folder op alle front-end Web servers Verzameling XML files (CAML) en ASPX pagina’s die gebruikt worden als helper files Basis schema definitions en helper files staan in de Global folder Site definitions localization met behulp van resource files in de Resource folder

17. Site Definitions en Templates Site Definitions –Basis beschrijving van de site –Geïnstalleerd op web front ends –Gemaakt door een developer Site Template –CAB package met verschillen ten opzichte van site definition –Opgeslagen in content database (Site Template Gallery) –Gegenereerd door een administrator

18. Site Definitions

19. Features

20. Feature Model in WSS Features zijn overal Features zijn herbruikbare modulaire bouwstenen Features kunnen ook bestaande sites uitbreiden Features zijn eenvoudig te activeren en deactiveren

21. Core Content Types WSS Core Links Core Column Templates Document Libraries Picture Libraries Discussion Boards Site Collection Features Site Collection Features Farm Features Farm Features Web Features Web Features Team Collaboration Contacts Hidden Feature Visible Feature Events Basic ListLinks Announce- ments Tasks Surveys Content Lightup WSS Out-Of-The-Box Features Basic Web Parts Basic Web Parts

22. Modular Provisioning Reusable pieces of functionality Extend existing sites Easy to activate/deactivate Feature Name ID Description Scope Receiver assembly Activation Dependencies Element Manifests Feature Name ID Description Scope Receiver assembly Activation Dependencies Element Manifests Feature.xml Elements.xml Custom Actions Custom Views Content Type Definitions Layouts Pages Modules (files) List Instances List Templates Event Receivers Delegate Controls Workflow Bindings Custom Actions Custom Views Content Type Definitions Layouts Pages Modules (files) List Instances List Templates Event Receivers Delegate Controls Workflow Bindings

23. Wat is een Feature? FEATURE # CAML/ ASPX files # Manifest Files Feature.xml Feature.xml definieert de metadata van de feature Andere XML bestanden genaamd “element manifest files” definieren wat de functie van de feature is: - Event handlers - Lijst en library definities - Custom workflows - Light-up van de SharePoint UI - Administratieve activiteiten

24. Feature Scopes Site Settings Links Site Web Part Definitions Workflow Definitions Site Content Types Layout Files List Instances List Definition + Forms + Views List Instances List Item Events Item Custom Actions Web Admin Custom Actions Layout Files Item Custom Actions Site Settings Links Admin Custom Actions

25. Feature Lifecycle

26. Feature (de)activation User Interface “activate” or “deactivate”

27. Feature Stapling

28. Functionaliteit toevoegen aan site definitions Kan gebruikt worden voor out of the box site definitions Niet nodig om de site definitions aan te passen Staple zoveel features als je wilt aan een site definition TIP: staple aan de GLOBAL site definition NOTE: je kunt niet staplen aan de blank site Feature Stapling

29. Features & Feature Stapling

30. Solution Deployment

31. Hoe deploy je de features, site definitions en web parts op je SharePoint server? Ouderwetse Methode: – Met de hand de files naar het file systeem kopieren – web.config entries toevoegen voor alle assemblies – IIS reset – En dat herhalen op elke web front end server! Nieuwe Methode: Solution Deployment!

32. Solution Deployment Developer verpakt een custom oplossing in een solution Deployment via Central Administration of stsadm: – Files worden naar alle web front end servers gekopieerd – Kan ook deployen naar application servers Solutions kunnen bestaan uit: – Feature definitions – Site definitions – Template Pages & Resources – Web Parts – Resources – Global, Bin assemblies

33. Solution Deployment Security Assembly deployment opties – Bin is veiliger (WSS_Minimal) – GAC geeft de assembly full trust Developer geeft de deployment locatie voor assemblies in een solution aan in manifest file Assemblies voor bepaalde functies MOETEN in de GAC gedeployed worden (Eventhandlers)

34. Solution Deployment HelpDesk.wsp (WSS Solution Cab) Feature Manifests WSS Config DB UI, Command Line, OM “deploy” command add delete deploy retract Template Files Assemblies Web Front End Servers NewWFE

35. Solution Deployment Solution Informatie – Status – Lang pack? – Deployed? Scheduled Deployment Solution kan gedeployed worden naar de GAC en naar de bin – Waarschuwt admin bij GAC install – Admin kan een specifieke Web Application kiezen

36. Solution Deployment

37. Forms Deployment

38. WSS Publishing, Opening, And Filling In Forms Rendering Validation Execute calculations Execute rules Editing actions Validation Execute calculations Execute rules Editing actions (All using script) Download XSN, XML Publish XSN Download script and data array Office “12” servers XSN ASPX Replay event log XSN, XML loaded Business logic execution XSN, XML loaded Business logic execution Forms Capabilities Generate and render HTML (using script) Return updated data array Generate InfoPath Client Browser Postback event log via XMLHTTP InfoPath Designer Take offline as needed

39. Web Service Server WSS Office “12” servers XSN ASPX XSN, XML loaded Business logic execution Forms Capabilities Submitting Forms Postback event log via XMLHTTP Submit Browser InfoPath Client Submit XSN, XML loaded Business logic execution

40. Design Once Overview One form for smart client and browser Shared –Controls –Business Logic –Data Connections –Digital Signatures –Managed Code Object Model Design Checker: Smart Client-only features –Some controls –Filters, Roles, ADO Adapter –Script, Custom Task Panes Smart Invocation –Open in smart client, if available. - Links in document libraries, Web pages, email, etc. –Special URL parameters to force opening in browser

41. Design Once With Code Design code once –Use new managed OM (CLR 2.0) –System.Xml. (No more MSXML) Smart client –Code runs in client –Data connections called from client Browser –Code runs on server –Data connections called from server –Conditional formatting, validation, rules, calculations: – all run in browser (Ajax) Out-of-band postback –Used for code, or for action that must run on server –Can control when postback happens

42. Two Types Of Form Deployment 1.Simple publishing by end users –Publish directly from InfoPath to SharePoint as document library or create Site Content Type (for use in multiple doc libs) –Form templates must be: Without code Domain trust Data connections using Data Connection Library

43. Two Types Of Form Deployment 2.Upload to server by administrator –Publish from InfoPath ready for upload to Office Server –Administrator then uploads via central administration site, or command line –Form can then be activated to any Site Collection –Supports forms with Code Data Connections managed by administrator Full trust Mobile

44. Server Administration Server administrator is the gatekeeper of forms with code: –Controls the form lifecycle Upgrade forms with no down-time Gracefully retire forms with quiescing –Makes forms available to site collections Any form template can be used in multiple places across the server Site content type for each form template Improved library integration and sharing –Uses standard WSS administration tools: Central admin site, command line, and object model

45. Forms Deployment 45

46. VRAGEN?

47. Macaw Beechavenue 140 1119 PR Schiphol-Rijk Tel +31 (0)20 8 510 510 Fax +31 (0)20 8 510 511