• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Turbo-Charge Collaboration by Automating Site Provisioning in SharePoint 2010
 

Turbo-Charge Collaboration by Automating Site Provisioning in SharePoint 2010

on

  • 593 views

Turbo charge collaboration by automating site provisioning in share point 2010 presented by Bob German 6 March 2013 at SPTechCon San Francisco

Turbo charge collaboration by automating site provisioning in share point 2010 presented by Bob German 6 March 2013 at SPTechCon San Francisco

Statistics

Views

Total Views
593
Views on SlideShare
589
Embed Views
4

Actions

Likes
0
Downloads
9
Comments
0

1 Embed 4

https://twitter.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Cars are:Tata NanoHonda AccordFerrari f430

Turbo-Charge Collaboration by Automating Site Provisioning in SharePoint 2010 Turbo-Charge Collaboration by Automating Site Provisioning in SharePoint 2010 Presentation Transcript

  • Turbo-Charge Collaboration byAutomating Site ProvisioningBob GermanSharePoint Practice DirectorBlueMetal Architects
  • BlueMetal Architects  We are experts at building solutions that exactly meet the needs of our customers by apply the right people, processes and platforms.  Our focus is on modernizing applications through expertise in Creative, Social, Development and Data.  We have offices in Boston, New York, and Chicago.Bob GermanSharePoint Practice Director and Principal Architectat BlueMetal ArchitectsDeveloper and architect on the SharePoint platformsince it was called “Site Server 3.0”Co-author of SharePoint 2010 Development withSilverlight for Addison-Wesleyhttp://blogs.msdn.com/BobGermanAbout the Speaker @Bob1German
  • The Challenge How do you empower end-users to create SharePoint sites while making sites consistent, organized, a nd discoverable?Some of us still miss the sitedirectory, which was removed inSharePoint 2010… @Bob1German
  • 1 Sites and Site Collections “Out of the Box” Site Creation Three models of success 2 ① Very simple: Client side 1 ② Medium: Sandboxed workflow 2 ③ Full featured: Farm solution 3 3Agenda @Bob1German
  • Item Site Collection Top-level List/Library Site Item Content Database List/Library Item Site Collection Top-level Site List/Library Item Web Site Application Site List/Library Item Content Top-level Site Collection List/Library Item Database Site Farm Item Site Collection List/Library Item Web Content Top-level Item Application Database Site List/Library Item SiteSharePoint Containers
  • • Independent Administration Item Site Collection Top-level List/Library • Storage Management Site Item • Connection to IIS and server URL(s) Content • Authentication and high- Database List/Library Item Site Collection level policy settings • Shared Service Connections Top-level Site List/Library Item Web Site• A set of servers in Application one location Site List/Library Item• A common configuration database Content Top-level Site Collection List/Library Item Database Site Farm Item Site Collection List/Library Item Web Content Top-level Item Application Database Site List/Library Item SiteSharePoint Containers
  • Many things are scoped at the Site Collection SharePoint Groups Root of permission inheritance Storage and Sandbox Quotas Content DB 1 Navigation Content DB 2 Rollups with SPQuery or Content Query Web Part Content DB 3 Content Types and Site Columns* A site collection cannot span content DB’s, but A content DB can have many site collections Lookup lists Galleries (Web parts, Solutions, Master Pages, etc.)Site Collections @Bob1German
  • SharePoint Site ModelShared IntranetServices Publishing Portal • Employee Communications• Search • Functional Portals (HR,• Metadata Functional Finance, etc.) Portals• User Profile • Group and Team Portals• BCS • Information Repositories Groups & Teams • Business Intelligence Collaboration Projects & Workspaces • Team / project workspaces • Social Networking My Sites • Personal publishing @Bob1German
  • SharePoint Site ModelShared IntranetServices Customized Portal• Search• Metadata Functional Portals• User Profile• BCS • Created by IT • Content Groups & Teams managed by business • Self-service Projects & Workspaces Standardized My Sites @Bob1German
  • A Place for EverythingSharedServices Portal Customized• Search Dashboard Dashboard• Metadata App• User Profile App App Portal Portal Portal Portal• BCS Repository Repository Repository • Created by IT • Content managed by Structured business Structured Structured Collaboration Collaboration Collaboration • Self-service Ad-Hoc App Ad-Hoc App Ad-Hoc Collaboration App Collaboration Collaboration Standardized My Site My Site My Site My Site My Site = Site Collection @Bob1German
  • Out of the BoxSelf Service Site Collection Provisioning @Bob1German
  • • Creates child sites in a site collection• Runs on the client using the Client Object Model - Can run in a Content Editor Web Part! - Can run as a SharePoint 2013 app!• Lists sites directly – no separate directory• Users need to have permission to create a siteScenario 1: Simple Site Provisioning 12
  • The same code works in a SharePoint 2013 app!Very Simple: Client SideClient-side site listing and creationWorks in Office 365 or On-Premises – or even as a SharePoint 2013 app! @Bob1German
  • • Runs in the sandbox and on Office 365• Custom workflow action creates and configures a child site• Out of the box workflow actions provide approval and directory update• Workflow runs as a privileged user to allow any user to request a siteScenario 2: Custom Workflow Activity 14
  • Medium: Sandboxed WorkflowCustom ActionWorks in Office 365 or On-Premises @Bob1German
  •  Site Definitions  SharePoint ships with several site definitions – team site, blank site, etc.  A developer can build a site definition, but it’s not a good idea Site Templates  Earlier versions of SharePoint supported site templates (.spt files) when you clicked “Save as a Template”  Now you get a declarative web template (.wsp file) Web Templates  Contain the differences between a site definition and the site you want  End users can get them with “Save as a Template” (sometimes)  Developers can build them from scratch but it’s painful WARNINGS:  Do not fake out “Save as a Template” for publishing sites … it doesn’t work well  Beware of the “Import .wsp file” option in Visual Studio to build web templatesSite Definitions and Web Templates
  • Creating a Site Collectionfroma Custom Web Template @Bob1German
  • • Create site collections, not just child sites• Use web templates to provide tailored and consistent sites• Maintain metadata and directories for multiple site types• Work robustly across farmsScenario 3: Advanced Scenario @Bob1German 18
  • Site Collection Site Collection Site Directory Site Collection Metadata Metadata Metadata Timer Timer Timer Job Job Job Workflow Workflow Workflow Request Request Request List List List APPS FARM COLLAB FARM Web app 1: Custom Apps Web app 2: Community SitesSite Collection: Request and Creation @Bob1German Web app 3: Project Sites
  • Full Featured: Farm SolutionMulti-farm solutionUses any approval workflowMaintains metadata and directoryCould create sites or site collections with this design @Bob1German
  •  Automate site creation to - Balance user empowerment with governance - Provision sites consistently - Maintain a directory and site metadata Choose wisely between sites and site collections In sandboxed solutions - Elevate privileges with workflow “Impersonation Steps” - Beware of calling sandboxed solutions from sandboxed solutions In SharePoint 2013 apps - Elevate privileges via app identitiesSummary @Bob1German
  • Thank You! @Bob1German