1. 1 Architecting End-to-End Enterprise Solutions with Microsoft Office InfoPath 2003 Kamaljit Bath Lead Program Manager Microsoft Corporation Kamaljit Bath Lead Program Manager Microsoft Corporation Session Code: Dat350 Speaker: Please: 1. fill in your session code, and 2. copy the appropriate “Virtual Track” icon(s) onto the title slide.

2. 2 Agenda InfoPath - Key Business Values Enterprise Scenario Demo InfoPath Architecture and Programming Model Web Services Interop BizTalk 2004 Interop Other Server and Data Interop Additional Resources InfoPath - Key Business Values Enterprise Scenario Demo InfoPath Architecture and Programming Model Web Services Interop BizTalk 2004 Interop Other Server and Data Interop Additional Resources

3. 3 What is InfoPath? A new program in Microsoft Office System Included in Office Pro Ent. Ed. 2003 Available standalone A desktop application The platform for a new generation of electronic forms A new program in Microsoft Office System Included in Office Pro Ent. Ed. 2003 Available standalone A desktop application The platform for a new generation of electronic forms

4. 4 InfoPath – Key Business Values Rich Office editing experience Spell check, rich UI, validation, offline … End-user oriented XML Authoring tool Out-of-box support for XML and XML Web services Support for customer-defined schema Deployment and RAD environment WYSIWYG design from existing schemas, XML Web services, etc. Visual Studio/Managed code integration Solution Caching & auto update Rich Office editing experience Spell check, rich UI, validation, offline … End-user oriented XML Authoring tool Out-of-box support for XML and XML Web services Support for customer-defined schema Deployment and RAD environment WYSIWYG design from existing schemas, XML Web services, etc. Visual Studio/Managed code integration Solution Caching & auto update

5. 5 Client Server InfoPath integration with the enterprise ecosystem Solution front-end Data Validation Workflow support Collaboration Process integration SQL Server Server InfoPath XML Schema Validation rules Managed code Form library Property promotion XML Web Services HTTP Post XML payloads Rich programming environment XML Web Services Rapid development and deployment Rich editing UI integration with other Office apps Rule engine SharePoint BizTalk InfoPath InfoPath Support SAP,Siebel..

6. 6 Sales Call Report Kamaljit Bath Lead Program Manager Microsoft Office InfoPath 2003 Kamaljit Bath Lead Program Manager Microsoft Office InfoPath 2003

7. 7 InfoPath: Architecture and Programming Model

8. 8 XML Structural Editing Building an XML document salesReport customers customer items item actions customer items item action

9. 9 Controls are bound to the main XML DOM Controls must be bound to a node in the primary data source’s DOM* All the programming is against Data, not against view, controls What this means: To change the data in a control, you write to the DOM To get the data from a control, you look at the DOM. Controls must be bound to a node in the primary data source’s DOM* All the programming is against Data, not against view, controls What this means: To change the data in a control, you write to the DOM To get the data from a control, you look at the DOM.

10. 10 Programmability Infrastructure OpenEditSubmitClose OnVersionUpgrade OnLoadOnSwitchView OnBeforeChangeOnValidate OnAfterChange OnClickOnSubmitRequest C#, VB.NET, JScript, VBScript XDocument lifecycle Events Event handlers OnBeforeChangeOnValidate OnAfterChange

11. 11 Data Validation Programming: DOM Editing Events ROOT items Totals item total unitPrice sold Bubbling trace Updated node Xml Tree Editing events item::OnValidate() item::OnAfterChange() item::OnBeforeChange() DataDOM Event Site = item Source = sold Operation = Update OldValue NewValue ReportError ReturnStatus ReturnMessage sold ROOT items item

12. 12 InfoPath: Web Services Interop

13. 13 Oracle, DB2, … SAP, PeopleSoft, Siebel,… InfoPath 2003 is a Smart Client for XML Web Services InfoPath BizTalk IIS SQL WSS* XML HTTP SOAP WSDL UDDI.XML SQL Access XML Submit WSS* Submit Save Send *Windows SharePoint Services

14. 14 InfoPath and Web Services Scenarios Design a InfoPath form as a front end to a Web Service Bind a control in an InfoPath form to lookup data from a Web Service call Design mode support UDDI based search for Web Services Generate schema based on selected Web Service call Edit mode support Automatically generate SOAP calls for getting/submitting data Limited OM access to Web Service call parameters Customizable submit for advanced scenarios Scenarios Design a InfoPath form as a front end to a Web Service Bind a control in an InfoPath form to lookup data from a Web Service call Design mode support UDDI based search for Web Services Generate schema based on selected Web Service call Edit mode support Automatically generate SOAP calls for getting/submitting data Limited OM access to Web Service call parameters Customizable submit for advanced scenarios

15. 15 InfoPath and Web Services Web Services Enhancements (WSE) Web Services are widely adopted Provide communication infrastructure WS-I is fully operational Web Services Enhancements (WSE) 2.0 Extends Web Services to support more complex intra- and inter-organizational scenarios Makes Secure, Reliable, Transacted Web services Targeted at early adopters Scenarios for InfoPath integration Connecting to secure Web Services Connect to Web Services over TCP and other protocols

16. 16 InfoPath and Web Services Indigo Integration In the short-term, do it in code Use WSE and Message-Bus APIs directly in InfoPath form Returned XML is automatically bound to form controls Possible enhancements in the long-term Built-in support for Message-Bus in the InfoPath Designer and Editor InfoPath pops-up authentication and other dialogs Built-in handlers for WS-Policy and other metadata tokens In the short-term, do it in code Use WSE and Message-Bus APIs directly in InfoPath form Returned XML is automatically bound to form controls Possible enhancements in the long-term Built-in support for Message-Bus in the InfoPath Designer and Editor InfoPath pops-up authentication and other dialogs Built-in handlers for WS-Policy and other metadata tokens

17. 17 InfoPath: BizTalk Interop

18. 18 Integration scenarios InfoPath BizTalkServer eMail Sharepoint Invoice Database Database 1 2 3 1 2 3 4

19. 19 InfoPath and BizTalk BizTalk 2004 features BizTalk accepts PIs and namespaces You can configure send and receive pipelines to preserve/Remove/Change PIs BizTalk uses XSD so no more issues with XSD/XDR conversion Orchestration can be exposed thru a Web service You can design your workflow starting either from BizTalk or InfoPath BizTalk accepts PIs and namespaces You can configure send and receive pipelines to preserve/Remove/Change PIs BizTalk uses XSD so no more issues with XSD/XDR conversion Orchestration can be exposed thru a Web service You can design your workflow starting either from BizTalk or InfoPath

20. 20 InfoPath and BizTalk Kamaljit Bath Lead Program Manager Microsoft Office InfoPath 2003 Kamaljit Bath Lead Program Manager Microsoft Office InfoPath 2003

21. 21 InfoPath: Other Server and Data interop

22. 22 InfoPath and Yukon XML Data type columns Yukon supports XML data type natively Advanced features for retrieving and updating XML docs stored in the database Hierarchical data can be stored in a relational DB Additional Contact Info Product Manufacturing Instructions Applicant resume InfoPath integration scenarios Build end-to-end solutions around XML data with rich UI and native store capabilities Yukon supports XML data type natively Advanced features for retrieving and updating XML docs stored in the database Hierarchical data can be stored in a relational DB Additional Contact Info Product Manufacturing Instructions Applicant resume InfoPath integration scenarios Build end-to-end solutions around XML data with rich UI and native store capabilities

23. 23 InfoPath and Yukon Retrieving and updating XML data XML Data type Use XML data type methods in SQL to access XML data type column via ADO.NET query(), value(), exist() Use SQL DML to update modify() Relational data Use SQL XML and “For XML” queries to retrieve relational data as XML Use OPENXML() to update XML back into relational data HTTP SOAP Listener WSDL must contain complete schema and no xsi:type declarations Updates need to go back thru custom Web Services XML Data type Use XML data type methods in SQL to access XML data type column via ADO.NET query(), value(), exist() Use SQL DML to update modify() Relational data Use SQL XML and “For XML” queries to retrieve relational data as XML Use OPENXML() to update XML back into relational data HTTP SOAP Listener WSDL must contain complete schema and no xsi:type declarations Updates need to go back thru custom Web Services

24. 24 InfoPath and LOB Servers Siebel Integration Scenarios Populate form fields from Siebel server Create custom forms rapidly to work against Siebel server Create a front-end Web Service to connect to Siebel Use ADO.NET to connect to DB and execute custom stored procs or Call Siebel business objects to access data Create an InfoPath Form based on the Web Service Siebel 7.5 will support Web Services natively Scenarios Populate form fields from Siebel server Create custom forms rapidly to work against Siebel server Create a front-end Web Service to connect to Siebel Use ADO.NET to connect to DB and execute custom stored procs or Call Siebel business objects to access data Create an InfoPath Form based on the Web Service Siebel 7.5 will support Web Services natively

25. 25 InfoPath and LOB Servers SAP Integration Scenarios Populate form fields from SAP Create custom forms rapidly to work against SAP Create a front-end Web Service to connect to SAP Install and configure the.NET Connector from SAP website Create and use SAP connection RFC proxy class C# classes for each unique SAP tables parameter and SAP structures parameter for the selected RFC Use SAP logon classes to create connection string Create an InfoPath Form based on the Web Service Scenarios Populate form fields from SAP Create custom forms rapidly to work against SAP Create a front-end Web Service to connect to SAP Install and configure the.NET Connector from SAP website Create and use SAP connection RFC proxy class C# classes for each unique SAP tables parameter and SAP structures parameter for the selected RFC Use SAP logon classes to create connection string Create an InfoPath Form based on the Web Service

26. 26 InfoPath and LOB servers Summary Scenarios Use InfoPath to easily build rich, custom forms that integrate with LOB servers via standard protocols Rapid development and deployment model for rich, custom forms Start from web service description or custom schema WSYWIG design mode Rich programming environment Dynamic controls to work with XML Simple deployment model like web pages Interoperability with business processes custom XML schemas, Web Services, open standards Rich UI and feature sets for structured data gathering Scenarios Use InfoPath to easily build rich, custom forms that integrate with LOB servers via standard protocols Rapid development and deployment model for rich, custom forms Start from web service description or custom schema WSYWIG design mode Rich programming environment Dynamic controls to work with XML Simple deployment model like web pages Interoperability with business processes custom XML schemas, Web Services, open standards Rich UI and feature sets for structured data gathering

27. 27 Developer Resources InfoPath included in PDC Office Kit Developer Resources DVD @ Product Booth Features Intensive Training, SDK, White Papers PDC Hands on Lab – HOL 607 MSDN InfoPath Developers Center http://msdn.microsoft.com/Office/InfoPath InfoPath SDK, Training, Solutions InfoPath Newsgroup microsoft.public.InfoPath InfoPath included in PDC Office Kit Developer Resources DVD @ Product Booth Features Intensive Training, SDK, White Papers PDC Hands on Lab – HOL 607 MSDN InfoPath Developers Center http://msdn.microsoft.com/Office/InfoPath InfoPath SDK, Training, Solutions InfoPath Newsgroup microsoft.public.InfoPath

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