Microsoft ESB Guidance
On November 8, 2007 Microsoft released the ESB Guidance. The ESB Guidance was developed by Microsoft patterns and practices team and the Connected Systems Division. It provides architectural guidance, patterns, practices, and a set of .NET and BizTalk Server components to simplify the development of Enterprise Service Bus (ESB) on the Microsoft platform and to allow companies to extend their messaging and integration solutions.
The Microsoft ESB Guidance is based on BizTalk Server 2006 R2 and extends its functionality to provide new capabilities that focus on building robust, connected, service-oriented applications. These capabilities include:
Policy driven mediation
- Itinerary-based service invocation that supports lightweight service composition at the time of message publication
- Dynamic resolution of endpoints and maps that enable decoupling the consumer from the services
- Message namespace normalization
- JMS/WMQ connectivity
- Support for messaging patterns that enable dynamic service aggregation, message routing, validation and transformation
- Service registry and repository integration using UDDI and WS-MetadataExchange
Management and Monitoring
- Exception mediation and fault management
- Support for message repair and resubmission
- Exception alerts and subscriptions
- BizTalk endpoint and registry integration, management and publication
- Reporting and analytics for exceptions, alerts, and registrations
- Sample management Web portal
- Integration with SOA governance solutions including SOA Software and AmberPoint
Microsoft ESB Guidance contains the following:
ESB Web Services
- Itinerary On-ramp – accepts external messages and submits them for processing. The ESB Itinerary SOAP headers contain metadata and processing instructions that describe what services or maps to execute and/or endpoints to route to.
- Resolver – provides resolution of endpoints or maps based on business rules policies, UDDI registrations, static invocation, WS-MetadataExchange interface, XPATH or custom .NET components that implement IResolveProvider interface.
- Transformation – performs message transformation
- Exception Handling
- UDDI – provides capability to look up endpoint based on the service name, business provider, or business category and manipulate business providers, services and categories stored in UDDI repository.
- BizTalk Operations – exposes information about BizTalk hosts, orchestrations, applications and status
- ESB Pipeline Interop Components – used in BizTalk pipelines
- ESB Resolver and Adapter Provider Framework – provides configurable and pluggable architecture for dynamic resolution of endpoints, transformation requirements and for routing messages
- Itinerary Processing – provides capability for dynamically describing, submitting and executing multiple service invocations or routing/transformation requests
- Exception Management Framework – captures exceptions from BizTalk Messaging and Orchestration subsystems and generates fault messages
- ESB Management Portal – provides exception and fault tracking, message resubmission, alerts, notification, UDDI integration, configuration, reporting and analytics.
- ESB Sample Applications