Using Itinerary Processing

Retired Content

This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

The ESB Guidance contains a powerful mechanism that enables lightweight dynamic itinerary specification and processing. Receive locations and receive pipelines are the “on-ramps” to the ESB from the outside world. Messages from external clients enter through a receive pipeline, and the ESB optionally uses metadata stored in each message to determine the processing requirements for each message. The Itinerary schema, exposed as the Itinerary SOAP header, defines these properties, which the client should set before submitting the message.

This section describes the itinerary processing features of the ESB Guidance. It contains the following topics: