1. Second SEED Workshop Enterprise Service Bus

2. P2P Architecture IS 2 IS 3 IS 4 IS 5 IS 1 Number of Connections = n*(n-1)/2 = 5*4/2 = 10 n – number of systems Adapter 12 Adapter 13 Adapter 14 Adapter 15 P2P – Point to Point IS – Information System Adapter 23 Adapter 34 Adapter 45 Adapter 24 Adapter 35 Adapter 25

3. EMS Architectures IS 1 IS 2 IS 3 IS 4 IS 5 Hub Message Broker and Central Integration Engine Adapter 1 Adapter 2 Adapter 3 Adapter 4 Adapter 5 Hub/Spoke Architecture Bus - Message Backbone IS 1 Adapter 1 + Integration Engine IS 5 Adapter 5 + Integration Engine IS 3 Adapter 3 + Integration Engine IS 2 Adapter 2 + Integration Engine IS 4 Adapter 4 + Integration Engine Bus Architecture Number of Connections = n = 5 n – number of systems EMS – Enterprise Messaging System IS – Information System

4. ESB Architecture ESB Safety and Protection Data integrity Integration based on standards Simple data transformation Existing tools and infrastructure ESB – Enterprise Service Bus IS – Information System SOAP – Simple Object Access Protocol WSDL – Web Service Definition Language SOAP IS 1 WSDL IS 2 WSDL SOAP IS 3 WSDL IS 4 WSDL IS 5 WSDL SOAP

5. 1. SOA vs. EAI vs. ESB Evaluation Parameter P2P Architecture Hub Architecture Bus Architecture Proprietary bus based product suit ESB Installation Effort Installation effort depends on the system that connects to the system Less installation effort compared to solutions with bus architecture. Moderate effort AdministrationComplicatedEasy 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. CostVery highHigh 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.

6. 2. SOA vs. EAI vs. ESB Evaluation Parameter P2P Architecture Hub Architecture Bus Architecture Proprietary bus based product suit ESB ScalabilityLow scalableHigh if federated architecture is used otherwise limited by the hardware of box used to host Hub Highly scalable StandardsGenerally not based on standards Mostly standard based but may use proprietary Internal formats Mostly standard based but may use proprietary Internal formats Standard based SOANot service oriented Can be implemented as service oriented Can be implemented as service oriented Service oriented

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

8. Current architecture DB Folder CountryA Service App. WEB App. MQ CDPS A SEED A XMLXML DB Folder CountryB Service App. WEB App. MQ CDPS B SEED B XMLXML INTERNE T VPN Queue

9. Current architecture DB Folder CountryA Service App. WEB App. MQ CDPS A SEEDA XM L DB Folder CountryB Service App. WEB App. MQ CDPS B SEEDB XM L DB Folder CountryD Service App. WEB App. CDPS D SEEDD XM L Service App. VPN Queue Folder CDPS C CountryC WEB App. DB SEEDC MQ XM L MQ Queue

10. INTERNE T ESB Current architecture with ESB DB Folder CountryA WEB App. CDPS A SEED A XMLXML MQ XMLXML XMLXML Queue FILE SOAP1SOAP2JMS 2 ESB ESB DB Folder CountryB WEB App. CDPS B SEED B XMLXML MQ XMLXML XMLXML Queue FILE SOAP1SOAP2 JMS 2 Validation Encoding Decoding JMS1 Routing

11. ESB Future architecture DB Folder CountryA WEB App. CDPS A SEED A XMLXML INTERNE T EMAIL MQ XMLXML XMLXML Queue FTP FILE LDAP DBHTTPSOAP JMS... ESB DB Folder CountryB WEB App. CDPS B SEED B XMLXML EMAIL MQ XMLXML Queue FTP FILE LDAP DBHTTPSOAP JMS... XMLXML

12. JBI Components of OpenESB ESB XMLXML... BPEL FILE SOAP JMS... CA 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 WSDL ports JBI Modules Binding Components: HTTP, File, JMS, SOAP, EMAIL, DB, SAP, … Service Engines: BPEL, XSLT, JavaEE, SQL, …

13. 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)