Using the Pipeline Support Components
| 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. |
Microsoft ESB Guidance includes the following pipeline components:
- ESB Itinerary. You can use this component on the receive side (within a receive pipeline) to promote ESB metadata properties from SOAP headers into the message context. For more information, see The ESB Itinerary Component.** **
- ESB Itinerary Cache. You can use this component to cache itineraries and reapply them to response messages received within Solicit-Response send ports. For more information, see The ESB Itinerary Component.
- ESB JMS Decoder. You can use this component on the receive side (in a receive location) of an orchestration or a send port to parse out IBM JMS (MQRFH2) headers and preserve them as context properties. You can then access these context properties and modify them in the same way as any other BizTalk context properties. For more information, see The ESB JMS Encoder and Decoder Components.
- ESB JMS Encoder. You can use this component in a send port to write IBM JMS (MQRFH2) headers to messages. For more information, see The ESB JMS Encoder and Decoder Components.
- ESB Add Namespace. You can use this component in either a receive location or a send port to add namespaces to XML documents. For more information, see The ESB Add Namespace and Remove Namespace Components.
- ESB Remove Namespace. You can use this component in either a receive location or a send port to remove namespaces from XML documents. For more information, see The ESB Add Namespace and Remove Namespace Components.
- ESB Exception Encoder. You can use this component to send fault messages to the file system, InfoPath, or SharePoint. This component is part of the ESB exception handling mechanism, and it normalizes and enriches all exceptions processed by a send port. The component serializes exception information (including embedded persisted messages and context properties) into a canonical format so that all contained messages and the exception itself are available.
- ESB BAM Tracker. You can use this component to intercept the fault message emitted from the ESB Exception Encoder and insert the data within the message into the BAM Primary Import table (using the BAM Event Stream in the pipeline). This component is part of the ESB exception handling mechanism.
- ESB Dispatcher. You can use this component in a receive location (inbound pipeline) to dynamically set endpoint location properties for outbound messages. For more information, see The ESB Dispatcher Component.
- ESB Dispatcher Disassemble. You can use this component in a receive location (inbound pipeline) to dynamically set endpoint location properties for outbound messages. This component behaves in a very similar way to the ESB Dispatcher component, except that it transforms the result message (if you specify a value for the Transform property). The message passes through the XML Disassembler, which promotes properties and message types. The ESB Dispatcher Disassemble component also supports batched dispatch of multiple messages to different endpoints. For more information, see The ESB DispatcherDisassemble Component.