salesforce Dreamforce On-Demand
Contact Us 1-800-596-4880
  1. Homepage
  2. CloudHub 2.0
  3. Deploying Apps to CloudHub 2.0

  4. Deploying Apps to Shared Spaces

Deploying Apps to Shared Spaces

You deploy apps to a shared space using Runtime Manager.

CloudHub 2.0 supports Mule runtime engine versions 4.3x through 4.4x. Mule 3.x is not supported.

Deploy an App to a Shared Space

  1. From Anypoint Platform, select Runtime Manager > Applications.

  2. Click Deploy application.

  3. On the Deploy Application page:

    1. Enter the name of the application.

      You cannot change the name of an app after you deploy it. To change the name, you must delete and redeploy the app using the new name.

    2. Select an application file:

      • To upload a Mule app JAR file from your system, select Choose file > Upload file.

      • To choose an example app from Anypoint Exchange:

        1. Select Choose File > Import file from Exchange.

        2. In the Get from Exchange page, enter hello in the Search assets by name:

          Get from Exchange page

        3. Click Hello World and then click Select.

    3. Select CloudHub 2.0, and then Shared Space for the region from the Deployment Target list.

      For the list of regions, see Shared Global Regions. If you have the global deployment entitlement, all regions are available. If you have region restrictions based on your subscription, only regions that are available to your organization appear.

    4. Configure options for deployment:

  4. Click Deploy Application.

Specify Runtime Options

Click the Runtime tab and specify the following options:

Runtime version

Specifies the Mule runtime engine version.

Replica size

Specifies the number of vCores in the replica to run your application.

For information on replica sizes, memory, and storage, see CloudHub 2.0 Replicas. CloudHub 2.0 limits the replica size per deployment to four vCores.

Replicas

Specifies the number of replicas, or instances, of the application to deploy.

A minimum of two replicas is required for high availability.

Run in Runtime Cluster Mode

Enables Mule clustering across each replica of the application.

This option requires at least two replicas.

Deployment model

  • Rolling update:

    • Maintains availability by incrementally updating replicas.

  • Recreate:

    • Terminates replicas before redeployment.

    • Redeployment is faster and doesn’t require additional resources.

Application Names

The application name you specify can contain between 3 and 42 alphanumeric characters (a-z, A-Z, 0-9) and dashes (-). They cannot contain spaces or other characters. The application name must start with a letter (a-z or A-Z). It cannot start with a number or dash and it cannot end with a dash.

To ensure that names are unique and avoid domain conflicts, CloudHub 2.0 adds a six-character unique-id to the application name that you specify in the public endpoint URL.

The application name identifies your application not only in Runtime Manager but also in the public cloudhub.io domain. For example, an application named myapp is accessible at http://myapp-unique-id.shard.usa-w2.cloudhub.io. You must have unique application names for each deployment target.

To further customize your app names, you can create a naming convention. For example, you could prepend your company name and department to all application names, such as mycompany-mydept-myapp. You can then add DNS records to hide the complex application name. For example, you might route requests to myapp.mycompany.com to mycompany-mydept-myapp-unique-id.shard.region.cloudhub.io.

Make application file names as unique as possible. An app cannot be deployed if it shares the same name as an asset in Exchange.

Change App Behavior with Properties

You can configure property values, such as specifying the environment or setting passwords and usernames, during app deployment.

For information about configuring app properties, see:

Configure Logging for the App

Logging is enabled by default for apps deployed to CloudHub 2.0.

Disable or Enable Logging

To disable or reenable logging for the app:

  1. Click the Logging tab.

  2. Deselect or select the Enable application logs option.

  3. Click Apply Changes.

If you disable logging, the Logs heading still appears in the Runtime Manager navigation menu, but application logs are not collected.

Configure Log Levels and Categories

To configure additional log levels and categories to include in logs:

  1. Click the Logging tab.

  2. Select the log level:

    • INFO: Informative messages

    • DEBUG: Debugging messages

    • WARNING: Warning messages

    • ERROR: Error messages, such as when an exception occurs

    • FATAL: Fatal messages for when an application fails

  3. Optionally, set the log level for specific a Java package class by selecting the log level, entering the package.name, and pressing the Enter key.

  4. Click Apply Changes.

See Also