Deploying Mule Runtime
|Mule runtime engine version 3.8 reached its End of Life on November 16, 2021. For more information, contact your Customer Success Manager to determine how to migrate to the latest Mule version.|
|This section deals with deploying to standalone instances of the Mule runtime. To take full advantage of managing and monitoring features, you can deploy to the same Mule runtime via the Runtime Manager. See Deployment Strategies for a deeper look at the different deployment alternatives offered by the platform.|
Mule standalone can run multiple applications. This means you can include the same name spaces within different applications and they neither collide nor share information.
In effect, Mule is an app server. Mule checks for new apps (in the apps directory) and starts them.
Mule also restarts apps if it detects that the apps have changed, meaning you can drop a revised version of an existing, running application into the /apps directory, Mule stops the existing app and restarts using the new files.
If Mule is embedded in another container, the Mule Management Console cannot perform Autodiscovery or server restarts.
To learn how to start and stop the Mule runtime instance see Starting and Stopping Mule
Get familiar with the Mule App Deployment Model
To deploy Mule on technologies, such as web app servers, see Mule Runtime Standalone Deployment Scenarios and Configuring Mule for Different Deployment Scenarios
To set up a cluster of runtime instances providing reliable backup in case an instance goes offline, move on to Mule High Availability Clusters