2. ● Lets create a new project which will be used
Mule ESB but Maven is a project in which the
dependencies of the libraries necessary for
running the application will be added. Luckily
MuleSoft have thought of everything and have
created an archetype that greatly facilitate this
task
3. ● First of all, create MULE_HOME environment
variable pointing to the directory where we have
installed Mule. In my case with Mac OS X
development edit the .bash_profile in the user's
home directory and add the following:
6. ● En artifactId use the name what we want and in
muleVersion, the plugin version.
● When execute:
●
7.
8. ● The plugin will make us some questions to set
up the project:
●
● Project description.
● Mule version you want to use.
● If we add to MuleForge which is a hosting
where they Mule extensions.
● What transport protocols we use.
● Which modules you want to include in the
project: jaas, scripting, xml, client...
9. ● After answering these questions we will have the skeleton of the project created.
We included in the project, a MULE-README.txt file where we report on the
sources that generated us are basically:
●
●
The pom.xml file with project information, compile plugins, maven integration with
mule, etc., plus all the necessary dependencies mule.
● The mule-config.xml with namespaces protocols and modules that have defined
at the point of creation of the archetype of the project and a basic flow of inbound to
a component input and output ounbound file.
● A JUnit test where test through a Mule client invoking the set flow.
●
A similar mule-config.xml required for operation of the test file.
●
10. ● After answering these questions we will have the skeleton of the project created.
We included in the project, a MULE-README.txt file where we report on the
sources that generated us are basically:
●
●
The pom.xml file with project information, compile plugins, maven integration with
mule, etc., plus all the necessary dependencies mule.
● The mule-config.xml with namespaces protocols and modules that have defined
at the point of creation of the archetype of the project and a basic flow of inbound to
a component input and output ounbound file.
● A JUnit test where test through a Mule client invoking the set flow.
●
A similar mule-config.xml required for operation of the test file.
●
