<plugin>
Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::example$mmp-concept-config.xml[]
<configuration>
<runtimeFabricDeployment>
<uri>https://anypoint.mulesoft.com</uri>
<muleVersion>${app.runtime}</muleVersion>
<username>${username}</username>
<password>${password}</password>
<applicationName>${runtime.fabric.application.name}</applicationName>
<target>${runtime.fabric.name}</target>
<environment>${environment}</environment>
<provider>${provider}</provider>
<properties>
<key>value</key>
</properties>
<deploymentSettings>
<publicUrl>${app.url}</publicUrl>
<cpuReserved>500m</cpuReserved>
<memoryReserved>800Mi</memoryReserved>
</deploymentSettings>
</runtimeFabricDeployment>
</configuration>
</plugin>
Deploy Applications to Runtime Fabric
Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended. Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted. MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements. |
In addition to using Anypoint Runtime Manager, to deploy applications to Anypoint Runtime Fabric, you can also deploy applications by using the Mule Maven plugin. To do so, you must meet certain prerequisites, and configure your Runtime Fabric deployment strategy in your project’s pom.xml
file.
Prerequisites
-
Ensure that the Mule Maven Plugin is added to your project
See Add the Mule Maven Plugin to a Mule Project for instructions.
-
You understand and have available the number of resources required to deploy to Runtime Fabric
See Allocating Resource for Application Deployment on Runtime Fabric for more information. -
The application is already published in Exchange
-
To do this from Studio, see Publishing a Project to Exchange.
-
To do this using Maven, see Publish and Deploy Exchange Assets Using Maven.
Studio allows you to select only two project types when uploading an application to Exchange: example
andtemplate
. To specify a different project type, publish your application using Maven.
-
Configure the Runtime Fabric Deployment Strategy
Inside the plugin
element, add a configuration for your Runtime Fabric deployment, replacing the following placeholder values with your Runtime Fabric information:
Deploy to Runtime Fabric
From the command line in your project’s folder, package the application and execute the deploy goal:
mvn clean package deploy -DmuleDeploy
Redeploy to Runtime Fabric
To redeploy the application, run the same command as you did to deploy.
Runtime Fabric rewrites the application you had deployed.
Authentication Methods
Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[]
Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[]
For a detailed description of the configuration parameters, see the Runtime Fabric Deployment Parameters Reference.
Runtime Fabric Deployment Parameters Reference
Parameter | Description | Required |
---|---|---|
|
Top-Level Element |
Yes |
|
Your Anypoint Platform URI |
No |
|
The Mule version that will run in your Runtime Fabric instance |
Yes |
|
Your Anypoint Platform username |
Only when using Anypoint Platform credentials to login. |
|
Your Anypoint Platform password |
Only when using Anypoint Platform credentials to login. |
|
The name of your application deployed in Exchange |
Yes |
|
The Runtime Fabric target name where to deploy the app |
Yes |
|
Set to |
Yes |
|
Target Anypoint Platform environment
|
Yes Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[] |
|
Any of the parameters documented in deploymentSettings Reference |
No |
deploymentSettings Parameters Reference
Parameter | Description |
---|---|
|
Enables clustering across two or more replicas of the application; default is
|
|
The number of instances for your application. Default is
|
|
Enable Last-Mile security to forward HTTPS connections to be decrypted by this application
|
|
Amount of memory to be allocated for each replica of the application. Default value is 700 MB.
This allocates 100 MB of memory per replica. |
|
Maximum memory allocated per application replica. Value must be equal to or greater than memoryReserved, if configured.
This allocates 200 MB maximum memory for each replica. |
|
Number of cores allocated per application replica. Default is 0.5 vCores.
This allocates 0.5 vCores per replica. |
|
Amount of max cores to be allocated for each replica of the application
This allocates a maximum of 1 vCore per replica. |
|
URL of the deployed application:
|
Encrypt Credentials
Unresolved include directive in modules/ROOT/pages/deploy-to-rtf.adoc - include::mule-runtime::partial$mmp-concept.adoc[]
+
<plugin>
...
<configuration>
...
<runtimeFabricDeployment>
...
<server>my.anypoint.credentials</server>
...
</runtimeFabricDeployment>
...
</configuration>
...
<plugin>
+ NOTE: Make sure that the username and password are not set in the deployment configuration, or they will overwrite the defined server ID.