Enterprise IT Architectures SOA Part 3

Transcription

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

2 SOA Because Innovation Requires Change and SOA Makes Change Easier a service? A repeatable business task e.g., check customer credit; open new account service oriented architecture (SOA)? An IT architectural style that supports integrating your business as linked services SOA can be your treasure map to innovation 2

3 SOA drives Greater Alignment Between Business and IT creating an Enduring Impact on Industry Business View Process View IT View 3

4 Key Models for SOA SOA Lifecycle SOA Reference Architecture Business Services Development Services Interaction Services Partner Services Process Services Enterprise Service Bus Business App Services Infrastructure Services Information Services Access Services Apps & Info Assets Management Services SOA Solution Layering Service Consumer Service Provider Consumers Channel Business Process Composition; choreography; business state machines Services atomic and composite Service Components Operational Systems Packaged Application B2B Custom Application OO Application Integration (Enterprise Service Bus) QoS Layer (Security, Management & Monitoring Infrastructure Services) Data Architecture (meta-data) & Business Intelligence Governance 4

5 Agenda I. Business Process Management from end-to-end II. SOA Entry Points & SOA Reference Architecture III. Student s Presentation(s) IV. Solutions of Case 2 5

6 I. Business Process Management from end-to-end (from Part 2) 6

7 II. SOA Entry Points & SOA Reference Architecture 7

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

9 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 9

10 Scenario Realizations Content integration Aggregating Services using a Managed Client Process modeling and simulation* Master data management Consume external services Create new services from scratch Adapting enterprise applications to Web services Adapt existing systems to multiple business channels WSRP to Aggregate Services From Federated Portal Env. Business Process Integration in WebSphere Portal Managing Processes through Rules Management Process automation and execution Data Cleansing Data Consolidation Service-enable existing assets using direct exposure Gateway Deploying Rich Web Based Application using AJAX portlets Monitoring & Tracking Business Processes (BAM) Data Federation Service-enable existing assets using indirect exposure Internal connectivity based on open standards Aggregating and Invoking Services using Simple Portlets Content-Centric Processing Information Service Enablement / Simple information service Service Creation Service Connectivity Interaction and Collaboration Services Business Process Management Information as a Service SOA Design SOA Governance SOA Security and Mgmt. Business service modeling for process composition Governance of reuse Service discovery Business transformation analysis and service design Standards compliance Change management Value realization End-to-end management of services Service security management 10

11 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

12 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 12

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

14 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 14

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

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

17 Interaction with WebServices for Remote Portlets (WSRP) Web Services for Remote Portlets All remote connections share a unified API No coding required, proxy and stub are coded once or generated automatically Stable and standardized transport mechanism (e.g. SOAP) Visual and user-facing Presentation and Interaction Layer Portlet API Generic Proxy SOAP Generic Stub Web App1 User Aggregation Generic Proxy SOAP WSRP API Generic Stub Web App2 Portlet API Portal Server WSRP API WS specific interface 17

18 Process: Business Process Management / Process Services in SOA Reference Architecture Integrates and synchronizes business systems and choreographs business and system activities into reusable process components Includes Business Process Modeling and Assembling of Business Processes with Services see SOA Part 2 Automated processes reduce administrative time and adaptable and reusable processes to enable faster reaction to business indicators provided by Business Process management see Chapter I Supports Human Interactions 18

19 Human Tasks Included in Portals Administrators May need to care about workload, monitoring etc beyond what the process engine does anyway Pure Human Task Independent task, has no dependency to other components Originators May need to start certain processes to complete business operations Ad-hoc Sub- and Follow-On tasks can be created if the initial user feels unable to complete the task alone Human Assistance...Human Tasks can be called from other Component types (e.g. Business Rules) Participants Need to actively work on tasks assigned by a the process/task engine 19

20 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 20

21 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 21

22 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 22

23 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 23

24 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 24

25 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.. 25

26 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 26 26

27 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 27

28 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 28

29 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 29

30 III. Student s Presentation(s) 30

31 IV. Solutions Case 2 (FACT) 31

32 Process Model / IDD / Class Models for Data Structures Process Model Process Step Input SOL IDD Class Models for Data Legacy Intermediate FACT 32

33 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 33

34 Technical Architecture Planning End of 2003 Technical Architecture Functional View Technical View Legacy SAP Legacy Middlew SAP V V

35 FACT Integration Layer Technical View Legacy Systems Legacy 1 FACT Integration Layer Adapter FACT File / DB File Adapter XML Adapter Legacy 2 File / DB Queue XML Broker XML IDOC API SAP Adapter Legacy 3 File / DB Std. API XML 35

36 Example use of Pattern: one-to-many with different messages (Feed and R/R Request/Reply) To Legacy Broker Scope To SAP 3 4b nonxml: 1 2 Broker nonxml: Or XML 4a XML Different messages to Multiple destinations 36

37 Patterns for Information Flow Feed 1: Legacy Legacy Scope Adapter Scope Broker Scope Program Start File / DB 2 Program terminates OR File is created 4 XML 5 Broker File / DB 37

38 Patterns for Information Flow Feed 2: Broker Flow In Validate Filter Lookup (Transform) Out 38

39 Patterns for Information Flow Feed 3: SAP SAP Scope Adapter Scope Broker Scope 6 SAP-DB 4 3 XML 2 1 Broker IDoc ALE 5 39

40 Technical Architecture Specifics: Switching supported by Country Dependent Routing Legacy Scope Integration Layer FACT IDOC API SAP Broker File / DB Legacy+ FACT Data Countries in roll-out cluster to SAP Old Financial systems Legacy Data 40

41 Technical Architecture Specifics: Translation of codes Legacy Patterns Legacy 1 File / DB Legacy 2 File / DB Legacy 3 File / DB Std. API File Queue FACT Integration Layer Adapter Adapter Adapter Lookup Broker Lookup Tables Runtime Environment Update Adapter Deploy Lookup Tables FACT IDO C SAP API X-ref part of SAP Bus. Doc. Lookup Tables Maintenance Environment Manual Update of Lookup Tables 41

42 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 42

43 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 43

44 Functional and Technical Specification: IDD and Regular Information Flow IDD Technical Specification (Legacy) IDD in Toolset IDD Functional Specification IDD Technical Specification Overview IDD Technical Specification (Broker) IDD Technical Specification (SAP) 44

45 Functional and Technical Specification: IDD and Multiple Information Flows IDD in Toolset IDD Functional Specification IDD Functional Specification IDD Technical Specification Overview IDD Technical Specification Overview IDD Technical Specification (Legacy 1) IDD Technical Specification (Broker 1) IDD Technical Specification (Legacy 2) IDD Technical Specification (Broker 2) IDD Technical Specification (SAP) IDD Functional Specification IDD Technical Specification Overview IDD Technical Specification (Legacy 3) IDD Technical Specification (Broker 3) 45

46 Overview Field Mapping in Functional Specification Mapping LEG Busterms To Data Model Mapping SAP Busterms To Data Model DevToolRepository Requirements To LEG Legacy Class Models Transforms Lookup IDoc Control SAP Class Models Requirements To SAP Metadata Deliverables XSD XSD of XSD of LEG of LEG LEG Relationship Specification Report XSD of SAP 46