The document discusses the ESB Toolkit and its evolving approach to integration compared to classic BizTalk, highlighting differences such as dynamic versus static bindings and the use of itineraries. It emphasizes the benefits of increased flexibility, faster adaptation to change, and enhanced visibility in complex integrations, while also noting the challenges and lack of extensive documentation. Additionally, it presents demos showcasing the deployment of changes without downtime and management of various schemas and orchestration services.

1. To ESB Toolkit or not to ESB
Toolkit
ESB Toolkit patterns and practices
Tomasso Groenendijk

2. Overview











2

3. So What’s The Difference?



4. Classic BizTalk


All decisions are made and locked in at
Design Time or at Deployment.
Any change is a re-development or
a system re-configuration.
Single
Schema
Single
Schema
Static Receive
Port
Static Receive
Port
Hard-Coded
Map Name
Hard-Coded
Map Name
Statically bound
orchestration
Statically bound
orchestration
Static
Schema
Static
Schema
Static Send
Port
Static Send
Port
Single
Service
Single
Service

5. Rethinking The Solution As A Set Of
Capabilities
Dynamic Resolution


Generic
On Ramp
Routing
Transform
Service
Process
Orchestration
Generic
Off Ramp
Resolved Itinerary
Multiple
Schemas (xN)
Multiple
Services (xN)

6. When to use it








Larger projects

7. Disadvantages


Little documentation.


Framework (BizTalk 2009 / BizTalk 2010)
Management Portal.


Instead it provides a base set of ESB components that
must be extended.
Management Portal is sample.

Off Ramps are Dynamic Ports.




8. Benefits


Pipeline components & Orchestrations

Orchestrations are not bound to a Map or a .XSD

Management Portal


Cache
Low latency
 Using Pipeline components instead of Orchestrations





9. 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 Services

10. Demo: Using ESB Itineraries
UBL
SalesOrder
SalesOrder Itinerary
WareHouse
DespatchAdvice
UBL
ReceiptAdvice
Generic
On Generic
Ramp
Tracking
Service
DynamicsAX
Service
Routing
Service
Policy
Rules
BSON
document
Dynamics AX
document
Warehouse
document
WareHouse

11. Changes in BizTalk artifacts & ESB Process




Modify Orchestrations
Modify Maps
Modify XSD schemas



Add / Remove Itinerary services
Modify Resolvers
Modify Business Rules


12. Change in a Map






13. Change in a XSD schema


Don't have to be removed when deploying a change

Don't remove the Assembly from the GAC so other
Maps can still be executed

Don't remove the Assembly from the GAC so other
XSD schemas can still be executed





14. Demo: Deploying changes with NO Downtime
for other Processes
In this demonstration, you will see:

Deploy a change in Business Process

Deploy a change in a Map

Deploy a change in a XSD schema

15. Demo: Deploying changes with NO Downtime
for other Processes
UBL
SalesOrder
SalesOrder Itinerary
WareHouse
DespatchAdvice
UBL
ReceiptAdvice
Generic
On Generic
Ramp
Tracking
Service
DynamicsAX
Service
Routing
Service
Policy
Rules
BSON
document
Dynamics AX
document
Warehouse
document
WareHouse

16. Summary
Provides the right benefits to cope with
complex and rapidly changing integration challenges

Higher levels of SOA, Service re-use

Faster adaptation to business changes

Visibility business and exception metrics

Highly extensible to introduce new functionality
or encapsulate patterns

Centralized exception management

17. Questions?
www.ithero.nl
tomasso.groenendijk@motion10.com
twitter.com/tlagroenendijk
linkedin.com/in/tomassogroenendijk