Transcript What’s new in BizTalk ServerDamir Bersinic IT Pro Advisor Microsoft Canada http://blogs.technet.com/damirb Agenda • Roadmap for business process and integration products • Introduction to BizTalk Server.

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
HIS 2006
Beta
Nov 7
Joint Launch
CS 2006
Beta
BTS 2006
Beta-1
BTS 2006
Beta-2
Windows
Workflow
Foundation
Beta
HIS 2006
RTM
CS 2006
RTM
BTS06 RTM
Accelerators
Adapters
Next
Generation
BPI Wave
Windows
Workflow
Foundatio
n
Comprehensive
Management and
Operations
Windows Server System
Alignment
MMC for Enterprise Management
Single View for Operations
and Monitoring
Application-level Management
Engine and Infrastructure Investments
Common Engineering Criteria support
Windows 64 bit (x86)
SQL Server 2005 Support
Visual Studio 2005/.NET 2.0
Virtual Server 2005
Business User
Empowerment
Real-time BAM Alerting
and Notification
BAM Portal and reusable
web components
SharePoint Adapter for deeper
WSS integration
Setup, Upgrade and
Deployment
Simplified Setup
Tools for Enterprise
Application Deployments
Seamless upgrade from
BizTalk Server 2004
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
BizTalk “Application” Now 

SendPortA
Orchestrati
on1
ReceivePor
t1
401k Application
Orchestrati
on2
•
•
•
•
Certificate1
Orchestrati
onB
Mortgage Application
ReceivePor
tA
Pipeline1
New concept in BizTalk Server 2006
Provides complete view of application
Simplifies management
Manage all related artifacts as a unit
SendPort1
SendPort1
SendPort
Group1
Receive
Port2
Orchestrati
Receive
Port1
onA
SendPortA
SendPort
GroupA
Receive
Receive
SendPortPort B
Port A
GroupA
Pipeline2
MapB-A
SendPort
Orchestrati Orchestrati
Group1
on1
on2
Pipeline1
Pipeline2
SchemaA
Orchestrati
onA
PipelineA
Orchestrati
onB
PipelineA
PipelineB
Receive
PortB
Map2-1
SchemaB
Schema1
Schema2
Map1-2
Map2-1
SchemaA
Map1-2
SchemaB
MapA-B
MapA-B
CertificateA
MapB-A
PipelineB
Rule1
Certificate1
Receive
Rule1
Port2
CertificateA
Rule2
RuleA
RuleB
RuleA
Rule2
Schema1
RuleB
Schema2
Management - 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 & 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.msi
BindingInfo.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 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 Pipelines
Use 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 Pipeline
Orchestration
Send Pipeline
Decode
Pre-ASM
DASM
ASM
Validate
Encode
Resolve
Party
Pipeline Components
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 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. Failed messages are suspended
4. 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
Standard Interchange Processing Example
Flat file
interchange
Doc1
Doc1’
Endpoint manager
Receive location
Doc2
Doc2’
Receive pipeline
Doc3
Doc3’
Doc4
Doc4’
Doc5
Doc5
Doc6
Flat file
Suspend
queue
interchange
In Message Box
Work queue
In Message Box
Recoverable Interchange Processing Example
Flat file
interchange
Doc1
Doc1’
Endpoint manager
Receive location
Doc2
Doc2
Receive pipeline
Doc3
Doc3’
Doc4
Doc4’
Doc5
Doc5
Doc6
Doc6’
Suspend queue
In Message Box
Work queue
In Message Box
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:
•ErrorType
•FailureCode
•Description
•MessageType
•ReceivePortName
•ReceivePortName
•InboundTransportLocation
•OutboundTransportLocation
•RoutingFailureReportID
• Subscriptions can be created to route valid messages
• Orchestrations can be created to subscribe to failed messages for rich error
handling beyond HAT/MOM
Message Resume 2004 vs. 2006
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
• *Messages requiring ordered delivery
(MSMQ, MQSeries) may not be
resume-able
• Inbound configuration changes affect
resumed messages
– Failed message routing
– Schema updates
– Map changes
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:
PO1999-10-20
US
Alice Smith
123 Maple Street Mill Valley CA 90952
US
Robert Smith
8 Oak Avenue
Old Town
PA 95819
Hurry, my lawn is going wild!
ITEMS,ITEM872-AA|Lawnmower|1|148.95|Confirm this is electric,ITEM926AA|Baby Monitor|1|39.98|Confirm this is electric|1999-05-21
• 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
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.