To ESB Toolkit or not to ESB Toolkit

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

2. Overview • 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 • Summary

3. So What’s The Difference? • BizTalk was positioned as a Hub and spoke • Now we’re saying it can be an Enterprise Service Bus?

4. Classic BizTalk Single Schema 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. 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 • Enables policy- or configuration-based routing at runtime • Avoids requirement to hard-code components and services Resolved Itinerary Routing Transform Service Process Orchestration Generic On Ramp Generic Off Ramp Multiple Schemas (xN) Multiple Services (xN)

6. 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 Downtime 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)

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

8. 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 • 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 Generic On Ramp Generic TrackingService DynamicsAX Service RoutingService WareHouseDespatchAdvice Policy UBLReceiptAdvice Rules Dynamics AX document BSON document Warehousedocument WareHouse

11. 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 Resolvers • Modify Business Rules

12. Change in a Map • Orchestrations are not bound to a specific map because transformations are performed by MapHelperclass • Don't have to be removed when deploying a change • 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

13. Change in a XSD schema • Orchestration are not bound to a specific XSD schema because the Message Type is XmlDocument • Don't have to be removed when deploying a change • Maps are bound to a specific 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

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 Generic On Ramp Generic TrackingService DynamicsAX Service RoutingService WareHouseDespatchAdvice Policy UBLReceiptAdvice Rules Dynamics AX document BSON document Warehousedocument 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