The undeploy operation undeploys a Mule Application. It can be used in deploy workflows. It requires that the artifact used to deploy the application be present so that it can be determined whether it is an application or domain which is being undeployed.
This operation is compatible with the following types of servers:
FDMULE_TYPE | Notes Specific to the FDMULE_TYPE | CloudHub | Anypoint Runtime ManagerRuntime Agent | |
|---|---|---|---|---|
Standalone | This operation runs on the Mule server endpoint(s). In order to undeploy an application from an entire cluster, set up multiple instances or endpoints. The operation will be run on all of them so the application will be removed from all of the cluster members. |
...
Property Name | Property Code | Required for which Mule Type | Description |
|---|---|---|---|
Mule Account |
| CloudHub, Anypoint Runtime Manager | The Mule Integration Account See Configuring a Mule Cloud Account for help creating a Mule Cloud Account. |
Mule Home |
| Standalone | Path to the Mule Standalone Install |
Mule Type |
| All | The type Mule server that this environment includes. (CloudHub, Anypoint Runtime Manager, Runtime Agent, Standalone) |
Timeout in Milliseconds |
| None | Timeout for deployment and utility operations such as start and stop application. Defaults to 600000 which is 10 minutes. |
Runtime Agent URL |
| Runtime Agent | The URL of Runtime Agent |
Mule Region Code |
| None. Used for CloudHub, but optional | Region Code for Mule |
...