ANY POINT STUDIO MULE

• Mule, the runtime engine of Anypoint Platform, is a lightweight Java-based enterprise service bus (ESB) and integration platform that allows developers to connect applications together quickly and easily, enabling them to exchange data.

• Mule applications accept and process eventsas messages through several message processors pluggedtogether in a flow.

WHY MULE ?

A flow is the construct within which you link together several individual elements to handle the receipt, processing, and eventual routing of a message.

How flows look like?

FLOWS

• Select From mule pallete flow.• Drag flow icon from mule pallete to

message flow.• Its looks like something

FLOW

AT THE SIMPLEST LEVEL, FLOWS ARE SEQUENCES OF MESSAGE-PROCESSING EVENTS. A MESSAGE THAT ENTERS A FLOW MAY PASS THROUGH A WIDE VARIETY OFPROCESSORS.

HOW TO CREATEFLOW

. In general, a building block corresponds to an icon in the Anypoint Studio GUI, which in turn represents a message source, processor, or component.

• Subflow

• Synchronous Flow

• Asynchronous Flow

TYPES OF FLOW

Subflows, which always run synchronously, inherit both the processing strategy and exception strategy of the flow that triggered its execution.

SUBFLOW

SYNCHRONOUS FLOWS

•LIKE A SUBFLOW, A SYNCHRONOUS FLOW PROCESSES MESSAGES SYNCHRONOUSLY RELATIVE TO THE FLOW THAT TRIGGERED IT. UNLIKE A SUBFLOW, A SYNCHRONOUS FLOW DOES NOT INHERIT THE TRIGGERING FLOW’S PROCESSING OR EXCEPTION STRATEGIES

Asynchronous flows begin processing a message when triggered by another flow. Since this type of flow does not need to return data to the flow which triggered it, it can execute simultaneously to its triggering flow.

ASYNCHRONOUS FLOWS

A batch job is a top-level element in Mule which exists outside all Mule flows. Batch jobs split large messages into records which Mule processes asynchronously; just as flows process messages, batch jobs process records.

BATCH JOBS

Again Search in pallete for batch.Drag it to message flow.

BATCH JOBS

Transformers convert message payloads to formats expected by their destinations. Mule ESB provides many standard transformers, which you configure using predefined elements and attributes in your Mule XML configuration file

The most powerful tool for transforming a message isthe DataWeave Transformer, which can not only change the format of the message, but also rename, aggregate, split or rearrange the fields in it in any way you desire.

TRANSFORMERS

CONFIGURING TRANSFORMERS-:YOU CAN CONFIGURE Atransformer locally or globally. You configure a local transformer right on the endpoint or in a flow or where you want to apply it, whereas you configure a global transformer beforeany <model> or <flow> elements in your Mule configuration file and then reference it.Chaining Transformers-:You can chain transformers together so that the output from one transformer becomes the input for the next. To chain transformers, you create a space-separated list of transformers in thetransformer-refs or responseTransformer-refs attributes or by creating multiple <transformer>elements as shown above.

TRANSFORMERS

ObjectToOutputHandler-: Converts a byte array into a String.

ObjectToString-: Returns human-readable output for various kinds of objects. Useful for debugging.

StringAppendTransformer-: Appends a string to an

existing string. StringToObjectArray-: Converts a

string to an object array. Use theconfiguration element <string-to-byte-array-transformer>

TRASFORMATION EXAMPLE

CONNECTORS

•ANYPOINT CONNECTORS FACILITATE EASY INTEGRATION OF YOUR MULE APPLICATIONS WITH THIRD-PARTY APIS AND STANDARD INTEGRATION PROTOCOLS. USE CONNECTORS WITHIN YOUR APPLICATION’S FLOWS TO SEND AND RECEIVE DATA USING A PROTOCOL OR SPECIFIC API.

TYPES OF

CONNECTOR

All connectors can function as endpoints by sending and receiving messages between flows or between a flow and some other data source outside of Mule. Some connectorsare endpoint-based, meaning that you configure them either as inbound or outbound endpoints in your flow, then specify other operation logic within the configuration of that endpoint. Some connectors are operation-based, meaning that they allow you to invoke specific actions against an API, Web service, or database.