EBIZ301 Intro to BizTalk Server 2004

1
(No Transcript)
2
Architecture
3
Architecture
Orchestration

• Message box stores messages
• Messages have rich properties
• Subscriptions link messages to services
• Declarative correlation
• Content-based routing
• Large Message Support

Activation Instance Management
Correlation Content-Based Routing
MESSAGE BOX
Message Pipeline
Decode Encode
Decrypt Encrypt
Parse Serialize
Extract Props
Auth Sign

Message Transport
SOAP
MSMQ
HTTP
MQSeries
Custom Adapters
4
BizTalk Solution Flow
5
Hosts
Host 2 (SvcAcct2)
Host 3 (SvcAcct3)
Host 1 (SvcAcct1)
Transport
Transport
Decrypt
Parse
Resolve Party
Serialize
Sign Encrypt
Message Box
6
Host Definition
Host A
AP1
AP2
AP3
Scale Invariant
Scale Invariant
Scale Variant
7
Adding Host Instances
Host Definition
Host Instances
Server1
Server2
Server3
Server4
8
Scalability

• BizTalk 2004 System is mostly stateless
• Routing is done in SQL Server by stored procs
• As long as DB is common its 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
• Stateless Exceptions
• Orchestration persisted (long running
  transactions)
• Correlation messages are routed to the correct
  machine
• Session-based protocols (e.g., MSMQT)

9
Scaling Out Processor Machines
Network Load Balance
SQL Server
Message box
Stored procs
Data (messages, subscriptions, etc.)
10
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

11
Scaling Out Storage
Network Load Balance
12
Storage Fail Over

• Generic SQL Cluster failover support
• 30-60 sec pause (!)

SQL Cluster
13
Biztalk Solution Development
14
Biztalk Dev Environment
Define Business Documents
Schemas
Orchestration
Model the Business Process
Pipelines
Visual Studio .NET
Mapping
Process Messages
Transform Data
15
Biztalk Development
DEVELOPMENT

• Developer produces
• Orchestrations
• Pipelines
• Schemas
• Maps
• Rules
• Use abstractions for physical locations
• Built into assemblies for deployment

16
Biztalk Deployment
DEPLOYMENT
DEVELOPMENT
Setup Copy Browser
Biztalk Config Db

• Get the bits on the box
• Deploy assemblies into GAC
• Register with Biztalk config db
• Configure the environment
• Map the developer logical to the real world
  environment
• Configure Relationships
• Partners, Roles

17
Biztalk Artifacts
18
Schemas
19
Supported Schema Types
Details
Schema Type

• Supports native XML message types
• Defined in XML Schema definition language (XSD)

XML

• Supports delimited or positional file formats
• Attribute tags are used to represent values
• Tag information is stored using the annotation
  capabilities of XSD

Flat File

• Special purpose schema type
• Defines promoted property fields
• Property fields can then be accessed by various
  BizTalk Server components

Property
20
Mapping
21
What is a Map?

• Defines the correspondence between records and
  fields in two different schemas

• Data Transformation
• Perform computational and other data operations
• Automatically inserts the data from one message
  into another during runtime
• Data Translation
• Change the format of data between messages
• Example translate to and from a flat file and an
  XML file

Destination Schema
Source Schema
Order
PO Number
Date
Item No
Quantity
Order Status
22
Types of Maps
Usage
Mapping Operation

• Most common type of mapping
• Values simply copied from input message to output
  message
• Supports most types of transformations and
  translations

Basic

• Records can occur multiple times for a single
  message (looping)
• Used for variable count record mapping

Complex
23
demo
Solution Development - 1
24
BizTalk Explorer

• Defines the deployment topology
• Integrated with Visual Studio
• UI for defining physical environment
• Define Send and Receive Ports
• Maps logical Orchestration ports to physical
  locations
• Maps applications to Hosts

25
Deployment Tools

• Deployment Wizard
• UI and Command Line
• GACs and registers assemblies
• Export config created by Explorer
• Biztalk Installer
• BizTalk specific VS Setup project
• Auto-packages BizTalk project output
• Point-n-click to add your projects
• Updates MSI package with every build
• Imports configuration scripts
• Extensible
• WMI APIs

26
Orchestration
27
BizTalk Orchestration

• Model and execute business processes
• .NET Integration
• .NET based engine
• Orchestration Designer Hosted in Visual Studio
• Rich semantics
• Long-Running Transactions and Compensation
• Flexible processes through business rules
• Deep Web Services Support including BPEL4WS
• Custom and advanced correlation
• Compose Orchestrations
• Rich document normalization
• Flexible binding options (Early, Late, Dynamic)

28
Stages of Orchestration Development
Define schemas to describe message formats
1
29
Orchestration Debugger Replay

• What path did this message take through an
  Orchestration?
• Replay shape for shape what happened
• Follow calls into other Orchestrations
• View exceptions thrown
• Examine compensation code executed

30
Orchestration DebuggerLive

• Why did the Orchestration do that?
• Attach to live Orchestrations
• Set Breakpoints
• Watch variables as you step through
• Retrieve current message contents
• Resume processing to next breakpoint

31
demo
Solution Development - 2