Deploying Digital Dashboards Howard Crow Lead Product Manager Microsoft 4-303

1. Deploying Digital DashboardsHoward CrowLead Product ManagerMicrosoft4-303

3. Agenda • DDRK • Architecture • Working with Parts • Dashboard Schema • Deployment • Part Distribution • Freedom2 • Questions

4. What’s New • Standardized nuggets – Web Parts • Share Web Parts • XML and WebDAV architecture • Open, extensible, internet ready • Designed as a Service • Hosted on the Server • Runs in IE Stand-alone • XSL skins can support many platforms

5. Resource Kit • Designed to help you understand the new Digital Dashboard Framework • SQL Server Sample Digital Dashboard • File System Sample Digital Dashboard • Digital Dashboard Service Component • Web Part SDK Documents • Web Part Builder • Web Part Gallery • The Web Store is Coming!

6. Choosing A Sample Store Advantage File System Simple Web Part Building Small Deployments SQL Server Relational user and part management Better Personalization security Scalable Application Server Exchange Web Store Active Directory Integration Office Integration Offline support Streaming Media Native WebDAV/XML

7. Installing The Samples • Requirements • Windows 2000 + IIS + (SQL 7) • Must have IP resolution • What is installed • Dashboard Factory • Admin Dashboard & Sample Web Parts • SQL WebDAV IIS Extension • Updates • www.Microsoft.com/digitaldashboard

8. Administration • Admin dashboard • One stop admin of all dashboards • Also manage parts • The only way to create a root dashboard • Great use of Digital Dashboard Service Component • Permissions (SQL) • File system managed in file system

9. Build A DashboardDemo

10. How The Samples Work

11. Architecture Digital Dashboard Office, Outlook, and IE WebPart WebPart WebPart WebPart Context, notification, and messages Digital Dashboard Services Component IIS Assembly of parts, dashboard and styles Dashboard Factory Dashboard.asp XSL ..Edit.asp XSL Dashboard APIs for read and writes Store.vbs WebDAV WebDAV Exchange 2000 SQL Server File System Storage of dashboard and part metadata

12. What Is A Web Part • Reusable component for rendering web content and services inside a digital dashboard • It is a document – HTML, XML, JS, VBS • Wrapped in rendering properties • Defined XML Interchange format • Stored in two parts • Document – HTTP Put, Get • Properties – WebDAV PropPatch • A Dashboard is a Folder of Parts

13. The Dynamic Dashboard • User Requests a Dashboard with a URL • Combination Factory + Dashboard • Dashboard makes webDAV call to folder • Security token is passed • XML stream is returned • Filtered for permissions • Dashboard XSL Transforms into dashboard • HTML is returned to client

14. Build A Web PartDemo

15. Deployment

16. Deploy With File System Only for small deployments • Everyone sees same dashboard • Save Dashboard in a folder called Template • Use wwwroot_default.asp • Save as default.htm in root • Creates an instance of template for each user • Redirects user from http://server • Parts updated through MasterPartLink

17. Deploy On SQL • Every dashboard has 2 states • Global – “template” • User – everyone sees a different view • Stored in a join table • Create a dashboard for each group • Deploy URL by department • Make default.asp a redirect • Assign url to AD OU - home dashboard • Script default.asp to AD

18. Outlook And Offline • Further Reading: July MSDN Mag • In Internet Explorer • Set as Offline Favorite • 2 Levels offline • Deploying in Outlook • Hosted as Folder Home Page – 2 levels • To Host in Outlook Today, use special registry switch [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\9.0 \Outlook\Webview\mailbox] "url"=http://digidash/home.htm "navigation"="yes"

19. Types Of Digital Dashboards • Personal Digital Dashboard • Personal Settings • Visible only to me • Team/Dept. Digital Dashboard • Everyone sees the same dashboard • Admin manages the look and feel • Corporate Portal • Hybrid • Parts and Dashboards

20. Customization • Tied directly to NT Security • Applies to Dashboards and Parts • Levels of Access • No Access – Can’t See • No NT access • Read Only – Can see, but not • Read access in NT • Personalize – Change General Props • Available only in SQL • Modify • Read & Write

21. Customization Demo

22. Dashboard Catalog • Corporate Catalog of Web Parts • Users can add parts to dashboard • Accepts .DWPs and WebDAV parts • Updates • IN SQL, everyone shares the same part • In File System us MasterPartLink • Extended Schema for Categorization • Searching Parts • Personalization

23. Enterprise Decision PortalDeployment And InteroperabilityJason Welchfreedom Architecture GroupInfoImage, Inc.4-303

24. Agenda • Real-world issues in deploying enterprise portals • freedom 2 Architecture Overview • freedom 2 + Web Parts = Interoperability • Demo • freedom 2 vs. DDRK 2.0

25. About InfoImage, Inc. • A Leading Enterprise Portal Software Company • A Microsoft Global Alliance Partner • Founded in 1992 • Offices nationwide • 300 employees

26. About The freedom 2 Decision Portal • A platform for developing, deploying, and maintaining enterprise portals that offer high degrees of scalability and interoperability

27. Real-World Issues In Deploying Enterprise Portals • Directory management • Object management • Integration with back-end systems • OLTP • OLAP • Reporting • Integration with collaborative systems • Scalability

28. Real-World Issues In Deploying Enterprise Portals • Flexibility • Reuse • Multiple Browser Support • Both Extranet and Intranet • Quick Deployments • Disconnected Users • Wireless

29. freedom 2 Architecture Overview

30. Architecture Overview • Federated Portal Architecture • Distributed • Metadata-driven • Based on Windows DNA • Not based on the DDRK • Our Goals • Scalability • Interoperability • Centralized management • Flexible framework with a rich programmability model • Ease of integration

31. Architecture Model USER Freedom Center Presentation Services Digital Business Identity/Personalization Freedom Federated Services Portal Layout Integration Rules Queries & Reports Portal Content Discovery Data Integration Security Object Rels Taxonomies Metadata Repository Management Configuation Versioning Registration Interchange Installation Deployment Tools Administrator Developer

32. Physical Architecture • Client support • MS IE 4 and 5 • MS Outlook 2000 • Other HTML 3.2 compliant browsers • Directory services based on Active Directory • Federated services engine based on COM+ and XML

33. Physical Architecture • Metadata repository • Microsoft Repository • SQL Server 7.0 • Tools • Microsoft Visual Studio • MMC • freedom Federation Tools

34. freedom 2 + Web Parts = Interoperability

35. Why Are Web Parts Important ? • Standard specification • Interoperability • We encourage our competitors to also adopt Web Parts • Extensibility

36. freedom 2 And Web Parts • freedom support for Web Parts • Store produces extended Web Part XML • Viewer consumes extended Web Part XML • Tools to import Web Part definitions (.DWP) • Tools to create/register new Web Parts within freedom • Tools to export Web Part definitions • Support for DDSC functionality

37. freedom 2 And Web Parts • Proprietary extensions to Web Part definitions • Added on import • Stripped-out during export • Once imported, freedom specific lifecycle, propagation, and personalization rules apply

38. Web Parts/freedom Architecture freedom Center (viewer) HTML Client Portal Definition + Decision Object XML FCD(Store Module) Import Facility ADO .DWPfile freedom Store Apply freedom Extensions to form Decisions Objects Export Facility Remove freedom Extension

39. Demo…

40. freedom 2 Versus DDRK 2.0 • InfoImage Federated Portal Architecture gives Enterprise Abilities • Scalability • Manageability • And now… Interoperability • Advanced Personalization Services • Advanced, Heterogeneous Data Integration