---
schema_version: "1"
id: 9fe9ee86628c1b60132282d098f32bb67af0a34d27f4a727c93d0932ff28e687
title: Configuring Mule to Access Anypoint Platform Control Planes
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/control-planes/configuring-mule-control-planes.md
canonical_url: https://docs.mulesoft.com/control-planes/configuring-mule-control-planes
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 3c5c758fcfe774b4065ea9363361cf2d076018e4fa7256780e0b6754ac9937c7
description: MuleSoft Documentation Site
latest: true
---
---
product: Anypoint Platform Control Planes
---

# Configuring Mule to Access Anypoint Platform Control Planes

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

A running Mule runtime engine (Mule) instance must know which Anypoint Platform control plane holds
your organization. Mule uses that connection for API gateway and, on Hybrid Standalone, for the
Runtime Manager agent. Mule connects to the US Cloud control plane by default. If your organization
is in any other cloud, set `anypoint.platform.base_uri`, `anypoint.platform.analytics_base_uri`, and
the
[client ID and client secret](https://docs.mulesoft.com/access-management/managing-business-groups#client-id-and-secret) of
the environment.

You don’t do this before you create your first Mule app. Design the app in Anypoint Studio or
Anypoint Code Builder; those IDEs don’t use these properties. Set them when you install and register
a Hybrid Standalone instance, or when you deploy an app to CloudHub or CloudHub 2.0 that must use
API gateway with a non-US Cloud control plane. If you leave the defaults, API gateway on Mule is
disabled in those clouds.

## When to Configure Mule

<table><colgroup><col> <col> <col></colgroup><thead><tr><th>Runtime</th><th>When to set <code>anypoint.platform.base_uri</code> and related properties</th><th>Why</th></tr></thead><tbody><tr><td><p>CloudHub or CloudHub 2.0</p></td><td><p>When you deploy the app, in the <strong>Properties</strong> tab in Runtime Manager, if the app must use API gateway with a non-US Cloud control plane. See <a href="#configure-runtime-manager-properties">Configuring App Properties in Runtime Manager</a>.</p></td><td><div><div><p>MuleSoft hosts Mule in that control plane. You don’t install it. Set these properties only if that app uses API gateway and your organization is not on US Cloud. Hosted Mule still defaults to US Cloud for the gateway connection.</p></div></div></td></tr><tr><td><p>Hybrid Standalone</p></td><td><p>When you install and register Mule, before you deploy apps onto that server. See <a href="#configure-hybrid-standalone">Configuring a Hybrid Standalone Instance</a>.</p></td><td><div><div><p>You host Mule. The instance cannot reach your organization until you point it at the same control plane and register the Runtime Manager agent. See <a href="https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone">Setting up Hybrid Standalone Instances</a>.</p></div></div></td></tr><tr><td><p>Runtime Fabric</p></td><td><p>Don’t set <code>anypoint.platform.base_uri</code>, <code>anypoint.platform.analytics_base_uri</code>, or the client ID and client secret on Mule</p></td><td><div><div><p>The fabric connects to the control plane when you install it. Configure network access for the cluster instead of setting <code>anypoint.platform.base_uri</code> on each Mule. See <a href="https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration">Configuring Your Network to Support Runtime Fabric</a>.</p></div></div></td></tr><tr><td><p>On-premises (not registered to Runtime Manager)</p></td><td><p>Don’t set <code>anypoint.platform.base_uri</code>, <code>anypoint.platform.analytics_base_uri</code>, or the client ID and client secret</p></td><td><div><div><p>Unregistered Mule doesn’t connect to a control plane, so <code>anypoint.platform.base_uri</code> has no effect. See <a href="https://docs.mulesoft.com/on-premises/latest/">Run Mule Runtime Engine On-Premises</a>.</p></div></div></td></tr></tbody></table>

For the `base_uri` and `analytics_base_uri` values, prefix the Anypoint Platform URL and Analytics
ingest hostname for your cloud with `https://`. See
[Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists).

## Configuring a Hybrid Standalone Instance

For Hybrid Standalone, set these properties on the Mule instance you installed, then register the
server. See [Creating Servers](https://docs.mulesoft.com/hybrid-standalone/creating-servers).

### Configuring Mule Properties in the Wrapper.conf File

To configure Mule in the `wrapper.conf` file, modify these properties, replacing `<n>` with an
integer value that is unique within `wrapper.conf`. Use `https://` plus the Platform URL and
Analytics ingest hostname for your cloud.

This example shows the `wrapper.conf` configuration for Canada Cloud:

wrapper.java.additional.<n>=-Danypoint.platform.client\_id=<environment client ID>
wrapper.java.additional.<n>=-Danypoint.platform.client\_secret=<environment client secret>
wrapper.java.additional.<n>=-Danypoint.platform.base\_uri=https://ca1.platform.mulesoft.com
wrapper.java.additional.<n>=-Danypoint.platform.analytics\_base\_uri=https://analytics-ingest.ca1.platform.mulesoft.com

### Configuring Mule Properties via the Command Line

To configure Mule from the command line, pass these options when you start Mule. The `./` prefix
applies only to Unix environments. Use `https://` plus the Platform URL and Analytics ingest
hostname for your cloud.

This example shows the command-line configuration for EU Cloud:

./mule -M-Danypoint.platform.client\_id=<environment client ID>
-M-Danypoint.platform.client\_secret=<environment client secret>
-M-Danypoint.platform.base\_uri=https://eu1.anypoint.mulesoft.com
-M-Danypoint.platform.analytics\_base\_uri=https://analytics-ingest.eu1.anypoint.mulesoft.com

## Configuring App Properties in Runtime Manager

When you deploy to CloudHub 2.0, or to CloudHub from US Cloud or EU Cloud, include these properties
in the **Properties** tab in Runtime Manager if the app must use API gateway with that control
plane. Use `https://` plus the Platform URL and Analytics ingest hostname for your cloud.

This example shows the properties configuration for Japan Cloud:

anypoint.platform.client\_id=<environment client ID>
anypoint.platform.client\_secret=<environment client secret>
anypoint.platform.base\_uri=https://jp1.platform.mulesoft.com
anypoint.platform.analytics\_base\_uri=https://analytics-ingest.jp1.platform.mulesoft.com

## See Also

- [Anypoint Platform Control Planes Overview](https://docs.mulesoft.com/control-planes/)

- [Creating and Deploying Mule Apps](https://docs.mulesoft.com/control-planes/creating-and-deploying-mule-apps)

- [Control Plane Hostnames and Allowlists](https://docs.mulesoft.com/control-planes/control-plane-hostnames-allowlists)

- [Setting up Hybrid Standalone Instances](https://docs.mulesoft.com/hybrid-standalone/setting-hybrid-standalone)

- [Download, Install, Configure, and Upgrade On-Premises Mule Runtime Engine](https://docs.mulesoft.com/on-premises/latest/runtime-installation-task)

- [Configuring Your Network to Support Runtime Fabric](https://docs.mulesoft.com/runtime-fabric/latest/install-self-managed-network-configuration)