Enterprise Systems Integration
Download as PPTX, PDF1 like721 views
Enterprise systems integration involves connecting disparate applications to produce unified functionality. There are different levels of integration maturity from point-to-point connections that require more maintenance over time, to integration tiers/middleware that standardize communication but have higher costs. The most advanced approach is service-oriented architecture (SOA) which defines services with standardized contracts to enable reuse and composite applications. Main architectural solutions for integration include message-oriented middleware with brokers, and business process management engines. Technical options cover messaging platforms and business process tools.
More Related Content
Similar to Enterprise Systems Integration (20)
Recently uploaded (20)
Enterprise Systems Integration
- 1. Enterprise Systems Integration Long way to SOA Adastra klub V鱈t Kotaka 19. 6. 2012 息 Adastra Group
- 2. Agenda Levels of Integration Maturity Architectural solutions Technical solutions Projects & practice 2
- 3. Enterprise Integration Enterprise integration is the task of making disparate applications work together to produce a unified set of functionality. 3
- 4. Levels of Integration Maturity 4
- 5. Point-to-point integration Easy & quick deal Easy & quick implementation Usually cheap cmp Streight Integration easy expose data Sytem A System B request data 5
- 6. Point-to-point integration problems Geometric progression complexity Different formats and protocols Transitive dependencies cmp Streight Integration difficult expose data for A Sytem A System B request data from B request data request data from C from x expose data expose data for A for B expose data for C System C System x request data from x 6
- 7. Integration tier Central control over data flow Unified message format Set of protocols (company communication standard) Services reuse Central data transformation, orchestration etc. cmp Middlew are expose data expose data MiddleWare Producer 1 Consumer A request data request data expose data expose data Producer 2 Consumer B request data request data 7
- 8. Integration tier problems Higher costs System complexity increasing Slow (implementation/management) reaction cmp Middlew are expose data expose data MiddleWare Producer 1 Consumer A request data request data expose data expose data Producer 2 Consumer B request data request data 8
- 9. Integration tier communication sd Integration Mi ddleWare Producer 1 Producer 2 Consumer A request data() transform request() request data() return data() request data() return data() transform response() return data() 9
- 10. Service Oriented Architecture Standardized contract Service reuse + impact analysis Composite services Service metadata somf SOA Management & Moni tori ng Process Orchestrati on Securi ty Servi ces Governance Data Abstracti on Data Reposi tory Metadata Reposi tory 10
- 11. SOA Governance Service portfolio management Service lifecycle management Policies management Service usage monitoring somf SOA Gov ernance Poli ci es Strategi es Rules Processes Moni tori ng Audi t Plani ng Certi fi cati ons Evaluati on Standards Servi ces SLA Appli cati ons Data QoS 11
- 13. Main Integration Styles File Transfer each application produce files of shared data for others to consume and consume files that others have produced. Shared Database applications store the data they wish to share in a common database. Remote Procedure Invocation each application expose some of its procedures so that they can be invoked remotedly, and have applications invoke those to initiate behavior and exchange data. Messaging each application connect to a common messaging system, and exchange data and invoke behavior using messages. 13
- 14. Two main architectural solutions Messaging + Broker BPM based engine 牟 BPEL engine 牟 BPMN engine 牟 Rule engine 牟 Workflow engine 14
- 16. EIP Diagram 16
- 17. BPM Engine 17
- 18. BPMN Diagram Business Process BPMN Acti vi ty2 FirstLine Acti vi ty1 StartEvent1 EndEvent1 Acti vi ty3 SecondLine Acti vi ty4 Use Case1 (from Use Case) 18
- 19. Canonical Data Model A common model independent from any specific application. Require each application to produce and consume messages in this common format. 19
- 21. Messaging & BPM Solutions IBM WebSphere MQ Oracle SOA Suite IBM WebSphere Message Broker Apache ActiveMQ Drools Apache Camel 21
- 22. IBM WebSphere Message Broker 22
- 25. JBoss jBPM BPMN diagram 25
- 28. Micros Java ws2ws mapping ActiveVOS Drools cmp Micros 束appli cati on損 Micros FE 束use損 束appli cati on損 束bpel損 Micros BE 束use損 ActiveVOS 束use損 束use損 Middleware 28
- 29. JLauncher Java batch processing 牟 file2file sd JLauncher 牟 file2db 牟 db2file JLauncher Producent Consument 牟 db2db *Check data() Expose data() Read data() Wri te data() Process data() 29
- 30. Online Integration WebSphere Message Broker Proprietary solution (TIF) Runtime registry (MDR) Weak governance cmp TIF Consumer WMB Provider TIF connector TIF TIF agent 束call損 束call損 30
- 31. ESB Oracle SOA Suite 31
- 32. 32