There are multiple ways of executing or invoking our itineraries, where the message sender provides explicitly more or less information about the itinerary to execute:
Submitting the message through the ESB Itinerary Web Services: The client sends the message invoking those web services and attaching to the request a SOAP header that contains the actual itinerary to execute. In this scenario, the initiator has full control and responsibility over what steps compose the itinerary. We will know more about this on the chapter dedicated to the ESB Web Services.
Using the Itinerary Selector pipeline component with dynamic resolution: The message is received through a port whose receive pipeline uses the Itinerary Selector, configured with a resolver connection string that will find out the itinerary to apply (for example, a BRI resolver connection string). In this scenario, the consumer has relative control over the selection of the itinerary, as some information provided...
