Your SlideShare is downloading. ×
0
External facing SharePoint site<br />By Manish Rawat<br />http://www.linkedin.com/in/manishra<br />
 Architecture and Design Choices<br />
Planning - Key Decision Points<br />
Planning - Structure<br /><ul><li>Site Collections– It’s container of sites. Decisions
Number  (How many) and Types (What kind) needed
Host header needs
Managed Paths – Enables where site collection will  get created & help interpret URLs to determine site paths
Separate Content Database  per site collection possible.Helps Performance and Scalability but rolling up data (query)from ...
Unique administrative & Security privileges per site collection
Backup/Restore can happen per site collection</li></li></ul><li>Planning – Structure… continued<br /><ul><li>SSP (v 2007) ...
Search
BDC – Business Data catalog to connect to any Line of Business (LOB) apps e.g. SAP
User Profiles
Usage Reporting …..
Scripting
Reusable Script needed. Useful in medium to large teams.
STSADM is main scripting tool. Free Extensions available.
STSADM scripts have options are not available via UI. E.g. assigning Specific DB to Site collection.
Navigation : Custom Navigation VS. Built in. </li></li></ul><li>Planning - Strategy<br /><ul><li>Branding :
Consistent Look and feel in different sites.
UI assets location
Upcoming SlideShare
Loading in...5
×

Building fast track external facing sharepoint site

2,892

Published on

Explains external facing SharePoint site development experience, techniques in agile manner

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,892
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
66
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Building fast track external facing sharepoint site"

  1. 1. External facing SharePoint site<br />By Manish Rawat<br />http://www.linkedin.com/in/manishra<br />
  2. 2. Architecture and Design Choices<br />
  3. 3. Planning - Key Decision Points<br />
  4. 4. Planning - Structure<br /><ul><li>Site Collections– It’s container of sites. Decisions
  5. 5. Number (How many) and Types (What kind) needed
  6. 6. Host header needs
  7. 7. Managed Paths – Enables where site collection will get created & help interpret URLs to determine site paths
  8. 8. Separate Content Database per site collection possible.Helps Performance and Scalability but rolling up data (query)from multiple Site collection is not OOTB
  9. 9. Unique administrative & Security privileges per site collection
  10. 10. Backup/Restore can happen per site collection</li></li></ul><li>Planning – Structure… continued<br /><ul><li>SSP (v 2007) - hosting shared services that will be used any MOSS Web applications.
  11. 11. Search
  12. 12. BDC – Business Data catalog to connect to any Line of Business (LOB) apps e.g. SAP
  13. 13. User Profiles
  14. 14. Usage Reporting …..
  15. 15. Scripting
  16. 16. Reusable Script needed. Useful in medium to large teams.
  17. 17. STSADM is main scripting tool. Free Extensions available.
  18. 18. STSADM scripts have options are not available via UI. E.g. assigning Specific DB to Site collection.
  19. 19. Navigation : Custom Navigation VS. Built in. </li></li></ul><li>Planning - Strategy<br /><ul><li>Branding :
  20. 20. Consistent Look and feel in different sites.
  21. 21. UI assets location
  22. 22. Document Management
  23. 23. Content Organization
  24. 24. Content Presentation & Customization
  25. 25. Content Publishing – OOTB publishing including Quick Deploy
  26. 26. Search : Sources, Scope, Keywords, Crawl, Best bets
  27. 27. Versioning and Workflow:
  28. 28. List versioned
  29. 29. Custom Workflow needs </li></li></ul><li>Planning - Objects<br /><ul><li>Reuse OOTB Web parts: Content Query Web Part
  30. 30. Data pull from anywhere in site collection. Provide RSS capability
  31. 31. Custom Look and feel : XSLT conversion
  32. 32. Site ColumnsReusable and central managed entity. Its like a data type.
  33. 33. Content TypeType definition/Functional unit – collection of setting & metadata.Usually references to site columns - Supports Inheritance - Identify Hierarchy
  34. 34. ListsDatabase table whose schema is defined by Content Type OR adding column individually.
  35. 35. Page Layouts – Review Wireframes, Identify sections & types of layouts needed</li></li></ul><li>Planning - Admin<br /><ul><li>Farm Topology needs
  36. 36. Small/Medium/Large Farm
  37. 37. Different environments connectivity
  38. 38. Automated build needs
  39. 39. Securing SharePoint-
  40. 40. Intranet, Internet, Extranet
  41. 41. Zones requirements
  42. 42. Roles and Permission
  43. 43. Data Protection, Recovery and Availability
  44. 44. Monitoring needs
  45. 45. Scalability & Capacity Planning</li></li></ul><li>Design Choices<br /><ul><li> Use SharePoint Field Controls vs. Webparts/Lists</li></ul> Source : Andrew Connell book - http://www.wrox.com/WileyCDA/WroxTitle/productCd-0470224754.html<br /><ul><li> Provide easy and flexible Page Content authoring (Inline)
  46. 46. Project Structure/Processes setup to minimize need of SharePoint knowledge
  47. 47. Use OOB controls/infrastructure of SharePoint
  48. 48. XCopy (WSP) based deployment
  49. 49. Run in Minimal Trust level
  50. 50. Feature Based development</li></li></ul><li>Models - .NET App & SharePoint App<br /><ul><li>Mix Model : Application consist of combination of SharePoint & asp.net web app
  51. 51. SharePoint Only : Application consist SharePoint only</li></li></ul><li>Mix Model Design<br />
  52. 52. Mix Model Design – continued…<br /><ul><li>ASP.Net page can use API to get content from SharePoint
  53. 53. Form Authentication cookie can Shared between multiple Web apps
  54. 54. Navigation Providers of ASP.NET & SharePoint combined to give Unified Look</li></li></ul><li>Execution<br />
  55. 55. Dev Environment<br /><ul><li>No one size fit all.
  56. 56. Own Domain environment (AD, TFS, DB, Middle tier Servers all in one domain)
  57. 57. All developers (10 to 12) machines/servers in same domain
  58. 58. Each developer has its own MOSS setup
  59. 59. Testing and Integration environment in same domain</li></li></ul><li>Dev Machines Setup<br /><ul><li>Create Base machine (Use 64 bit dev machines )
  60. 60. Use Scripts to setup/configure in medium to large Teams/Farms
  61. 61. Unattended MOSS installation scripts
  62. 62. Setup PDF ifilter to search pdfs
  63. 63. Create SSP via scripts
  64. 64. Create Web Application
  65. 65. Next Steps</li></li></ul><li>Solution Structure – Separation of Projects<br /><ul><li>Feature based development is recommended development methodology. It’s a way to deploy functionality (e.g. Page Layout, List) to SharePoint infrastructure
  66. 66. Typical SharePoint solution will have
  67. 67. Branding Project: Contains master page, page layouts and their corresponding content types
  68. 68. Types Project: Contains CAML definition of site columns, List content types etc
  69. 69. UserControl Project: Contains ascx controls . V2010 supports visual web parts
  70. 70. WebParts Project: Contains web parts definitions and code
  71. 71. MetaTag Project – supports adding (http://www.mtelligent.com/journal/2008/1/11/using-the-delegate-control-to-add-meta-tags-to-sharepoint-pa.html)</li></li></ul><li>Requirement-Design phase <br /><ul><li>Conditions /Needs
  72. 72. Requirements not fully flushed => Page Template/Layout keeps changing
  73. 73. PLD (Presentation developer) need isolated environment within SharePoint (Branding VS. Net Project)
  74. 74. Process
  75. 75. Person ‘X’ to be owner of SharePoint content database. i.e. responsible for types/building blocks
  76. 76. Change to Lists, Content Type, Site columns to be performed by Person ‘X’ and distribute the content database backup to team.
  77. 77. Page Layout
  78. 78. Person ‘X’ to create page layout with required elements (coming from content type)
  79. 79. PLD to use SharePoint designer to design Page Layout.
  80. 80. Use DisplayMode (Edit /Display) if SharePoint control default rendering is not sufficient</li></ul> <PublishingWebControls:editmodepanelrunat="server" id="editmodepanelEditModeQuickLinks" PageDisplayMode="Edit" ><br />       <PublishingWebControls:RichLinkFieldFieldName="QuickLink1" runat="server" id="RichLinkField0" /></li><br /></PublishingWebControls:editmodepanel><br /> <br /><PublishingWebControls:EditModePanelrunat="server" id="QuickLink1DisplayMode" PageDisplayMode="Display"><br />     <pmxServerControls:LinkFieldRendererrunat="server" LinkFieldName="QuickLink1" /><br /></PublishingWebControls:EditModePanel> <br />
  81. 81. Design-Development phase <br /><ul><li>Conditions /Needs
  82. 82. Requirements close to finalization => Page Template/Layout doesn’t change often
  83. 83. PLD need isolated environment within SharePoint
  84. 84. Process
  85. 85. Move SharePoint assets as Features
  86. 86. Anyone is team is owner of SharePoint content database.
  87. 87. Page Layout
  88. 88. PLD to use Visual Studio to design Page.
  89. 89. PLD to use Visual Studio -> WSPBuilder -> Copy to 12 Hive to test page. (v 2007)</li></li></ul><li>Securing External facing site<br /><ul><li>Enable ViewPageLockdown Feature </li></ul>http://technet.microsoft.com/en-us/library/cc263468.aspxstsadm -o activatefeature -url <site collection url> -filename ViewFormPagesLockDownfeature.xml<br /><ul><li>Allowing and denying access by using the Web.config filehttp://technet.microsoft.com/en-us/library/ee191479.aspx</li></ul><location path="_vti_bin“> <system.web> <authorization> <deny users="?" /> </authorization> </system.web> </location><br />
  90. 90. Securing Sensitive documents<br /><ul><li>Use Separate Site Collection (if possible)
  91. 91. Break permission inheritance & disable Anonymous
  92. 92. Set NoCrawl property to True
  93. 93. Exclude Library in SSP Search Index crawling
  94. 94. HTTPHandler to retrieve document - use following in code to retrieve document from library. SPSecurity.RunWithElevatedPrivileges (delegate() { <Insert/Select code to document library>})</li></li></ul><li>Tools<br /><ul><li>WSPBuilder (v 2007)
  95. 95. Package of related file set deployable to SharePoint from VS.NET
  96. 96. Copy to 12 Hive -> Use once a features is deployed
  97. 97. You can controls where the assemblies will go (Bin vs. GAC). Bin is preferred because GAC assemblies runs in full control by default.
  98. 98. Highly configurable
  99. 99. Andrew Connell stsadm extensions
  100. 100. Usage: Create Site columns, content types from SharePoint GUI and use following to generate XML to create them as a Feature
  101. 101. Generate Site columns from existing SharePoint infrastructure</li></ul>STSADM.EXE -o GenSiteColumnsXml -url http://wcm -outputFile "c:siteColumns.xml“<br /><ul><li> Generate Site Content Types from existing SharePoint infrastructure</li></ul>STSADM.EXE -o GenContentTypesXml -url http://wcm -outputFile "c:ContentTypes.xml"<br /><ul><li> Generate Site columns from existing SharePoint infrastructure</li></ul>STSADM.EXE -o GenSiteColumnsXml -url http://wcm -outputFile "c:sitecolumn.xml“<br /><ul><li> http://www.andrewconnell.com/blog/articles/MossStsadmWcmCommands.aspx</li>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×