Presentation is loading. Please wait.

Presentation is loading. Please wait.

Microsoft BizTalk Server 2006 R2 The Features, The Framework and The Future.

Similar presentations

Presentation on theme: "Microsoft BizTalk Server 2006 R2 The Features, The Framework and The Future."— Presentation transcript:

1 Microsoft BizTalk Server 2006 R2 The Features, The Framework and The Future

2 Agenda BizTalk R2 Features (WinFX and BPM Tools) What an Adapter provides Why the R2 LOB Adapter SDK exists Architecture Benefits The LOB Adapter SDK vs WCF The LOB Adapter SDK and the BizTalk Roadmap Demos Q & A

3 R2 Goals and Supporting Features.NET Framework 3.0 Support LOB Adapter SDK LOB and WCF Adapters BAM monitoring of WF workflows and WCF services Support for Composite Applications via Service-Oriented Architecture BizTalk LOB Adapters Office SharePoint Server 2007 Integration Partner BPM Solutions Modeling, simulation, rules Support for People-Ready Processes Device Abstraction and Management Tools Event Filters, Alerts and Transforms API: Design, Runtime, Management Back-office Integration Support for End-to-End RFID Processes Native EDI engine X12, EDIFACT, AS2 support B2B Standards Support HIPAA, HL7, SWIFT, RosettaNet Global Supply-chain Collaboration GXS partnership Support for End-to-End B2B Processes

4 BPM Tools in R2 ESB Guidance toolkit – Exception handling – Management portal for ESBs – Core ESB namespacing, APIs, and code samples – Web and WCF services for endpointing – Enveloping (itineraries) – Code for writing on and off ramps Software as a Service (SaaS) support SOA-enabling tools – Federated processes across trading partners and devices

5 Microsoft BizTalk Server 2006 R2 LOB Adapter SDK (formerly Adapter Framework)

6 Common Adapter Functionality Connectivity – Physical connectivity to target system Metadata – Harvest metadata from target system – Search, Browse, Resolve metadata Message Exchange Flow – Implement Handlers for supported Message Exchange patterns like Outbound, Inbound etc. Other – Transaction bridging, Ordered delivery etc

7 Evolution of Architectures Hub and Spoke managed / centralized Supports loose coupling of systems Message Broker n lines of connectivity Centralized management Limited scalability Single point of failure Point-to-Point unmanaged / decentralized Suitable for small environments n² lines of connectivity No unification Difficult to manage Highly-coupled Message Bus managed / decentralized Common communication infrastructure Common command infrastructure n lines of connectivity Proprietary communication protocols Complex management

8 Hybrid Hub/Bus Architecture BizTalk Mgmt DB Cluster Send Hosts Receive Hosts Network Load Balancer Processing Hosts Outbound Inbound MsgBox 1 MsgBox 3 MsgBox 2 Cluster Tracking DB Cluster BizTalk Server Admin Host BizTalk Server Tracking Host Monitoring (MOM) DataIndexesLogsDataIndexesLogs SAN

9 Conceptual Architectural Problem Point-to-PointHub and Spoke (BizTalk) Message Bus Time to DeliveryHigh: each host has custom logic Mid to Low: As most are pre-written, time is spent to use adapters High: most time is spent writing code to get on the bus (create adapter endpoints and service containers) Architectural Design Footprint Large: hosts are tightly-coupled Large: messaging engine and adapters are tightly-coupled Small: distributed message bus and distributed integration capabilities ConsistencyNoneLittle/None: Some across Microsoft adapters; next to none with ISV adapters Little/None: none across LOB and 3 rd party adapters; service containers only as consistent as dev who wrote them ScalabilityPoor: scale outward, not upward Good: scales upward and outward, but cost prohibitive Excellent: scale upward and outward and can minimize cost ManageabilityPoor: depends on host capabilities Mid: heavily tied to WMI, and involves a lot of planning Mid: depends on how its implemented

10 Technical Problem No unified framework on which to develop adapters in.NET Today’s adapters are specific to the consuming host – Too many (different) adapters – A lot of redundant functionality

11 Solution Provide a framework for and the implementation of adapters that are – High quality (written in WCF, C#, Managed Code) – Metadata-driven – Host agnostic – Customized to the LOB system – Scalable – Distributable

12 Adapter Bindings Architecture WCF Service Programming Model WCF Channel Architecture WCF Apps SQL-SSIS Office Biz Apps MIIS SAP adapter SAP AF Runtime MIIS Controller ADO.NET provider WCF HTTP binding My adapter AF Runtime Siebel My System Siebel adapter Web Service WCF BizTalk Server

13 Architectural Benefits Enables surfacing multiple programming models (i.e. WCF channel, ADO.NET, Service Model Programming) Enables exposing a Web Service face to the system being adapted automatically (via the Adapter host) WCF channel architecture extensibility points enable easy customization of Adapter behavior Development Tools – AF ships with a rich set of development tools to automate and simplify much of the coding required for Adapter development – Consistent deployment and administration experience

14 Adapters and WCF If Adapter consumption is identical to WCF Service consumption then when does one write an Adapter and when does one write a vanilla WCF Service to expose existing systems for integration? – Adapters are appropriate when it is impractical to capture the target system’s functionality in a static monolithic contract, i.e., The metadata of the system is “dynamic” i.e., new functions can get added, e.g., Oracle stored procs There is a lot of metadata e.g., SAP – WCF service is more appropriate when the target system metadata is more or less “static” and “small”

15 Adapter vs. WCF Services WCF Service The Service Contract LOB Adapter Contract1 Contract2 Contract3 Contract n Fixed Service ContractDynamic Composable Contract(s)) Large Metadata

16 Demo: Adapter Service Reference

17 Adapter Architecture Channels Implementation Connection Management Connection Factory Metadata Management LOB Connection Handler Metadata Browse / Search WSDL Builder Metadata Handler Credentials Extractor URI Builder Metadata Driven XML reader/writer Implemented by Developer AF Adapter

18 AF Artifacts Code Generation Wizard OM for components to be implemented by developer Common Metadata Search/Browse UI component BizTalk design time integration components

19 Demo: Code Generation Wizard

20 Object Model Overview Metadata Browse Handler Transaction Bridging Guaranteed Delivery In-order Delivery Session Correlation Adapter Operation Metadata Type Metadata Inbound Message XML Reader Outbound Message XML Writer Optional Required Custom Only in Beta1, will be implemented by AF in Beta2 Connection Factory Connection Inbound Handler Outbound Handler Metadata Resolver Handler Metadata Search Handler

21 Consuming Adapters Identical to consuming WCF bindings Adapters can be consumed via – WCF Channel programming model – WCF Service Programming Model The WCF Adapter shipping in the R2 box enables consumption of all WCF services and bindings Send/Receive ports should be configured with WCF-CustomAdapter with the associated binding pointing to the specific Adapter binding

22 Demo: Consuming an Adapter

23 Connectivity Design Connection Factory Connection Adapter Outbound Handler Inbound Handler LOB Metadata Resolver Handler Metadata Browse/Search Handler

24 Creating Connectivity Implement the Connection Factory – Establishes connection pool based on URI, user credentials Implement Connection – Defines low-level communication contract with the target system – Encapsulates native communication APIs and/or connection handles Implement Handler(s) – Defines the message exchange pattern(s) supported by the adapter

25 Handlers Outbound Handler – To support One-Way Send or Request/Response patterns Asynchronous Outbound Handler – Async flavor of the above. Inbound Handler – To support One-Way Receive or Reply patterns Metadata Resolver Handler – To expose metadata governing the execution of target system logic Metadata Search Handler – To search for metadata in systems where unfiltered metadata is too large or unwieldy Metadata Browse Handler – To browse for metadata in systems with large metadata where some meaningful categorization is possible

26 Steps To Implement Metadata Support Implement calls to any native metadata harvesting APIs for target system Implement OperationMetadata objects and TypeMetadata objects for methods and types harvested – Each distinct programming model supported by the target system needs an OperationMetadata class e.g., COM programming model access, Win32 library etc., Implement search, browse methods for metadata if appropriate

27 Metadata Services Provided In The AF Encapsulation – Enables OO representation of target system metadata – OperationMetadata & TypeMetadata are key base classes Caching – Internal in-memory cache for metadata WSDL Generation – Automatic WSDL generation from OO metadata model (can be overridden for scenarios requiring custom WSDL generation)

28 Timing Diagram-Design Time

29 Timing Diagram-Run Time

30 How Do Adapters Differ From WCF Transport Bindings? Adapters differ from regular WCF transport bindings in the following ways – Adapters are Metadata Centric Require metadata at run time Require metadata cache mgmt To provide rich metadata at design time they require filtering /pruning/search /browse protocol – Adapters are always Connection Oriented The connection is a very central concept for the adapter Require connection pooling and life cycle mgmt Adapters are effectively “in-proc WCF Services”

31 Microsoft BizTalk Server 2006 R2 Future Directions

32 BizTalk 2006 R2 includes separate installs – BizTalk 2006 R2 Server – BizTalk 2006 R2 Accelerators – BizTalk WCF LOB Adapters – BizTalk WCF LOB Adapter SDK Microsoft plans to offer the WCF LOB Adapter SDK as a free download The.NET Adapters will most likely be sold as a standalone product or given out to select customers depending upon licensing agreements Packaging

33 Future Directions Microsoft’s officially stated goals for vNext: – Radical gains in productivity thru advances in model-driven development and management – Rich business process modeling and simulation for the business analyst – Further advance and integrate the use of Windows Workflow Foundation – Continued commoditization of low-level integration

34 Future Predictions BizTalk 2006BizTalk 2006 R2BizTalk vNext IntegrationAdaptersAdapters & AFAF 2.0 Business ProcessingXLANG Custom WF Activities / Xml Itineraries CommunicationsPortsPorts & WCFWCF WorkflowHWS WF TransformationXSLT XLINQ.NET Fx Support2.03.0 (Partial)3.5 Complete Data AccessADO.NET / Adapters ADO.NET / DLINQ

35 Resources Questions: BizTalk Team Server Blog: blog blog Microsoft’s site on SOA and ESB guidance: Beta 2 bits available for download at

36 Corporate Office 100 West Rd. Ste. 408 Baltimore, MD 21204 410-583-9393 Calverton Office 4061 Powder Mill Road, Ste. 700 Calverton, MD 20705 301-273-2126 Software Development & Integration / Program & Project Management / Architectural Oversight / Software Integration / Business Process Improvement / HIPAA / Consulting / Staffing / Knowledge Sharing & Mentoring

Download ppt "Microsoft BizTalk Server 2006 R2 The Features, The Framework and The Future."

Similar presentations

Ads by Google