Your SlideShare is downloading. ×
Enterprise Systems Integration
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Enterprise Systems Integration


Published on

Presentation about integration of the enterprise systems.

Presentation about integration of the enterprise systems.

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Enterprise Systems IntegrationLong way to SOAAdastra klubVít Kotačka19. 6. 2012© Adastra Group
  • 2. Agenda  Levels of Integration Maturity  Architectural solutions  Technical solutions  Projects & practice2
  • 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 Maturity4
  • 5. Point-to-point integration  Easy & quick deal  Easy & quick implementation  Usually cheap cmp Streight Integration easy expose data Sytem A System B request data5
  • 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 x6
  • 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 data7
  • 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 data8
  • 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 tory10
  • 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 QoS11
  • 12. Architectural solutions12
  • 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 engine14
  • 15. Message Broker15
  • 16. EIP Diagram16
  • 17. BPM Engine17
  • 18. BPMN DiagramBusiness 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
  • 20. Technical solutions20
  • 21. Messaging & BPM Solutions  IBM WebSphere MQ  Oracle SOA Suite  IBM WebSphere Message Broker  Apache ActiveMQ  Drools  Apache Camel21
  • 22. IBM WebSphere Message Broker22
  • 23. WMB, components23
  • 24. JBoss jBPM IDE24
  • 25. JBoss jBPM BPMN diagram25
  • 26. Oracle SOA Suite26
  • 27. Projects & practice27
  • 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» Middleware28
  • 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 Suite31
  • 32. 32