1. Microsoft Office SharePoint 2007 Technical Enablement Tour Patrick Tisseghem (Managing Partner – U2U) patrick@u2u.be

2. Introducing the Microsoft Office Forms Server

3. © 2006 Microsoft Corporation. Agenda ●Office Forms Server ●The Business Data Catalog

4. © 2006 Microsoft Corporation. Microsoft InfoPath ●Rich-client desktop app ●Platform creation and delivery of electronic forms  Capture business data  Dynamic, XML-based forms  Rich data entry and validation  Automate business processes  Integration with multiple back- end systems and services  Rapid solution development  Conditional and rule-based logic  Script and.NET support

5. © 2006 Microsoft Corporation. Challenges ●Forms can only be filled in with smart client ●Hard to offer off-line capabilities ●Integration in Office and own apps ●Programming against InfoPath OM is often a challenge on its own

6. © 2006 Microsoft Corporation. The InfoPath Template Manifest XSF Default Sample XML Views XSLT Main Data Source XSD Secondary Data Sources XSD Code.NET JS/VBS Resources XSN File

7. © 2006 Microsoft Corporation. Designing InfoPath Templates ●Basically same steps as designing an InfoPath 2003 template ●Improvements for template designers –New controls –Additional functions (date-related operations) –Better management of data connection definition files –Better off-line support –Re-use InfoPath chunks via template parts –Document and data importers

8. DEMO Designing an expense report

9. © 2006 Microsoft Corporation. Publishing InfoPath Templates ●Publishing wizard –As an Installable File (MSI or JS) –To a Network Folder –Via an Email –To a SharePoint Library ●InfoPath Forms Services –Part of MOSS 2007 –Available as stand-alone product on top of WSS v3 –Fill out InfoPath forms with or without the InfoPath client

10. © 2006 Microsoft Corporation. InfoPath Forms Solutions Topology InfoPath Client (Design Mode) IntranetExtranet / Internet Browser InfoPath Client (Edit Mode) Server Farm Forms Services IW : InfoPath Designer Developer : VS Tools Browser InfoPath Client (Edit Mode)

11. DEMO Deploying for a browser-based scenario

12. © 2006 Microsoft Corporation. Integration with WSS v3 ●Windows SharePoint Services 2007 –Form Template Library ●Master library of all admin deployed forms –Document Libraries ●Multiple form templates per library –Content Type Templates ●Simplify document library creation

13. © 2006 Microsoft Corporation. Integration with Office 2007 ●Forms in Email –Integrate the InfoPath forms experience with Outlook ●Office - Document Life Cycle –Workflow –Document Information Panel

14. © 2006 Microsoft Corporation. Integration in Custom Applications ●Web Applications –Opening forms from links in Web pages –Embedding forms in aspx pages using the XMLFormView ASP.NET control ●Windows Applications –ActiveX hosting of InfoPath in native or managed application ●Rich API exposed –Interact with InfoPath content

15. © 2006 Microsoft Corporation. Supporting the.NET Developer ●Fully Managed (CLR 2.0): No more PIAs ●System.Xml: No more MSXML ●Improved Development Experience –Visual Studio Tools for Applications (VSTA) ●Out of the Box development ●Lowers the bar for forms with managed code ●Compatible with Visual Studio Tools for Office –Visual Studio Tools for Office (VSTO) ●Embedded designer for professional devs ●One IDE for all your projects: Workflow, etc. ●Integrated toolbox, project wizard, etc.

16. DEMO Integrating InfoPath in your own apps

17. © 2006 Microsoft Corporation. Customer Needs Based on SPS 2003 feedback ●Less integration code ●Deep integration of data into the places users work ●New application types that blend data and collaboration ●Lack of structured data search ●Bridge portal and business application UI ●Centrally manage security, auditing, connections

18. © 2006 Microsoft Corporation. Business Data Catalog (BDC) Connects Office servers to business data MetadataMetadata Business Data Catalog Web Parts ListsListsSearchSearch User Profiles Custom Apps DatabaseDatabase WS Proxy ADO.NETADO.NET Web Service List store SearchIndexSearchIndex Profile Store

19. © 2006 Microsoft Corporation. Design Motivations Why do we need the BDC? ●No code integration ●Centralized deployment ●Low latency ●Centralized data security ●Designed for portal & collab. scenarios –Data query, indexing, personalization ●The BDC is not: Transactions, workflow, data transformation, adapters

20. © 2006 Microsoft Corporation. Business Data Web Parts Simple business apps with no code ●Scenario –360-degree view of customer ●Today –Clipping, custom web parts, data view ●MOSS 2007: Reusable biz data web parts –Show new data with no new code or binaries –Master-detail applications with no code –Integrated with dashboards and filters –Customizable in FrontPage

21. DEMO Bringing in business data in SharePoint sites

22. © 2006 Microsoft Corporation. Business Data Search Search data, not just documents ●Scenario: Find an account manager in Siebel ●Today –Vertical applications lack full-text search –Most users can’t locate or access vertical apps –Hard to crawl business data with SharePoint ●MOSS 2007: Search any database or web service –No need to write custom IFilters or protocol handlers –No need to create HTML representations of data –Highly customizable results –Integrated with scopes and search center

23. DEMO Searching for business data

24. © 2006 Microsoft Corporation. Business Data in Lists Collaborate around business data ●Scenarios –Tag a proposal with a customer –Track and annotate key support cases –Pick from the canonical list of cost centers ●Today –Text or lookup fields –Irregular data, duplicated lists of values ●MOSS 2007: Business data column –One column type that stores any entity –One-click refresh –Integrates with list features: workflow, versioning, etc.

25. DEMO Looking up business data in lists

26. © 2006 Microsoft Corporation. Business Data in User Profiles Business-specific targeting & personalization ●Scenarios –Show news about your customers –Automatically filter dashboard by region ●Today –Code required to augment user profile with non-Active Directory data –Personalized web parts require custom code ●Office 12: Join user profile store and BDC –Map user profile property to field of entity –Filter web parts with user-profile filters

27. © 2006 Microsoft Corporation. Review ●Office Forms Server ●The Business Data Catalog

28. Questions?

29. Section title here Sub title here