To ESB Toolkit or not to ESB Toolkit - PowerPoint Presentation

Slide1

To ESB Toolkit or not to ESB Toolkit

ESB Toolkit patterns and practices

Tomasso GroenendijkSlide2

Overview

2

So What’s The Difference?

Classic BizTalk

Rethinking The Solution As A Set Of

Capabilities

When to use it

Disadvantages

Benefits

Demo:

Using

ESB Itineraries

Changes in BizTalk artifacts & ESB Process

Change in a Map & XSD

Demo:

How

to deploy changes

SummarySlide3

So What’s The Difference?

BizTalk was positioned as a Hub and spoke

Now we’re saying it can be

an Enterprise Service Bus?Slide4

BizTalk...

BizTalk+ESB Toolkit

...

ESB

Toolkit is all about runtime

resolution

I

t

interacts with external services

to get operational configuration in a JIT manner ESB Toolkit adds a set of runtime resolution capabilities that BizTalk developers would need to create from scratch

BizTalk is all about providing solutions based on

configuration Configuration happens at dev time or post-deploymentSlide5

Classic BizTalk

Static Receive Port

Hard-Coded Map Name

Static

Schema

Static Send Port

Statically bound

orchestration

Single

Service

Single

Schema

Static Receive Port

Hard-Coded Map Name

Static

Schema

Static Send Port

Statically bound

orchestration

Single

Service

Single

Schema

All

decisions are made and locked

in at

Design Time or at

Deployment.

Any change is a re-development or

a

system

re-configuration.Slide6

Rethinking The Solution As A Set Of Capabilities

Dynamic Resolution

Resolved Itinerary

Generic

Off Ramp

Generic

On Ramp

Multiple

Schemas (

xN

)

Multiple Services (

xN

)

Transform Service

Routing

Process Orchestration

Enables

policy- or configuration-based routing at

runtime

Avoids requirement to hard-code components and servicesSlide7

When to use it

In the project is a need for Reusable Components, SOA & Agile

Larger

projects

The

business processes in BizTalk can be

divided

in Reusable

Components. It’s required to have NO D

owntime when

deploying a change The complexity of the business processes that is going to be automated in BizTalk is relatively

simple.

As few as possible Receive Ports or Send Ports in BizTalk.

Low Latency scenarios.

You don't use Parties in the BizTalk solution (EDI)Slide8

Disadvantages

ESB Toolkit is Complex.

Little documentation.

Installation is

difficult.

Framework (BizTalk 2009 / BizTalk 2010)

Management Portal.

It’s

not fully functional out of the box. Instead it provides a base set of ESB components that must be

extended.

Management Portal is sample.

Performance

Off Ramps are Dynamic Ports.Slide9

Benefits

Reusing of services

Pipeline components & Orchestrations

Deployment of changes / new versions

Orchestrations are not bound to a Map or a .XSD

Out of the box

BAM

Centralized Error handling

Management Portal Performance

CacheLow latency

Using Pipeline components instead of OrchestrationsSlide10

Demo:

Using ESB Itineraries

In this demonstration, you will see

:

Using itineraries

Itinerary Services

Resolvers

Using Business Rules in a Resolver

Using Custom Messaging Services Using Custom Orchestration ServicesSlide11

Demo:

Using ESB Itineraries

Policy

Rules

UBL

SalesOrder

BSON

document

WareHouse

Dynamics AX

document

Warehouse

document

UBL

ReceiptAdvice

WareHouse

DespatchAdvice

Generic

Generic

On Ramp

SalesOrder

Itinerary

DynamicsAX

Service

Tracking

Service

Routing

ServiceSlide12

Changes in BizTalk artifacts & ESB Process

In

the event of a

change,

there’s much less disruption with this model.

Modify Orchestrations

Modify Maps

Modify XSD schemas

The ESB layer can modify the configuration without changing the individual applications themselves.

Add / Remove Itinerary services

Modify ResolversModify

Business RulesSlide13

Change in a

Map

Deployment steps

:

Disable

specific Receive

Locations

Only

remove the maps from BizTalk

BizTalkMgmtDb when deploying a

change

Don't remove the Assembly from the GAC so other maps can still be executed

Orchestrations are not bound to a specific map because transformations are performed by MapHelper

classDon't have to be removed when deploying a

changeSlide14

Change

in

a XSD schema

Deployment steps:

Disable

specific Receive

Locations

Only

remove the maps from BizTalk

BizTalkMgmtDb

Don't remove the Assembly from the GAC so other Maps can still be executed

Only remove the XSD schemas from BizTalk BizTalkMgmtDb

Don't remove the Assembly from the GAC so other XSD schemas can still be executed

Orchestration are not bound to a specific XSD schema because the Message Type is XmlDocument

Don't

have to be removed when deploying a changeMaps are bound to a specific XSD schema Slide15

Demo: Deploying changes

with NO

Downtime

for other Processes

In this demonstration, you will see

:

Deploy a change

in

Business ProcessDeploy a change in a Map

Deploy a change in a XSD schema Slide16

Policy

Rules

UBL

SalesOrder

BSON

document

WareHouse

Dynamics AX

document

Warehouse

document

UBL

ReceiptAdvice

WareHouse

DespatchAdvice

Generic

Generic

On Ramp

SalesOrder

Itinerary

DynamicsAX

Service

Tracking

Service

Routing

Service

Demo: Deploying changes

with NO

Downtime

for other ProcessesSlide17

Demo: UBL Schemas & Maps in the ESB

Canonical Schemas:

Assembly:

itHero.UBL.Schemas

UBL_DespatchAdvice_2_0

UBL_Order_2_0

UBL_Invoice_2_0

UBL_ReceiptAdvice_2_0

Maps:

Assembly: itHero.Warehouse.TransformsDespatchAdvice_to_UBLDespatchAdvice

UBLOrder_to_Order

Assembly: itHero.DynamicsAX.Transforms

UBLOrder_to_AXSalesOrderUBLReceiptAdvice_to_AXCustomerSlide18

Summary

Provides the right benefits to cope with

complex and rapidly changing integration challenges

Higher levels of

SOA,

S

ervice re-use

Faster adaptation to business

changes

Visibility business and exception metricsHighly extensible to introduce new functionality or encapsulate patterns

Centralized exception management Slide19

Questions?

linkedin.com/in/

tomassogroenendijk

twitter.com/

tlagroenendijk

www.ithero.nl

tomasso.groenendijk@motion10.com