Groove: Building Enterprise Workgroup Applications Hugh Pyle OFF303 Senior Product Manager Microsoft Corporation

Building Enterprise Workgroup Applications With Groove 3.1 video:

Agenda Groove: What, why, where Groove Forms Groove Web Services Groove Enterprise Data Bridge (EDB) and Process Integration Questions

Surveys … Documents Discussions TasksContacts Members Calendar Team Flexible workspace collaboration tools that match how work gets done Rich client Mobile Cross- organization Small teams Short term Thinclient Thin client Broad reach Searchable Communities Scalability & Availability Long term Ad hoc Collaborative Workspaces Stay on the same page in a common work area

Relay Server Disconnected Employee Partner How Groove Works A hybrid architecture

Relay Server Disconnected Employee Management Server Employee Partner Business Apps. (e.g. Siebel) Databases (e.g. SQL Server) Information Sharing (e.g. SharePoint Portal Server) Enterprise Data Bridge How Groove Works A hybrid architecture

Groove Synchronization Every user change creates a “Delta” Transaction applied to local copy of workspace Queued for dissemination to each other user Via relay if direct connection is not available Queued locally if no communications Groove Dynamics: subsystem responsible for transaction synchronization Guarantees that all users see the same sequence of transactions (even if incomplete) “Push”; also can “fetch” missing transactions

Groove Security All on-disk data is strongly encrypted User passphrase provides the Account key Account file contains list of workspaces, and key for each workspace Each workspace has its own key Workspaces re-keyed on membership change All on-the-wire data is strongly encrypted “Immune to user indifference”

Where Should I Use Groove? Virtual workgroups Geographically dispersed Need to collaborate outside the enterprise Mobile or occasionally connected employees Teams dealing with adverse infrastructure Best fit with: professional services, IT project management and public sector Some new Office “12” integration coming InfoPath, RTC, WSS Extends what we’ll see today

Integration Scenario Contacts form Read data from Groove into Read data from Groove into Using Groove client Write data from into Groove Using Groove EDB Orchestrate Create workspace, add data, invite members

Agenda Groove: What, why, where Groove Forms Groove Web Services Groove Enterprise Data Bridge (EDB) and Process Integration Questions

Agenda: Groove Forms What, why Example applications Demo: build a simple form

Groove Forms Customizable tool for workgroup apps Forms Designer Fields, Forms, Views Forms UI Distributed database Records Parent/Response relationships

Groove Forms: Fields Simple field types Text, Multi-Line Numeric, Currency Checkboxes, Option Buttons, Dropdown, Listbox Extended field types Rich Text AttachmentsContact Others: Script Buttons, layout elements

Groove Forms: Views Multiple views per tool Easy to build views Select columns (scalar, richtext, etc) Select sorting, grouping, defaults Add selection conditions Display only records from selected forms Display only records matching particular criteria User-visible views Hidden views; lookup fields, lookup script

Programmability Scripting in a Form User Interface: DHTML + CSS + Script Add/change/move/show/hide form elements Dynamic validation (on UI events) Record data: Script + Forms API Read/write fields on records Navigate related records Send IM, navigate Non-record data (persistent & non-persistent) Macros (script) Web Services: external access

Design Changes Your Forms design is part of the workspace When design is updated, all workspace members receive the changes Design management facilities: “Save Tool as Template” (GTA) “Save Workspace as Template” (GSA) “Replace Design”

Demo: Building a Form

Forms Examples More on Downloadable solution templates Run “as-is” or customize

Agenda Groove: What, why, where Groove Forms Groove Web Services Groove Enterprise Data Bridge (EDB) and Process Integration Questions

Agenda: GWS What, why, history Example applications Building Groove Web Services applications Web references Headers, security Structure: Account, Identity, Space, Tool, data Forms Data and.NET DataSet

Groove Web Services Groove is a web services server SOAP access to Groove services Accounts, Identities, Contacts Presence / Awareness, Messaging Workspaces, Tools, Data (CRUD) Local UI (navigate, open dialogs) Developer kit provides WSDL, XSD Code samples, Documentation

GWS Applications Local access to Groove Local data integration Adding Groove services to existing applications Remote access to Groove Specialized applications: server-based Security Secret request key in SOAP header Request keys in registry HKCU

Demo: Reading Forms Data Outlook addin Read Forms data from Groove (Groove Forms data is a serialized DataSet) Write to Outlook Contacts

Demo: Writing Forms Data Standalone executable (Windows Forms) Read list data from WSS, to DataSet Write records to Groove

Agenda Groove: What, why, where Groove Forms Groove Web Services Groove Enterprise Data Bridge (EDB) and Process Integration Questions

Groove EDB Component Enterprise Data Bridge: Groove data server Always-OnAlways-Connected Privileged connections – host in data center Scalable workspace member Thousands of workspaces Scalable GWS server Optimized Web services HTTP stack

Groove EDB UI

Casahl Component Third-Party Companion Product: Casahl Off-the-shelf record data synchronization Product bundle available with Groove EDB EDB + Casahl ecKnowledge + Casahl’s Groove connector + one other Reduce or eliminate controller development Build vs. Buy (many connectors available) Scheduled synchronization jobs XML-RPC API for controllers Create synchronization targets and jobs Trigger synchronization, query job status

Integration Examples Siemens Medical Logistics Quote (from Siebel) and/or Sales Order (SAP) Groove workspace created on EDB Initial data populated from SQL Server Invitations sent to members User data synchronized to SQL Server Florida SERT “Constellation” of workspaces Controller listens for GWS events (data change) Groove-to-Groove synchronization

Integration Example Windows SharePoint Services (WSS) site List of contacts List of workspaces Create workspace from template Populate workspace data from WSS list Save invitation file as WSS attachment

Controller Architecture Typical controller – very repeatable Manage workspace status, creation, archival Manage member status, invitations Listen for events Synchronize data on event, or on schedule Deployment options Console application + Task Scheduler Windows Forms application Windows Service

Agenda Groove: What, why, where Groove Forms Groove Web Services Groove Enterprise Data Bridge (EDB) and Process Integration Questions

Community Resources At PDC For more information, go see Hands-On Lab OFFHOL22: Using Groove Web Services in a Windows Forms Application OFF Track Lounge Hugh Pyle, Paresh Suthar, Bob Doyle After PDC Presentation & code on DVD More background: Developer resources:

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.