Hi Karthi,

To avoid missunderstandings: Saddle can not be used to monitor Mule instances. Saddle needs some local Mule installation to be able to deploy and start the configurations it has created. If you want to deploy to a remove mule installation you will have to have a file share or some other possibility to access the remote mule's folder structure.

Although Saddle has some monitoring functionality for running instances this functionality is currently only working with mule 2.2 and where it's working it doesn't work perfect. We will rework this monitoring module in the future, so that it will work with all mule versions from 2.2 to 3.x, but for now it is only usable in parts and therefor disabled for mule 3.x.

Saddle is meant to be a huge simplification for configuring mule and also provides a great unified API to access and modify messages. I recommend that you have a short look at the documentation to get a better overview over the functionalities provided by Saddle.

Don't hesitate to ask if you've got further questions.

Best regards,
Matthias