Contact Free trial Login

Automatic Domain Support for Mule 4 API Proxies

Mule runtime allows share common resources among other Mule applications by defining these resources within a Mule Domain, and declaring other Mule applications to inherit this domain. This way, all resources declared in your domain, can be accessed by all Mule applications under it.
More information about this can be found in the runtime’s Shared Resources topic.

Since each auto-generated proxy is a pre-configured Mule application, you can also define multiple API Proxies under the same domain.

Typically, API Proxy users install a domain when auto-deploying multiple proxies that have to use the same host and port and only vary their path.
If you are deploying to a Hybrid deployment target, and your API Proxy is based on Mule 4.x, you can configure your proxy to automatically inherit an API Proxy domain.

Automatically Configuring and Deploying an API Proxy to Reference a Domain

If you are deploying a proxy to an Hybrid deployment target, and the proxy is based on Mule 4.x, API Manager allows you to automatically configure this proxy to inherit an existing API proxy domain.

You can download a specific API Proxy domain from Exchange following this link.
Configure all your necessary resources and deploy this proxy domain.

Whenever you want to deploy a Mule 4.x API Proxy to inherit this domain, you can follow this process to have it automatically configured:

  1. In the API Administration tab, select Manage API and either import the API from Exchange, or from your local machine.

  2. Define you API Name, asset type, and version and asset versions.

  3. In Managing Type select Endpoint with Proxy, and then in Proxy Deployment Target select Hybrid.

  4. In Mule Version select the Check this box if you are managing this API in Mule 4 or above checkmark.

  5. In Implementation URI, type in your API’s URI.
    Additionally you can specify:

    1. A TLS Context.
      See the Building an HTTPS API Proxy article for more information.

    2. The path for your implementation URI if it’s diferent than /.

  6. Click the Advanced Options drop-down.

  7. Select your schema (HTTP/HTTPS) and optionally an API Instance label.

  8. Specify the port for your API Proxy inbound connections, and optionally set a response timeout.

  9. Select the Reference User Domain check-mark.

  10. Click Save.

    proxy domain support bb01e

After saving these configurations, in the Settings tab, under Deployment Configuration, click Deploy.

Manual Configuration

If you choose to download your API Proxy and configure it manually on your end, you need to keep in mind the following details:

  • Add the API Gateway domain dependency to your API Proxy’s pom.xml file:

  • You have two listeners name:

    • api-proxy-listener-http.
      Binds to all interfaces and uses port 8081

    • api-proxy-listener-https.
      The listener configuration for HTTPS communications.
      To use it you must uncomment code from your API Proxy template and configure your certificates and passwords.

      Your API Proxy listeners should inherit your Proxy domain HTTP Listener configuration by using any of these listeners name:

      <http:listener-config name="api-proxy-listener-http">
        <http:listener-connection host="" port="${proxy.port}" protocol="${implementation.protocol}"/>
  • The domain you inherit contains a file with default properties in its file. This resource provides settings dynamically without the need to recompile the domain.
    The properites in this file are:


Avoiding Port Conflicts

To successfully register an API, you must deploy the API proxy to a Mule runtime using a unique endpoint URL. Automatically generated proxies use the path To avoid a conflict, ensure that the proxy paths and ports are different.

Servers try to expose every interface, privileging the most declarative ones. For example local_ip is privileged against localhost.

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.