Nav

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 on it, once deployed.

This document refers to applications that are deployed via the cloud 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. Here you will be able to read additional information about the application and access its settings.

dashboard

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

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 runtime version, worker size, worker amount and region. You will also see buttons that allow you to view Logs, Insights and enter the Manage Application menu.

Accessing App Settings

Sign in to the Anypoint Platform and view the Applications tab of the Runtime Manager. Select one of your CloudHub running applications to open a panel on the right side. On that panel, 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 aso see the Alerts History tab, that displays a record of the triggered alerts on this 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 virutal 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’ve made your selection, click the Apply changes button, which restarts your application in the new region.

SetRegion

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

Note: Domains for applications deployed to Europe automatically update to http://myapplicationdomain.eu.cloudhub.io

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.

WorkerSize

All applications are limited by default to no more than four workers of any size, and 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 us 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 configuration 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 0.0.0.0. But if you use CloudHub, you might configure it to be an Amazon RDS server.

To create an environment variable or application property, select the Properties tab in the Settings section. You can define a variable by either using a text key=value format or by using the list format with two text boxes. After you’ve made the change, click Apply changes. Here’s an example using the text format:

SetProperties

Here’s another example using the list format:

SetPropertiesList

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


         
      
1
2
3
4
<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}"/>
</spring:bean>
If you also have the same variables set in a mule-app.properties file inside your application, the environment variables you set here in the console always override the values in 'mule-app.properties' 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.

DownloadAppFile

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, click Choose file on the Deployment screen for that application. The new filename appears in italicized text. 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. You can click Logs to see a live redeployment of your 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

image2014-10-24+16%3A43%3A57

The application update is deploying.

image2014-10-24+16%3A44%3A47

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:


         
      
1
<http:listener-config name="HTTP_Listener_Configuration" host="0.0.0.0" 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: