Mulesoft 简明教程

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.

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.

Integrating two or more applications − Use of ESB architecture is beneficial when there is a need to integrate two or more services or applications.

Integration of more applications in future − Suppose if we want to add more services or applications in future, then it can be easily done with the help of ESB architecture.

Using multiple protocols − In case if we need to use multiple protocols like HTTP, FTP, JMS etc., ESB is the right option.

Message routing − We can use ESB in case if we require message routing based on message content and other similar parameters.

Composition and consumption − ESB can be used if we need to publish services for composition and consumption.

Service Registry − Mule ESB has Service Registry/Repository where all the services exposed into the ESB are published and registered. It acts as a point of discovery from where one can consume the services and capabilities of other applications.

Centralized Administration − As the name implies, it provides a view of transactional flows of performance of interactions occurring inside the ESB.

V(Validate) − As the name implies, it validates the schema validation. It requires a validating parser and up-to-date schema. One example is an XML document confirming to an up-to-date schema.

E(Enrich) − It adds additional data to a message. The purpose is to make message more meaningful and useful to a target service.

T(Transform) − It converts the data structure to a canonical format or from a canonical format. Examples are conversion of date/time, currency, etc.

*R(*Routing) − It will route the message and act as a gatekeeper of the endpoint of a service.

O(Operate) − The main job of this function is to invoke the target service or interacts with the target app. They run at the backend.

Community Edition

Enterprise Edition

It has simple drag-and-drop graphical design.

Mule ESB is capable of visual data mapping and transformation.

User can get the facility of 100s of pre-built certified connectors.

Centralized monitoring and administration.

It provides robust enterprise security enforcement capabilities.

It provides the facility of API management.

There is secure Data Gateway for cloud/on-premise connectivity.

It provides the service registry where all the services exposed into the ESB are published and registered.

Users can have control through a web-based management console.

Rapid debugging can be performed using service flow analyzer.

WSO2 ESB

Oracle Service Bus

WebSphere Message Broker

Aurea CX Platform

Fiorano ESB

WebSphere DataPower Gateway

Workday Business Process Framework

Talend Enterprise Service Bus

JBoss Enterprise Service Bus

iWay Service Manager

At least 2 GHz CPU or 1 Virtual CPU in virtualized environments

Minimum 1 GB RAM

Minimum 4 GB storage

It provides an instant run of Mule application inside a local runtime.

Anypoint studio gives us visual editor for configuring API definition files and Mule domains.

It has embedded unit testing framework enhancing the productivity.

Anypoint studio provides us the Built-in support to deploy to CloudHub.

It has the facility to integrate with Exchange for importing templates, examples, definitions and other resources from other Anypoint Platform organization.

Anypoint Studio 7 is required to use Dataweave scripts.

After installing Anypoint Studio, we need to set up a project with a Transform Message component in order to use DataWeave scripts.

Groovy

Nashorn(javaScript)

jython(Python)

jRuby(Ruby)

With the help of attributes, we can easily see which data is available, because attributes are strongly typed.

We can easily access information contained in attributes.

Metadata

Key performance Indicators (KPIs)

Firstly, it evaluates an expression that should result in another script.

Then it evaluates that script for the final result.

First, this router copies (Scatter) a Mule event to two or more parallel routes. The condition is that each route must be a sequence of one or more event processors which is like a sub-flow. Each route in this case will create a Mule event by using a separate thread. Every Mule event will have its own payload, attributes as well as variables.

Next, this router gathers the created Mule events from each route and then consolidates them together into a new Mule event. After this, it passes this consolidated Mule event to the next event processor. Here the condition is that the S-G router will pass a consolidated Mule event to the next event processor only when every route is completed successfully.

The first characteristics of Mule Error Types is that it consists of both, a namespace and an identifier. This allows us to distinguish the types according to their domain. In the above example, the Error Type is HTTP: UNAUTHORIZED.

The second and important characteristic is that the Error Type may have a parent type. For example, the Error Type HTTP: UNAUTHORIZED has MULE:CLIENT_SECURITY as the parent which in turn also has a parent named MULE:SECURITY. This characteristic establishes the Error Type as specification of more global item.

INDIFFERENT [Default] − If we choose this configuration on try block, then the child actions will not be treated as a transaction. In this case, error causes neither rollback nor commits.

ALWAYS_BEGIN − It indicates that a new transaction will be started every time the scope is executed.

BEGIN_OR_JOIN − It indicates that if the current processing of the flow has already started a transaction, join it. Otherwise, start a new one.

In MUnit framework, we can create our Mule test by using Mule code as well as Java code.

We can design and test our Mule apps and APIs, either graphically or in XML, within Anypoint Studio.

MUnit allows us to easily integrate the testing into existing CI/CD process.

It provides auto-generated tests and coverage reports; hence the manual work is minimal.

We can also use local DB/FTP/mail servers to make testing more portable through the CI process.

It allows us to enable or disable tests.

We can also extend the MUnit framework with plugins.

It allows us to verify message processor calls.

With the help of MUnit testing framework, we can disable endpoint connectors as well as flow inbound end points.

We can check error reports with Mule stack trace.

MS Windows 8+

Apple Mac OS X 10.10+

Linux

Java 8

Maven 3.3.3, 3.3.9, 3.5.4, 3.6.0

For creating and designing MUnit tests

For running our tests

For viewing test results as well as coverage report

For debugging the tests

By Right-Clicking the Flow − In this method, we need to right-click the specific flow and select MUnit from the drop-down menu.

By Using the Wizard − In this method, we need to use the wizard for creating a test. It allows us to create a test for any flow in the workspace.

Application overall coverage

Resource coverage

Flow coverage