---
schema_version: "1"
id: dfaf87104d25a5264fa655ceb2e6702317d463d83215ae508e16538d26fcd423
title: Setting Environment Variables
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/mule-runtime/4.4/setting-environment-variables.md
canonical_url: https://docs.mulesoft.com/mule-runtime/4.4/setting-environment-variables
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 2425694e30e79038fedded5e8eb1c57167b4d8b1494dc457590097a0b659c7d8
description: MuleSoft Documentation Site
release: "4.4"
latest: false
---
---
product: Mule Runtime
version: 4.4
keywords: anypoint studio, esb, environment variables, system variables, system properties
---

# Setting Environment Variables

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

If you’re deploying multiple applications as a shared resource, you shouldn’t set any properties in
the project properties files. This might cause conflicts between the various apps that share a
domain. Instead, you can set environment variables over the scope of the deployed app, its domain,
and other apps under that domain.

The steps below explain how to set environment variables in Studio. These variables are only used
when you deploy locally through Studio. When you deploy your applications to a standalone server,
you must provide these variables through the command line.

1.  Under **Run**, select **Run Configurations**.

2.  Select the corresponding run configuration. If a run configuration does not exist for your
    project, you can create one by using the new button.

3.  Select the **Environment** tab, and add the variables you need.

    The environment variables you create are defined at the domain level. These will affect all of
    the applications associated with that domain when you deploy locally using Studio.

Setting environment variables only works when running the application in the Mule runtime engine
within Studio. This configuration does not affect design time operations such as DataSense,
automatic completion, or validation.

## See Also

- [Shared Resources](https://docs.mulesoft.com/mule-runtime/4.4/shared-resources)

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