Microsoft Office SharePoint Server 2007 As a Development Platform

1. Microsoft Office SharePoint Server 2007 As a Development Platform Peruri Srinivasulu psrinivasulu@bennettadelson.com Sept 24 ,2009

2. Agenda • Typical Development Projects • Technology Overview of MOSS 2007 • Platform Architecture • Understanding Customizations vs. Custom Components (Applications) • Development Life Cycle • Deployment • Q&A

3. Typical Web Application - Development Project Scenarios • Forms Applications – LOB with basic CRUD operations. • Event Driven and Workflow based Applications – Approvals, Reviews • Search / Retrieve – Data from LOB and Enterprise Systems. • Reporting data from LOB andEnterprise Systems. • Classifications • Collaborative / Content Management /Forms • OLTP – Transactional Systems (Financial, Orders, B2B) etc… • Data warehouse

4. A typical Distributed Application – Logical Architecture

5. Typical Distributed applications – Quality of Service needs • Scalable • Secured • Reliable / Highly available • Manageable • Monitoring , Patch management , etc…

6. Typical Distributed Applications - Deployment • XCOPY, MSI’s

7. Business Intelligence Collaboration Windows SharePoint Services Portal BusinessProcess Content Management Search Overview of MOSS Server-based spreadsheets plus BI portals built on SQL Server Analysis Services Next generation e-mail, project management, blog and wiki support Server-based forms and workflow with smart client and browser interfaces Enhanced SharePoint Portal aggregation and personalization Integrated document, records and Web content management Great relevance with rich search of people and business data

8. SharePoint Development Platform

9. SDK – Software Development Kit • Everything you see in previous slide is exposed through APIs – • Rich Object Model, SOAP, Events. • A well documented APIs and rich set of samples (How To’s). • Extensible Object Model • Key to the adoption by the Developer Community.

10. Customizable Elements in a SharePoint Web Application • Site Collection • Site • Lists and Folders • Document Folders (type of list) • Images, Documents, Style Sheets, Java scripts, Templates, etc… • List Items • E.g. Pages, News, Tasks , Orders, Suppliers, Document • Fields • Properties /Metadata of List Items • Master Pages & Layouts • Content Types • Policies • Auditing, Versioning, Archive etc… • Workflows • Approvals , Reviews, Custom ….. • Features

11. SharePoint Page • Controlled Layouts – Look & Feel, Styles, Fonts Master Page Page Layout Web Part Zone Web Part Zone

12. Web Parts ASP.NET 2.0 Runtime WSS V3 Runtime WSS Web Parts ASP Web Parts ASP Web Parts WSS V2 Runtime WSS Web Parts WSS Web Parts

13. Web Parts – When do I create one • When Out-of-Box web parts not meeting the requirements. • Need to retrieve/submit data to external data sources (data stored outside of SharePoint). • BDC to the rescue. – MOSS Enterprise Edition. Look into Developer Community before Creating one  www.codeplex.com

14. What is Business Data Catalog? • A catalog of business data • Access to LOB Data in SharePoint

15. Business Data Catalog – Application Definition • What is it? • XML that connects LOB Data to SharePoint • Contains • Connection information / Security • Entities (what exists) • Methods (how to access it) • Associations (relationships between entities) • Actions (external interaction) • Use SDK

16. Customization Options & Tools Change Site Logo, Format, Parts Browser complexity Change Colors, Backgrounds, Fonts Edit CSS files SharePoint Designer • Change Page Layout and Content • Edit Master PagesEdit Page Templates (MOSS only) Share Your Customization with Others Build Themes and Site Definitions SPD + Visual Studio

17. Office SharePoint Designer + Browser Microsoft Visual Studio Web site construction Custom Coding (if necessary) Create lists and doclibs Web Controls and Parts Design Page Masters/ Page Layouts ASP.NET page coding No-code data view/forms Workflow actions No-code workflows Event handlers Web part hookup Development Tools - Choices

18. Package Customizations for Deployment • Featuresenhance modular provisioning • Group logical elements into scenario-driven “features” • New features can be activated in existing site to add functionality. • Features scoped at web, site, web application, farm • Features can be add to and reused across site definitions. • Staple Features to existing Site Definitions. • Solutions • SharePoint features, webparts, and files are deployed using a solutions file with the extension wsp. The wsp files are actually just a “.cab” file. • Solutions can be deployed to the Farm using Central Admin or STSADM.exe

19. Sample Features / Solutions

20. Application Templates for Windows SharePoint Services 3.0 • Application templates are out-of-the-box custom scenarios tailored to address the needs and requirements of specific business processes or sets of tasks in organizations of any size. They also provide a starting point for partners and developers looking to build deeper SharePoint-based solutions.

21. 40 Application Templates

22. Development Life Cycle for SharePoint Projects • Requirements • Build • Source Control Management • Testing • Deploy • Packaging Customizations into Features and Solutions.

23. Team Development for MOSS - Individual Developer Visual Studio Extensions for SharePoint

24. Push Code from Build Servers to Integration

25. Promotion of Code and Content to Production • Code - Assembly • Content - Artifacts

26. For a large scale SharePoint custom application Deploy .wsp files , Activate Features

27. References • http://www.microsoft.com/downloads/details.aspx?FamilyId=6D94E307-67D9-41AC-B2D6-0074D6286FA9 • MOSS SDK • http://technet.microsoft.com/en-us/library/cc263199.aspx • Lots of Visio – MOSS Architectures. • http://www.codeplex.com • Community Tools for SharePoint • WSPBuilder , SharePoint Features • http://www.microsoft.com/downloads/details.aspx?familyid=7BF65B28-06E2-4E87-9BAD-086E32185E68&displaylang=en • Visual Studio Extensions for SharePoint

28. Q&A