IBM公司ESB、WEBSPHERE、SOA技术交流.pptVIP

* * * * * * * * * Thank You ! * Note that several parts of the are SOA Foundation inter-connected by the ESB, namely the Interaction Services, Process Services, Information Services, Partner Services, Business Application Services and Access Services, have been grouped into a single category labeled Applications Services positioned outside the ESB. The parts of the Foundation grouped as application services are used to implement different forms of service requesters and service providers, i.e., the application or business logic in a solution, targeted at achieving domain-specific business goals. The ESB implements the connectivity or integration logic in a solution, performing service virtualization and aspect oriented connectivity, targeted at achieving on-demand inter-connectivity between application service requesters and providers. In an ideal service oriented solution, separation of application/business logic and connectivity/integration logic is “clean,” meaning that the service requesters and service providers, i.e., the application service contain no connectivity/integration logic, and that the ESB contains no application/business logic. Only by architecting this clean separation can an enterprise achieve the flexibility, agility and reuse sought from SOA. It is sometimes difficult to distinguish between application/business logic and connectivity/integration logic. There are no strict guidelines, and in fact, the choice may depend on the nature of the enterprise, or even a particular situation within the enterprise. One guideline that often works leverages the distinction between semantics and syntax. If the logic creates, reads, updates or deletes the semantics associated with achieving business goals, it is application/business logic. If the logic only modifies syntax associated with achieving the necessary inter-connectivity, it is connectivity/integration logic. A related guideline leverages interaction characteristics. Application/business logic is ac