The startApplication operation stops a running Mule Application. It is normally used in deploy workflows or utility workflows.
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 should run on the Mule server where the project will be stopped. Since standalone servers don't natively support this operation, this operation runs a FlexDeploy specific process to mark the application as one to be stopped. The application will be shown as undeployed in the logs, but the application will be able to be started by the startApplication operation without providing the artifact again. This means that any local changes to the files will be preserved by the stop and start. In order to stop an application on an entire cluster, set up multiple instances or endpoints. The operation will be run on all of them so the application will be stopped on all of the cluster members. |
...
Property Name | Property Code | Required for which FDMULE_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 |
...