ESB Notes

• End to end integration problem: a set of autonomous services can quickly devolve into a spaghetti-code-like structure that becomes difficult to maintain. A change will be big impact

• ESB: moving the logic away from each individual set of endpoints into a logically centralized layer

• Benefit of ESB: software is easy to maintain
• What ESB provides:

•        data transformation

•         protocol conversion

•         dynamic routing, and error handling

•         Visibility into what is happening to a particular application or interaction.

• If a service changes, the application need not even be aware of that change because the ESB layer can modify that configuration without changing the application
• BizTalk ESB Toolkit uses existing BizTalk Server features is a codification of many BizTalk best practices

• Traditional approach: A typical BizTalk application might have these elements bound together statically during design or deployment, making agile modification more difficult.

• Workaround: can use orchestration and other ways to get the message to message box with promoted properties acting as a OnRamp receive port

• BizTalk supported adapters:
  • WCF-BasicHttp
  • WCF-Custom
  • WCF-WSHttp
  • FTP
  • File
  • SMTP
  • WebSphere MQ

• the framework provides facilities for normalizing all exceptions, enriching them, applying Business Activity Monitoring (BAM) tracking, and publishing the final output to the Exception Management database for display and reporting in the ESB Management Portal.

• The resolver can

•        Determine itinerary

•        Determine endpoint information

•        Which orchestration to use

•        Which map to apply

• enterprise service bus (ESB) is a software architecture construct which provides fundamental services for complex architectures via an event-driven and standards-based messaging engine (the bus).