Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.7)
  3. Deploying
  4. Mule Deployment Model

  5. Application Format

Mule Application Format

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.

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:

  • .zip file (a regular archive with a 'zip' extension)

  • unpacked version of the same .zip file (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.