Start Mule by running
<MULE_HOME>/bin/mule or starting Mule as a service. By default, all applications in the
<MULE_HOME>/apps directory deploy.
Mule applications, either zipped or exploded can be dropped into $MULE_HOME/apps. If the Mule runtime is already started, the application deploys dynamically.
|All applications in Mule are unpacked at runtime and the original zip is removed. This means, for example, that dropping a zip file into the 'apps' dir creates a new folder with the same name (without the 'zip' extension) and delete the zip.|
A successful app deployment is confirmed by:
Having an unpacked application folder in the apps dir. For example, for
An anchor file created for a running app, for example,
If you wish to store your applications in a different location, you can do this on Unix-based systems by creating a symlink to your application directory from
You can also include the -app flag when you start a Mule runtime. This flag designates the applications to start (separated by the colon - :).
mule -app foo
foo is a Mule application at
$MULE_HOME/apps/foo. In this case the Mule runtime respects the specified order when starting the applications, and only the applications specified are started.
mule -app first:second
second are both Mule application folders in
We recommend that you not delete the application folder directly, but rather an application’s anchor file only. This:
Prevents any interference from the hot-deployment layer and doesn’t leave room for concurrent conflicting actions.
Avoids potential application JAR locking issues on some operation systems and allows for clean shutdown and undeployment.
For example, if the
stockTrader app is running (app folder is there as well as the
$MULE_HOME/apps/stockTrader-anchor.txt file, just delete the anchor file to have the app removed from the Mule instance at runtime. Application folder is removed once the app terminates.
After a Mule application is deployed into a Mule runtime, the Mule runtime polls the
$MULE_HOME/apps folder every three seconds for updates to
$MULE_HOME/apps/<appname>/mule-config.xml (or any config.resources file specified in an application’s mule-deploy.properties file). You can update or replace the application folder contents and touch/modify the application’s configuration file to have Mule reload the config and automatically re-deploy the application.
Updating a Mule application at runtime can be a complex change involving class modifications, endpoint modifications, changing ports, and reconfigured flows. As a result, application update cause a graceful app shutdown under the hood and reconfigures itself. In practice, this is transparent to the user and happens within seconds.
There are several ways an application can be updated:
By dropping the modifications over an existing exploded app folder and touching the 'master' configuration file (
mule-config.xmlin app root by default).
By dropping a new zipped version of the app into
$MULE_HOME/appsdir (with the same name). Mule detects this as an existing app update and ensures a clean redeployment of the app. Note that any modifications to the old app folder are discarded - the new app folder is a clean exploded application from a zip.
As you see, both integrate with existing build tools, the preference for one over another really depends on established development practices only.
|Hot redeployment can be dangerous in a production environment. It may be safer to undeploy the production application first, then replace the Mule application deployable archive. For some application changes, such as modified files in the application’s classpath, you may also need to restart the Mule runtime before deploying the new application version.|
If you’re deploying multiple applications to the same place and those applications share the same resources, you can create a common domain where you define common configurations that can be referenced by multiple projects. This allows you to, for example, expose different services in different projects through the same HTTP host and port and be able to deploy everything without any conflicts. See Shared Resources.
If you want to run Mule 3 the legacy 2.x way, edit
$MULE_HOME/conf/wrapper.conf file and replace the following line:
1 2 # Java Main class wrapper.java.mainclass=org.mule.module.reboot.MuleContainerBootstrap
With this one:
1 2 # Java Main class wrapper.java.mainclass=org.mule.module.boot.MuleBootstrap
When run in this legacy mode, none of the new application deployment features apply.
When Mule is embedded in an application server, Java application, unit test, IDE, etc, and started programmatically, the deployment functionality is disabled and Mule follows the legacy application model.
If application fails to start, such as when a broken configuration file is provided, Mule does not monitor the app for changes (as there is no application running). To update such an app, simply redeploy the app by dropping an updated archive into the apps folder.