Share via

ESB Web Services

  • Article
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 Microsoft ESB Guidance contains the following Web services:

  • Itinerary On-ramp Web services. These accept external messages and submits them for processing. The ESB Itinerary SOAP headers contain metadata and processing instructions that describe the services (orchestrations) or maps to execute and/or the endpoints to route to. These services support both one-way and request-response processing for SOAP or WCF-WSHttp methods. The Itinerary On-ramp services are not message type-specific, and they accept any message type.
  • Resolver Web service. This allows external applications to call the Microsoft ESB Guidance Resolver Framework to look up ESB endpoints based on resolution mechanisms supported by the Resolver Framework. The service is exposed through SOAP and WCF-WSHttp. The available resolution mechanisms include the following:
    • Business rules policies
    • UDDI registrations
    • Static invocation
    • WS-MetadataExchange interface
    • The content of the message (XPATH)
    • Any custom .NET component that implements the IResolveProvider interface
  • Transformation Web service. This provides features to transform message content and fulfill business requirements. Transformations can take place directly on an incoming message or on messages retrieved from the BizTalk Message Box database. This service leverages the BizTalk caching libraries but circumvents the requirement to publish messages directly into the BizTalk Message Box database, allowing execution of BizTalk maps by non-BizTalk applications. The service is exposed through SOAP and WCF-WSHttp.
  • Exception Handling Web service. This accepts exception messages from external sources and publishes them to the ESB Exception Management Framework. From there, the fault processor pipeline will normalize, track, and publish the exception message to the ESB Management Portal. The service is exposed through SOAP and WCF-WSHttp.
  • UDDI Web service. This allows applications and users to look up endpoints based on the service name, business provider, or business category; it also allows applications and users to manipulate the business providers, services, and categories stored in a UDDI repository. This is a key infrastructure service used by the ESB Management Portal and third party providers. The service is exposed through SOAP.
  • BizTalk Operations Web service. This exposes information about BizTalk hosts, orchestration, applications, and status. Users and third parties can easily query for application and host status, regardless of the location of computer(s) within the BizTalk group. Queries can include message status and flow, status changes, current service instances, and message details. The service can also update receive locations. This is a key infrastructure service used by the ESB Management Portal and third party providers. The service is exposed through SOAP.

For information about the Web services provided with the ESB Guidance, see Using the ESB Guidance Web Services.