ESB Toolkit Tip #12: Use the Broker Service to make routing decisions in itineraries

The Broker Service in the ESB Toolkit is a powerful Itinerary Service but it’s not heavily documented and therefore probably not often used. Which is a shame because the Broker Service is the only service that allows you to select the next Service in the Itinerary, and thus change the entire path of execution that the Itinerary takes. In the current implementations the Broker Service is only available as a Messaging Service that executes within the Pipeline. No Orchestration-based Broker Service is provided.

Note that because it can only execute within a Pipeline you can’t use an Orchestration Service to connect to it but the Broker Service itself can connect to other Orchestration Services.

Itinerary Broker service








See Also

For more information on the Itinerary Broker Service in the ESB Toolkit see:

About the author

Tomasso Groenendijk lives in Netherlands and is a senior integration consultant at Motion10. He has over 15 years’ experience in software development and software design. Tomasso is specialized in application integration with a strong interest in the Windows Azure cloud platform. In 2014, 2015 and 2016 Tomasso was awarded with the Microsoft Azure MVP award. He is an active contributor to the integration community through his work on his blog, MSDN samples, TechNet Wiki and also speaking on events.

MVP profile Tomasso Groenendijk
Sentinet Product Specialist
BizTalk360 Product Specialist

Month List