MuleSoft Training

MuleSoft Training Manual
Training
Table of Contents:
1. Introduction to Mule ESB

2. Dev environment set-up
3. API Design
4. API Manager
5. Implementation
6. Rest Services
7. Configuration Properties & Secure Configuration Properties
8. Error Handling
9. Batch Processing
10. Miscellaneous
11. Dataweave
12. Deploying to Cloud Hub
13. Functional testing of Mule flows using MUNIT
Introduction to Mule ESB
ESB stands for Enterprise Service Bus which is basically a middleware tool for
integrating various applications together over a bus-like infrastructure.
Implementing ESB:
The main focus of ESB architecture is to decouple the systems from each other and allow them to
communicate in a steady and controllable way. ESB’s implementation can be done with the help
of ‘Bus’ and ‘Adapter’ in the following way −
• The concept of “bus”, which is achieved through a messaging server like JMS or AMQP, is used to decouple different
applications from one another.
• The concept of “adapter”, responsible for communicating with backend application and transforming data from
application format to bus format, is used between applications and bus.
ESB’s Guiding Principles
We can call these principles as core integration principles. They are as follows −
• Orchestration − Integration of two or more services to achieve synchronization between data and process.
• Transformation − Transforming data from canonical format to application specific format.
• Transportation − Handling protocol negotiation between formats like FTP, HTTP, JMS, etc.
• Mediation − Providing multiple interfaces to support multiple versions of a service.
• Non-functional consistency − Providing mechanism for managing transactions and security also.
Integrations Before Middleware – Legacy way
Total Systems - n Total Integrations - n ( n-1)

Life Before Middleware – Drawbacks
Drawbacks Of Point-to-Point integrations :
• Change in Message Producer's Endpoint URL will affect the message consumers which
are accessing it.
• If Message Producers and consumers are Exposed by different Protocols, they can’t
interact.
• If Message type of two applications are differs.
• Happens more at application-to-application level, may not be aligned properly with
business goals
• Tightly Coupled connections between components.
Life After Middleware – New Integrations
Different ways of Integrations
• File ( SFTP/FTP)
• Database
• Messaging ( JMS/MQ)
 Webservices
 SOAP
 REST
• Application Based Connections ( Connectors)
 SAP
 Workday
 Salesforce
 Service Now
Advantages Of MuleSoft:
• Accessible - any developer can learn Mule

- Development is Drag and Drop based.
• Lightweight
- Mule runtime is lightweight not in terms of size but also cost of making changes to existing
integrations.
• Not just mediation
- Mule provides a light and scalable service container for publishing REST and SOAP services.
• Message agnostic
- It is not tied with any specific format, supports all message formats ( XML, JSON, Plain text)
• Cloud ready
- Mule softs cloud hub is an integration platform ( iPass) that get your integrations up and running in
minutes.
- i.e, Ready made runtime available in cloud. No need of any installations and setup.
• Connector support to all major technology applications.
Hardware – Prerequisites
• A computer with at least 4GB available RAM, 2GHz CPU, and 10GB available
storage and a minimum screen resolution of 1024x768
• Anypoint Studio 7.6 with embedded Mule 4.3 runtime

https://www.mulesoft.com/lp/dl/studio
• An Anypoint Platform account : http://anypoint.mulesoft.com
• REST Client (or some other REST client application)

Postman : https://www.getpostman.com/downloads/
Adv Rest Client : https://install.advancedrestclient.com/install

System Environment set-up
To install Apache Maven on Windows, you just need to download the Maven’s
zip, unzip it to a folder, and configure the Windows environment variables.
Tested with:
1. JDK 10
2. Maven 3.8.7
3. Windows 10
1. JDK and JAVA_HOME. Make sure JDK is installed, and JAVA_HOME environment variable is configured
2. Download Apache Maven
1. Visit Maven Official Link download the Maven zip file:
2.2 Unzip it to a folder. In this article, we
are using C:\Software\apache-maven-
3.8.7
3. Add MAVEN_HOME system variable Add a MAVEN_HOME system variables, and point it to the Maven
folder. 3.1 Press Windows key, type adva and clicks on the View advanced system settings
3.2 In System Properties dialog, select Advanced tab and clicks on the Environment Variables... button.
3.3 In “Environment variables” dialog, System variables, Clicks on the New... button and add a MAVEN_HOME
variable and point it to C:\Software\apache-maven-3.8.7
What is Anypoint Platform
 A unified, highly productive, hybrid integration platform that creates

a seamless application network of apps, data and devices with API-
led connectivity.
 A collection of runtimes, frameworks, tools and web

applications for deploying, running , managing and
monitoring applications.
 Mule runtime for running applications and applying

policies
 On-premise
 CloudHub
 Anypoint URL :
https://anypoint.mulesoft.com/
Components Of Anypoint Platform
MuleSoft's Anypoint Platform offers several tools and services, viz:
 API Designer is a web-based, graphical tool that a developer can use to design and document an API.
 Anypoint Studio is a graphical, Java-based design environment where a developer can implement APIs.
 Anypoint Connectors are a set of built-in connectors that a developer can use to integrate applications with
third- party applications.
 CloudHub is a multi-tenant integration platform as a service ( iPaaS ) offering.
• CloudHub is offered as a managed service, which means a development team does not need to install or operate any
hardware or software to use it.
 Anypoint Runtime Manager is a central console from which a developer can provision and monitor all
resources deployed on the Anypoint Platform across hybrid cloud architectures.
 Anypoint Exchange
• Is a central hub that a development team can use to store and access APIs, templates, connectors, documentation and other
resources.
 API Manager
• Used to manage and secure APIs via an API gateway.
• control user access to APIs, ensure secure connections to back-end data sources and create policies around API calls and throttling.
 Anypoint Analytics
• Is an analytics tool to track API metrics, such as performance and usage.
• A developer can use this tool to create custom charts and dashboards to visualize API performance, as well as identify the root
cause of any performance issues.
 Anypoint Monitoring
• Is a dashboard that helps a development team monitor application health.
 Anypoint Visualizer
• Is a graphical tool to map APIs and their dependencies in real time.
 Mule applications can first be designed with API specifications that are easier for less technical stakeholders to understand
• Write, publish, and version APIs in Anypoint Design Center
• Manage APIs with Anypoint API Manager
 Offload API governance and policies from the API implementation (the Mule application) to a centralized management plane used by runtime admins, not
developers
 Share, mock, test, and reuse APIs with Anypoint Exchange.

Components to design, build, test, share and manage APIs

API Designer
Practical Lab
Hands-on for Designing RAML and publishing it to exchange

MuleSoft Training

Uploaded by

Copyright:

Available Formats

MuleSoft Training

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

MuleSoft Training

Uploaded by

Copyright:

Available Formats

MuleSoft Training Manual

1. Introduction to Mule ESB

Total Systems - n Total Integrations - n ( n-1)

Drawbacks Of Point-to-Point integrations :

• Accessible - any developer can learn Mule

• Anypoint Studio 7.6 with embedded Mule 4.3 runtime

• An Anypoint Platform account : http://anypoint.mulesoft.com

• REST Client (or some other REST client application)

Adv Rest Client : https://install.advancedrestclient.com/install

 A unified, highly productive, hybrid integration platform that creates

 A collection of runtimes, frameworks, tools and web

 Mule runtime for running applications and applying

 Share, mock, test, and reuse APIs with Anypoint Exchange.

Components to design, build, test, share and manage APIs

Hands-on for Designing RAML and publishing it to exchange

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.