Mule integration-application
- 1. l All contents Copyright © 2015, MuleSoftInc. Module 2: Building Integration Applications with Anypoint Studio
- 2. Goal 2 l All contents Copyright © 2015, MuleSoft Inc.
- 3. Objectives • In this module, you will learn: - About Mule applications, flows, messages, and message processors - To use Anypoint Studio to create flows graphically using connectors, transformers, components, scopes, and flow control elements - To build, run, test, and debug Mule applications - To read and write message properties - To write expressions with Mule Expression Language (MEL) - To create variables 3 l All contents Copyright © 2015, MuleSoftInc.
- 4. Introducing Mule applications l All contents Copyright © 2015, MuleSoftInc.4 l All contents Copyright © 2015, MuleSoftInc.
- 5. Mule applications • Accept and process messages through a series of message processors plugged together in a flow - A message can be initiated by an events like ∙ A consumer request from a mobiledevice ∙ A change to data in a database ∙ The creation of a new customer ID in a SaaS application 5 l All contents Copyright © 2015, MuleSoftInc.
- 6. Mule applications • Are written in XML (primarily) - Under the hood, are Java applications using Spring • Can be created and tested visually with Anypoint Studio - Available as a stand-alone or as an Eclipse plug-in • Are deployed to a Mule Server Runtime - A standalone app to a Mule runtime(typically) - A WAR file with an embedded Mule instance to an app server 6 l All contents Copyright © 2015, MuleSoftInc.
- 7. Mule Server Ru ntime • A JVM server that - Can handle many concurrent requests for different Java (Mule) applications in a single JVM - Decouples point-to-point integrations by having all (non- Mule) applications talk to the bus (to a Mule app) instead of directly to each other - Decouples applications by using ∙ Protocol adaption • Communication can be over different protocols, like HTTP or FTP ∙ A canonical data format • A common format all messages are transformed to 7 l All contents Copyright © 2015, MuleSoftInc.
- 8. Mule runtime edit ions • Enterprise and community editions - Mule ESB Server runtime EE - Mule ESB Server runtime CE • CE is open-source • EE is a hardened code line with support and additional capabilities • By default, Anypoint Studio uses EE - You can install other versions and select which one to use • http://www.mulesoft.com/platform/soa/mule-esb- enterprise 8 l All contents Copyright © 2015, MuleSoftInc.
- 9. Mule runtime E E • 24/7 global support • Additional connectors Visual debugging DataMapper and DataSense Batch module • Caching and transaction support • Performance monitoring • Security module • Templates Deployment and performance management 9 l All contents Copyright © 2015, MuleSoftInc.
- 10. • Mule applications accept and process messages through a series of message processors plugged together in a flow Mule applications and flows Message Flow Message Source 10 l All contents Copyright © 2015, MuleSoft Inc. Message Processors Error Handling
- 11. Mule flows • A typical flow has - A message source ∙ Accepts a message from an external source triggering the execution of the flow - Message processors ∙ Transform, filter, enrich, and process the message • An application can consist of - A single flow - Multiple flows - Multiple flows connected together 11 l All contents Copyright © 2015, MuleSoftInc.
- 12. Set from the message source Added by message processor Mule messages Inbound Properties Outbound Properties Mule Message The core of the message Ancillary info to the message Payloa d Attachment s 121 2 l All contents Copyright © 2015, MuleSoftInc.