The deploy operation deploys a Mule Application. It should be used in deploy workflows.
...
It is always recommended to externalize any configuration parameters (user names, passwords, URLs etc.). Instead of hard-coding these values inside application code, we recommend to create creating a properties file for your mule application. Please follow these steps to achieve property replacement in FlexDeploy.
...
Property Name | Property Code | Required for which Mule Type | Description |
|---|---|---|---|
Mule Application Name | FDMULE_APP_NAME | All | Name of the Mule Application to stop |
| Target Server Type | FDMULE_TARGET_TYPE | Anypoint Runtime Manager | Mule Target Server Type (Server, Cluster, ServerGroup) If necessary, this property can be overridden at the property/environment/instance level. |
| Target Name | FDMULE_TARGET_NAME | Anypoint Runtime Manager | Name for the Target Server, Cluster or Group If necessary, this property can be overridden at the project/environment/instance level. |
| Static IP Address | FDMULE_STATIC_IPADDRESS | None. Used for CloudHub, but optional | Static IP Address for the Application If necessary, this property can be overridden at the project/environment/instance level. |
FDMULE_WORKERS_COUNT | None. Used for CloudHub, but optional. | Workers Count | |
FDMULE_WORKER_TYPE | None. Used for CloudHub, but optional. | Type of the Worker Size (Micro,Small,Medium,Large,xLarge,xxLarge) Defaults to Small | |
FDMULE_PERSISTENT_QUEUES | None. Used for CloudHub, but optional. | Enable Persistent Queues Defaults to false | |
FDMULE_STATIC_IPADDRESS | None. Used for CloudHub, but optional. | Static IP Address for the Application | |
FDMULE_PROPERTY_FILE | None. Used for CloudHub, but optional. | Name of the property file to create with Mule Properties | |
FDMULE_AUTO_START | None. Used for CloudHub, but optional. | Defaults to true | |
FDMULE_MONITORING_ENABLED | None. Used for CloudHub, but optional. | Defaults to true |
...