Deploying Digital Dashboards

Deploying Digital Dashboards Howard Crow Lead Product Manager Microsoft 4-303 Agenda         DDRK Architecture Working with Parts Dashboard Schema Deployment Part Distribution Freedom2 Questions What’s New  Standardized nuggets – Web Parts  Share Web Parts Open, extensible, internet ready  XML and WebDAV architecture   Designed as a Service  Hosted on the Server XSL skins can support many platforms  Runs in IE Stand-alone  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! Choosing A Sample Store File System Advantage Simple Web Part Building Small Deployments Relational user and part management Better Personalization security Scalable Application Server Active Directory Integration Office Integration Offline support Streaming Media Native WebDAV/XML SQL Server Exchange Web Store Installing The Samples  Requirements   Windows 2000 + IIS + (SQL 7) Must have IP resolution Dashboard Factory Admin Dashboard & Sample Web Parts SQL WebDAV IIS Extension  What is installed     Updates  www.Microsoft.com/digitaldashboard 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 Build A Dashboard Demo How The Samples Work Architecture Office, Outlook, and IE Context, notification, and messages Assembly of parts, dashboard and styles Dashboard APIs for read and writes Digital Dashboard WebPart WebPart WebPart WebPart Digital Dashboard Services Component IIS Dashboard Factory Dashboard.asp XSL ..Edit.asp XSL Store.vbs WebDAV WebDAV Storage of dashboard and part metadata Exchange 2000 SQL Server File System 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 Document – HTTP Put, Get Properties – WebDAV PropPatch  Stored in two parts    A Dashboard is a Folder of Parts The Dynamic Dashboard  User Requests a Dashboard with a URL  Combination Factory + Dashboard  Dashboard makes webDAV call to folder  Security token is passed Filtered for permissions  XML stream is returned    Dashboard XSL Transforms into dashboard HTML is returned to client Build A Web Part Demo Deployment 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 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 Assign url to AD OU - home dashboard Script default.asp to AD  Make default.asp a redirect   Outlook And Offline   Further Reading: July MSDN Mag In Internet Explorer   Set as Offline Favorite 2 Levels offline Hosted as Folder Home Page – 2 levels To Host in Outlook Today, use special registry switch  Deploying in Outlook   [HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\9.0 \Outlook\Webview\mailbox] "url"=http://digidash/home.htm "navigation"="yes" Types Of Digital Dashboards  Personal Digital Dashboard   Personal Settings Visible only to me Everyone sees the same dashboard Admin manages the look and feel Hybrid Parts and Dashboards  Team/Dept. Digital Dashboard    Corporate Portal   Customization    Tied directly to NT Security Applies to Dashboards and Parts Levels of Access  No Access – Can’t See  No NT access Read access in NT Available only in SQL Read & Write  Read Only – Can see, but not   Personalize – Change General Props   Modify  Customization Demo Dashboard Catalog  Corporate Catalog of Web Parts   Users can add parts to dashboard Accepts .DWPs and WebDAV parts IN SQL, everyone shares the same part In File System us MasterPartLink Searching Parts Personalization  Updates    Extended Schema for Categorization   Enterprise Decision Portal Deployment And Interoperability Jason Welch freedom Architecture Group InfoImage, Inc. 4-303 Agenda      Real-world issues in deploying enterprise portals freedom 2 Architecture Overview freedom 2 + Web Parts = Interoperability Demo freedom 2 vs. DDRK 2.0 About InfoImage, Inc.      A Leading Enterprise Portal Software Company A Microsoft Global Alliance Partner Founded in 1992 Offices nationwide 300 employees About The freedom 2 Decision Portal  A platform for developing, deploying, and maintaining enterprise portals that offer high degrees of scalability and interoperability Real-World Issues In Deploying Enterprise Portals    Directory management Object management Integration with back-end systems    OLTP OLAP Reporting   Integration with collaborative systems Scalability Real-World Issues In Deploying Enterprise Portals        Flexibility Reuse Multiple Browser Support Both Extranet and Intranet Quick Deployments Disconnected Users Wireless freedom 2 Architecture Overview Architecture Overview  Federated Portal Architecture     Distributed Metadata-driven Based on Windows DNA Not based on the DDRK Scalability Interoperability Centralized management Flexible framework with a rich programmability model Ease of integration  Our Goals      Taxonomies Installation Object Rels Deployment Security Architecture Model USER Freedom Federated Services Freedom Center Presentation Services Digital Business Identity/Personalization Administrator Versioning Queries & Reports Tools Management Configuation Registration Interchange Portal Layout Metadata Repository Developer Integration Rules Portal Content Discovery Data Integration 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 Physical Architecture  Metadata repository   Microsoft Repository SQL Server 7.0 Microsoft Visual Studio MMC freedom Federation Tools  Tools    freedom 2 + Web Parts = Interoperability Why Are Web Parts Important ?   Standard specification Interoperability  We encourage our competitors to also adopt Web Parts  Extensibility 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 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 Web Parts/freedom Architecture freedom Center (viewer) HTML Client Portal Definition + Decision Object XML FCD (Store Module) ADO Import Facility Apply freedom Extensions to form Decisions Objects freedom Store .DWP file Remove freedom Extension Export Facility Demo… 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