Deploying an API Proxy to CloudHub
In API Manager, follow this procedure to deploy a proxy to CloudHub if you use Mule 3.8 Runtime, API Gateway 2.1 or later, or Mule 4.x.
During the configuration of an API instance, you specify to manage the instance as a basic endpoint or as endpoint with a proxy. If you specify deployment to CloudHub of an endpoint with a proxy, use this deployment procedure.
In API Manager, click Manage API > Manage API From Exchange, and configure management of the proxy asset.
In API Configurations, if you want to deploy the API to Mule 4, check this box: Check This Box If You Are Managing This Api In Mule 4. The checkbox is located at the bottom of API Configurations as shown in the following RAML, SOAP, and HTTP configuration screenshots:
After saving API Configurations, Deployment Configuration appears:
In Deployment Configuration, in Runtime Version, select a Mule Runtime version. In Proxy Application Name, type a name for the proxy.
Check Update Application If Exists if you want to redeploy the proxy to Cloudhub. Uncheck this option if you do not want to continue with deployment if the proxy is already deployed. In the latter case, deployment fails.
Deploying to CloudHub, which shows the status of deployment, appears.
After deployment, you can manage the deployment from Runtime Manager.
If you chose HTTPS for the scheme of the deployment, complete the steps to build HTTPS services.