Introduction to mule Esbs
•Download as PPT, PDF•
0 likes•393 views
introduction to mule ESBs and overview
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Introduction to mule Esbs
Similar to Introduction to mule Esbs (20)
More from Prabhat gangwar
More from Prabhat gangwar (20)
Recently uploaded
Recently uploaded (20)
Introduction to mule Esbs
- 1. INTRODUCTION TO ESBS: MULE By Prabhat Gangwar
- 2. AGENDA What is an ESB? Java Business Integration (JBI) Mule Architecture Mule in the Real World
- 3. PROBLEMS ADDRESSED BY ESBS Integration of existing systems Refactorable in real time Flexibility to change as requirements change Decentralized (service-location transparency) Scalable (point solutions to full enterprise) Sharing of services across enterprise Ability to separate Business Services from Service Implementations Leverages standards
- 4. DEFINITION(S) Gartner Group Giant exercise in Separation of Concerns
- 5. ESB FEATURES Routing Message Transformation Message Enhancement Protocol Transformation Service Mapping Message Processing Process Choreography Service Orchestration Transaction Management Security
- 6. AN ESB BLUEPRINT General case Client calls Choreographer Client calls Mediator vs
- 7. JAVA BUSINESS INTEGRATION (JBI) JSR-208 Standard Defines service engines (SE – choreographers, transformers, security, etc) and binding components (BC – xml, http, etc) Concerned with how internal customers (not external services) interact with service providers COTS
- 8. JBI EXAMPLE XSLT – message transformation PXE – choreography Groovy – scripting
- 9. JBI CASE STUDY: SERVICE MIX Service Mix Binding Components Service Engines
- 11. MULE FLOW VIEW Channel – a method of connecting between two points (not part of Mule) Connector – a transport provider (e.g., http, jms, soap, smtp, etc) implementing message receive and message dispatch Transformer – converts message structure/format (e.g., http to xml) Router – moves messages amongst UMOs and connectors
- 12. MULE CONNECTOR VIEW http://myapp.com pop3://user@userland.comhttp→xml xml→pop3 myUMO (xml→xml) [Mule]
- 13. MULE TRANSPORTS AS400 DQ EJB E-mail File FTP HTTP IMAP JDBC JMS Multicast POP3 Quartz RMI Servlet SMTP SOAP SSL Stream TCP UDP VFS VM WSDL XMPP
- 14. UMO EXECUTION Requires a component resolver (e.g., Spring or Pico) for Instantiation of UMOs Configuration of UMOs Event processing Asynchronous Synchronous Request-Response
- 15. MULE PROGRAMMING MODEL Application logic Application glue Mule glue
- 16. MULE ROUTERS
- 17. SELECTIVE CONSUMER (INBOUND) Applies one or more filters to incoming payload, then branch based on filter <inbound-router> <catch-all-strategy className="org.mule.routing.ForwardingCatchAllStrategy"> <endpoint address="jms://topic:error.topic"/> </catch-all-strategy> <router className="org.mule.routing.inbound.SelectiveConsumer"> <filter expression="msg/header/resultcode = 'success'" className="org.mule.routing.filters.xml.JXPathFilter"/> </router> </inbound-router>
- 18. FILTERING OUTBOUND (OUTBOUND) <outbound-router> <catch-all-strategy className="org.mule.routing.ForwardingCatchAllStrategy"> <endpoint="jms://error.queue"/> </catch-all-strategy> <router className="org.mule.routing.outbound.FilteringOutboundRouter"> <endpoint address="smtp://ross@muleumo.org"/> <filter expectedType="java.lang.Exception" className="org.mule.routing.filters.PayloadTypeFilter"/> </router> <router className="org.mule.routing.outbound.FilteringOutboundRouter"> <endpoint address="jms://string.queue"/> <filter className="org.mule.routing.filters.logic.AndFilter"> <left-filter expectedType="java.lang.String" className="org.mule.routing.filters.PayloadTypeFilter"/> <right-filter pattern="the quick brown (.*)" className="org.mule.routing.filters.RegExFilter"/> </filter> </router> </outbound-router>
- 19. NESTED ROUTER Allows synchronous callouts that can be intercepted and routed <mule-descriptor name="InvokerComponent" implementation="org.mule.foo.Invoker"> <inbound-router> <endpoint address="jms://Invoker.in"/> </inbound-router> <nested-router> <binding interface="org.mule.foo.HelloInterface"> <endpoint address="axis:http://192.168.2.14:81/services/HelloWebComponent? method=helloMethod" remoteSync="true"/> </binding> </nested-router> <outbound-router> <router className="org.mule.routing.outbound.OutboundPassThroughRouter"> <endpoint address="jms://Invoker.out"/> </router> </outbound-router> </mule-descriptor>
- 20. ESB FEATURES Routing Message Transformation Message Enhancement Protocol Transformation Service Mapping Message Processing Process Choreography Service Orchestration Transaction Management Security X X √ √ √ √ √
Editor's Notes
- Routing – ability to channel a request to a particular service provider based on deterministic or variable routing criteria (e.g., static/deterministic, content-based, policy-based, or complex rule-based) Message Transformation – ability to convert the structure and format of the incoming business service request to the structure and format expected by the service provider (e.g., xml→xml, xml→Cobol Copybook, object→xml) Message Enhancement – ability to add or modify the information contained in the message as required by the service provider (e.g., date format conversion, supplemental data, data conversion, rules-based enhancement) Protocol Transformation – The ability to accept one type of protocol from the consumer as input (e.g., SOAP/JMS) and communicate to the service provider through a different protocol (e.g., IIOP) – concerned with message structure, not payload – has attributes of physical connection and logical connectivity Service Mapping – The ability to translate a business service into the corresponding service implementation and provide binding and location information (includes implementation service name, service protocols and binding information, protocol-specific information, service-specific routing information) Message Processing – The ability to manage state and perform request management by accepting an input request and ensuring delivery back to the client via message synchronization Process Choreography – The ability to manage complex business processes that require the coordination of multiple business services to fulfill a single business service request (usually BPEL-based, often a manifestation of a use case or business process) Service Orchestration – The ability to manage the coordination of multiple implementation services (usually inter-service communication or aggregate services) Transaction Management – The ability to provide a single unit of work for a business service request by providing a framework for the coordination of multiple resources across multiple disparate services (e.g., compensatory transactional framework, WS-Coordination or JSR-95 Activity Service) Security – The ability to protect enterprise services from unauthorized access (e.g., Authentication, Authorization, Auditing, and Administration via access to external managers)
- Choreographer entrypoint (containing business processes and rules) requires that all services have BPEL coordination. Problems with performance, maintenance, and complexity. Common vendor solution. Mediator entrypoint allows choreography where appropriate. Good scalability, performance, reduced complexity. Avoids layers … and mediators are fast (~ms). Choreographer is just another service provider.
- Create standards-based architecture for integrating middleware components to perform ESB capabilities Concerned with how internal customers (not external services) interact with service providers – transformation, security, etc. Defines service engines (SE – choreographers, transformers, security, etc) and binding components (BC – xml, http, etc)
- avoids vendor lockin incentivizes best of breed SE and BC Not addressing federation of ESBs
- Mule is a lightweight UMO container UMO = Universal Messaging Objects (POJO) UMOs are endpoints that know how to send and receive requests
- Constructor is called by component resolver to create object Initialize called when component is registered with Mule model Start is called when the component (server/UMO) is started onCall is called when event is received for component … can resolve to any method within UMO Stop is called when Mule server is stopped Dispose is called when Mule server is shut down
- Routing – ability to channel a request to a particular service provider based on deterministic or variable routing criteria (e.g., static/deterministic, content-based, policy-based, or complex rule-based) Message Transformation – ability to convert the structure and format of the incoming business service request to the structure and format expected by the service provider (e.g., xml→xml, xml→Cobol Copybook, object→xml) Message Enhancement – ability to add or modify the information contained in the message as required by the service provider (e.g., date format conversion, supplemental data, data conversion, rules-based enhancement) Protocol Transformation – The ability to accept one type of protocol from the consumer as input (e.g., SOAP/JMS) and communicate to the service provider through a different protocol (e.g., IIOP) – concerned with message structure, not payload – has attributes of physical connection and logical connectivity Service Mapping – The ability to translate a business service into the corresponding service implementation and provide binding and location information (includes implementation service name, service protocols and binding information, protocol-specific information, service-specific routing information) Message Processing – The ability to manage state and perform request management by accepting an input request and ensuring delivery back to the client via message synchronization Process Choreography – The ability to manage complex business processes that require the coordination of multiple business services to fulfill a single business service request (usually BPEL-based, often a manifestation of a use case or business process) Service Orchestration – The ability to manage the coordination of multiple implementation services (usually inter-service communication or aggregate services) Transaction Management – The ability to provide a single unit of work for a business service request by providing a framework for the coordination of multiple resources across multiple disparate services (e.g., compensatory transactional framework, WS-Coordination or JSR-95 Activity Service) Security – The ability to protect enterprise services from unauthorized access (e.g., Authentication, Authorization, Auditing, and Administration via access to external managers)