(EBZ201) Introduction to Microsoft® BizTalk® Server 2004 Michael Woods Sr. Technical Product Manager eBusiness Server Group

Agenda Standards Architecture Security Scale Out XML Web Services User Experiences Trading Partner Management Wrap-Up

BizTalk Server 2004 Vision Connecting Systems, People and Trading Partners Through Manageable Business Process Key Takeaways Make the Hard Simple Developers – Standardized Interfaces to Functionality IT Pros – Standardized links to Enterprise Systems Information Workers – Standardized views of Business Data, Knowledge and Process Accelerating Web Services Adoption Orchestration and composition of Web Services Unlock Legacy Business Logic

Deep Standards Support

Standards XML Web Service support is core BizTalk Server 2004 functionality WS-I basic profile, WS-Security plug-in XML foundation Schema based on W3C XML standard Schema mapping based on W3C XSLT Business Process Execution Language (BPEL)

Standardizing Business Process With BPEL BPEL is a GXA compliant specification Created by Microsoft, IBM, and BEA for: Business Process Interop Across Boundaries Best Practice Business Processes Specification submitted to OASIS

Architecture

BizTalk End-To-End Architecture Message Pipeline DecodeEncodeDecryptEncryptParseSerializeExtractPropertiesAuthenticateSign Orchestration Activation & Instance Management Correlation & Content-based Routing MessageBox Transport Handlers HTTP SOAP-RM MSMQSAP MQSeries BusinessIntelligenceReportingMonitoringAdministrationDeploymentProcessManagement Trading Partner ManagementOtherApps ….

BizTalk Solution Flow DecryptParseResolveParty MessageBox SerializeSignEncrypt TransportTransport Receive Pipeline Send Pipeline Orchestration

Universal MessageBox Architecture Consistent scale-out model built on SQL Server 2000 SP3 Pub/sub architecture Stateless servers Low-latency high volatility routing Large Message support Pluggable adapters Security and auditing Message Pipeline DecodeEncodeDecryptEncryptParseSerializeExtractPropertiesAuthSign Orchestration Activation & Instance Management Correlation & Content-based Routing UNIVERSAL MESSAGEBOX Adapters HTTP Web Services Services MSMQAdapters MQSeries ….

Security

Host 3 (SvcAcct3) Host 2 (SvcAcct2) Host 1 (SvcAcct1) Authentication Trust DecryptParseResolveParty MessageBox SerializeSignEncrypt TransportTransport Barrier prohibiting Message SID/PartyId from Un-trusted Hosts Barrier which rejects messages with no PartyId No Guest Messages

Enterprise Single-Sign On Maps user credentials from Windows to non-windows systems Authenticate once and securely access target systems Secret store contains user mappings encrypted E.g., domain\jonqp => mySAPaccount/mypass Integrates with SPS to provide SSO for portal Web Services front-end for any client to any platform Configuration information stored in secure store Security is important – reviewed 3 times by the windows security team and independent experts

Single Sign 0n DecryptParseResolveParty MessageBox SerializeSignEncrypt Transport Transport SSO Server

Scalability

BizTalk 2004 System is “mostly” stateless Routing is done in SQL Server by stored procs As long as DB is common it’s possible to add many processing machines Allows scale out message parsing, conversion, extraction of properties, as well as transport Enables use of Network Load Balancing Exceptions from stateless second layer Orchestration – persisted (long running transactions) Correlation messages are routed to the correct machine Session-based protocols (e.g., MSMQT) Exceptions are not a problem for scaling out

Scaling Out Processor Machines Message box Host Machine SQL Server Stored procs Data (messages, subscriptions, etc.) Host Machine Host Machine Host Machine Network Load Balance

Scaling Out Storage Several databases maintain identical configuration data Master database contains all subscriptions Relations between processing and SQL machines are many-to-many For activation messages it makes no difference which message box does processing (chosen by Round Robin) For correlation messages routing/copying to correct message box(es) is sometimes necessary

Message box Scaling Out Storage Network Load Balance Host Machine Host Machine Host Machine Host Machine Stored procs Data Data SQL Server Machine SQL Server Machine (Master)

Storage Fail Over Generic SQL Cluster failover support sec pause (!) Host Machine SQL Cluster SQL Server Machine Message box Stored procs Data SQL Server Machine Message box Stored procs Data

XML Web Services

XML Web Service Interaction Simple, automated generation of E-Business Web Services Access to any web service from within Orchestration Tightly integrated design experience with the Orchestration Designer and Visual Studio.NET

XML Web Service Support Similar to other BizTalk transports Document Tracking Auditing Scaling across servers Fault Tolerance Standards support ASP.NET Microsoft SOAP Toolkit WSDL v1.1 UDDI

XML Web Services Overview

Simplified Persona-Based User Experiences

Developer

One Microsoft Development Environment Visual Studio.NET Unified and simplified development Visual Studio.NET solution BizTalk 2004 project contains Editor Mapper Orchestration Designer Pipeline Designer Explorer Any.NET language (e.g., C#, Visual Basic) Seamless source control to your favorite source control system

One Developer Experience Leverage existing skills Harness the.NET framework Build with standards

Rich Business Process Design Super-set of BPEL capabilities Nested processes Long running transactions Simplified correlation Flexible mapping between messages

Information Worker

Simple Business Analyst Surface Less complex Simple Visio template Available for any Visio user to download Hand-off to developer “Two way” reportable

Business Rules/Policy Use business process rules for simple cases or complete inference engine for more complex scenarios Rules change more often than processes Business Rules provide increased flexibility Rules are abstracted from process and user code Complements orchestration Rules engine is high throughput low latency

Rules As A Driver Inside Process Code Any change is a code change Layered process and code Independently change Code Process Layered rules, process and code Independently change Code Process Rules Increasing agility

Business Process Automation Engine OrchestrationRules Tracking Discount Rule: If Customer is a Gold Customer Then Apply 10% discount Validation Rule: A valid credit card number must be provided Dynamic Business Policy management Dynamic Business Policy management Cross-Field/Constraint Validation Cross-Field/Constraint Validation Decision support Decision support Messaging Bus Business process Routing Rule: If the customer wants to buy cars Then route to Ford dealer If the customer wants to buy books Then route to Barnes and Nobles Notification If purchase order amount is more than $1000 Then notify sales manager ServiceServiceService Intelligent Routing Intelligent Routing Intelligent Notification Intelligent Notification BAM OLAP Purchase Volume Rule: If the purchase volume is over 100 Then launch the premier procurement process KPI Reasoning KPI Reasoning Humanbasedworkflow Customization Rule: If the purchase amount is over 500 Then obtain Manager’s approval Workflow customization Workflow customization Additional Rules Scenarios

Deep Office/InfoPath Integration Scenarios Route InfoPath documents through the enterprise Input data from InfoPath documents into enterprise systems Capabilities Open XML Schema directly inside BizTalk Send from InfoPath through XML Web Services to BizTalk Much, much more…

Business User: Activity Monitoring (BAM) SQLOLAP BizTalk Server Ask real-time questions How long is production taking right now? Ask aggregation questions How much money did we make last month? Use Data from documents or Process Complements existing SQL BI solutions

BAM Overview Excel Workbook WSS Site Business Analyst Defines business data to collect and how to interpret and how to interpret Developer Business End User View Business Activities And perform everyday business operations BAM Storage BAM Query WS WS BAM XML

Human-Based Workflow Goals Overcome flexibility issues with traditional human-based workflow Modifying the model at run-time Enable knowledge workers to leverage what they know Task orientated in Office

Imaginary Boundaries Process Styles StyleCharacterization AdhocEnd-user build as you go processes Directed CollaborationSemi-structured processes that can be changed mid-stream by an end-user Classical Human Based WorkflowHighly structured pre-defined process involving people that can be changed by a “power user” Structured EAIHighly structured pre-defined process involving systems that can be changed by a developer Structured B2BHighly structured pre-defined process involving trading partners that can be modified by a developer

HWS Methodology Modularized Can be used stand-alone Integrated Leverages the orchestration engine Works well with Office Based on Open Standards Built on BPEL foundations Extensible Exposed as Web Services and.NET APIs Client Agnostic

IT Professional/System Admin

Real-Time Tracking For Admin And Debugging View a process end-to-end Track Messages Processes Debug Suspend Resume Manage suspended messages

System Administration Versioned deployment based on the.NET framework One console to Manage server farm including adapters Scale solution to new servers New Processing Servers New Database Servers Create secure boundaries

Trading Partner Management

Hub: Large Scale Trading Partner Management Manage relationships with thousands of trading partners Relationship is separated from process increasing reusability Enable Easy configuration of new trading partners Communicate across heterogeneous messaging and transport protocols Deal with large variety of data formats Enable Multi-party Business Processes

Service Links Partner Management Allows for dynamic binding of entire set of Ports based on Partner or Message data Service Link defines business protocol exchange between partners Linked to Partner Management Subsystem Determines which set of port bindings will be executed at runtime

Service Links Buyer Supplier A Send RFQ Send Receipt Send Quote Send Receipt Send PO Send Receipt Supplier B Supplier C Business Protocol defined by Service link containing Sends and Receipts of Business Messages Business Protocol defined by Service link containing Sends and Receipts of Business Messages Can apply entire set of interfaces to another partner at runtime Can apply entire set of interfaces to another partner at runtime

Spoke: Rapid Trading Partner Roll-Out Next generation SEED technology Trading partner obtains package Trading partner completes deployment with simple Office wizard Trading partner manages orders with WSS Web Services available to any client User Interface leverages WSS

Summary Make the Hard Stuff Simple Give them what they need Developers – Visual Studio.NET IT Professionals – Windows – standard, repeatable process Information Workers – Rich Office view into business Standards Fully Leverage Mature Standards (XML, XSD) Champion Emerging Standards (XML WS, WS-I) Opportunistically Partner with the Industry to build frontier standards (BPEL) Beta availability now at

More BizTalk Server 2004 Sessions EBZ302 Orchestration EBZ303 Human Workflow Services EBZ304 Admin, Deploy, and Secure EBZ306 Advanced Orchestration EBZ327 InfoPath & BizTalk Server EBZ329 XML Tools EBZ330 EAI End-to-End Sample EBZ342 Rules Engine EBZ343 Business Activity Monitoring

Community Resources BizTalk Server 2002 Newsgroups BizTalk Server 2004 Beta Newsgroups User Groups: Sites of Interest

Community Resources Most Valuable Professional (MVP) Newsgroups Converse online with Microsoft Newsgroups, including Worldwide User Groups Meet and learn with your peers

Ask The Experts Get Your Questions Answered I will be at the booth: directly after this session various other times during the week If you: miss me at the booth, want to set a time to meet, or just want to keep in touch… :^)

evaluations evaluations

© 2003 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.