Contact Us 1-800-596-4880
  1. Homepage
  2. Anypoint Code Builder

  3. MuleSoft Settings

MuleSoft Settings

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

Open Beta Release: The cloud IDE and AsyncAPI implementation support are in open beta. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.

Anypoint Code Builder provides configurable settings that apply at the IDE level, across all your Anypoint Code Builder projects. Many of the default settings are suitable for most users. However, if you use the EU cloud, it is important to change the default US cloud setting. Some settings are configurable in the desktop IDE only.

To open the settings:

  1. If an API specification is open in the Explorer panel of the IDE, close the project to avoid a synchronization error when you switch clouds.

    • In the desktop IDE, click File > Close Folder.

    • In the cloud IDE, click the (menu) icon, and select File > Close Folder.

  2. Open the Settings tab in the desktop IDE:

    Selecting the EU cloud from the desktop IDE

    Show me how

    • From the Anypoint Code Builder panel, click the (gear) icon.

    • From the activity bar, click the (gear) icon, select Settings, and search for mule in the Settings tab.

    • Provide the command MuleSoft: Open ACB Settings in the Command Palette.

For information about specific Mule settings, see the sections that follow.

Mule › Application: Group ID

Set the Maven group ID value for the IDE 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.

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) that is used when running a local deployment that incorporates secure configuration properties, or for a variable (such as -M-Denv=dev) that Mule uses when selecting a configuration properties file by its file name. For more information about these uses, see Defining and Securing Properties for a Mule Application.

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

If you are using the cloud IDE, be aware of the memory available to the container before changing this value.

Mule: Control Plane

Select a control plane for your desktop IDE:

  • US Cloud (default)

  • EU Cloud

In the cloud IDE, this setting is not configurable because it is set automatically based on the region where your Anypoint Platform account resides.

For more information, see US and EU Cloud Hosts.

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, the IDE sends anonymous usage data to the MuleSoft team. The data helps identify important usage trends.

Mule > Logging: Level

Set the verbosity of logs that appear in the Anypoint Code Builder extension and Mule DX Server 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: Home Directory

Set a home directory for downloaded assets, which include Mule runtime (runtime/) and Java (java/) versions for your implementations and integrations, as well as the acb_settings.xml file in maven/ (see Maven Settings Files in Anypoint Code Builder).