Deploying to CloudHub

• You can deploy a CloudHub application from:

• Anypoint Studio - Right-click your project and click Deploy to Anypoint Platform → Cloud.

• Runtime Manager - in the cloud-based version of the Anypoint Platform. Go to the Runtime Manager section, and then from the Applications tab, click the Deploy application button.

• This page describes the options on the Deploy Application panel that is identical in both cases.

From Anypoint Platform

• To deploy an application:

• Sign in to the Anypoint Platform or click Sign up on the sign on page.

• Hover your mouse over the Runtime Manager icon and click on it, or click Open

Click Deploy application:The Deploy Application page opens:

• Limitations

• Only a CloudHub Administrator can move applications between environments.

• To avoid domain name conflict, an application cannot exist in two environments at the same time. Alter the application’s name slightly to deploy it to another environment.

• You cannot move the same application into the same environment. CloudHub prevents you from duplicating applications in a single environment. If you wish to have the same, or similar applications in a single environment, modify one application’s file to distinguish it from the original.

From Anypoint Studio

• You can easily deploy your applications to CloudHub, straight from Anypoint Studio. This is specially helpful if you’re still developing the application and want to deploy it often to an online test environment.

• With your application open in Anpoint Studio as a Mule Project, Right-click on the project node in the package explorer. Then select Deploy to Anypoint Platform > Cloud from the cascading menu.

• If this is your first time deploying in this way, a popup menu asks you to provide your login credentials for the Anypoint Platform. Studio stores your credentials and uses them automatically the next time you deploy to CloudHub.

After you sign in, the Deploy Application menu opens.

Creating an Application Name

• Every application requires a unique application domain name. The application domain identifies your application in the Runtime Manager and also provides you with a public URL, http://myapplicationdomain.cloudhub.io, for accessing the application if it exposes any inbound endpoints.

• In the Deploy Application dialog, enter a unique application name. The Application Name also becomes the cloudhub.io domain name that you use to access your application; for example the Application Name, abcde is accessible at http://abcde.cloudhub.io. Valid names contain alphanumeric characters and dashes, and contain at most 42 characters. If the name is valid, the Runtime Manager alerts you whether it is available or already reserved by another user.

Deployment Target

• If you already have any servers registered to the Anypoint Platform, you will see a Deployment Target field that lets you specify where you want to deploy your application:

• On the CloudHub worker cloud

• On an on-premises server, server group, or cluster

• This document focuses on deploying to CloudHub, for more information on deploying to servers, server groups and clusters, see Deploying to Your Own Servers.

Application File

• Upload a new file for deployment. Click the Choose file button, select your application file, and then click Open. You can also click the Get from sandbox button to copy a file from a non-production environment into your current environment. (If the Get From Sandbox button does not appear, you may first need to create a non-production environment to view this option.)

• Note: The application file size limit is 200 MB.

Runtime Version

• Using the drop-down menu, select the Runtime version to which you to deploy:

Worker Sizing

• After you deploy your application, you can allocate an amount and a size for the Worker size of your application. On each application, workers are responsible for executing your application logic. • There are 5 different worker sizes to choose from, with the compute

and memory capacities described in the following table:

Worker Sizes 0.1 vCores500 MB Mem

0.2 vCores1 GB Mem

1 vCores1.5 GB Mem

2 vCores3.5 GB Mem

4 vCores7.5 GB Mem

• Workers that have less than 1 vCore capacity (0.1 vCores and 0.2 vCores) offer limited CPU and IO for smaller work loads. Each worker has 8 GB of storage, which is used for both system and application storage. Applications with greater storage needs (verbose logging etc.) should use one of the larger worker sizes - 2 vCores or 4 vCores, which have additional storage as follows:

• 2 vCores workers have an additional 32 GB of SSD storage mounted on /tmp

• 4 vCores workers have an additional 80 GB of storage, mounted as two volumes on /tmp (40 GB), and /opt/storage (40 GB)

Region

• If you have global deployment enabled on your account, you can change the Region to which your application deploys using the drop-down menu. Administrators can set the default region on the Organization tab in Account Settings, but that region can be adjusted here when the application is deployed, if necessary.

• Note that applications deployed to Europe automatically have their domain updated to http://myapplicationdomain.eu.cloudhub.io.

• Note that applications deployed to Asia / Pacific automatically have their domain updated to http://myapplicationdomain.au.cloudhub.io.

Automatic Restart

• If you are deploying to a runtime that supports worker monitoring (3.4.0 runtime or later), you have the option to check Automatically restart application when not responding. With this box checked, CloudHub automatically restarts your application when the monitoring system discovers a problem with your application. If this box is not checked, CloudHub produces all the log messages, notifications, and any configured alerts, but takes no action to restart the application.

• Read more about Worker Monitoring.

Persistent Queues

• Check this box to enable persistent queues on your application. Persistent queues protect against message loss and allow you to distribute workloads across a set of workers. Before you can take advantage of persistent queueing, your application needs to be set up to use queues. See CloudHub Fabric for more information.

Properties Tab

• You can also optionally specify properties that your application requires. 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’re using a Mule application locally, you might configure your database host to be localhost. But if you’re using CloudHub, you might configure it to be an Amazon RDS server.

• To create an application property, click the Properties tab and set the 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.

Overriding Properties in CloudHub vs. On-Premises Mule Runtimes

• Just like with on-premise Mule runtime deployments, applications that you deploy to CloudHub can still bundle their own property placeholder or secure property placeholder files inside the deployable archive file. CloudHub substitutes these properties into the application when the application starts. With an on-premise Mule runtime, there are several ways you can override property values bundled inside the application.

Overriding Secure Properties

• Note that you can flag application properties as secure so that their values are not visible to users at runtime or passed between the server and the console. You can also include an 'applications.properties' file in your application bundle, which can include properties that are marked as secure, and they will be automatically treated as such. These properties can also be overriden by new values you can set via the Runtime Manager console at runtime. See Secure Application Properties for more information.

Insight Tab

• The Insight tab lets you specify metadata options for the Insight analytics feature. For more information, see Insight.

Logging Tab

• The Logging tab lets you change the logging setting (INFO, DEBUG, WARN, or ERROR). For more information, see Viewing Log Data.

Static IPs Tab

• To enable a static IP address for your application, go to the Static IPs tab, then check the Use Static IP checkbox.