Mule Basics

Question 1

MuleSoft

Answer 1

Java based Enterprise Service Bus (can be deployed anywhere). Decouples point-to-point integration (apps talk to ESB, not directly to each other).

Question 2

Mule Runtime

Answer 2

the engine for Anypoint Platform. Mule apps are deployed to a Mule runtime.

Question 3

Mule Event

Answer 3

An event source receives a trigger (http, jdbcs, ftp, jms) and creates a corresponding mule event object and forwards the processing.
Mule events are immutable. Any change to an instance of a mule events results in the creation of a new mule event instance.

Question 4

Mule Message

Answer 4

Connector operator receive and return mule messages. I.e. When a listener receives a HTTP request, it creates a mule message with the HTTP body as the payload and sets HTTP headers and other metadata in the attributes.

Question 5

Variables

Answer 5

are used to store messages, attributes, or payload as an object number or string

Question 6

RAML

Answer 6

language designed to describe a restful API.

Question 7

API

Answer 7

provides a way of communicating with a software component. It allows functionality to be independent of implementation.

Question 8

API proxy

Answer 8

app that controls access to a web service through an API gateway.

Question 9

Web service

Answer 9

method that allows two software systems to exchange data over the internet,

Question 10

SOAP web services

Answer 10

archaic, communication rules are defined in XML.

Question 11

Rest

Answer 11

similar to SOAP but uses HTTP protocols.

Question 12

DataWeave

Answer 12

language for formulating expressions in mule. DataWeave uses Transform Message (script) core component to access access, manipulate, transform, and extract data from a Mule event.

Question 13

Batch Processing

Answer 13

useful for streaming input or for performing near real-time data integration between Saas.

Question 14

Mule Components (three of them)

Answer 14

core components, connectors, and modules

Question 15

Core Components

Answer 15

core functionality of mule runtime (logging, setting payloads, transforming messages, try catch, batch processing)

Question 16

Connectors

Answer 16

group together components to facilitate integration of mulesoft. (i.e. Salesforce Connector provides components that lets you perform operations).

Question 17

Modules

Answer 17

group together components to add flexibility to your app. Modules offer application coding functionality, like Java features and JSON processing. Modules show up in both your xml and in the Anypoint GUI.

Question 18

Mule Flow

Answer 18

Groups together a sequence of event processors. Mule apps are built around one or more flows for modularity and for error handling.

Question 19

Flow Ref

Answer 19

routes mule event to another flow or subflow and back. (think of it as a function in java that accepts an input and return a processed value). Alternatively you can use the DataWeave lookup function. Typically used to trigger flows that lack a source. Try to make the flow specific and reusable.

Question 20

Subflow

Answer 20

Also groups together a sequence of event processors, but does not have an event source nor error handling. Always called by Refs or lookup.