Architecture for Integration

Transcription

1 Architecture for Integration Hans-Peter Hoidn 2 October 2003

2 Agenda Motivation I. Integration Layer in General II. EAI Environments, Cases III. EAI meets J2EE IV. Enterprise centric view V. References Conclusion 2

3 Problem statement I. Integration Layer in general 3

4 Situation and Approach Situation: Successful isolated solutions exist New Challenges Objectives: Flexible solutions addressing customer needs end-to-end solutions Re-use of existing applications Approach: Integration Coexistence of existing applications and packaged solutions 4

5 Business Situation (Communication Flow among Applications) Customer Facing Customer Contact Center Service Order Entry Provisioning Customer Database Billing System Service Inventory Network Facing Network Inventory Thresholds Performance Management Trouble Workforce Ticketing Management Events Collection Filtering Correlation Network Elements 5

6 Goal for a Manageable System Architecture Customer Facing Customer Contact Center Service Order Entry Provisioning Customer Database Billing System Service Inventory Middleware Network Facing Network Inventory Thresholds Performance Management Trouble Workforce Ticketing Management Events Collection Filtering Correlation Middleware Network Elements 6

7 EAI-Problem Analysts report that more than 80 % of corporate data is exchanged using point-to-point integration. Logistics Financials ecommerce Web server Purchasing Too complex! Not manageable! Not flexible! Sales force automation Order entry Marketing Call center Given an average of 50 applications, a corporation might need to build 2,450 point-to-point connections to integrate the entire enterprise. Maintenance costs! Too many technologies! Business changes hard to adapt! 7

8 EAI Solution What if there were an integration layer that would simplify the tasks of integration and sharing of data between systems? Sales Force Automation NT/Sybase Logistics Financials Mainframe/VSAM EAI Marketing AS/400, OS/400 Order Entry AS/400, OS/400 Unix/Oracle AS/400, OS/400 Call Center E-Commerce Unix/Oracle Mainframe/VSAM Purchasing 8

9 Integration Layer Characteristics Overcome Missing flexibility for new business Historical redundancies Many point to point integrations - critical complexity Provide Strong business process orientation Consolidated applications Ease of future changes Smooth legacy replacement Addressing Various business systems 9

10 Lessons learned - An architectural Approach is Required Legacy systems can no longer be adapted to current business needs need for flexible solutions Flexibility cannot be provided by vertical stove pipe solutions which do not support horizontal issues as needed by a customer oriented viewpoint Flexible solutions need a component approach providing business components which can be composed to various business systems Architectural and integration issues raise in importance flexible solutions need to be based on solid blueprints for application and technical architecture 10

11 II. EAI Environments 11

12 II: EAI Environments Key Functionality: Asynchronous Messaging Guaranteed Delivery Data Transformation Message Routing Components: Core Middleware Adapter and Message Broker Business Process Administration (including Workflow) 12

13 EAI Framework Functional View (Increasing Value of Integration) Transportation: Transport from application to application, Routing Data Transformation: Mapping of semantics Mapping among protocols (e.g. IDOC to/from XML) Business Rules: Business Processes, Data depending Routing Business Processes: Business Process Automation, Workflow 13

14 EAI Scope Enterprise Application Integration Integration spanning the entire enterprise and community. Not just a few applications. Communication platform for the applications. Not just a database replication. Open system architecture. Not just an applicationto-application interface based interoperability. 14

15 EAI Key Components Core Middleware: Message-Transport (transactional) Adaptors / Connectors: Links to applications (e.g. SAP) Message Broker: Message Routing and Data Transformation Application Server Linking to Program Execution Business Process Automation 15

16 EAI Functional and Technical Views Functional View Technical View Inter-Enterprise Process Automation Business Process Automation Business Integration Logic Application Content Transformation Communication Services MetaData Services Operational Services Application Connectivity Connectors Business Process Automation Service Components Message Brokers Application Servers Core Middleware Metadata (XML / XSL(t) ) Enterprise System Management 16

17 EAI Waves Connectors EAI Wave 2 EAI Wave 1 Business Process Automation Service Components Message Brokers Application Servers Core Middleware Metadata (XML / XSL(t) ) Enterprise System Management Connectors The EAI product landscape is evolving from packages which we classify as EAI Wave 1 to frameworks / platforms which we classify as EAI Wave2 EAI Wave1 products are packaged based which you need to configure and extend, based on common approaches but proprietary implementations, and typically utilise proprietary process based runtime environments and connectors EAI Wave 2 products are open standards based flexible integration frameworks that benefit from proven scalable, reliable execution run-time environments and are evolving to provide the functionality of EAI Wave 1 products and include EIP functionality. 17

18 Applications / Components and Information Flow Source Transformation Transformation Target Loose coupling including reliability, security etc. Transformation to common semantics Transformation to target specific semantics 18

19 EAI Example with ERP Strategic Business Initiatives: Enterprise Resource Planning Traditional Approach to ERP Accounting Shipping EAI Approach to ERP Accounting Shipping ERP EAI Production Production Legacy Logistics Planning Logistics Planning ERP Legacy 19

20 Examples of Application Landscapes Examples: Operational systems in each company feed FI/CO system providing controlling functionality Production planning on the corporate layer drives production in local plants Consolidation of planning Central procurement system Implications of new IT Strategies: Implementing new business processes for reporting Replacement of local FI/CO systems by a global solution Centralization of IT support per country 20

21 Business and Application Landscape Apps FI/CO... SAP... 21

22 Example Pilot Implementation Danzas Country Italy Data Center Solution Provider P R O D U C T I O N S Y S T E M S JCA JCA JCA JCA JCA JCA HP CPU xxxxx 1 WLI/WLS EAI SW HP CPU xxxxx 2 WLI/WLS EAI SW HP L/3000/550 CPU 1 WLI/WLS EAI SW J C HP L/3000/550 CPU 2 J C A J C A WLI/WLS EAI SW J C Cluster HP CPU Lp8400/750 3 SAP/R3 Core HP CPU L/3000/550 4 SAP/BW HP CPU Lp8400/750 5 SAP/R3 Core HP CPU L/3000/550 6 SAP/BW Virtual Array VA7400 Virtual Array VA7400 Monitoring BMC Cent. Monitoring 22

23 Benefits Facilitates: Integration of standard packages Migrations General: Reduction of development time approx % Reduction of maintenance approx % Example: 23 Applications: Reduction of devlopment time approx. 88% ROI: 379%, Payback: 0.55 years 23

24 Gartner Report To summarize, the key drivers of ROI include the period of use and the complexity of organizations environments. We found quite consistently that these organizations broke even or nearly broke even in their first six to twelve months of using the [EAI] product. Their ROI varied by the amount of time using the integration broker and by the complexity of their operating environments. ROI ranged in value from 48% to 209%. 24

25 III. EAI meets J2EE 25

26 J2EE Framework Provides environment with Services: Transaction Messaging Provides architecture JDBC (Java Database Connectivity) JCA (Java Connector Architecture) 26

27 J2EE Services 27

28 J2EE Framework 28

29 Example: One Business System, Several Components 29

30 Result Multiple complexities Software development of components Information flow Data transformations Multiple transactions Need to be managed By an enterprise centric view Appropriate levels of abstractions Use of modeling Apply MDA (Model Driven Architecture) 30

31 IV. Enterprise Centric View 31

32 An Enterprise Architecture has to provide Unified Views of Rules and Procedures to capture business processes with the needed precision Semantics and ontologies use the same terminology Service definitions definitions of components and interfaces access methods Addressing different abstraction layers Hiding details of the implementation Providing platform-independent view that is J2EE independent view (Going beyond) 32

33 Architectural Approach Platform Independent Component view Models Platform Specific Solutions 33

34 Consistency by Modeling Mappings and Transformations Service Provisioning Component Independent Business Model Billing Component Independent Business Model Platform Independent Component view Platform Independent Component view Platform Specific Platform Specific 34

35 Main Aspects Business components arise at several tiers according to Herzum- Sims: presentation, workspace, enterprise, resource Separation of Concerns Every component can be seen on various abstraction levels platform-independent where the implementation technologies do no matter platform-dependent like WDSL, J2EE, 35

36 Components: Process versus Tiers Vertical Integration: Tiers Presentation 1 Workspace 1 Presentation 2 Workspace 2 Enterprise 1 Enterprise 2 Resource 1 Resource 2 Horizontal Integration: Process 36

37 Components: Example Topology Multiple Systems 37

38 V. References 38

39 IBM Coverage of an Open and Modular EAI Architecture Process Modelling And Control Workflow Task A Task B Task C Task D Task E Long Transactions Business Integration Workflow Transformation & Routing Hub and Spoke architecture (asynchronous) Application Server Bus architecture (synchronous) Adapters Gateways Message queueing FTP Mail EJB CORBA SOAP 39

40 IBM Websphere Enterprise Integration Business Modeling and Monitoring Browser WebSphere Portal User Interaction Services WebSphere Business Integration Server Process Integration Services Process Human Automation Activity WebSphere Business Integration Connect Partner Services Business Partner Application Presentation Personalization Process Choreography Cross- Reference Transaction / Compensation State Management Audit Staff Business Protocol Business Partner Exchange Hubs WAP Common Business Object Model Events Application Connectivity Services Routing Pub/Sub Transformation Mediation Transport WebSphere Business Integration Adapters HR Legacy Finance ERP CRM... 40

41 OMG s MDA (Model Driven Architecture) 41

42 Conclusion - Success Factors A holistic view is needed Technology is only a part of the picture Separation of abstraction layers (logical, technical) Stepwise approach IT matters (Response to Nicholas Carr) 42