Twin Cities BizTalk User Group BizTalk 2006

1. Twin Cities BizTalk User GroupBizTalk 2006 September 2005 Stephen Kaufman Principal Consultant Microsoft Consulting Services

2. Disclaimer • This information is based off the beta version of BizTalk 2006 and is subject to change • This information is accurate as of August 2005 • Please check the BizTalk web site, the MSDN BizTalk site as well as the blog sites for additional and updated information

3. Windows Server System Integration Comprehensive Management and Operations • MMC for Enterprise Management • Single View for Operations and Monitoring • Application-level Management • Engine and Infrastructure Investments • Windows 64 bit (x64) • SQL Server 2005 Support • Visual Studio 2005/.NET 2.0 • Virtual Server 2005 Setup, Upgrade and Deployment Business User Empowerment • Real-time BAM Alerting and Notification • BAM Portal and reusable web components • SharePoint Adapter for deeper WSS integration • Simplified Setup • Tools for Enterprise Application Deployments • Seamless upgrade from BizTalk Server 2004 Areas of investment

4. Setup & Migration

5. Improved Setup • Get going faster! • Dramatically simplified one box install experience with minimum number of clicks • Pre-requisite installation • Component downloader included to pull pre-reqs from the Web, SUS Server, pre-downloaded CAB • Friendlier IT focused deployment wizard • Greater flexibility for multi machine installs • Built into the MMC for consistency

6. BizTalk 2006 Upgrade – not Migrate • Seamless upgrade from BizTalk Server 2004 • All artifacts just work • Upgrade requires shutting down BizTalk Server 2004 services, and updating to BizTalk Server 2006 • Migration to BizTalk Server 2006 should not affect accelerators/adapters • Support for SQL Server 2005 • If upgrading to SQL2005, perform SQL upgrade after BizTalk Server 2006 migration

7. Management, Monitoring & Deployment

8. BizTalk “Application” Before  BizTalk “Application” Now  • New concept in BizTalk Server 2006 • Provides complete view of application • Simplifies management • Manage all related artifacts as a unit

9. Management - MMC • Builds on the “BizTalk Application” Concept • Logical collection of BizTalk artifacts • Greatly simplifies management and deployment • Single MMC for Management & Operations • Group & “BizTalk Application” Hub Pages • Scalable UI for handling large amounts of artifacts! • Operations side of Monitoring moved from HAT • Visual Studio no longer required for management!

10. Monitoring & Tracking • Monitoring • Scalable management of runtime instances • Hub pages summarize system health • Resubmit capability • MOM Support • Tracking • Tracking & Reporting API • Messaging Tracking for BAM • Improved Runtime Scalability when tracking enabled

12. Exporting an Application • Accessible via MMC • Right-click application • Choose to export • MSI • Bindings Expense.msi BindingInfo.xml

13. Installing & Importing an Application • Run setup on each server • Copies required assemblies locally • Installs to the GAC • Import Application • Registers DLLs into the BTS configuration dB • Need occur only once • Import into either • Existing application • Create a new application

14. Operations • The Administration Console can now be used to administer multiple BizTalk groups simultaneously

15. Business User Empowerment

16. Business User Empowerment • Significant Investments in BAM • Minor Investment for BAS & Visio • Business Rules Engine remains as-is • No new investment until “Longhorn” timeframe (Windows Workflow Foundation) • Human Based Workflow Engine (HWS) • Human Based Workflow Designer (HWS)

17. BAM Investments • Business Alert experience for end users • Out-of-the-Box Dashboard (BAM Portal) • Native integration with BizTalk Messaging • BAM Interceptor for Pipelines • Updated Tracking Profile Editor • Distributed BAM infrastructure • SDK Samples • Support for Web Parts, Scorecards, SQL Reporting Services • Interception of Web Services (pre-Indigo)

18. Tracking Profile Editor • Support for Messaging • Retrieve Activities from the BAM Database • Activity Centric

19. Screen Shots

25. Core Engine

26. Pipeline Improvements • Large Message Parsing • Large Message Mapping • < threshold performed in-memory • > threshold • Default threshold = 1MB, configured via registry ‘TransformThreshold’ ‘HKLM\\Software\\Microsoft\\BizTalk Server\\3.0\\Administration’. • Pipeline API accessible via ODX \SDK\Samples\Pipelines\Aggregator • Recoverable Interchange Processing

27. Interchange Processing • In BizTalk, an Interchange can contains 2 or more messages, such as a batch • Standard Interchange Processing • At arrival, an interchange is broken down into individual messages & passed to a pipeline • Messages are individually validated, but collected within the end-point manager (EPM) • If any message fails validation the entire interchange, as a single message is suspended • Recoverable Interchange Processing • At arrival, an interchange is broken down into individual messages & passed to a pipeline • Messages are individually validated, but collected within the end-point manager (EPM) • Failed messages are suspended • Successful messages are sent to the message box

28. Interchange Processing in 2006 • Support for either • Standard Processing or • Recoverable Processing • Where to set processing type • Design-time: pipeline property • Run-time: receive location property BizTalk Server 2004 Only Supports Standard Processing

29. Doc5 Doc5 Standard Interchange Processing Example Flat file interchange Endpoint manager Receive pipeline Doc1 Receive location Doc1’ Doc2 Doc2’ Doc3 Doc3’ Doc4 Doc4’ Suspend queue In Message Box Work queue In Message Box Flat file interchange Doc6

30. Doc2 Doc2 Doc5 Doc5 Recoverable Interchange Processing Example Flat file interchange Endpoint manager Receive pipeline Doc1 Receive location Doc1’ Doc3 Doc3’ Doc4 Doc4’ Suspend queue In Message Box Work queue In Message Box Doc6 Doc6’

31. Failed Message Routing in 04 • When message fails within the receive pipeline, messages automatically placed into a suspended state • Messages can be viewed via HAT • Notifications can be sent using MOM • Failed messages cannot be subscribed by end points (i.e., orchestrations or send ports)

32. Failed Message Routing in 06 • New configuration setting on the receive port allows for routing of failed messages. • Provides the flexibility to either suspend failed messages or select to have failed messages be routed • When enabled, failed messages include additional properties: • Subscriptions can be created to route valid messages • Orchestrations can be created to subscribe to failed messages for rich error handling beyond HAT/MOM

33. Message Resume 04 vs. 06 • *Messages requiring ordered delivery (MSMQ, MQSeries) may not be resume-able • Inbound configuration changes affect resumed messages • Failed message routing • Schema updates • Map changes

34. Updated & New Adapters • New adapters out-of-box • MSMQ adapter • MQSeries adapter • POP3 receive adapter NEW • SharePoint Adapter NEW (sort of) • Enhancements in existing adapters • More granular perf counters • Enhanced email composing in SMTP adapter • Usability improvements

35. Commerce Server 06 Adapter • Accelerate integration of eCommerce Websites • Included with CS2006: • Orders • Profiles • Inventory • Orders • Features • Bidirectional • Configuration Wizard • Scenarios • LOB Integration • Multiple Trading Partners • CS Site-to-Site Data Interchange

36. Developer Productivity

37. Developer Tools • Flat-File Import wizard • Visual Studio 2005 support only • Runtime built on .NET Framework 2.0 • Orchestration Designer • Zoom in / Zoom Out • Collapsed and expanded shapes preserved across saves • Array support for Web Services (consuming only, no publishing) • Jagged array support (no multidimensional arrays) • Access the context properties of the message part of a multipart message • Calling pipelines from within orchestrations • Exists operator support for properties • .NET method invocation (ex: public static methods of a .NET class can be called such as invoking pipelines components) • Allow variable number of message parts. • Unique event log id’s for better MOM support. • Add syntax and API’s to access correlation contents.

38. Flat File Import Wizard • Legacy application produces data in the following format: • To enable processing of this format in BizTalk Server developer needs to define a flat file schema • Flat file schema is an xsd with additional flat file annotations PO1999-10-20 US Alice Smith 123 Maple Street Mill Valley CA 90952 US Robert Smith 8 Oak Avenue Old Town PA 95819 Hurry, my lawn is going wild! ITEMS,ITEM872-AA|Lawnmower|1|148.95|Confirm this is electric,ITEM926-AA|Baby Monitor|1|39.98|Confirm this is electric|1999-05-21

39. XSLT Debugging • Which side are you on • You can’t be serious • It’s about time • Remember BizTalk now uses the 2.0 version of the .NET framework & VS 2005 • VS.NET now has XSLT debugging • Jon Flanders Blog discusses 2 methods • http://www.masteringbiztalk.com/blogs/jon/PermaLink,guid,bc5e05f0-659f-4ace-a6fe-d864cdf1fbe2.aspx

40. BizTalk Mapper • Invalid Link improvements • 2004: • 2006:

41. BizTalk Mapper • New Functoids • IsNil (Logical Functoid) • Takes one parameter and returns true if the input is set to Nil • Nil (Value Functoid) • Sets the destination node to Nil • Assert • Takes three parameters • Expression to evaluate or a result from a logical functoid • Text to throw for the exception if the first param is false • Text to use if the first param is true • Only works for assemblies built in development mode

42. External Assemblies • .NET 1.1 & .NET 2.0 be installed side by side on the same box • Custom code that was referenced or called by orchestrations or pipelines in 04 do NOT need to be recompiled • Unless the component uses some of the API’s that have changed or are not supported in 2.0 • Check out the list of breaking changes from 1.1 to 2.0 at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetdep/html/netfxcompat.asp

43. Other Productivity Information • Virtual Server • BizTalk is now supported on Virtual Server 2005 in production • But not recommended for all situations • Web Services • New check box on port selector page • “Merge all selected ports into a single web service” • Pipelines can have per instance configuration

44. Answers to Questions • Will there be an Indigo Adapter? • There will be a community adapter available • Does versioning take place at the application level? • Versioning still takes place at the assembly level • What can the BizTalk Explorer configure versus the Admin Console? • The Admin Console has been updated to be more robust and is capable of viewing and configuring artifacts bucketed into applications, and configuring platform settings such as Host, adapters, etc.  The BizTalk Explorer in VS is still a dev tool and will not show applications but will show all artifacts deployed to all applications. • Can the new Admin Console MMC be used to administer a BTS 2004 group? • No

45. Answers to More Questions • Will MSMQ 3.5 be supported? • Not yet • Does the SQL Adapter support SQL Server 2005 (Yukon)? • Yes, but it does not support the new datatypes (i.e., XML data type) • Does BizTalk 2004 support SQL Server 2005? • At this point BizTalk 2004 will not support SQL Server 2005. If you need SQL Server 2005 then you will need BizTalk 2006

46. Answers to even more questions • What version of SQL Server will BizTalk 2006 support • BizTalk 2006 will support both SQL Server 2000 and SQL Server 2005