The ESB Dispatcher Component
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 Dispatcher component dynamically sets endpoint location properties for outbound messages. It uses the resolution mechanisms registered with the ESB Guidance, which consists of resolvers and adapter providers within the Resolver Framework and the Adapter Provider Framework.
Resolver and Adapter Types
The ESB Guidance includes the following resolvers:
- WS-MetaDataExchange
- XPATH
- STATIC
- Business Rules Engine
- UDDI
The ESB Guidance includes the following adapter providers:
- WCF-WSHttp
- WCF-BasicHttp
- MQSeries
- FTP
- FILE
The Dispatcher component also uses the Transform libraries that ship with the ESB Guidance to execute BizTalk maps.
Component Properties
The component has three properties:
- Enable. This property enables or disables the component.
- EndPoint. This property is a connection string in a format registered with the ESB Guidance, such as in the following example:
STATIC:\\TransportType=;TransportLocation=https://localhost/ESB.CanadianServices/SubmitPOService.asmx;Action=;EndPointConfig=;JaxRpcResponse=false;MessageExchangePattern=;TargetNamespace=https://globalbank.esb.dynamicresolution.com/canadianservices/;TransformType=;
WSMEX:\\serverUrl=https://localhost:9904/wsmex;QName={http://globalbank.esb.dynamicresolution.com/canadianservices/}OrderPurchaseWebService
UDDI:\\serverUrl=https://localhost:9901/rmengine;serviceName=OrderPurchaseWebService;serviceProvider=Microsoft Practices ESB
UDDI:\\serverUrl=https://localhost/uddi;serviceName=OrderPurchaseWebService;serviceProvider=Microsoft.Practices.ESB
XPATH:\\TransportType=;TransportLocation=/*[local-name()='OrderDoc' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/']/*[local-name()='ID' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/'];Action=;EndPointConfig=;JaxRpcResponse=;MessageExchangePattern=;TargetNamespace=/*[local-name()='OrderDoc' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/']/*[local-name()='customerName' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/'];TransformType=;
STATIC:\\TransportType=WCF-WSHttp;TransportLocation=https://localhost/ESB.CanadianServices/SubmitPOService.asmx;Action=;EndPointConfig=;JaxRpcResponse=false;MessageExchangePattern=;TargetNamespace=https://globalbank.esb.dynamicresolution.com/canadianservices/;TransformType=;
BRE:\\policy=GetCanadaEndPoint;version=;useMsg=;
- Transform. This property is either the fully qualified name of a map or a connection string format registered with the ESB Guidance:
- The following is an example of a map name:
GlobalBank.ESB.DynamicResolution.Transforms.SubmitOrderRequestNA_To_SubmitOrderRequestCN, GlobalBank.ESB.DynamicResolution.Transforms, Version=1.0.0.0, Culture=neutral, PublicKeyToken=c2c8b2b87f54180a
- The following are examples of connection strings:
BRE:\\policy=CanadaSubmitOrderMaps;version=;useMsg=;
WSMEX:\\serverUrl=https://localhost:9904/wsmex;QName={http://globalbank.esb.dynamicresolution.com/canadianservices/}CanadaSubmitOrderMaps
UDDI:\\serverUrl=https://localhost:9901/rmengine;serviceName=CanadaSubmitOrderMaps;serviceProvider=Microsoft Practices ESB
UDDI:\\serverUrl=https://localhost/uddi;serviceName= CanadaSubmitOrderMaps;serviceProvider=Microsoft.Practices.ESB
XPATH:\\TransportType=;TransportLocation=/*[local-name()='OrderDoc' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/']/*[local-name()='ID' and namespace-uri()='http://globalbank.esb.dynamicresolution.com/northamericanservices/'];Action=;EndPointConfig=;JaxRpcResponse=;MessageExchangePattern=;TargetNamespace;TransformType=;
- The following is an example of a map name: