What’s new in BizTalk Server 2006

Damir Bersinic

IT Pro Advisor

Microsoft Canada

http://blogs.technet.com/damirb

Agenda• Roadmap for business process and

integration products

• Introduction to BizTalk Server 2006

• Release Themes Features– Setup & Migration– Management, Operations, & Deployment– Developer Experience– Business User Empowerment

Next Generation BPI Wave

HIS 2006RTM

HIS 2006Beta

BTS06 RTMAccelerator

sAdapters

WindowsWorkflow Foundatio

nBeta

BTS 2006

Beta-2

Windows Workflow Foundati

on

CS 2006RTM

CS 2006Beta

Nov 7 Joint Launch

BTS 2006

Beta-1

MMC for Enterprise ManagementMMC for Enterprise ManagementSingle View for Operations Single View for Operations and Monitoringand MonitoringApplication-level ManagementApplication-level ManagementEngine and Infrastructure Engine and Infrastructure InvestmentsInvestments

Comprehensive Comprehensive Management and Management and

OperationsOperationsCommon Engineering Criteria Common Engineering Criteria supportsupportWindows 64 bit (x86)Windows 64 bit (x86)SQL Server 2005 SupportSQL Server 2005 SupportVisual Studio 2005/.NET 2.0Visual Studio 2005/.NET 2.0Virtual Server 2005Virtual Server 2005

Windows Server System Windows Server System AlignmentAlignment

Real-time BAM Alerting Real-time BAM Alerting and Notificationand NotificationBAM Portal and reusable BAM Portal and reusable web componentsweb componentsSharePoint Adapter for deeper SharePoint Adapter for deeper WSS integrationWSS integration

Business User Business User EmpowermentEmpowerment

Simplified SetupSimplified SetupTools for Enterprise Tools for Enterprise Application DeploymentsApplication DeploymentsSeamless upgrade from Seamless upgrade from BizTalk Server 2004BizTalk Server 2004

Setup, Upgrade and Setup, Upgrade and DeploymentDeployment

Setup & Migration

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 Pro focused deployment wizard– Greater flexibility for multi machine installs– Built into the MMC for consistency

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

Management, Monitoring & Deployment

BizTalk “Application” Before

SendPortA

ReceivePortA

ReceivePortB

SendPort GroupA

OrchestrationA

OrchestrationB

SchemaA

SchemaB

MapA-B

PipelineA

PipelineBCertificateA

RuleA

RuleB

MapB-A

SendPort1

ReceivePort2

ReceivePort1

SendPort Group1

Orchestration1

Orchestration2

Schema1Schema2

Map1-2

Pipeline1

Pipeline2

Certificate1

Rule1

Rule2

Map2-1

401k Application

SendPort1Receive

Port2Receive

Port1SendPort Group1

Orchestration1

Orchestration2

Schema1 Schema2 Map1-2

Pipeline1 Pipeline2

Certificate1 Rule1 Rule2

Map2-1

Mortgage Application

SendPortAReceivePort A

ReceivePort B

SendPort GroupA

OrchestrationA

OrchestrationB

SchemaA SchemaB MapA-B

PipelineA PipelineB

CertificateA RuleA RuleB

MapB-A

• New concept in BizTalk Server 2006

• Provides complete view of application

• Simplifies management

• Manage all related artifacts as a unit

BizTalk “Application” Now BizTalk “Application” Now

Management - MMCManagement - 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!

Monitoring & TrackingMonitoring & 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

BizTalk Administration Console

Exporting an Application

• Accessible via MMC• Right-click application• Choose to export

– MSI– Bindings

Expense.msiExpense.msi

BindingInfo.xmlBindingInfo.xml

Installing and 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

Business User Empowerment

Business User EmpowermentBusiness User Empowerment• Significant Investments in BAM• Minor Investment for BAS & Visio• Business Rules Engine remains As-is• No new investment until “Longhorn” timeframe

– Human Based Workflow Engine (HWS)– Human Based Workflow Designer (HWS)

Business Activity Monitoring Investments• Business Alert experience for end users• Out-of-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)

Tracking Profile Editor

• Support for Messaging

• Retrieve Activities from the BAM Database

• Activity Centric

BAM Portal

Core Engine

Review of BizTalk PipelinesUse pipelines to:• Normalize data from various formats to XML• Translate data from XML to various formats• Assemble and disassemble documents• Decode and encode documents • Decrypt and encrypt documents• Assign and verify digital signatures

Receive PipelineReceive Pipeline OrchestrationOrchestration Send PipelineSend Pipeline

Pipeline Components

DecodeDecode

DASMDASM

ValidateValidate

Resolve

Party

Resolve

Party

Pre-ASMPre-ASM

ASMASM

EncodeEncode

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

Interchange Processing Explained• In BizTalk, an Interchange can contain 2 or more

messages, such as a batch• Standard Interchange Processing

1. At arrival, an interchange is broken down into individual messages & passed to a pipeline

2. Messages are individually validated, but collected within the end-point manager (EPM)

3. If any message fails validation the entire interchange, as a single message is suspended

• Recoverable Interchange Processing1. At arrival, an interchange is broken down into individual messages &

passed to a pipeline2. Messages are individually validated, but collected within the end-point

manager (EPM)3. Failed messages are suspended4. Successful messages are sent to the message box

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

Flat file interchange Endpoint managerEndpoint manager

Standard Interchange Processing Example

Doc1Doc1

Doc2Doc2

Doc3Doc3

Doc4Doc4

Doc6Doc6

Doc1’Doc1’

Doc3’Doc3’

Doc2’Doc2’

Doc4’Doc4’

Receive pipelineReceive pipeline

Receive location

Work queueWork queueIn Message BoxIn Message Box

Suspend queueSuspend queueIn Message BoxIn Message Box

Doc5Doc5Doc5Doc5 Flat file

interchange

Work queueWork queueIn Message BoxIn Message Box

Flat file interchange Endpoint managerEndpoint manager

Recoverable Interchange Processing Example

Doc1Doc1

Doc3Doc3

Doc4Doc4

Doc6Doc6

Doc1’Doc1’

Doc3’Doc3’

Doc4’Doc4’

Doc6’Doc6’

Receive pipelineReceive pipeline

Receive location

Suspend queueSuspend queueIn Message BoxIn Message Box

Doc2Doc2

Doc5Doc5

Doc2Doc2

Doc5Doc5

Failed Messaging Routing in 2004

• 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)

Failed Messaging Routing in 2006

• New configuration setting on the receive port allowing 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

•ErrorType•FailureCode•Description •MessageType•ReceivePortName

•ReceivePortName•InboundTransportLocation•OutboundTransportLocation•RoutingFailureReportID

Message Resume 2004 vs. 2006

• *Messages requiring ordered delivery (MSMQ, MQSeries) may not be resume-able

• Inbound configuration changes affect resumed messages

– Failed message routing– Schema updates– Map changes

2004 2006

Can resume send-side messages Yes Yes

Can resume receive side messages No Yes*

Item-level resume on send side via HAT Yes Yes

Bulk Message Resume & Termination No Yes

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

Commerce Server 2006 Adapters• 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

Developer Tools

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

– 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.

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-20US Alice Smith 123 Maple Street Mill Valley CA 90952US Robert Smith 8 Oak Avenue Old Town PA 95819Hurry, 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

EDI Changes for BizTalk 2006

• Support for any EDI document (same as BTS2004 SP1)• Support for KEDIFACT

– Korean EDIFACT– Support for Korean multi-byte character sets

• XSD2EDI.exe now supports remove (-r)• Improved error reporting when performing validation• Pseudo Pipeline Support

– Exposing an API to access the EDI Subsystem– EDI Pipeline component can be used with any receive location

• The pipeline simply uses the API to call the subsystem

• Covast EDI Accelerator provides complete EDI support

For more information• Public Newsgroups

msnews.microsoft.com• MSDN Community

http://msdn.microsoft.com/bpi/• Download the beta today!

www.microsoft.com/biztalk

© 2004 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.