Mule Application Format
|MuleSoft recommends against deployments to Mule 3.8. Standard Support for this version ended on November 16, 2018, and Mule 3.8 will reach its End of Life on November 16, 2021, when Extended Support ends.|
The deployment unit of a Mule application encapsulates everything an application needs to function, such as libraries, custom code, configuration, deployment descriptor and any environment properties accompanying the application. It exists in one of two formats:
.zipfile (a regular archive with a 'zip' extension in lower case)
unpacked version of the same
.zipfile (exploded app)
/ \- classes // application-specific expanded resources (e.g. logging configuration files, properties, etc |- lib // application-specific jars |- plugins // application plugins files \- lib // application shared plugin jars (FROM 3.7 and +) |- mule-config.xml // Main Mule configuration file, also monitored for changes |- mule-deploy.properties // Application deployment descriptor (optional) |- mule-app.properties // custom properties to be added to the registry instance used by the application (optional) |- *.grf files // produced by DataMapper to plot its data mapping
Mule supports the deployment of both packaged (zipped) and exploded (unzipped) applications.
You can share libraries between applications via the application deployment descriptor attribute.