Enterprise IT Architectures SOA Part 1

Transcription

1 Enterprise IT Architectures SOA Part 1 Hans-Peter Hoidn hans-peter.hoidn@ch.ibm.com November 17, 2008

2 Agenda I. SOA Introduction II. Move from C/S to SOA III. Exercise: Integration Architecture for FACT IV. SOA Reference Architecture & SOA Entry Points 2

3 I. SOA Introduction 3

4 Why SOA (Service Oriented Architecture) Business is constantly changing (no longer stable) IT is required to be more flexible Monolithic applications can t be reused (historical limitations of current IT) SOA ties together changing Business Models and supporting IT Architecture SOA separates concerns, locations SOA follows essential principles: loosely coupled, federated, contract based SOA provides integration and supports business processes 4

5 Service Oriented Architecture Moves IT Logic Out of Services Information Factory Customers Web Orders Inventory Shipments Sales Orders Services defined as units of business logic separated from Flow of control and routing Data transformation and protocol transformation 5

6 SOA addressing IT as well as Business common shift 6

7 What is SOA SOA is an architectural style or approach whose goal is to achieve loose coupling among interacting software agents All functions (that need to be used by more than one system) are defined as "services Service providers agree to a defined, implementation-independent interface with service clients Services oriented architecture is the policies, practices and frameworks - that enable application functionality and IT services to be - provided and requested as a set of services - using a standards based form of interface. 7

8 SOA Principles Componentized Interoperable Modular Scaleable Standardized services interfaces for applications and resources Easy information exchange between applications and/or resources Mix and match, add or remove, business processes and infrastructure Start with what you have and add additional resources as needed 8

9 SOA is different things to different people A set of services that a business wants to expose to customers and clients an architectural style which requires a service provider, requestor and a service description. a set of architectural principles and patterns which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composable and single implementation. A programming model complete with standards, tools, methods and technologies such as web services. Roles Business Architecture Implementation 9

10 Greater flexibility from business models and supporting IT architecture Flexible Business Models Transformation Business Process Outsourcing Mergers, Acquisitions & Divestitures Composable Processes Requires Flexible IT Architecture On demand Operating Environment Service Oriented Architecture (SOA) Development Infrastructure Management Composable Services Software Development Integration Infrastructure Management 10

11 II. From C/S to SOA 11

12 Elements for a successful End-to-End Implementation Success with SOA Requires a Core Infrastructure The SOA reference architecture is a way of looking at the set of services that go into building an SOA. The backbone of the reference architecture is the ESB (Enterprise Service Bus), which facilitates communication between services. The reference architecture is a great tool for laying out roadmaps for pursuing SOA. 12

13 ESB (Enterprise Service Bus) An Enterprise Service Bus (ESB) is an architectural pattern defining a flexible connectivity infrastructure for integrating applications and services. The architecture pattern is a guiding principle to enable the integration and federation of multiple service bus instantiations. An ESB performs: - Routing messages between services - Converting transport protocols between requestor and service managing multiple protocols - Transforming message content between requestor and service - Handling business events from disparate sources 13

14 ESB Pattern in Action Retail Scenario Enterprise Business Functions Adapter Adapter Adapter App Server SWO POS JMS ESB Message Queuing Store i ESB Mediations (routing) SWO SOAP/HTTP, Other SWO App Server POS Terminals Services POS SOAP/HTTP 14

15 ESB is the next stage in the technology evolution Lines of maintainable code Direct Connectivity (No middleware) Connectivity, mediation & custom adaptation logic Application Message Queuing / CORBA Connectivity logic Mediation & custom adaptation logic Application Enterprise Application Integration Connectivity and mediation logic Custom adaptation logic Application Enterprise Service Bus Connectivity, mediation & custom adaptation logic Application as a service All connectivity, mediation and custom logic buried within the application. Removes the connectivity logic from the application Removes the connectivity + mediation logic from the application Reduces application to its core business functions (i.e. a service) Reduced development and maintenance; increased flexibility and reuse 15

16 ESB Core Principle Service Virtualization ESB acts as an intermediary (proxy) between requestor and provider ESB provides service virtualization of - Location and identity - Interaction protocol - Interface Interactions are decoupled, supporting separation of concerns 16

17 Expanded View of the Enterprise Service Bus Interaction, Interaction, Process, Process, Information, Information, Partner, Partner, Business Business App, App, Access Access Services Services Business Logic Enterprise Service Bus Interaction Patterns Message Flows Flows Mediation Patterns Message Models Models Transport Protocols Security Management IT Management Services Registry 17

18 Case: Multi-protocol Exchange Intermediary decoupling heterogeneous consumers and suppliers Tooling Domain of interest - Intranet Exchange WebSphere (WAS/Portal) SOAP/JMS SOAP/JMS WebSphere provider.net Client SOAP/HTTP SOAP/HTTP.NET provider Some Client XML/HTTP ESB XML/HTTP Some provider XML/MQ COBOL Copybook/MQ XML/MQ Client CICS Text/MQ Text/MQ Client 18

19 What is NOT in the Enterprise Service Bus? In the ESB capability necessary to support service virtualization Not in the ESB everything else! - But things not in the ESB may use or be used by the ESB Infrastructure Infrastructure Services Services Security Management Registry Business Business Logic Logic 19

20 Mediation Patterns Request / Response Request / Multi Response Event Propagation Protocol Switch Transform Enrich Route Distribute Monitor Correlate Canonical Adapter Transform Log - Route Gateway 20

21 Example JK Enterprise a virtual company with an Open Account Process Consumers Sales Application Central Office Sales Application Regional Office Open Account Business Process Composition; choreography; business state machines Account Activation Account Verification Determine Applicant Eligibility Address Verification Services atomic and composite Account Inquiry indirect exposure AR Setup indirect exposure Account Activation Account Setup direct exposure Create Account Determine Eligibility create from scratch Address Verification third-party reuse Service Components EJB Message Flow SCA EJB Operational Systems (Applications & Data) Customer (CICS 2.x) Billing (CICS 3.1) GL (SAP) 21

22 Example A: Multiple Channel Access to Backend Service WebSphere Integration Developer (WID) Review Export and Import Review Export and Import Build mediation flows Build mediation flows Deploy Service Module Deploy Service Module ESB Account System Java Client Appl High Value Accounts SOAP/ HTTP XML/ JMS Service Export (ACT) Service Export (HVA) Service Component Eligibility Mediation Transform Request/Response Transform Business Objects Request/Response Business Log Message Objects Infos Log Message Infos Service Import HQ Eligibility SOAP/ HTTP Applicant Eligibility Service J2EE Appl J2EE Appl Determine Eligibility Service Module 22

23 Example B: Create SAP Service Websphere Integration Developer (WID) Test Client Enterprise Service Discovery Deploy Deploy Adapter Adapter Discover Discover Enterprise Enterprise Service Service Generate Generate BAPI BAPI Business Business Objects Objects Deploy/Test Deploy/Test Service Service Import Import ESB Service Import SAP Outbound Business Objects WebSphere SAP Adapter RFC/ BAPI SAP Create New Customer Record Create Account Service Module 23

24 III. Exercise Integration Architecture for FACT 24

25 Financial Accounting for Container Business Financial Accounting performed by SAP Long lasting Business Processes from taking the order to delivery at destination Global IT environment (140 countries) Integration of approx. 40 operational applications 25

26 Container Business Value Chain Purchase Order Management Consolidation Labeling, Scanning M&R (Container, Vessel) Equipment Leasing Origin Trucking/ Intermodal Warehouse Terminal Warehouse & Distribution Trucking/ Intermodal Destination Depot Management Deconsolidation, Re-label Crewing Ship Owning 26

27 Process Model describing IDD (Interface Detailed Definitions) Process Model Process Step IDD Class Models for Data Legacy Intermediate SAP 27

28 Overview IDD (Interface Detailed Definition) related to a step in the Business Process may include multiple information flows FS (Functional Specification) - Functional Specification (FS) defines data (SAP and Legacy) from Business Perspective, including some transformations - Data Structure include IDoc / BAPI as well as Legacy interface data structure to be used and or customized TS (Technical Specification) - Technical Specifications (TS) (Overview, SAP, Legacy, Broker) include AND data models and XSD (XML Schema Definition) for XML of SAP IDocs, XML of Legacy Application Interfaces, Transformations 28

29 Deliverables of Data Structures for an IDD Process Model Process Step IDD One Flow IDD Def Data Field Mapping FS Metadata XSD Legacy Metadata Relationships XSD SAP IDoc 29

30 Integration Architecture is about breaking Interfaces into smaller chunks Legacy Systems Interface FACT Legacy 1 File / DB A miracle occurs SAP Integration Architecture Legacy Data Legacy Adapter Broker SAP Adapter SAP IDOC 30

31 Exercise Apply SOA Principles to the described environment Define SOA Infrastructure 31

32 IV. SOA Reference Architecture & SOA Entry Points 32

33 Governance Data Architecture (meta-data) & Business Intelligence QoS Layer (Security, Management & Monitoring Infrastructure Services) Integration (Enterprise Service Bus) Enterprise IT Architectures Moving to Services-Oriented Solutions Layered Architecture View Channel B2B Consumers Business Process Composition; choreography; business state machines Service Consumer Services atomic and composite Service Components OO Application Service Provider Custom Application Packaged Application Operational Systems 33

34 The SOA Reference Architecture and its Key Principles Providing IT Flexibility to Meet the Demands of Business Linkage between business and IT through support of the entire SOA Lifecycle Business Innovation & Optimization Services Connectivity and Service Isolation through the Enterprise Service Bus Development Services Interaction Services Process Services ESB Information Services IT Service Management Separation of Concerns/Modularity for incremental adoption Partner Services Business App Services Access Services Apps & Info Assets Component-based Programming and Solution Development Infrastructure Services Business and IT Monitoring and Management Open Standards 34

35 Separation of Concerns The SOA Reference Architecture in Action Business Dashboard Open Account Development Services Business Innovation & Optimization Services Facilitates better decision-making with real-time business information Interaction Services Process Services Information Services Enables collaboration between Portal people, processes & information Orchestrate and automate business processes Manages diverse data Federated in a unified manner Query IT Service Management Integrated environment Approved for design and creation of solution assets Partner Services Business App Services Access Services Connect Community with trading Manager partners Facilitates communication ESB between services Build on a robust, scaleable, EJBs and secure services environment Apps & Info Assets CICS Facilitates interactions DB Access with existing Siebelinformation Access and application Adapter assets DB Access Manage and secure services, applications & resources Infrastructure Services Optimizes throughput, availability and performance IT Management Console 35

36 Enterprise IT Architectures SOA Scenarios People: Interaction & Collaboration Services SOA Scenarios Process: Business Process Management Reuse: Service Creation SOA Design 36 Connectivity: Service Connectivity SOA Governance Information: Information as a Service SOA Security & Management

37 SOA Entry Points are Both Business Centric and IT Focused People Deliver role-based interaction and collaboration through services Process Achieve business process innovation through treating tasks as modular services Information Provide trusted information in business context by treating it as a service Reuse Service-enable existing assets and fill portfolio gaps with new reusable services Connectivity Connect systems, users, and business channels based on open standards 37

38 People: Interaction & Collaboration Services / Interaction Services in SOA Reference Architecture People are the drivers of the business they interact with reusable business services using the right information at the right time! Starting point for SOA - enabling people to interact with application and information services supporting business processes. Provided by Portals using Portlets, relying on security for the managing user access Based on Web Servers, new is the use of AJAX Link with Web

39 What is an Interaction Service? UI Portlets Portlets can be A Service Consumer (1) A Service Provider (3) Portlets can Initiate processes (1) Act as a Participant in a process (3) Communicate with each other Enterprise Service Bus Service A Service B Service C Service D WMQ SOAP/HTTP SOAP/JMS HTTPS 3 1 Request/Response Coarse Grained Request Fine Grained Request/Response Fine Grained Request/Response Coarse Grained The Portal Framework Provides Service Aggregation 39

40 Building User Interaction Services Developing and Deploying the New Account Application Building Role-Specific Portlets and Dashboards 40

41 SOA Interaction and Collaboration Realizations Interaction and Collaboration Services Basic UI Advanced UI Process Portal Distributed Portlets Managed Client Aggregating and Invoking services onthe-glass through portlets Rich Web Based Applications deployed as portlets in the Portal. Business Process Integration in the Portal. Web Services for Remote Portlets - Distributed Portlets with Federated Portal Servers Based on Eclipse on the Client 41

42 Traditional Interaction: Interrupted interaction with request driven processing with static page refresh 42

43 AJAX Web Interaction: Continuous user interaction with event driven processing and dynamic content refresh Page Request Page Render 43

44 Information: Information as a Service / Information Services in SOA Reference Architecture Delivering actionable information to people and processes Connect, enhance and deliver in-context information across diverse operating systems, applications and legacy systems through reusable services The Information Services enables consistent views and maintenance of data and content, providing a single view of the truth to people and processes 44

45 Information: Tight coupling causes inconsistent results Create Quote Process Flow Create Estimate Process Flow Trigger Trigger Access Transform Cleanse Legacy Application Data Warehouse Packaged Application Access Transform Cleanse Inconsistent view of the data Inconsistency in sources and how data is derived Inconsistent rules applied to data Multiple points of maintenance No flexibility to change information sources and formats 45

46 Information as a Service (IaaS) as Solution Create Quote Process Flow Create Estimate Process Flow Trigger Trigger Access Transform Cleanse Legacy Application Information as a Service (Shared Metadata) Data Warehouse Packaged Application Consistent packaging of data Leverages understanding of metadata relationships Applies consistent rules to data Centralized control and maintenance Flexibility to add and change information sources and formats 46

47 Separation of Concerns exists Even Before SOA Separation of concerns is a well-known architecture principle for application design Interaction Services Development Easy to understand & manage for single Servicesapplication Integrated Information environment architecture is an integral for design and part of enterprise architecture creation solution assets Information services are more than data storage and retrieval Business Services Supports enterprise business process and goals through businesses functional service Process Services Enables Enables collaboration Orchestrate and Orchestrate and automate between people, people, processes & automate business processes processes information & informationwebsphere business Portal processes Enterprise Service Bus Information Services Process Services Workflow Manages diverse Manages data and Interaction Services Management diverse content data in a unified and content WebSphere in a manner unified Process manner Server Services Presentation Manage and secure services, applications & resources Business App Services Business Partner Services Business App App Services Services Access Services Build Build on on a robust, robust, Facilitate interactions with Connect with trading scaleable, and secure existing information and partners services environment application assets Apps & Info Assets Application Logic Infrastructure Services Optimizes throughput, availability and utilization Information Services Data 47

48 Separations of Concerns Focussing on Exposing Application Services Exposing application logic as services is straight-forward and enabled by tooling The integration of services focuses on mediation (brokering) and orchestration (workflow) of application logic Process Services Workflow Interaction Services Presentation Enterprise Service Bus As a result, data is tightly coupled with the corresponding application logic Business App Services Application Logic Information Services Data 48

49 Information as a Service Critical business initiatives depend on Information Key Issues Separation of Information & Process In-context delivery Web Site Contact Center Enterprise Systems Data Warehouse Create Quote Create Estimate Enablers Information Infrastructure Metadata Management Master Data Services Hot Topics Dynamic Warehousing Analytic Services Models and Metadata MDM Information Integration Services Content Mgmt Applications Others.. 49

50 Classifying Information Services patterns Identifying usage patterns to focus the business case Data Complexity, & Accessibility Enterprise Content Management Deliver trusted information as a service Build services to integrate content into processes Multiple Versions of the Truth Real time access to analytical information Build master data services for product and customer info An enterprise-wide information management strategy increases the chance of success for service oriented architecture efforts by at least 70%... Gartner, February 2006 Deliver analytical services for structured an unstructured data 50 50

51 IAAS Patterns in JK Enterprises Account Open Process Account Open Process Account Open Process Account Open Process Store//Retrieve Application Lookup Customer Store/Update Customer Request Documentation XML Account Application Database 1 Account Data 2 Customer Master MDM 3 Account Documents 4 Information Service Enablement Integrated information services Master Data Management Content Management 51

52 IaaS Example Transform Your Data Create Trusted Information from Disparate Sources As-Is Environment Data resides in disparate sources Manual & redundant integration of data by multiple consumers results in high costs and inconsistent/inaccurate data Slow response time due to large data volume and complex transformations Solution Characteristics Apply transformations on extracted source data; copy into consolidated target and expose consolidated data as services Invoke population from business process Results Multiple consumers can access trusted, accurate and integrated information through a service Data availability aligned with business process Data Population Server Analyze customer info Data Population Service Legacy Database apply / load transform Review historical data SOA context gather / extract account data traditional context Legacy Database Consolidated Data Access Service Data Warehouse Metadata 52

53 IaaS Example Deliver Your Data Virtualized Through Services As-Is Environment Data resides in disparate sources Manual & redundant integration of data by multiple consumers results in high costs and inconsistent/inaccurate data Slow response time due to inefficient real-time access Federated Data Service Review current accounts (Reporting) Application Solution Characteristics On demand integration instead of redundant data Transparent & optimized access to distributed, heterogeneous sources Results Real-time access to distributed information, fast response time Scalable approach for adding more data sources SOA context Data Virtualization Through Data Federation Server Legacy Database account data traditional context Legacy Database Metadata 53

54 Closing Remark 54