Business Process Integration BizTalk Server 2004 Lex Oskam Developer and Platform Evangelism...

Business Process IntegrationBizTalk Server 2004

Lex OskamLex OskamDeveloper and Platform EvangelismDeveloper and Platform [email protected]@microsoft.com

Connection ImperativeImplications & Challenges

The ability to react on information Always up to date information

Adapt rapidly to changing business Mandate to connect “islands” of information

Integrate the virtual company Multi-system, multi-company, multi-audience

Company ACompany A

The Integration Challenge

Remote Office/ConsumersRemote Office/Consumers

MobileMobileEmployeesEmployees

Company BCompany B

Customers Customers Partners Partners SuppliersSuppliers

Remote Office/ConsumersRemote Office/Consumers

MobileMobileEmployeesEmployees

Business demand = everything connectedBusiness demand = everything connected

IT ChallengesIntegration “hurt” reached breaking point

Lack of integration Systems not designed to work together Interoperability an afterthought Expensive, hard, time consuming, brittle

Current model can’t keep up with businessCurrent model can’t keep up with business

Islands of Software and Data

?

??

?

Internet Internet BankingBanking

WirelessWireless

AggregationAggregation

Branch BankingBranch Banking

CRMCRM

Core Core BankingBanking

Wealth Wealth ManagementManagement

Treasury / Treasury / ForexForex

Trading / Back Trading / Back office office

Payment Systems and Card Payment Systems and Card MgmtMgmt 3D Secure3D Secure

Business Business IntelligenceIntelligence

EAIEAI

Straight through Straight through ProcessingProcessing

ATM / POSATM / POS

No Application is an island

Enterprises TodayTightly coupled applications

Packaged Application

Y

ERP Application

Unix Application

J2EE Application

.NET Application


X

CICS Application

AS/400 Application

Business Process IntegrationChallenges Different OS platforms Different application communication protocols

IIOP, RMI, DCOM, .NET Remoting… Different network protocols

TCP/IP, SNA… Different document formats

EDIFACT, CSV, XML… Different document definitions

SAP.Order ≠ JDEdwards.Order Different business processes

AKZO.ProcessOrder() ≠ DOW.ProcessOrder() Maintenance expensive

~ $7 per business application $ spent

Business Process IntegrationAn Idealized Picture


Y

ERP Application

Unix Application

J2EE Application

.NET Application


X

CICS Application

AS/400 Application

SOAP

Business Process IntegrationWeb services only part of solution… They provide a solution for:

Network protocol independancy HTTP anywhere

Platform independancy On any OS platform

Application platform independancy SOAP anywhere

Document format independancy XML anywhere

But in reality… Not all apps use web services… No standard XML.Order… (only branche specific)

No standard business process…

Business Process Integration Decoupling of applications


Y

ERP Application

Unix Application

J2EE Application

.NET Application


X

CICS Application

AS/400 Application

Business Process

Decoupling of applications

What is needed… Sending/Receiving messages Adapters: File, FTP, SAP, Webservice, …

Processing messaging Decoding, (Dis)Assemble, Party

Resolution,… Mapping message to Business

Process Subscriptions

Defining Business Processes

Business Process Integration Role of BizTalk Server


Y

ERP Application

Unix Application

J2EE Application

.NET Application


X

CICS Application

AS/400 Application

Business ProcessMessagingMessaging

OrchestrationOrchestrationBizTalk ServerBizTalk Server

Company BCompany B

Company ACompany A

BizTalk Server 2004EAI, B2B & BPM

Internet

Internet

ApplicationApplication





BizTalk ServerBizTalk Server

Reliable Messaging Process Orchestration Business Rules Engine Enterprise Single Sign-On Health and Activity

Tracking Business Activity Monitoring Human Workflow Services Off the Shelf Adapters &

Development Framework Web Services

AdapterAdapter

Receive PortReceive PortAdapterAdapter

HostHost

BizTalk Server 2004Basic Architecture

Orc

hes

trat

ion

#1

Orc

hes

trat

ion

#1

Orc

hes

trat

ion

#2

Orc

hes

trat

ion

#2

Send PortSend Port

TrackingTrackingDBDB

Config DBConfig DBDBDB

Business Business RulesRules

Send PipelineSend Pipeline

Publish and SubscribePublish and SubscribeMessage Box (SQL)Message Box (SQL)

Message Format 1Message Format 1Message Format 2Message Format 2

Receive PipelineReceive Pipeline

Connecting LOB applications

BTS 2004 Adapters Standard adaptersfrom Microsoft include: Web Services adapter

WSE 2.0 beta

MQSeries adapter SAP adapter File, HTTP, …

For building adapters: Microsoft.BizTalk.Adapter.Framework

namespace

Many third-party adapters: EDI adapter PeopleSoft

adapter Lots more

Messages Tools Within Visual Studio.NET:

Pipeline Designer Used to create custom pipelines

BizTalk Editor Used to create XSD message schemas

BizTalk Mapper Used to define mappings and XSLT

transformations between message schemas

BizTalk Mapper An Example Map

Business Process DesigningOrchestrations

Define the operations in a business process using shapes Compile into standard .NET assemblies

Example shapes: Decide: an if-then-else statement Loop: performs an action repeatedly Send: sends a message Receive: receives a message Parallel Actions: performs multiple

operations in parallel

Business Process Designing Design Tools

Within Visual Studio.NET: Orchestration Designer

Used to organize shapes that define a business process

Within Visio: Orchestration Designer for Business

Analysts Orchestrations can be imported and

exported between this and the Orchestration Designer

Business Process DesigningOrchestration Designer

Business Process Designing OD for Business Analysts

BizTalk Server 2004 Other Integration Platform

BPEL Definition

Generated

Process Definition ExchangeThe Business Process Execution Language for Webservices (BPEL4WS)

Web Services

Import/Export BPEL

Import/Export BPEL

MessageBox

Orchestration

State

Process

For processes with stable rules: inline

For processes with volatile rules: external

Modifiable Business Rules The Business Rules Engine

MessageBox

Orchestration

State

Process and Rules

Business RulesEngine

Rules

Process ImplementationState

Construct Message: allows declaring message variables, then setting their values

An orchestration’s state is automatically stored and reloaded as needed

MessageBox

State

Scope Y: Long-running

ERP Application

Process Implementation Scopes Scope: supports transactions

Atomic: recovery via rollback Long-running: recovery via compensation

BizTalk Server 2004 Engine x

2) Attempt update, fail

Scope X: Atomic

CICS Application

.NET Application

1) Update and commit

3) Compensate

Process Implementation Correlation Routes messages to an orchestration

instance based on their contents Doesn’t require the orchestration to

block waiting for a response message

BizTalk Server 2004 Engine

1

2

. . .

PO# 5978

Purchase Order

. . .

PO# 6013

Purchase Order

. . .

PO# 5978

Invoice

. . .

PO# 6013

Invoice

ERP Application


Process Implementation Aggregating Services into SOA


Unix Application

J2EE Application

CICS Application

AS/400 Application

Web Services Clients

Process Monitoring Health and Activity Tracking (HAT) Graphical access to information

about: When an orchestration starts and ends When each step it is executed When message is sent/received What’s in each message …

Tool: Health and Activity Tracking tool

Process Monitoring A HAT Tool Example


Process Monitoring Business Activity Monitoring Allows information workers to

monitor business processes

Tracking

Monitored Events and Messages

Microsoft Excel

Other Clients

Business Activity Monitoring (BAM)

Process Monitoring An Example BAM View

Scalability Support Host Instances

Requests are automatically load balanced across orchestrations and MessageBoxes

MessageBox

Machine B

Machine A

Orchestrations

Host Instance

P

Q

Orchestrations

R

S

Host Instance

Machine C

Orchestrations

Host Instance

P

Q

Machine D

Orchestrations

Host Instance

P

Q

MessageBox

Machine E

© 2004 Microsoft Corporation. All rights reserved.© 2004 Microsoft Corporation. All rights reserved.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.Content created by 3 Leaf SolutionsContent created by 3 Leaf Solutions

Business Process Integration BizTalk Server 2004 Lex Oskam Developer and Platform Evangelism...

Documents

Transcript of Business Process Integration BizTalk Server 2004 Lex Oskam Developer and Platform Evangelism...