Contact Free trial Login

Managing Applications on CloudHub

logo cloud active logo hybrid disabled logo server disabled logo pcf disabled

After you deploy an application to CloudHub, you can use the Runtime Manager to manage your application at runtime.

Depending on if your application is deployed to CloudHub or to your own servers, there is a different set of possible actions you can perform.

This document refers to applications that are deployed through the Runtime Manager console to CloudHub. To view the basic management tools that are common to all types of deployments, see Managing Deployed Applications. See Deployment Strategies to understand the different deployment scenarios that the platform offers.

With applications deployed to CloudHub you can handle the following features:

Applications Dashboard

If you select any of the applications on the Applications tab, a panel opens on the right, where you can read additional information about the application and access its settings.


What this dashboard displays depends on if your application is deployed on CloudHub or on Mule.

Applications deployed to CloudHub display the status, the time of the last modification, and the deployed application ZIP file, which you can change from this menu through the Choose File button.

They also display additional info about the CloudHub worker they run on, namely the Mule version, worker size, worker amount and region. You will also see buttons that allow you to view logs and insights, and enter the Manage Application menu.

Accessing App Settings

  1. Sign in to the Anypoint Platform and view the Applications tab of the Runtime Manager.

  2. Select one of your CloudHub running applications to open a panel on the right side.

  3. In the panel on the right, click the Manage Application button to open up the application’s settings.

manage app

In this menu you will be able to change most of the settings you can configure when deploying. For applications on CloudHub, you will also be able to access Log data, Insights, Alerts, queues, set up and manage schedules and application data. You can also see the Alerts History tab, which displays a record of the triggered alerts on the app. See Alerts on Runtime Manager for more on this.

Monitoring Applications

If your application is deployed to CloudHub, a rich set of tools exists for monitoring events that may occur on your application and the performance of the virtual servers it’s running on. See Monitoring Applications for more details.

Redeploying to a Different Region

If you have global deployment enabled on your account, you can select a different region for your CloudHub deployments. . On the settings page, pick the Runtime section, and then select the desired region from the drop-down menu. . After you select the region, click the Apply changes button, which restarts your application in the new region.


Administrators can set the default region on the Organization tab in Account Settings, but that configuration can be overridden when the application is deployed, if necessary.

Domains for applications deployed to Europe automatically update to

Scaling Your Application

You can dynamically scale your applications by selecting options from the Worker size drop-down menu, and clicking the Apply Changes button. Your application uses the worker size and amount that you specify. For more information about deploying to multiple workers, see Worker Sizing.

By default, all applications are limited to no more than four workers of any size. Free and professional accounts are limited to a single worker per app. If you need more workers or more total vCore capacity, update your subscription. If you need more than four workers for a single domain, contact MuleSoft directly.

Updating Environment Variables and Application Properties

You can configure environment variables for your application using CloudHub. This allows you to externalize important pieces of configurations, which may switch depending on the environment in which you’re deploying.

For example, if you use a Mule application locally you might configure your database host to be But if you use CloudHub, you might configure it to be an Amazon RDS server.

To create an environment variable or application property:

  1. Select the Properties tab in the Settings section.

  2. Define a variable by using either a text key=value format, or by using the list format with two text boxes.

  3. After you’ve made the change, click Apply changes. Here’s an example using the text format:

    Set Properties

    Here is another example using the list format:


These environment variables can be used inside your Mule configuration. For example:

<spring:bean id="jdbcDataSource" class="org.enhydra.jdbc.standard.StandardDataSource" destroy-method="shutdown">
   <spring:property name="driverName" value="com.mysql.jdbc.Driver"/>
   <spring:property name="url" value="${database.url}"/>
If you also have the same variables set in a file inside your application, the environment variables you set here in the console always override the values in '' when your application deploys.

To delete an existing environment variable, either delete the line in text format, or in the list format, hover over the variable on the page and select the "X" button on the right side. To edit an existing variable, just select the name or value on the page and edit it.

When you complete adding, deleting, or editing your environment variables, click Apply Changes to save the changes and redeploy them.

Secure Environment Variables

CloudHub also supports secure environment variables to protect sensitive information.

Downloading a Copy of Your Deployed Application

The application most recently deployed is always available for download from the console. Select the Properties tab on the application Settings page, then click Choose file. Specify a location on your computer to save the file.


Link not available?

If you can see the application name, but the name is not a live link, your administrator has disabled application downloads for users with developer and support account types. Contact your administrator if you need a copy of the application.

Updating Your Application

If you made changes to your applications and would like to upload a new version:

  1. Click Choose file on the Deployment screen for that application. The new filename appears in italicized text.

  2. Click Apply changes to use the new file for deployment.
    Within a few seconds, your application successfully redeploys. While redeploying, the application status indicator changes to blue, and then turns green after the deployment completes.

  3. You can click Logs to see a live redeployment of your application.

After successfully starting a new worker with the application’s latest version, CloudHub overwrites the previous version and you can no longer download the previous archive or revert back to the previous version of application.

Zero Downtime Updates with CloudHub

CloudHub supports updating your application so users of your HTTP APIs experience zero downtime. During your application update, CloudHub keeps both the old version and the new version of your application running. Your domain points to the old version of your application until the new version is fully started. This allows you to keep servicing requests from your old application while the new version of your application is starting.

Icon Description


The application update is deploying.


The updated version of the application didn’t start correctly. Mule shuts down the new version and leaves the old application running.

Static IPs

CloudHub supports allocating a static IP for applications so that they can be whitelisted for other services. To enable a static IP for your application, go to the Static IPs tab on your application settings page, then enable the Use Static IP checkbox. A static IP is allocated to your application and displayed in the table below; it will be used by the application when it restarts. If your application is not running, you can pre-allocate a static IP before starting the application. For details, see Deploying to CloudHub.

If your application is deleted, the static IP will be lost and you must request a new one.

Creating HTTP Services For Your Application

To make HTTP-based services available under your domain, use the ${http.port} variable in your configuration. For example:

<http:listener-config name="HTTP_Listener_Configuration" host="" port="${http.port}" .../>

CloudHub specifies this port for you and automatically load-balances your domain across the number of workers that you specified.

See Also

Additional tools for managing your applications:

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.