---
schema_version: "1"
id: aa215493dc0b1be05cb5a0501bafe962962779d2dcce65b6e43b7a27c11b06a6
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.4/intro-configuration.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.4/intro-configuration
source_site: docs.mulesoft.com
content_type: documentation
content_hash: d5e9a5cb64b7e8b296b82431e6df3aaf62a1362b5fe4af2237776514b00346cc
description: MuleSoft Documentation Site
release: "4.4"
latest: false
---
---
product: Mule Runtime
version: 4.4
---

# 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.4/configuring-properties)