Mule Application Deployment to Cloudhub Using Connected App

In this article, we will create a Mule application and deploy the same to the cloud hub using Connected App.

Connected APP

The Connected Apps feature provides a framework that enables an external application to integrate with the Anypoint Platform using APIs through OAuth 2.0 and OpenID Connect. Connected apps help users delegate their access without sharing sensitive credentials or giving complete control of their accounts to third parties. Actions taken by connected apps are audited, and users can also revoke access. Note that some products do not currently include client IDs of the Connected Apps features. The Connected Apps feature enables you to use secure authentication protocols and control an app’s access to user data. Additionally, end-users can authorize the app to access their Anypoint Platform data.

Create a Mule Application in Anypoint Studio

Let’s first create a mule application, and below are the steps:

  • First, download a RAML zip file from
  • Go to the design center and import this RAML file for creating API specifications. Give name as COVID-19 Data Tracking API.
  • Publish the same RAML file to exchange with version 1.0.0.
  • Go to Anypoint studio and create a new project as covid-data-tracking-api. Next, choose import a published API. It will prompt a new window and enter your Anypoint credentials. Next, search Covid and import the RAML you have posted from your organization account.
  • Run the application in Anypoint studio and hope it will be successfully completed.

Configure Maven Settings Using Connected App

We will create a global Maven settings.xml that allows a Maven build outside of Studio to retrieve artifacts — such as the COVID-19 Data Tracking API specification — from your Anypoint Platform organization’s Exchange.

  • Maven-build: In a command-line interface, navigate to the base directory of covid-data-tracking-api and run a Maven build of this Mule app; This should succeed:
  • Delete local Maven repo: Now, go to the directory .m2repository and run the below command to delete all artifacts downloaded from any exchange.
    rm -rf ~/.m2/repository/*-*-*-*-*

  • Maven-build: Re-run the Maven build from a command-line interface; This should now fail due to unresolvable dependencies
    [ERROR] Failed to execute goal on project covid-data-tracking-api: Could not resolve dependencies for project com.mycompany:covid-data-tracking-api:mule-application:1.0.0-SNAPSHOT: Failed to collect dependencies at 4dfec539-dc02-40fe-8618-8747d32cfc66:covid-19-data-tracking-api:zip:raml:1.0.0: Failed to read artifact descriptor for 4dfec539-dc02-40fe-8618-8747d32cfc66:covid-19-data-tracking-api:zip:raml:1.0.0: Could not transfer artifact 4dfec539-dc02-40fe-8618-8747d32cfc66:covid-19-data-tracking-api:pom:1.0.0 from/to anypoint-exchange-v2 ( authentication failed for, status: 401 Unauthorized -> [Help 1]
  • Create Exchange Viewer Connected App: In Anypoint Access Management, create a new Connected App that acts on its behalf (client credentials) for reading assets from Exchange, adding the Exchange Viewer scope, and retrieving its client ID secret. client ID and secret will be used in the password section of settings.xml
  • Create settings.xml: In a text editor, create settings.xml in ~/.m2/ with credentials for reading from your Anypoint Platform organization’s Exchange as a Maven repository:

  • To use Connected App authentication, provide basic authentication and define the username ~~~Client~~~ and the password as clientID~?~clientSecret. Replace clientID with the client ID and clientSecret with the client secret from the Connected App.
  • Maven-build: In a command-line interface, re-run a Maven build of covid-data-tracking-api as before; This should now succeed

Deploy to CloudHub Using the Mule Maven Plugin

This section will use the existing Maven build configuration to perform automated deployments to CloudHub. First, we need to create a Connected App for authentication for deployment. We will deploy the mule application covid-data-tracking-api to the CloudHub prod environment from the Maven command-line interface, passing the client ID and secret.

  • Configure CloudHub deployment: Add the below configuration to the Mule Maven plugin configuration for a simple deployment to CloudHub, utilizing Object Store v2, and using your initials as the hostname prefix as before, such as shyam2603-:
                <connectedAppClientSecret> ${}</connectedAppClientSecret>
                  <anypoint.platform.client_id> ${ap.client_id}</anypoint.platform.client_id>
                  <anypoint.platform.client_secret> ${ap.client_secret}</anypoint.platform.client_secret>

  • Create CloudHub Deployment Connected App: In Anypoint Access Management, create a new Connected App that acts on its behalf (client credentials) for deployment to CH, adding the Cloudhub Organization Admin, Create Applications, Delete Applications Read Applications, View Environment, and View Organization scopes and applying to all environments and retrieve its client ID and secret. These client Id and secret will be used in the above configuration as and
  • Create Environment: In Anypoint Access Management, create a new environment dev in the sandbox and retrieves its client ID and secret. These client ID and secrets will be used in the above configuration as ap.client_id and ap.client_secret
  • Maven-deploy: In a command-line interface, deploy to CloudHub using the Mule Maven plugin, supplying the same client ID and secret of your Anypoint Platform organization as previously and the client ID and secret of your Connected App; This should result in a successful build:
    mvn -DmuleDeploy deploy -Dap.client_id=<insert-envirnoment-client-id> -

  • Wait and observe: In Runtime Manager, verify the successful deployment of covid-data-tracking-api with your chosen hostname prefix to the dev environment, resulting in the same fully qualified domain name and endpoint URL.
  • Invoke: Invoke the API using this endpoint URL; this should return an HTTP 200 OK response with body:
    curl --location --request GET '' 

  • Note: The hostname will be different for you. The above endpoint URL will not be accessible after some time, as I am using a trial account.


Leave a Comment