About Mule 3.x Proxies (Nov 2017)

API Manager automatically generates the proxy app when you configure the API as an endpoint with a proxy and includes an auto-discovery element in the app. Mule locks the API until all policies have been applied. The client app (consumer) calls the proxy which forwards the call to the API. After you deploy the app, Mule Runtime 3.x and earlier calls API Manager using the environment client ID and secret to get the policies for the API.

In most cases, the proxy you generate in API Manager is suitable for deployment. However, you can modify the proxy to log data to a file or send data to a Splunk account with the Anypoint Splunk Connector, for example.

You can import a proxy that you download from API Manager into Studio as a Mule Deployable Archive. You can then modify the proxy in Studio.

If you configured an endpoint with a proxy to use the HTTPS scheme, you need to modify a proxy to add HTTPS credentials.

Now, you’re ready to deploy an auto-generated proxy for Mule 3.x.

In this topic: