Introduction to Mulesoft

Transcript

1. MuleSoft An Introduction to the powerful ESB platform -- Narasimhan Chenduru
2. Agenda  Introduction to ESB  What is Mulesoft  Terminology  Studio  Palette  Mule message  Examples
3. What is an ESB??  Enterprise Service Bus  applications talk to a common bus instead of the point to point interaction  Highly Scalable  More than 3 systems to integrate
4. What is Mulesoft?  Java based ESB and an integration platform  Rapid development  Integrate plain old java object to a component from other frameworks  HIPPA compliant  Runs both on Premise and cloud  Abundance of connectors
5. Versions  Community version – free to use  Enterprise version – Paid version  Benefits of an enterprise version include:  Deployment management console  The Batch Processing module  Premium connectors such as SAP, and HL7  Support for Caching  Provision of technical support and assistance from Mulesoft Additional Details : : https://www.mulesoft.com/platform/soa/mule-esb-enterprise
6. Terminology  Anypoint Studio :  graphical editor that is used to develop the mule projects  Eclipse based IDE  Ability to use both drag and drop or the use of XML
7.  The different components of the studio include:  Package explorer : explore the various projects in the workspace  Connection explorer : a quick glimpse of the various connections used  Palette : Place to find all the available building blocks viz. components, transformers, scopes, etc.  Canvas: the area where the application is constructed or designed.  Console : The logging details and the output of the flows can be found here.
8. Flows and Subflows – the Backbone  The application is built around the flows.  Flows receive messages, process them , route the message to other systems if needed.  Flow types:  Subflow : Synchronous, no explicit message input section.  Synchronous : Similar to a subflow but has the input section. The processing happens sequentially.  Asynchronous : Simultaneously process the messages, does not wait for a response.
9. Mule Message  data that passes through the application via one or more flows  Key components:  Header: contains the metadata about the message.  Payload: contains the actual data that would be acted upon.  The Mule message object contains the following:  Mule message:  Header:  Inbound properties  Outbound properties  Payload  Variables  Attachments  Exception payload
10. Example – Use of a HTTP Connector  The HTTP Connector is used to call or make a request to external endpoint via HTTP.  Can be used as an input to listen for the requests.  The HTTP Connector is very easy to use and has minimal configuration required.
11.  It uses a Connector configuration as a reference. This reference contains the details about the host name, proxy details, Security details such as SSL / TLS  The port to listen on, etc.
12. Conclusion  Mulesoft is very easy to use, yet very powerful.  The applications to be designed varies from requirement to requirement.  A quick hands on the tool would give us a flavor of the application, and the studio with the embedded runtime can be downloaded from here : https://www.mulesoft.com/platform/studio  The community and forums can be used as a starting place to learn about the various offerings and features of Mulesoft.
13. Questions!!