3 days.

• How to develop and test Mule ESB Applications
• Ways of developing integration solutions with common transports such as HTTP and JDBC
• Building REST and SOAP web services quickly and easily
• Creating custom Java components to process business logic

• Java developers wishing to transition to Mule.
• Enterprise Architects or development managers wishing to get an introduction to Mule but do not want to develop may find the first morning interesting, and can even participate in the first lab.

Prerequisites for this course include:

• Basic Java skills: a few months of practical experience is recommended.
• A desire to learn development in Mule

Requirements:

The most significant requirement for the training is the attendees’ full attention. The pace is rapid, and there is substantial amount of time for individual assignments and lab work. It is encouraged in the program to have people who finish each exercise early help those attendees that have not yet completed the assignments. Attendees who find themselves in the situation where they are forced to tend to outside work can quickly fall behind since labs are progressive in nature. It is best to assume that these people are unavailable during the training and not assign additional duties during this period.

Software Requirements:

The following software must be installed on students’ computers:

• Java Developer Kit SE 6, _26 or better
• Mule Studio
• Mule Enterprise Edition 3.2.1, full standalone edition with MMC

Detailed Syllabus

Day One:

On the first day, participants will be introduced to the Mule ESB. They will learn:

• Basic layout and configuration of a Mule application
• The Mule Message and how data is represented in Mule
• How to unit and functional test Mule applications using Junit and the Mule API
• Routing patterns and options including basic filters

Labs on the first day include:

1. Introduction to Mule, introduction to the use case for the progressive labs, and basic configurationb
2. Basic unit testing on a Mule Application
3. Using routing patterns to call multiple endpoints using multicast

Instructors Note: The first day can go as rapidly as students are able to complete the labs. Pre-work to get their development environment setup will greatly enhance the students’ pace. If able, the instructor may start to bring in new material as time allows. A more advanced set of students will often be able to complete the first segment of material and lab work from day 2.

Day Two:

The second day starts to develop more ideas along the lines of routing, with the addition of Message Properties and using Meta-data to enhance the options allowable to the developer.

Topics covered on the second day include:

• Message Properties and the 4 different scopes of properties
• Expressions and how expressions are used to route, filter, and transform messages
• Transport Architecture and the most common transport technologies: HTTP, JDBC, JMS, FTP, etc.

Labs performed on the second day include

1. Routing based on Message Properties
2. The HTTP transport and calling your application from a browser
3. Using JDBC to get information from a database
4. Using JMS to create a synchronous information request

The end of day 2 leaves developers with the sense of having built a “real” application that can be deployed and used standalone to perform a few basic tasks.

Day Three:

The third day of training goes into more depth around the web services use cases and how to build custom Mule components. Web Services will be developed both as a Client calling a web service, and as a Server handling requests. An introduction to the Mule Management Console, and maven is included in the afternoon of Day 3 as time permits.

Topics covered on Day three Include:

• How to build a server and client for both REST and SOAP web services in Mule
• Developing custom components in mule and getting access to the entire Mule Message in java POJOs
• Using the Mule Management Console to control a server and application deployment

Lab Exercises on Day three Include:

1. Building a SOAP web service and client
2. Building a REST web service and client
3. Building a Custom Transformer and Custom Component
4. Deploying the developed application to the Mule Management Console

Conclusion:

Mulesoft works to keep the trainings as fulfilling to the students as possible and fully utilize the times allocated. Often there is a little time left over in the last day to answer questions or go over customer use cases.