Contact Us 1-800-596-4880

Setting Environment Variables

This version of Mule reached its End of Life on May 2, 2023, when Extended Support ended.

Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted.

MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements.

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.