---
schema_version: "1"
id: 3161d78affb6e285a1b40890538e5918bc6ae6c8d5191f441c3d0ffe666bd61e
title: Manage Properties for Applications On-Premises
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/runtime-manager/hybrid-manage-props.md
canonical_url: https://docs.mulesoft.com/runtime-manager/hybrid-manage-props
source_site: docs.mulesoft.com
content_type: documentation
content_hash: b41f64c114a99c059f1522f9f078e427e2ef60a52299e776c5910656cdec0888
description: MuleSoft Documentation Site
latest: true
---
---
product: Runtime Manager
---

# Manage Properties for Applications On-Premises

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

[![logo hybrid active](/mulesoft/current/en-us/_/img/icons/hybrid-cloud.svg "Hybrid")Hybrid](deployment-strategies#hybrid-deployments)[ ![logo server active](/mulesoft/current/en-us/_/img/icons/server-cloud.svg "Anypoint Platform PCE")Private Cloud Edition](deployment-strategies#anypoint-platform-private-cloud-edition)

In an on-premises (hybrid or Anypoint Platform PCE) deployment, you can add properties to an
application by using either a properties file or Anypoint Runtime Manager.

For example, you can define application-specific properties in a properties file and then later add
environment-specific properties from Runtime Manager during deployment.

Specifying properties in Runtime Manager enables you to define an application’s properties in one
place rather than in multiple files in multiple environments.

After deploying an application, you can modify application properties or create new ones from the
application **Settings** page. If you change properties after an application is deployed, you must
restart the application and any server group or cluster where the application is deployed.

The values of properties defined on the **Settings** page override any application properties
defined in the properties file or other properties of Mule.

The following security considerations apply to properties:

- Values sent between Runtime Manager and Mule runtime engine are encrypted over HTTPS.

- Values stored in the Runtime Manager internal database are encrypted.

- Runtime Manager displays the values of the properties only in the **Settings** page.

## Add Application Properties by Using a Properties File

You can add properties to an app by including property placeholder YAML file in the deployable
application archive file. See
[Configuring Properties](https://docs.mulesoft.com/mule-runtime/latest/configuring-properties).

Mule runtime engine then loads these properties into the application when the application starts.

## Add Application Properties in Runtime Manager

You can override the property values in the properties file bundled inside the application in
Runtime Manager:

1.  From Anypoint Platform, select **Runtime Manager**.

2.  Click the **Applications** tab.

3.  Click the **Status** column to display the details pane.

4.  Click **Manage Application**.

5.  On the **Settings** page, click the **Properties** tab:

    ![\*Properties\* tab](/mulesoft/current/en-us/runtime-manager/_images/rtm-manage-props.png)

    Figure 1. The screenshot shows (**1**) the **Properties** tab, (**2**) the **Key** and **Value**
    fields, and (**3**) the **…​** menu on the application **Settings** page.

6.  Enter the property name in the **Key** field.

7.  Enter the property value in the **Value** field.

8.  Click **Save** > **Redeploy Application**.

You can edit or delete a property using options in the **…​** menu.

## Other Methods for Overriding App Properties

The following are some alternative methods for overriding app properties:

- Configure an external location to add property placeholders or secure property placeholder files
  to override properties.

- Set Java system environment variables at deployment time to override properties.

  To do this, deploy the app using the following command:

  mule -M-Dsecret.key=toSecretPassword -M-Denv=prod -M-Ddb.password=secretPassword -app myApp.zip

  In this case, all the values typed into the command are stored only in memory and must be provided
  every time. The values are never stored in any file.

## See Also

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

- [Configuring Environment Properties](https://docs.mulesoft.com/mule-runtime/latest/deploying-to-multiple-environments)

- [Setting a Specific Environment when Starting Mule On-Premises](https://docs.mulesoft.com/mule-runtime/latest/deploying-to-multiple-environments#setting-a-specific-environment-when-starting-mule-on-premises)

- [Deploy to Your Servers](https://docs.mulesoft.com/runtime-manager/deploying-to-your-own-servers)

- [Safely Hide Application Properties](https://docs.mulesoft.com/cloudhub/secure-application-properties)