Hide Notes 

Slide 1: Service Oriented Architecture Based Integration Mike Rosen CTO, AZORA Technologies, Inc. Mike.Rosen@Azoratech.com
Slide 2: Mike Rosen systems ACCESS TO THE EXPERTS Consultant • Chief Enterprise Architect for service and component based – Finance, Insurance, Telecom • SOA, EA, MDA implementation and training • 20 years experience in distributed applications Author • Cutter Consortium – “Service Oriented Integration – Aligning SOA with Enterprise Integration” – “Implementing SOA on Common Technologies” • Implementing SOA Applications, due 2005 • Developing e-Business Systems and Architecture: A • Manager’s Guide, 2000, Morgan-Kaufman Integrating CORBA and COM Applications, 1998, Wiley. © Michael Rosen 2005 Slide 2
Slide 3: Agenda Enterprise Application Integration Web Services to the Rescue What is Service Oriented Architecture? Business and Integration Services Enterprise Architecture for SOI Conclusion © Michael Rosen 2005 Slide 3
Slide 4: A Typical Integration Scenario Data Bank 1 Account System EAI Data Integration Bank 1 Loan System Data Data EAI Method Integration Data Bank 2 Account System Bank 1 Credit System Bank 2 Loan System Data Data Bank 2 Credit System © Michael Rosen 2005 Slide 4
Slide 5: Typical Enterprise Application Integration Enterprise Integration Server Adapter CICS System Transform Process Automation Adapter Integration Point ERP CRM … Packaged Application © Michael Rosen 2005 Slide 5
Slide 6: Enterprise Application Integration Described by Process Automation/Workflow Adapters interface with applications at their integration points Transformers change data and/or message format Enterprise Integration Server provides runtime Good concepts to apply to a bus model, rather than pointto-point © Michael Rosen 2005 Slide 6
Slide 7: The EAI Solution Doesn’t Scale Data Bank 1 Loan System Bank 1 Account System Data Data Bank 2 Loan System Bank 1 Credit System Bank 2 Account System Data Data Data Bank 2 Credit System © Michael Rosen 2005 Slide 7
Slide 8: Enterprise Application “Spaghetti” © Michael Rosen 2005 Slide 8
Slide 9: EAI and Web Services Then… • Previous EAI products used proprietary protocols and techniques • EAI applications were too expensive to implement. Many attempts • at EAI failed Most EAI implementations created point-to-point connections, essentially new EAI stovepipes Now… • All EAI vendors are transitioning to Web Services to replace • • proprietary protocols COTS vendors are also supporting Web Services, thus driving down the cost of connectivity and integration Service Oriented Integration, using a new class of product call the Enterprise Service Bus, is now the target of EAI © Michael Rosen 2005 Slide 9
Slide 10: Web Services to the Rescue? Service Web Service Service Web Service … SOAP Service Bus Web Service Web Service Service Application Service Adapter … © Michael Rosen 2005 Slide 10
Slide 11: SOA History Service Oriented Architecture (SOA) is NOT new! Many Successful SOA Applications have been built in the past: • CORBA (Wells Fargo, Credit Suisse) • Tuxedo Many, many more attempts at SOA failed But, we can learn from what failed, and what succeeded © Michael Rosen 2005 Slide 11
Slide 12: SOA is Hard! Previous technical infrastructures were very difficult to master We did not adequately understand the characteristics of services and service design Requires an understanding of the business and information and a strategic vision Requires an architectural based approach • But architecture is hard too! Requires an appropriate methodology Requires a supporting organizational structure © Michael Rosen 2005 Slide 12
Slide 13: …And Now, the Rest of the Story Business Business Model Model Enterprise Business Process Infrastructure and Frameworks Web Service Web Service Defines tools, processes and technology for combining services into EBP define Service Specifies Definition and requirements of a service Defines communications technology for application integration ‘SOAP Service Bus’ Web Service Defines common semantics and data Processes, Processes, Guidelines, Guidelines, Tools Tools © Michael Rosen 2005 Common Semantics and Data Application Service Adapter Specifies service wrapping techniques Slide 13
Slide 14: What is an SOA? SOA is concerned with the independent construction of services which can be combined into meaningful, higher level business processes within the context of the enterprise. A Service Oriented Architecture describes several aspects of services within an enterprise: • The granularity and types of services • How services are constructed • How the services communicate at a technical level • How the services are combined together (i.e. orchestrated) • How the services interoperate at a semantic level (i.e. how they • share common meanings) How services contribute to IT and Business Strategy Slide 14 © Michael Rosen 2005
Slide 15: Service Oriented Integration SOI An architectural and technology based approach to exposing and integrating existing applications as services Builds on EAI technology, using new Web services based platforms Exposes services to a bus, not point-to-point Extends SOA to integration solutions © Michael Rosen 2005 Slide 15
Slide 16: SOI: A Better Solution Channels Customer Management Marketing Pricing ESB Business Service Bus Account Service Loan Service Credit Service Other Services ESB Integration Service Bus Bank 1 Account System Bank 1 Loan System Bank 1 Bank 2 Bank 2 Credit System Account System Loan System Bank 2 Credit System © Michael Rosen 2005 Slide 16
Slide 17: Benefits of SOA Integration Approach Integrate once, connect many • Each system is integrated once into the service bus, rather than many time • for each point-to-point connection Less cost, consistent access Build up higher level business services • Combine lower level operations into business services that align with the • goals and strategy of the new enterprise, rather than of the old systems Quickly construct high-level, high-value business processes from the business services in response to new initiatives, competitive pressures, regulatory changes, … Flexibility • Multiple services can be easily constructed from the integration of existing • applications New processes can be constructed from the service © Michael Rosen 2005 Slide 17
Slide 18: Benefits of SOI Approach (2) Adaptability to change • Business Processes change quickly • Operational Systems are difficult, costly and slow to change – Layered SOI approach enables quickly reconfiguring processes or services without needing to change operational systems • Operational systems are retired or replaced – Layered SOI approach allows operational systems to change without affecting business processes Incremental Approach • Start small • Add new integration services, business services and processes • over time, as part of specific projects, in response to specific business needs Flexibility and capabilities increase exponentially with each new service. Slide 18 © Michael Rosen 2005
Slide 19: Hierarchy of Service Types Enterprise Business Process uses Business Service ... uses uses Business Service Domain Service ... uses uses Domain Service Implemented by Internal Business Process uses Business Component ... Integration Service © Michael Rosen 2005 Slide 19
Slide 20: Factors Affecting Services Granularity – Amount of work performed per invocation • Fine • Medium • Large Visibility – Who can see and invoke the service • Published • Public • Private Scope – Organization unit or boundary for the service • Application • Workgroup • Line-of-business or division • Enterprise © Michael Rosen 2005 Slide 20
Slide 21: Integration Services An architectural and implementation approach to integration using Web services and SOA Data Integration Service – provides data integration between multiple applications. Initiated by a legacy system in which data has changed. Frequently implemented as Publish and Subscribe. Functional Integration Service – provides shared functionality between multiple applications. Initiated by the application requiring the functionality. Not the same as SOA Business Services!!! • Although often treated the same. © Michael Rosen 2005 Slide 21
Slide 22: Integration Services (2) Integration services provide interface to existing application Interface granularity influenced by existing applications Synchronous Invocation is common ACID Transactions may be required Not exposed directly to business services • Wrapped by business components or other services • Hide internal API’s, data models and application topology • Enhance, modify or combine existing functionality © Michael Rosen 2005 Slide 22
Slide 23: Integration Service Pattern Service Invocation Service Facade Legacy Adapter Component Component Legacy Applications Component Legacy Adapter Component Service Implementation © Michael Rosen 2005 Slide 23
Slide 24: Common ‘Bottom Up’ Approach Start with existing application functionality • Expose functionality as a ‘service’ using existing API • Expose data model in the service interface • Creates dependency between existing application and new service • • interface API and data model dependencies create functionally and semantically incompatible service interactions, essentially limiting service to point-topoint integration Not driven by enterprise requirements Promoted by tool vendors • Service interface can be generated • Makes a great demo EAI all over again • New Web services technologies • Same old architectural problems © Michael Rosen 2005 Slide 24
Slide 25: Layered Enterprise SOI Architecture Business Processes Business Services Components and Integration Services WS WS WS IS IS IS IS IS Enterprise Resources © Michael Rosen 2005 Slide 25
Slide 26: SOI Enterprise Architecture Layers Layer 1 – Enterprise Resources and Operational Systems • Consist of existing applications, legacy and COTS systems, CRM • • and ERP applications, and older OO implementations Provide ‘business operations’ – transactions implementing single units of work within the operational systems Typically access or modify data in a ‘System of Record’ Layer 2 – Components and Integration Services • Integration Services provide access to the resources and systems • • • • of Layer 1 Components wrap integration services Components provide a ‘single point of contact’ for integration services, preventing a proliferation of cut-and-paste code Components are typically implemented with EJB or .NET Integration services are increasingly being implemented with Web services Slide 26 © Michael Rosen 2005
Slide 27: SOI Architecture Layers (2) Layer 3 – Business Services • Provide high level business functionality throughout the enterprise • Provide a ‘service interface’ layer of abstraction to the functionality • • of layer 2 Services are managed, governed enterprise assets with SLAs Represent a logical grouping of component, integration services and operations Layer 4 – Business Processes • Processes are a series of activities which are executed in an • • • ordered sequence according to a set of business rules (called a choreography or business process model) Executed in response to business events Provide long-running sets of activities Composed of multiple services and typically involving multiple service invocations Slide 27 © Michael Rosen 2005
Slide 28: Enterprise Information Design Equally important to enterprise flexibility and agility Defines the business semantics needed to support the enterprise processes and services Critical to ‘ad-hoc’ combination of services into business processes Coordinated with enterprise process design © Michael Rosen 2005 Slide 28
Slide 29: Enterprise Information Layers Process Data Model Documents Semantic Data Model Enterprise Data Virtual Object Model Semantic Objects Consolidated Data Xform Xform Integration Data Operational Data Model SOR Physical Model Operational Data © Michael Rosen 2005 Slide 29
Slide 30: Enterprise Information Layers (2) Operational Data • Resides in systems of record and other operational data stores • Described by the ‘Physical Data Model’ Integration Data • Operational data is exchanged between operational systems • Data is extracted from one system, transformed, and the loaded to another Semantic (Consolidated) Data • Provides the data required by the service interfaces • Described by the ‘Virtual Data Model’ • Implemented by a mapping/transformation of the operational data Enterprise Data • Business Documents provide a composite of semantic business objects to support enterprise processes © Michael Rosen 2005 Slide 30
Slide 31: Scope of SOA Constructs Enterprise Scope Enterprise Concerns Line of Business Scope Workgroup Scope Application Scope Organizational independence Scope Slide 31 © Michael Rosen 2005
Slide 32: Putting it all Together Enterprise Data Enterprise Scope Documents Business Processes Business Services Consolidated Data Semantic Objects WS WS WS Line of Business Scope Components and Integration Services IS IS Integration IS IS IS Data Workgroup Scope Enterprise Resources Operational Data SOR Application Scope © Michael Rosen 2005 Slide 32
Slide 33: The Enterprise Service Bus Provides an ideal platform for SOI Applications Integration Infrastructure – exposing existing applications as services Service Infrastructure – defining, implementing, invoking and combining services Enterprise Strength – enterprise class management, scalability, performance, reliability Full Disclosure Notice: The author does not represent or promote any specific ESB products (although he has used several and has his own opinions (incidentally not shared by the International House of Architecture). He does not own stock or stand to profit in anyway should you decide to follow his recommendations (actually, I still have a pile of BEA, but that’s another story…) © Michael Rosen 2005 Slide 33
Slide 34: Requirements of Different Service Types Requirement Design Semantics and Data Invocation Development Integration Service Expose existing application functionality and data Based on operational data models, required significant transformation services Event driven, or invoked by other services: Synchronous request/reply, events, fire-and-forget Business Service Provide services aligned with Enterprise Business Model Based on enterprise semantic model. Some aggregation, minimal transformation Invoke by a business process Asynchronous request/reply or fire-and-forget Requires specialized adapters for New development using ESB connection to legacy systems APIs directly Synchronous request/reply, events, publish and subscribe • Integration • Message Processing • QoS • Security and Management • • • Asynchronous request/reply Important Features © Michael Rosen 2005 Service Interaction • Process Orchestration • SLA • Security and Management Slide 34
Slide 35: We’re all Bozos on this Bus Business Process Business Process Business Service ESB Business Service Business Service Integration Service ESB Integration Service Integration Service Existing Enterprise Application Existing Enterprise Application © Michael Rosen 2005 Slide 35
Slide 36: Summary SOI combines Web service, EAI and SOA Driven top down by business requirements and model Driven bottom up by existing applications SOI provides an level of indirection between operational system’s API and data and Enterprise defined semantics, services and processes This leads to a more flexible, agile enterprise Integration Services are fundamentally different than Business Services Slide 36 © Michael Rosen 2005
Slide 37: Integration Service Summary Provides service access to existing systems Responsible for mapping between Enterprise business / service model and existing application functionality Responsible for mapping between Enterprise Semantic model and existing application data model Simultaneously insulates and integrates © Michael Rosen 2005 Slide 37
Slide 38: Implementing SOI Integration Requires… Architecture • Describe the essential context to enable cooperating services • But phase in the details as needed Business Model • Describe processes, services, interfaces, enterprise data and semantics Tools • Support service construction • Incorporate architectural concepts • Implement Service composition • Provide platform independence of business logic © Michael Rosen 2005 Slide 38
Slide 39: Questions