Presented by :Srinivas Vothukudi GovindarajUniversity of Colorado Boulder03/22/2011Pre RequisitesTerms and DefinitionsArchitecture Use caseDemo References Questions Support2 Service Oriented Architecture (SOA) What is Enterprise Service Bus (ESB) What is Java Business Integration (JBI) Spring Framework Maven SOAP3 Enterprise Service Bus (ESB) Java Business Integration(JBI) Normalized Message Router (NMR) Binding Component (BC) Service Engine (SE) Message Exchange Patterns(MEP) Service Unit (SU) Service Assembly (SA)4 SOA is an underlying computer systems structure that supports the connection between various applications and the sharing of data Service-oriented architecture (SOA) helps the business processes be better, easier to change and cheaper to create Building business processes is faster and cheaper because the existing services can more easily be reused, applications can expose their services in a standard way The next slide shows the illustration of Service Oriented Architecture56 Middleware architecture which helps in integrating the business functions and specific applications Identifies messages and routes them between applications and services Provides an abstraction for endpoints Enables loose coupling and easy connection between services Based on pluggable components7Source: http://en.wikipedia.org/wiki/File:ESB.svg8 Java standard for structuring business integration systems along SOA lines Defines an environment for plug-in components that interact using a services model based directly on WSDL 2.0 Viewed as Container of Containers Integration model based on WSDL JBI components can function as a service provider or a service consumer or both910Source: JBI Components: Part 1 (Theory) by Ron Ten-Hove, Sun Microsystems,2006 Consists of Binding Components , Service Engines and a Normalized Message Router Binding Component provides connectivity for applications that are external to the JBI Service Engine provide business logic and transformation services The separation of business and processing logic from communication logic makes the implementation of components much less complex11 Normalized Message Router is a light weight messaging infrastructure  NMR helps in mediated message exchange between components  NMR routes normalized messages between service providers and consumers A normalized message consists of two parts: the message content (payload) and the message metadata A message can be routed through several JBI components depending on what processing is needed12 JBI component interact with each other via a process of message exchange, which is fully described WSDL documents, as published by the service provider  Each operation that a service provider makes available has a particular message exchange pattern(MEP) associated with it An MEP defines the sequence, direction, and cardinality of all message exchanges that occur in the course of invoking and performing the operation JBI defines four MEPs: in-only, robust in-only, in-out, and in-optional-out13 Service descriptions in JBI are made using the web services description language (WSDL). These descriptions are published by service providers and read by service consumers Service consumer sends an appropriate request message, via a messaging infrastructure (in this case JBI), to the service provider.14 Open Source Enterprise Service Bus Built on Java Business Integration specification Lightweight , easily embedded and has integrated Spring Support Combines functionality of Service Oriented Architecture and Event Driven Architecture Provides clustering, high availability, remote access, failover Provides extensive JMX support for management1516Source: http://servicemix.apache.org/home.data/ServiceMix3.png servicemix-bean servicemix-camel servicemix-cxf-bc servicemix-cxf-se servicemix-eip servicemix-file servicemix-ftp servicemix-http servicemix-jms servicemix-mail servicemix-quartz servicemix-saxon17 Service Unit(SU) contains one or more components of same implementation type/binding type Service Units are useful when you want to distribute/load balance deployment of your application Service Assembly(SA) is a collection of one or more service units In order to deploy a service into a JBI container, it is necessary to package the files into a service assembly file18 Source: http://documentation.progress.com/output/Iona/celtix/1.1/getting_started/N049B4680.04CE80E8.html19 As in the previous slide, SA consists of a jbi.xml which contains sequence of service unit descriptions. For each service unit, the descriptor specifies the constituent files and indicates which target JBI component the service should be deployed into. These jbi.xml’s get generated only after the generation of Service Assembly and Service Units. These jbi.xml’s are present in the META-INF folder. The next slide shows jbi.xml for SA having two service units namely eip-bc and http-bc.20<?xml version="1.0" encoding="UTF-8"?><jbi xmlns="http://java.sun.com/xml/ns/jbi" version="1.0"><service-assembly><identification><name>handson-sa</name><description>Apache ServiceMix :: Service Assembly</description></identification><service-unit><identification><name>http-bc-su</name><description>http-bc-su</description></identification><target><artifacts-zip>http-bc-su-1.0-SNAPSHOT.zip</artifacts-zip><component-name>servicemix-http</component-name></target></service-unit><service-unit><identification><name>eip-su</name><description>eip-su</description></identification><target><artifacts-zip>eip-su-1.0-SNAPSHOT.zip</artifacts-zip><component-name>servicemix-eip</component-name></target></service-unit></service-assembly></jbi>21 As shown, the handson-sa.zip contains a META-INF folder. In this folder, there is jbi.xml describing the components used for the handson service assembly.22 User sends a SOAP/HTTP request User expects the soap message to be transformed according to the style sheet System dumps result in a configured directory23 Send SOAP request to the HTTP BC HTTP-BC sends IN-ONLY message to EIP(Enterprise Integration Pattern) Service Engine component  EIP-SE converts the IN-Only to IN-Out MEP(Message Exchange Patterns) The IN-Out message is sent to Saxon Component24 The Saxon-SE transforms the message and