BizTalk Server 2002 Architecture and Functional Overview

BizTalk Server 2002 Architecture and Functional Overview Mike Cramer Principal Technology Specialist BSG – New England

Agenda • BizTalk Server 2000 Overview • BizTalk Server 2002 Release Themes • BTS 2002 Functional Overview • Q&A

Roadmap • BizTalk Server 2000 • Released December 2000 • BizTalk Server 2002 • Code name “Bizet” • Enterprise Edition • Most commonly requested features in Enterprise customer base • Currently in Beta

BTS 2002: Functional Overview • Target Enterprise Operational areas • Deployment • Intra-Company • Inter-Company • Monitoring • Management • Tools and “Add-On” Features • EDI Enhancements • XML Tools Enhancements • Orchestration Enhancements • Documentation/High-End Samples

Deployment Scenarios • Intra-Company Deployment: • How can operations managers move BizTalk Server solutions from one environment to another (e.g. dev test staging production)? • How can operations managers deploy BizTalk Server solutions between machines in a server farm? • Inter Company Deployment: • How can an enterprise hub help its trading partners connect without incurring costs associated with technical hand-holding?

Deployment Requirements • Encapsulate a BizTalk Application • Simple and intuitive experience • Facilitate deployment across clusters/firewalls • Staging : Development to Test to Staging to Production • Deploy Now • Scheduled replication • Automatically within a cluster

Production Server Farm Intra-Company Deployment Development/Staging Environment Firewall

Intra-Company Deployment • Solution based on Application Center • BizTalk driver for Application Center: • Enumerates configuration artifacts hierarchically • Messaging ports, distribution lists, custom counters, receive functions (channel, docdefs, maps, envelopes, etc… • Native Application Center drivers: • File System: Orchestration schedule files. • COM+: COM+ apps. • Web sites.

Inter-Company Deployment • Goal: Rapidly create B2B relationships • Scenario • Typical Hub-Spoke model • IT Dept woes • Ensuring data from client is in order • Client Configuration debugging • Connectivity testing • SEED Tools – Super Effective and Efficient Deployment

SEED Methodology • Hub Tasks • Create SEED packages • Establish Testing Service (BTS in the sky) • Spoke Tasks • Download SEED • Run client tools • Perform • Self Test – Local Loopback • Remote Loopback • Request to do Business • IT Manager approval

1. Package the configuration items 2. Spoke reads the package 3. Spoke configures itself 1. Package the configuration items 4. Local testing on spoke 2. Spoke reads the package 5. Remote testing with Hub 3. Spoke configures itself 4. Local testing on spoke 5. Remote testing with Hub 6. Done Inter-Company DeploymentSEED™ Hub 6. Done Spoke

Monitoring: Customer Feedback • Target Users • IT operations • Business User • We need: • Richer, user defined, events and counters. • Guidance on interpreting NT Events • More powerful alerts and notifications. • Orchestration related performance counters.

Monitoring/Tracking • Solution will be based on Microsoft Operations Manager (MOM) • Features • Health Monitoring across server farms • User definable monitoring, alerts, and notification • Better problem resolution support • Event consolidation and alert/notification throttling

New Tracking/Monitoring Features • Custom Counters • Richer Suspended Queue Event • MOM Management Pack • NT Event rules and KB • Alerting and Notification • New Orchestration performance counters

Custom Counters • Need to monitor, alert, and notify based on richer set of document processing info. • Example: • Important Customer: NorthWind • If the orders per day from my fulfillment organization to NorthWinddrop below 100, raise an alert in MOM and notify me via email.

Alerts Notifications Rules Script Create Custom Counter Counter DTA BTM MOM WMI Inbound Interchange Outbound Interchange BTS Messaging

Custom Counters (cont.) • Custom Counter Properties • Counter (WMI class instance) name • Source Organization • Source Qualifier • Source Value • Destination Organization • Destination Qualifier • Destination Value • Document Type • Time Interval • BTS Group Name

Suspended Queue Event • Additional Properties • Document Source • Document Destination • Document Type • Processing Stage (e.g., parsing, transform, Transport • Channel & Port IDs • User created MOM rules consume, filter, alert, and notify. • Will ship sample MOM rules.

NT Events • BTS 2000: single event ID • Bizet: unique event IDs in description • MOM Rules and KB for consuming and responding to NT Events • Rules are language neutral

MOM • MOM management pack • Basic providers and rules • Knowledge base, local and MS.com links • NT Events • Custom counters • Suspended queue event enhancements • Performance Counters (includes new XLANG) • Samples • Globalization/localization

EDI Enhancements • Outbound batching-Functional Acknowledgements of EDI Documents • EDI Parser Enhancements • All versions, all schemas, Industry specific subsets – Partnership with 3’rd party

BizTalk XML Tools • Standards support • Export XSD schemas • Upgrade DTD Import module • Jscript in functoids • Map grid scalability • Instance based map testing

Orchestration • Schedule Instance based Correlation • Avoid per-schedule instance queues • Samples • Schedule Instance Pooling • Exception Handling • DB Maintenance scripts

Documentation • Documentation • More of “why”, rather than “how” • Scenario based concept section • Integrating documentation with samples • White Papers • Dynamic ports and how to use them • BizTalk for EAI • Commerce Server and BizTalk integration paper • Native XDR Schemas and BTS • High-End Samples • 25 applications

Summary • Targets deployment, management, monitoring and commonly requested features • Due for release in Q4 CY 2001

BizTalk Server 2002 Architecture and Functional Overview