Syllabus for Enterprise Integration with Mule ESB

Prerequisities: 6 months hands on experience working on Java

(It Is mandatory to accomplish the training prerequisite conditions before nominating for the session)

Day 1

What is enterprise integration

–What is enterprise integration

–Understanding the enterprise integration patterns

–Understanding the data flow pipeline

–Different options in java world for integration

–Overview of Apache Camel

–Overview of Spring Integration

–Micro-Services based enterprise integration solutions

–Understanding Spring Cloud Streams

–Overview of building real-time data flow pipelines

Understanding API Oriented Applications

–Significance of API in micro-services world

–The principles of API

–Designing APIs

–The case study

Understanding MuleSoft Product Landscape

–Understanding Anypoint platform

–Overview of Mulesoft API Designer

–Overview of MuleSoft API Manager

–Overview of Mule Connectors & Exchange

–Overview of Mule Runtime Engine

–The Mule Anypoint Studio

Day 2

Introduction to Mule Apps

–Creating Mule Apps with Studio (Hands-On)

  –Create a simple app

–Add Http Listener Connector

–Use Set Payload for Hello world

–Put a logger

–Simply run the application and see the results

–Understanding Mule App Building Blocks

–Message Sources

–Messages | Processors | Flow : Mule application

                accept & process messages through a series of message processors plugged togehther in a flow

–Anypoint Connectors : Message sources are

  usually Anpoint Connectors

–Connectors provide connectivity to external resources such as

1.Databases, protocols, or APIs

2.HTTP, FTP, SMTP, AMQP

3.3rd Party like SalesForce, Workday etc.

1.The very first building block is the message receiver that receives new messages and allows

   subsequent processing

–Anypoint Connectors

1.Endpoint-based Connectors

2.Operation-based Connectors

–Endpoint based Connectors

–Operation based connectors

–Connection vs Endpoint vs Transport

–Endpoints

–Connectors & Endpoints & Global Elements

–Http Connector

–Message Processors

Day 3

Running testing & debugging Mule App (Hands-On)

–How to start and stop Mule Application

–Use PostMan to invoke the API (same one which was created earlier)

–Change the payload

–Do not deploy - hot deployment happens

–Debug

1.Put a break point on Set Payload

2.Debug Mule Application

3.Use Postman and send request

4.Check the state in debug mode; study the debug info

5.Check - by default the Logger prints the entire Message Object

6.Change the Logger message to print #[payload]

7.Step Over / Continue and see the response coming back in Postman

8.Change the value of payload in debug mode

Day 4

Reading & writing Mule messages

–Mule Messages contains

1.Inbound properties

2.Outbound properties

3.Payload

4.Attachements

–Inbound & Outbound properties (Message Properties)

1.Outbound Properties

2.Payload

3.Attachment

–Payload Representation

–Hands-Ons

1. Using MEL (Mule Experession Language) in Set Payload Transformer

1. Use Mule expression to print value of name ( a query parameter) in the log

2. Also use toUpper case in MEL expression to change the payload.

2.Using Property Transformer to set the outbound property

1.Get the query parameter called name and put it in outbound property using property transformer

  2.Print the value of value of outbound property in Logger

Day 5

Creating Variables (Hands-On)

–flowVars : flow Variable have scope through the flow

–sessionVars : these have scope across multiple flows in an application

–Hands-On

1.Create flowVariable called qpName and set the value of name parameter into using MEL

2.Use qpName in Logger - using concatenation in MEL expression.

3.Also create a session variable by the name and hard code the value only to show the existence and concept of it.

Project