IBM’s Approach to SOA Governance

This Presentation Courtesy of the International SOA SymposiumOctober 7-8, 2008 Amsterdam Arenawww.soasymposium.cominfo@soasymposium.comFounding SponsorsPlatinum SponsorsGold SponsorsSilver SponsorsSOA Symposium October 7-8, 2008, AmsterdamESB Reference Architecture and Product Selection GuidelinesAndré TostSenior Technical Staff Member, SOA TechnologyIBM Software Services for WebSphere© 2008 IBM Corporation1SOA SymposiumAgenda Introduction Definition / Reference Architecture Patterns Federation Product Selection Criteria Sample Scenarios3ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumIntroduction4ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation2SOA SymposiumSOA Addresses Many PerspectivesBusiness ServicesSOA Entry PointsInfrastructure & Management in Support of SOAServiceManagementServiceSecurityBusiness Process ManagementServiceVirtualizationSOA Governance andService Lifecycle Management5ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumSOA Entry Points Help You Get StartedBoth Business Centric and IT FocusedWhat is it?ValueImproved productivity and flexibility by enabling targeted user Deliver role-based interaction and collaboration interactions for improved business operations and collaborationthrough servicesPeopleAchieve business process innovation through Greater innovation and flexibility treating tasks as modular servicesthrough faster deployment and Process modification of business processesProvide trusted information in business context Better business operations, more informed decisions and reduced by treating it as a service risk with information delivered in-line and in-contextInformationService-enable existing assets and fill portfolio Lower risk and faster time to market gaps with new reusable servicesby leveraging proven, time-tested functionalityReuseConnect systems, users, and business channels Reduced maintenance costs and based on open standardsgreater reliability and consistency Connectivitythrough flexible, any-to-any linkages6ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation3SOA SymposiumWhat are some of today's business challenges that SOA Connectivity can address?How do you…? Ensure seamless flow of information from anywhere at anytime using anything Execute broad business processes that span your company and business partners?  Build trusted relationships with your partners? Scale your business to grow smoothly? Deliver a consistent user experience regardless of channel or device?7ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumHow do you connect the assets and services that support your business process?Connectivity needsEnable "any-to-any" linkage and communication inside and beyond your companySimplify connectivity by ensuring secure, reliable, and scaleable pipeline of information8ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation4SOA SymposiumBusiness Value……Through SOA Connectivity…by exposing the same process Deliver a secure, consistent user experience…through new business channels and devicesStrengthen trading partner …with managed Service-based relationships…connections… over custom-built or traditional Potential savings of 2X-4X…connectivity*Minimize complexity in your … through anyorganization…-to-every connectivity…through scaleable access to Increased business flexibility and responsiveness…information in the right format and at the right time…by extending IT assets rather than Eliminate redundancy…duplicating themDecreased development and … through decoupling of function maintenance costs…and interface*Software Strategies“Enterprise Integration Chal enge” 20059ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumThree examples of SOA connectivityDeliver a process across multiple business channelsConnect to Connect external service business providerssystems1. Internal connectivity based on open standards 2. Deliver an existing process through new business channels3. Securely connect to external 3rd parties and trading partners10ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation5SOA SymposiumESB Definition11ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumCore Principles of the ESB Architectural PatternService Service ESBRequestorProvider ESB inter-connects requester and provider– Interactions are decoupled– Supports key SOA principle – separation of concerns ESB provides Service Virtualization of– Identity via routing– Interaction via conversion– Interface via transformation ESB also enables Aspect Oriented Connectivity– Security – Management – Logging– Auditing– … 12ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation6SOA SymposiumAn ESB-centric view of the Logical ModelBusiness ServicesInteractionProcessInformationyitruvicescrvicesreeeSSSt t nneeESBRegistrymtmeneglopamneaga MDeveBusiness ServicesnaTIMPartnerBusiness AppAccess Outside ESB Tightly coupled to ESB– Business Logic (Business Services)– Service Registry–ESB does contain integration logic or connectivity logic–Registry is a Policy Decision Point for ESB–Criteria: semantics versus syntax; aspects–ESB is a Policy Enforcement Point for Registry–But, Registry has a broader scope in SOA Loosely coupled to ESB–Tooling required for ESBSecurity and Management––Policy Decision Point outside the ESBDevelopment–ESB can be Policy Enforcement Point– Administration– Configuring ESB via Service Registry13ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumExpanded view of the ESBEnterprise Service BusMediation FlowsMediation PatternsMessage ModelsMeta modelsCommunication ProtocolsInteraction Patterns Communication Protocols–Supply basic connectivity to requesters and providers–Impact QoS (e.g., reliable delivery, transactions)–Supply inherent Interaction Patterns (e.g., request/reply, one-way, pub/sub) An ESB leverages underlying communication fabrics of SOA infrastructure–ESB provides on-ramps and off-rampsTypical requirements Standards are important–HTTP (SOAP/HTTP, XML/HTTP)–MQ (SOAP/JMS/MQ, XML/MQ, text/MQ, …)–Adapters (legacy, EIS)–WS-I, WS-Security–RAMP14ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation7SOA SymposiumExpanded view of the ESBEnterprise Service BusMediation FlowsMediation PatternsMessage ModelsMeta modelsCommunication ProtocolsInteraction Patterns Message Models–Describe messages exchanged with requesters and providers–Based on Meta-models–Fundamental means of describing messages Typical requirements–For example, XML Schema language– XML schema definition – Content models define specific messages– Industry specific content models–For example, XML schema An ESB supports one or more message meta-models An ESB supports multiple message content models–Can include industry standard models as well as enterprise specific models–Can include weakly-typed models15ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumExpanded view of the ESBEnterprise Service BusMediation FlowsMediation PatternsMessage ModelsMeta modelsCommunication ProtocolsInteraction Patterns Mediation Flows– Process messages exchanged between requester and provider via ESB– Large grained– Moderately reusable– Constructed from Mediation Patterns– Mediation Patterns define processing “steps” of a mediation flow– Small to middle grained–Typical requirementsHighly reusable––Dynamic routingESB products include pre-built “mediation primitives”– Logging16ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation8SOA SymposiumESB Mediation Flows and Mediation Patterns Mediation enables Service Virtualization of– Identity via routing–Using basic mediation patterns (context, content, contract)–Using composed mediation patterns (retry, failover, Distribution/aggregation, …)–Dynamic, driven by metadata in registry–Impact aspects of QoS (e.g., SLA, failover)– Interaction (of protocol and pattern) via conversion–Protocol conversion inherent with support for more than one transport protocol–Impact aspects of QoS (e.g., reliable delivery, transactions)– Interface via transformation–Using specific mediation patterns–Using adapters–Impact aspects of QoS (e.g., performance)–NOTE: other forms of mediation should be agnostic to interface (weakly-typed processing) Mediation enables Aspect Oriented Connectivity– Security & Management– Logging– Auditing– …  Provided by a mediation framework – Offering pre-built mediation pattern (primitives) support– Enabling mediation pattern composition17ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumMediation Patterns - ExamplesRequest / Request / Multi Event ResponseResponsePropagationProtocol TransformRouteDistributeMonitorCorrelateSwitchEnrich+++Canonical Transform – Log - RouteGatewayAdapter18ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation9SOA SymposiumAdapters for Existing Systems Integration An ESB must allow access to existing Enterprise Information Systems Adapters typically used, and may or may not be part of the ESB– Technology– Application– Legacy The following are the placement options for adapters, based on domain where adapter configuration managed:– Outside of the ESB, and inside the EIS domain– Outside the ESB, and the EIS domain– On the boundary of the ESB– Inside the ESB19ESB Reference Architecture and Product Selection Guidelines© 2008 IBM CorporationSOA SymposiumESB Patterns20ESB Reference Architecture and Product Selection Guidelines© 2008 IBM Corporation10