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

  4. Managing Global Configuration Elements

Managing Global Configuration Elements

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

Open Beta Release: The cloud IDE is 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.

Use the Global Configurations view to manage the configurations your Mule application depends on, including HTTP Listener configurations, database connections, properties files, TLS contexts, and error handlers.

Before You Begin

Open the Global Elements Panel

Access the Global Elements panel from Project Properties to view and manage the global configurations defined in your project.

To open it:

  1. Use one of the following options:

    • In the canvas toolbar, click the Manage Global Elements icon to open Project Properties with the Global Elements tab already selected.

    • In the Explorer, right-click your project and select Project Properties, then select Global Elements from the left menu.

The panel shows a searchable table with the Type, Name, and Notes for each element. Use the Selected File dropdown to select a configuration file and view its elements. The table updates in real time as you make changes.

Add a Global Configuration

You can add global configurations through MuleSoft Vibes using natural language. The element is created with the correct structure and placed in the right file automatically.

From the Global Elements panel, use the MuleSoft Vibes chat to describe what you need, for example:

  • "Add a Salesforce connector config"

  • "Register a new properties file"

  • "Create an HTTP Listener global config on port 8081"

For more details on using Vibes to manage global elements, see Use MuleSoft Vibes to Manage Global Configurations.

Edit a Global Configuration

To edit an existing element, use one of the following methods:

  • Form editor — For connector configurations like HTTP Listener or Salesforce, click the More actions (…​) menu next to the element and select Edit. A form-driven editor opens with field validation so you can update connection details visually.

  • Source editor — Click More actions (…​) > Go to Source to jump directly to the element’s location in the XML file and edit it in context.

  • MuleSoft Vibes — Describe your change conversationally and Vibes applies it for you.

Remove a Global Configuration

To remove a global configuration element, use MuleSoft Vibes. For example:

  • "Remove the Salesforce connector config"

  • "Delete the HTTP Listener global config"

Before removing an element, Vibes identifies any flows that reference it and warns you of the impact before making any changes.

Manage Configuration Properties Files

When you create a new project, ACB automatically generates a global-configs.xml file for storing configuration properties separately from flow definitions. If you open a project migrated from Studio, ACB preserves the existing project structure.

Register a Properties File

To register a .yaml or .properties file as a configuration source, use MuleSoft Vibes. For example:

  • "Register a new properties file"

  • "Add config.yaml as a configuration properties file"

ACB adds a <configuration-properties> element to your global config XML and the file appears in the panel under Configuration Properties.

Add Inline Global Properties

To add <global-property> key-value pairs, use MuleSoft Vibes. For example:

  • "Add a global property named env with value dev"

All inline properties are stored in global-configs.xml instead of individual application XML files.

Set Up Multi-Environment Configuration

ACB supports the $site.yaml file pattern for environment-specific property files.

If your project contains files such as dev.yaml, qa.yaml, and prod.yaml, they appear in the Environments section of the Global Elements panel.

To set the default environment, use MuleSoft Vibes. For example:

  • "Set the default environment to dev"

  • "Set up multi-environment configuration for dev, QA, and prod"

Vibes adds a corresponding <global-property> element to your global configuration file, for example: <global-property name="env" value="dev"/>.

Use Preview Mode to switch the active environment and verify that property placeholders resolve correctly before you deploy.

Work with Secure Properties

ACB supports the Mule Secure Properties module:

  • Generate encrypted property values from the IDE.

  • ACB warns you when a properties file contains unencrypted credentials.

For information about encrypting values and referencing them in your Mule application, see Defining and Securing Properties for a Mule Application.

Global Element Types

In addition to connector configurations, the Global Elements panel supports the following component configuration types:

Component What It Does

Global Error Handler

Set any error handler as the application-wide default. You can also reference handlers from imported projects for consistent exception management across teams.

API AutoDiscovery

Configure your Mule application for API Manager auto-discovery at deployment time. Select from the flows defined in your application when configuring the auto-discovery settings.

TLS Context

Set up Trust Store and Key Store configurations once, then reference them from any connector that supports TLS.

Import Project Reference

Import a JAR containing a shared Mule project. Use its flows, error handlers, and connection configurations. ACB handles POM dependency management.

Caching Strategy & Object Store

Define centralized caching strategies and object stores that can be referenced across all flows in the project.

For API AutoDiscovery configuration details, see Configure API Autodiscovery for Local Testing and Tracking Requests with Autodiscovery.

Use MuleSoft Vibes to Manage Global Configurations

You can use MuleSoft Vibes to create and update global elements by using natural language prompts.

Automatic Generation

When Vibes generates a flow that uses a connector, it also generates the corresponding global configuration element. Credentials are stored as property placeholders, and a sample properties file is created for the generated configuration.

Natural Language Examples

You can ask Vibes things like:

  • "Create an HTTP Listener global config on port 8081"

  • "Set up multi-environment configuration for dev, QA, and prod"

  • "Centralize all global configs into the global-config.xml file"

  • "What global elements are defined in this project?"

  • "Validate my property placeholders"

Centralize Configurations from Studio Projects

If your project has global elements scattered across multiple config files (common in projects migrated from Studio), ask Vibes to consolidate them:

"Move all global configs into global-config.xml"

Vibes identifies every global element across your config files, moves them to global-config.xml, and updates all flow file references automatically.

The manage-global-configurations skill powers these operations. For more on skills in MuleSoft Vibes, see Using Skills with MuleSoft Vibes.

See Also