Transcript 07-SEED-ESB
Second SEED Workshop Enterprise Service Bus P2P Architecture IS 2 Adapter 23 Adapter 12 Adapter 24 Adapter 13 IS 1 IS 3 Adapter 14 Adapter 15 Adapter 34 Adapter 25 Adapter 35 IS 5 P2P – Point to Point IS – Information System Adapter 45 IS 4 Number of Connections = n*(n-1)/2 = 5*4/2 = 10 n – number of systems EMS Architectures Bus Architecture Hub/Spoke Architecture IS 2 Adapter 2 IS 1 IS 1 IS 5 IS 3 Adapter 1 + Integration Engine Adapter 5 + Integration Engine Adapter 3 + Integration Engine IS 3 Adapter 1 Hub Message Broker and Central Integration Engine Adapter 5 IS 5 Adapter 3 Bus - Message Backbone Adapter 4 IS 4 EMS – Enterprise Messaging System IS – Information System IS 2 IS 4 Adapter 2 + Integration Engine Adapter 4 + Integration Engine Number of Connections = n = 5 n – number of systems ESB Architecture ESB Safety and Protection Integration based on standards Data integrity Simple data transformation SOAP SOAP SOAP WSDL IS 1 WSDL IS 2 SOAP WSDL IS 3 WSDL IS 4 SOAP WSDL IS 5 ESB – Enterprise Service Bus IS – Information System SOAP – Simple Object Access Protocol WSDL – Web Service Definition Language Existing tools and infrastructure 1. SOA vs. EAI vs. ESB Evaluation Parameter P2P Architecture Hub Architecture Bus Architecture Installation Effort Installation effort depends on the system that connects to the system Less installation effort compared to solutions with bus architecture. Moderate effort Moderate effort Administration Complicated Easy to maintain and administrate because of central hub. Administration may be complex depending upon the integrated systems. Administration may be complex depending upon the integrated systems. Cost Very high High High Low cost because it doesn’t use proprietary formats to enhance performance. Also it doesn’t provide all the services usually provided by proprietary product suits. Proprietary bus based product suit ESB 2. SOA vs. EAI vs. ESB Evaluation Parameter P2P Architecture Hub Architecture Bus Architecture Proprietary bus based product suit ESB Scalability Low scalable High if federated architecture is used otherwise limited by the hardware of box used to host Hub Highly scalable Highly scalable Standards Generally not based on standards Mostly standard based but may use proprietary Internal formats Mostly standard based but may use proprietary Internal formats Standard based SOA Not service oriented Can be implemented as service oriented Can be implemented as service oriented Service oriented The key advantages of ESB • Faster and cheaper adaptation of existing systems • Greater flexibility: easier to make changes to the changing requirements • Foundation for global standards • Scalability: easy extension of the initial application to only one location on the application of the whole business system (distributed bus) • More configuration, less coding Current architecture Folder Folder CDPS A XML XML Country A WEB App. DB Service App. Service App. MQ MQ SEED A CDPS B VPN WEB App. DB Queue INTERNE T SEED B Country B Current architecture CDPS A Folder Folder XM L Country A WEB App. SEED A DB CDPS B XM L Service App. Service App. MQ MQ Country WEB App. B SEED DB B Queue Queue Queue VPN Queue SEED DB D Country WEB App. MQ MQ D XM L CDPS D Service App. Service App. Folder DB WEB App. SEED C Country C XM L Folder CDPS C Current architecture with ESB CDPS A Country Country A B Folder XML JMS1 FILE Validation SOAP1 XML XML FILE ESB JMS 2 Routing Encoding Decoding SOAP2 SOAP2 Queue XML DB WEB App. SEED A CDPS B Folder MQ XML JMS1 ESB JMS 2 Queue MQ SOAP1 XML WEB App. SEED B INTERNE T DB Future architecture CDPS A Country Country A B Folder XML LDAP EMAIL XML ... ... FILE FTP FILE HTTP SOAP XML JMS SOAP DB SEED A SOAP Queue XML WEB App. FTP EMAIL LDAP HTTP DB ESB ESB DB CDPS B Folder MQ XML JMS Queue MQ INTERNE T SOAP XML WEB App. SEED B DB JBI Components of OpenESB ESB WSDL ports FILE BPEL SOAP JBI Modules BPEL ... JMS ... BPEL • ESB – Enterprise Service Bus • CA – Composite Application • BPEL – Business Process Execution Language • WSDL – Web Service Definition Language • SOAP – Simple Object Access Protocol (HTTP+XML) • JMS – Java Message Service • XML – eXtensible Markup Language XML CA Binding Components: HTTP, File, JMS, SOAP, EMAIL, DB, SAP, … Service Engines: BPEL, XSLT, JavaEE, SQL, … Why OpenESB is attractive • • • • Easy to install Easy to understand Very easy to use An open source Standards based (JSR 208) ESB easier to install, configure, use, manage and maintain than most other ESB-s in the market. • Binds with: The best java IDE NetBeans 6.x Excellent integration with Glassfish 2.x (Possible integration with IBM WebSphere or standalone application)