MuleSoft Settings

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.

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, <groupId>com.mycompany</groupId> 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 in the Apache Maven Project documentation.

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:

You can enable and control the verbosity of LogTrace notifications to VS Code from the muleLanguageServerProtocol service.

Available settings:

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:

To set the maximum JVM heap size to 2 GB, add the following argument:

To also set the initial heap size:

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. For information about secure configuration properties, see Defining and Securing Properties for a Mule Application.

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).

Select a control plane for Anypoint Code Builder:

For more information, see US and EU Cloud Hosts.

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.

Set a home directory for downloaded assets, which include Mule runtime (runtime/) and Java (java/) versions for your implementations and integrations.

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.

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.

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.

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.

Select the FIPS compliance level. This setting only applies when Fips Enabled is selected.

Available options:

For more information, see Configuring FIPS Compliance in Anypoint Code Builder.

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.