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.








See Also

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