Developing Integrations in Mulesoft

Developing Integrations in Mulesoft To integrate the data between Magento and salesforce, we will use MULE ESB. The tools available to develop the integration application in Mulesoft.

Anypoint Studio:

Anypoint Studio is the graphic editor used to develop Mule projects. This is built on top of the Eclipse IDE. The editor includes a drag and drop canvas on which the flows are designed. All feeds designed using the drag and drop canvas is stored internally as XML files. Therefore, we can also use the XML editor of Anypoint Studio to design the projects. Let’s take a look at the different components available in the studio.

Package Explorer As shown above, on the left side of the canvas in Anypoint Studio is the package, Explorer. It contains all the content of a mule application that we are developing. Each time we create a new Mule project, a default feed is created.

Canvas: Canvas is the area where we design the flow. It is a graphic editor in which we can drag and drop the elements of the Mule palette on the right side. The palette contains the basic elements of flow.It contains various predefined components that can be used. Looking more closely at the canvas, we can see that there are three tabs at the bottom, namely:  Message flows: drag and drop the interface to create flows.  Global items: contains items that can be reused. It is generally recommended to keep all the attributes and configurations related to the connection of the whole project in a single global element flow.  XML configuration: In addition to the graphic editor, the studio also provides an XML editor. All building blocks placed on the canvas are represented by their equivalent XML structure in the configuration.xml file.

XML is the exact equivalent of the stream that is dragged and dropped. So we can edit either in the canvas or in the XML editor.

Mule Palette: The studio comes with a set of predefined building blocks that can be dragged onto the canvas to create the applications. These building blocks vary from a straightforward file connective to enterprise connectors like SAP, PeopleSoft, etc. The components of the Mule palette are classified into the following types:        

Connectors: used to interact with APIs or third party systems Scopes: used to define the area or limit up to which the flow and messages in the flow are visible Components: used to execute business logic Transformers: used to modify or bulk data Filters: used to conditionally transmit data Flow control: used to route or broadcast the same message to multiple processor components.

Error handling: used to handle exceptions Security: used to provide secure access to information, applications and services

Mule message: The Mule message is the data that passes through the application via one or more streams. The message consists of the following elements:  Header: contains the metadata about the message.  Payload: contains the actual data that would be processed. The entire mule message is wrapped in an object called the Mule Message object. This object contains the following: Message mule o Header, incoming properties, outgoing properties o Payload, variables, attachments, exceptional payload.

Inbound properties are immutable properties and are defined by message sources, while outbound properties are defined in the stream and can act as inbound properties for the next connector. Variables as in any other programming language are used to store useful data. The variables are further classified into the following types:  Flow variables: specific to a flow  Session variables: available for all application streams  Record variables: used when saving a batch context

For More Information about Mulesoft Online Training Visit our Website