Moss 2007 Wcm Architecture And Development Best Practices In A Team Based Environment


Published on

SharePoint Saturday Kansas City

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Moss 2007 Wcm Architecture And Development Best Practices In A Team Based Environment

  1. 1. MOSS 2007 - WCM Architecture and Development Best Practices in a team based environment<br />KarthikVenkataraman<br />
  2. 2. Agenda<br />Architecting a MOSS-Internet Facing Site<br />Content Management Techniques<br />Team Based Development<br />Deployment Configuration<br />Code Deploy / Content Deploy<br />Tiered Development Model <br />DEV-STAGE-PRODUCTION<br />Questions?<br />
  3. 3. About Me<br />Background:<br />SharePoint Architect with focus on ECM, WCM<br />Software Developer working with MS technologies<br />MS degree in Comp Science – UMKC<br />From India with a not so easy to pronounce last name..<br />Call me Kar or Car-Thick!<br />
  4. 4. Introduction<br />Slide content - Experiential<br />Partial focus on Architect/Senior developer topics<br />Some background in MOSS is assumed<br />Working background in Visual Studio is assumed<br />Snapshots of identified scenarios<br />Concepts<br />Questions – Raise your hand!<br />
  5. 5. WCM in MOSS 2007<br />WCM Options in MOSS 2007<br />Publishing Portal<br />Collaboration Portal<br />Publishing Portal<br />starter site hierarchy for Internet website <br />Workflow is enabled <br />Collaboration Portal<br />starter site for Intranet portal<br />Workflow is not enabled by default<br />
  6. 6. Design / Architectural Elements<br />Consists of:<br />Custom Branding <br />Master Pages / CSS<br />Content Authoring <br />Custom Page Layouts <br />Source Control<br />Deployment<br />Custom / STSADM for Code<br />Custom / CD for Content<br />
  7. 7. Content Management<br />Authoring Techniques<br />Smart Client authoring<br />Create content using Office tools<br />Deploy as HTML pages<br />Browser-based authoring<br />In-context, rich-text editing experience<br />Add-ons support from third-party<br />Customizable editing and HTML toolbar<br />Commonly used approach for Content Management<br />
  8. 8. Design and Planning<br />Information Architecture Plan<br />Site Structure <br />Site collections, Sites, Pages<br />Roles and Permissions <br />People and Groups<br />Inheritance model <br />Branding and Customization<br />OTB versus Custom Development<br />Use Features and Packaged development<br />Backup, Recovery and Archival Planning<br />
  9. 9. Implementation<br />Framework Design<br />Identify Core functionality early in the design process for re-use<br />Build Base libraries inheriting from the WSS 3.0 and ASP.NET OM<br />MOSS Artifacts<br />Group UI artifacts and identify repositories for storage (CSS, Images etc)<br />Group functional modules and re-usable components (ASPX, ASCX)<br />
  10. 10. Pause<br />Questions?<br />
  11. 11. Server based Development!<br />Runs on Windows Server 2003 <br />server/remote debugging<br />External tools to emulate team development<br />Virtual Machines<br />Customized Deployment scripts<br />Source Control Integration<br />Needs specific structuring<br />Overall, not a seamless experience (yet!)<br />Challenges<br />
  12. 12. Conceptual Architecture<br />
  13. 13. MOSS 2007/VS2005/TFS<br />Virtual PC 2007 <br />H/W – At least 1.5 GHz with 4GB RAM<br />Base Install of Windows Server 2003 R2<br />Install SQL Server 2005 and MOSS 2007 (SP1)<br />Install SP Designer and Office 2007 (as needed)<br />Visual Studio Team System <br />Visual Studio 2005<br />Team Explorer 2005<br />WSS 3.0 / VS Extensions for SharePoint<br />How to Create a MOSS VPC Image link below:<br /><br />
  14. 14. Source Control<br />Visual Studio / Team Foundation Server 2005<br />Source Control<br />Project Management and Reporting<br />Integrates with TFS using Team Explorer<br />Source Control Explorer<br />
  15. 15. VSTS Solution Architecture<br />Visual Studio Solution<br />Web Application Test Harness<br />Core Class Library Project<br />SharePoint Integration Project<br />Web Application Project<br />Allows for RAD using ASP.NET<br />Can be used as a test harness<br />Class Library Project<br />Framework consisting of Base classes, DAL/BLL<br />SharePoint Integration Project<br />Mimics 12 Hive<br />Allows for deployment to local VPC<br />
  16. 16. MOSS Deployment<br /><ul><li>VSTS 12 Hive Structure
  17. 17. Maps to SharePoint 12 Hive
  18. 18. Relates code artifacts to MOSS
  19. 19. Generate WSP Solution
  20. 20. Packages “Features” into .wsp
  21. 21. BuildSharePointPackage.ddf
  22. 22. MakeCAB
  23. 23. Deploy Package
  24. 24. RemoveAndDeploy.bat
  25. 25. STSADM commands for deploying .wsp into MOSS Solution Store</li></li></ul><li>Custom Deployment<br />
  26. 26. Process must<br />be repeatable/failsafe<br />allow for flexible deployments<br />be configurable by environment<br />Options<br />Manual scripts with XCOPY<br />Server builds (MSBuild) and PsExec<br />Third Party tools (FinalBuilder)<br />Code - Build and Deploy<br />
  27. 27. DEV-STAGE-PRODUCTION<br />Variations include H/W and S/W specifications<br />E.g.: Dev could be 32-bit single-server farm while STAGE/PROD is 64-bit dual-server<br />Content Deploy versus Code Deploy<br />In WCM scenario, typically STAGE is an authoring environment with live content<br />Code deploys follow exact procedures while Content Deploys are fluid in nature<br />Content Deploys using CD API / Third party tools<br />Environment Considerations<br />
  28. 28. Hardening a MOSS Server Farm<br />Topology<br />Firewalls b/w App Server, DB servers<br />Logical Architecture<br />Configure Anonymous Access<br />SSL for content deployment<br />Block access to CA<br />Lockdown Mode<br />Secure Permissions for published sites<br />Ports, Protocols and IIS<br />
  29. 29. Production Environment<br />Design Considerations<br />Consists of Default (Windows zone) and extended Internet Zone<br />Internet Zone is configured for Anonymous access<br />Alternate URL Mappings for multiple public URLs<br />Security Considerations<br />Read Only access to content on the Internet zone<br />Secure user permissions and lockdown user access to admin folders<br />
  30. 30. Development Best Practices<br />VPC Set Up<br />Use differencing disks to build a clean image<br />Install software with latest Service Packs<br />External HDD / Allocate at least 2 GB of memory<br />Role based development<br />Understand functional impact in different SP roles – End-User, Admin, Stakeholder<br />Resources<br />Keep up to date with MSDN/SharePoint releases<br />Use the SP community and blogs<br />
  31. 31. Tips N Tricks<br />Cross Browser testing for WCM sites<br />Optimizing page size for anon access (Core.js)<br />Configuring anon access on Internet Zone<br />32-bit versus 64-bit components<br />Third party components (make sure they are packaged as MOSS solutions for easy install)<br />Performance counters for metrics after go-live<br />For advanced tips, check in with author after session!<br />
  32. 32. Speaker Blog: <br /> (tat-tvam-asi)<br />Thou art that | That you are<br />References<br />MSDN<br /><br />TechNet site for MOSS 2007<br /><br />Wrap Up<br />
  33. 33. Thanks for attending!<br />Questions?<br />Contact: <br /><br /><br />Blog:<br />