--- schema_version: "1" id: 91e95502930023ceb7adeb03ccf3d52775967242f8739a0f264556f100931be9 title: MuleSoft Settings collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/ref-mule-settings.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/ref-mule-settings source_site: docs.mulesoft.com content_type: documentation content_hash: f0105ee146844d0a376f1aca2c5c6ec83bdf9e81423aa3045eae55d97d1744fd description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # MuleSoft Settings > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Anypoint Code Builder provides configurable settings that apply across all your Anypoint Code Builder projects. Many of the default settings are suitable for most users. However, if you use the EU cloud or Private Cloud Edition, it is important to change the default US cloud setting. To open the settings: 1. If an API specification is open in the Explorer panel, close the project to avoid a synchronization error when you switch clouds. - Click **File** > **Close Folder**. 2. Open the **Settings** panel: ![Selecting the EU cloud from Anypoint Code Builder](/mulesoft/current/en-us/anypoint-code-builder/_images/acb-activity-bar-select-cloud.png) Show me how - From the Anypoint Code Builder panel, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-settings-gear.png) (gear) icon. - From the activity bar, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-settings-gear.png) (gear) icon, select **Settings**, and search for `mule` in the **Settings** tab. - Provide the command `MuleSoft: Open ACB Settings` in the [Command Palette](https://docs.mulesoft.com/anypoint-code-builder/start-use-command-palette). For information about specific Mule settings, see the sections that follow. ## Mule › Application: Default Mule Runtime And Java Versions Set a default Mule runtime engine and Java version for new Mule projects (integrations and implementations) by clicking the link **Edit defaults through command palette**. ## Mule › Application: Group ID Set the Maven group ID value for Anypoint Code Builder to use when you create a Mule integration or implementation project. This setting populates the `pom.xml` file for each Mule project. The default is `com.mycompany`, for example, `com.mycompany` in the `pom.xml`. You can change the setting within your project, as needed. For information about Maven group IDs, see [Introduction to the POM](https://maven.apache.org/guides/introduction/introduction-to-the-pom.html) in the Apache Maven Project documentation. ## Mule > Logging: Level Set the verbosity of logs that appear in the Anypoint Code Builder extension, Mule DX Server, and Mule DX Server: Scaffolding logs. Verbosity options are progressive: - Off: No issues - Fatal: Fatal issues only - Error: Fatal and Error issues - Warn (default): Fatal, Error, and Warn issues - Info: Fatal, Error, Warn, and Info issues - Debug: Fatal, Error, Warn, Info, and Debug issues - Trace: Fatal, Error, Warn, Info, Debug, and Trace issues ## Mule › Lsp › Trace: Server You can enable and control the verbosity of `LogTrace` notifications to VS Code from the `muleLanguageServerProtocol` service. Available settings: - **off** (default) - **messages** - **verbose** ## Mule › Runtime: Default Arguments Set default command-line arguments to use when starting Mule Runtime engine (Mule). Mule starts when you run a Mule application in an integration or implementation project. Common uses of this setting are to: - Append an encryption key value (such as `-M-Dencryption.key=my-key`) when running a local deployment that incorporates secure configuration properties - Set a variable (such as `-M-Denv=dev`) that Mule uses when selecting a configuration properties file by its file name - Increase the JVM heap size (such as `-M-Xmx2g`) when running memory-intensive Mule applications locally To set the maximum JVM heap size to 2 GB, add the following argument: ```text -M-Xmx2g ``` To also set the initial heap size: ```text -M-Xms512m -M-Xmx2g ``` For more information about passing properties and arguments when running Mule applications, including examples, use cases, and troubleshooting, see [Pass Runtime Properties and Arguments to Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-run-mule-apps-with-properties). For information about secure configuration properties, see [Defining and Securing Properties for a Mule Application](https://docs.mulesoft.com/anypoint-code-builder/int-create-secure-configs). ## Mule › Runtime: Default Metaspace Size Metaspace is an area for non-heap memory used to store class metadata, constant pool information, and method bytecode. Typically, the default of **1g** (1 GB) is sufficient. However, you can change the metaspace size when installing Mule Runtime engine (Mule). ## Mule: Control Plane Select a control plane for Anypoint Code Builder: - **US Cloud** (default) - **EU Cloud** - **Canada Cloud** - **Japan Cloud** - **India Cloud** - **Australia Cloud** - **United Kingdom Cloud** - **Private Cloud Edition** For more information, see [Cloud Hosts](https://docs.mulesoft.com/anypoint-code-builder/#us-eu-clouds). Starting with Anypoint Code Builder 1.28.0, you can select **Private Cloud Edition** to connect to a Private Cloud Edition (PCE) 4.3.0 or later control plane. Set [Mule: Control Plane PCE URL](#setting-pce-url) to your PCE control plane URL. To add a Mule runtime version that Anypoint Code Builder does not include, see [Add a Mule Runtime Version Locally](https://docs.mulesoft.com/anypoint-code-builder/start-acb#add-local-mule-runtime). For more information, see [Set Anypoint Code Builder to a Different Control Plane](https://docs.mulesoft.com/anypoint-code-builder/start-acb#change-clouds). ## Mule: Control Plane PCE URL Set the URL of your Private Cloud Edition (PCE) control plane, for example `[https://pce.example.com](https://pce.example.com)`. Anypoint Code Builder uses this URL when **Mule: Control Plane** is **Private Cloud Edition**, and imports custom SSL certificates for the PCE host automatically. After you set the URL, restart Anypoint Code Builder and sign in from the Command Palette with **MuleSoft: Login to Anypoint Platform**. The command opens the PCE sign-in page. For more information, see [Set Anypoint Code Builder to a Different Control Plane](https://docs.mulesoft.com/anypoint-code-builder/start-acb#change-clouds). ## Mule > Telemetry You can enable or disable telemetry services in the US cloud. By default, this setting is disabled and not used for the EU cloud. When telemetry services are enabled, Anypoint Code Builder sends anonymous usage data to the MuleSoft team. The data helps identify important usage trends. ## Mule: Home Directory Set a home directory for downloaded assets, which include Mule runtime (`runtime/`) and Java (`java/`) versions for your implementations and integrations. ## Mule > Editor > Auto-completion: Enablement Enable auto-completion suggestions in the API design editor in Anypoint Code Builder. This setting prevents the need to press Ctrl+Space to activate a list of suggestions and is disabled by default. See also [Mule > Editor > Auto-completion: Trigger Delay](#setting-auto-complete-debouncer). ## Mule > Editor > Auto-completion: Trigger Delay Set the time in milliseconds to wait before displaying auto-completion options. This setting defaults to 1500 milliseconds. See also [Mule > Editor > Auto-completion: Enablement](#setting-auto-complete). Avoid setting a long delay. If you activate the auto-completion menu but initiate other actions in your project before the delay period ends, Anypoint Code Builder automatically returns focus to the editor and opens the menu where you activated auto-completion. Such actions include opening the command palette or using the command terminal after activating the menu. If you move your cursor to a new location or use the up or down arrow keys in the editor before the trigger delay expires, the request to open the auto-completion menu is cancelled. ## Mule > Runtime: Fips Enabled Enable FIPS compliance mode for your Mule applications. When enabled, the embedded JVM uses Bouncy Castle FIPS (BCFIPS) modules for all cryptographic operations. Required for regulated PCE and GIA2H environments. Enabling this setting automatically configures BCFIPS libraries, generates a custom `java.security` file, creates a BCFKS-format keystore, and updates each Mule application run configuration with the required FIPS parameters. For more information, see [Configuring FIPS Compliance in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-fips-compliance). ## Mule > Runtime: Fips Mode Select the FIPS compliance level. This setting only applies when [Fips Enabled](#setting-fips-enabled) is selected. Available options: - **FIPS 140-2** - **FIPS 140-3** For more information, see [Configuring FIPS Compliance in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-fips-compliance). ## Mule > Runtime: Fips Custom Cacerts Path Optional path to a custom `cacerts` file. If not specified, the default `cacerts` from the JDK is used. When FIPS mode is enabled, this file is automatically converted to BCFKS format. For more information, see [Configuring FIPS Compliance in Anypoint Code Builder](https://docs.mulesoft.com/anypoint-code-builder/start-fips-compliance).