---
schema_version: "1"
id: b2aa88ab913dd7120547673bbd0c46f2ec0f646ee7e043f4d21b316435bea028
title: "Introduction to Mule 4: Configuring Mule Apps"
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.3/intro-configuration.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.3/intro-configuration
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b36e9a6e059cc4d6d0f4397ceca95a57821f34cf0819672460e3d0f2393fae51
description: MuleSoft Documentation Site
release: "4.3"
latest: false
---
---
product: Mule Runtime
version: 4.3
---

# Introduction to Mule 4: Configuring Mule Apps

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

In Mule 3, Spring property placeholders are often used to configure apps dynamically for the
environment in which they are deployed. Mule 4 contains a built-in mechanism for this that allows
you to set default values and avoid the need to learn Spring.

These properties are stored in a YAML file:

```yaml
http:
  path: service
  port: "10000"
```

You can add the YAML file to your Mule app through the Global Element called Configuration
Properties. The XML for it looks like this:

```xml
<configuration-properties file="myConfiguration.yaml" />
```

MuleSoft highly recommends that you do not package the configuration files for all the environments
inside your app. Instead, you should use this file to provide defaults, then use Runtime Manager to
override each of these properties at deployment time.

## See Also

[Configure Properties](https://docs.mulesoft.com/mule-runtime/4.3/configuring-properties)