1. Applicatieplatform congres 12 & 13 maart

2. Choosing Integration Alternatives with BizTalk Server and Windows App Server When to use what? Ofer Ashkenazi Senior Product Managerofera@microsoft.com

3. BizTalk Server & Windows Server (“Dublin”) Storyboard Question: Cant I just build my own integration solution? Question: When do I use each? Question: What is each? Initial decision: What is an integration suite? Do I need one? I need an integration suite Windows (w/Dublin): Application Server Build your own App Absolutely, Use Windows but there is a better way… BizTalk Server: Enterprise Integration Suite Integrate systems Use BizTalk, Its Better, Cheaper and supported

4. Why do I need an Integration Solution? To interoperate with LOBs, IBM Systems To connect with partners via B2B protocols To simplify and automate system interactions To leverage existing IT investments

5. The Changing Landscape Application Integration Domain is Rapidly Evolving

6. Why do I still need an integration solution for services? You don’t want to end up with a “Spaghetti” of services use a service broker implement the ESB pattern Some LOB and legacy apps are hard to service enable – an integration broker can do it better A hybrid approach (Integration Broker + ESB) is better CRM HR E-Commerce ERP Business Partner CR M HR E-Commerce ER P Even with web services, point to point solutions appear easy at first, but become hard to manage and maintain.

7. Market Trends Integration categories are converging Gartner: The Integration Suite and ESB Markets Have Merged The Role of ESB Suites in Implementing and Integrating With Cloud-Based Applications Forrester: The enterprise service bus (ESB) is fast becoming the “kitchen sink” of integration middleware. The core of most ESBs includes many of the basic integration capabilities evolved from earlier (EAI) products, with the major differentiator being the ability to do all of these things with both traditional and Web services protocols.

8. Forrester’s Integration Product Categories Feature SetESBIC-BPMSB2B gateway Messaging  Routing  Transformation  Connectivity  SOA & WS Integration  Distributed Processing  Service Endpoint/SLA Management  Lightweight orchestration  Standard base process modeling Support  Process Orchestration  Business Activity Monitoring (BAM)  Comprehensive IDE  Partner Management  Role based process modeling  Human Interactions  Business Rules  Business Event Management (BEM)  Complex Event Processing (CEP)  Shared Metadata Management  Legend:  Full support  Partial  None

9. What is each technology? Windows (Application Server Role): Apps Server Hosting, monitoring & managing capabilities for WCF services and processes built with WF (.NET 4.0 + Dublin) BizTalk Server: Connectivity & Integration Solution Connectivity and integration capabilities to heterogeneous technologies for Windows applications

10. Windows App Server (.NET + “Dublin”) Codename “Dublin” a set of extensions for the Windows Server’s application server role “Dublin” extends (IIS) and provides a hosting middle-tier WCF/WF services. “Dublin” extends (IIS) and provides a hosting middle-tier WCF/WF services. “Dublin” will simplify for composite applications the: DeploymentConfigurationManagementscalability Not released yet!

11. BizTalk Server 2009 Integrates distributed applications, processes and services across various boundaries (e.g. OS, security, LOB, device, enterprise) Caters to the following workloads: Messaging, ESB, Orchestration, Business Rules, B2B, BAM and RFID Suitable for mission-critical workloads with high availability and high throughput Highly scalable to grow with the business Provides out-of-the-box support for dozens of standards, protocols and Line-of-Business Systems

12. When Do I Use Each? Windows Server (Application Server Role) Build your own Application: use.NET WF and WCF to build new process and services BizTalk Server Integrate Systems: use BizTalk to service enable or interconnect exiting applications/services

13. Forrester’s Integration Product Categories Feature SetESBIC-BPMSB2B gateway Messaging  Routing  Transformation  Connectivity  SOA & WS Integration  Distributed Processing  Service Endpoint/SLA Management  Lightweight orchestration  Standard base process modeling Support  Process Orchestration  Business Activity Monitoring (BAM)  Comprehensive IDE  Partner Management  Role based process modeling  Human Interactions  Business Rules  Business Event Management (BEM)  Complex Event Processing (CEP)  Shared Metadata Management  Legend:  Full support  Partial  None  BizTalk BizTalk                   

14. Within AppsAcross Heterogeneous AppsBetween Enterprises Self-Contained (Atomic) Service Physical Events Visibility (RFID) Connecting Business Partners (B2B) Dynamically Updateable Process Flow LOB/IBM App Integration Enterprise Business Rules across the (BRE) Process Monitoring and Analytics (BAM) Enterprise Service Bus (ESB)/ Enterprise Message Broker Web Service Composition Service Aggregator Long Running Business Logic (Durable Service) Long-Running Business Process UI Page Controller (Embedded WF) Collaboration & Human Workflow Dublin (with WF & WCF) BizTalk Server (with WCF) It depends, but mostly BizTalk Server (based on interface heterogeneity & Complexity) SharePoint Server with WF/Dublin Legend:

15. Guidance based on Interface and Complexity Grey Area: customer prefers to.. Buy - use BizTalk Build – use Dublin Application Interface Not Service EnabledService Enabled Mediation/Composition Complexity Simple Complex B2B ESB Pub/SUB Advanced Routing & Transformations QoS & Reliability Rule Based Process Monitoring Long Running Process Service Aggregator WS Composition Durable Service UI page controller Updateable process Self Contained Service Dublin BizTalk Server Legend: Complex Not Service Enabled Simple Not Service Enabled Complex Service Enabled Simple Service Enabled

16. ESB & Orch. Patterns with BizTalk Pub/Sub Orchestration patterns: Async Aggregation Inverse Direct Bound Port First In First Out Splitter Interrupter Pattern Terminate Retry Pattern Non-uniform Sequential Convoy Calling Pipelines Parallel Convoy Filter Uniform Sequential Convoy Message Broker Suspend With Retry Error Handling There are a lot of integration design patterns that are enabled out of the box with BizTalk.

17. Better Together Use Dublin to host: New services built with WF 4.0 Simple composition of services that is needed for a specific application Use BizTalk as the “glue” between apps to: Deliver high agility with ESB Provide connectivity & service enablement Implement centrally managed mediation broker Many organizations will see considerable benefit by using both BizTalk and Dublin within their environments.

18. Can’t I Just Build My Own Integration Solution? Absolutely! – use Windows, but there’s a better way.. Use BizTalk to get the plumbing out of the box and focus on the integration business logic It’s better: highly scalable and trusted by customers for mission critical workloads It’s cheaper: faster time to solution and less expensive to maintain It’s supported by Microsoft: less risky, tested and regularly updated for new standards & LOBs versions

19. A few more facts about BizTalk BizTalk Server 2009 is the 6 th release of the product More than 5 millions of lines of code Validated and trusted by 8,500+ customers Maintains compatibility for changing standards, protocols & APIs Scales up and out to provide high throughput of more than 1,200 orch. per sec Support and maintenance available from Microsoft Extensive customer evidence for rapid ROI BizTalk is a mature and robust product

20. How about the future? In the long-term you can expect BizTalk to support also Windows Workflow Foundation (WF) Your investment in either BizTalk orchestrations (XLANG) or WF will move forward BizTalk Roadmap: http://www.microsoft.com/biztalk/en/us/roadmap. aspx http://www.microsoft.com/biztalk/en/us/roadmap. aspx http://www.microsoft.com/biztalk/en/us/roadmap. aspx

21. BizTalk a Multi-Year Roadmap for a Premium Integration Solution Maintain release rhythm of roughly every 2 years New & Enhanced Scenarios Low-latency ESB B2B BI/BAM Asset Tracking (RFID) Faster Time to Solution Productivity e.g. Complex Mapping Better Together Integration with the latest new platform Updated platform support SOA and Web Services Business to Business Integration Developer & Team Productivity Main themes for the future releases of BizTalk Server:

22. BizTalk & Windows App Server (“Dublin”) Summary Question: Cant I just Build My own Integration solution? Question: When do I use each? Question: What is each? initial decision I Need Integration solution Windows (w/Dublin): Application Server Build your own App Absolutely, Use Windows but there is a better way… BizTalk Server: Enterprise Integration Suite Integrate Systems Use BizTalk, Its Better, Cheaper and supported Both technologies will work together to provide enterprise solutions. Your investment in both will be preserved.