You can define properties when you are creating or editing objects such as channel templates, channels, packages (or repositories), instances, servers, and environments. These properties become environment variables when you run a command. You can also create or edit global server properties that are available on all these objects by default.

When BMC Release Package and Deployment (RPD) prepares to perform an action on a managed computer, it creates environment variables for all the properties that are relevant to that context. For example, when the system deploys a package instance to a channel, the system makes available the relevant instance, channel template, and channel properties as environment variables on the computer.

Creating properties as environment variables ensures that the properties are available to shell scripts on the remote computer: A UNIX script can access a property as $propertyName, and a Windows batch script can access a property as %propertyName%.


Do not use braces, { and }, in a property. These characters might interfere with property evaluation.

Property precedence

You can define a property with the same name on different objects. The system assigns values to the properties using the following order of precedence from the highest to the lowest:

  • Package reference instance (highest level)
  • Instance
  • Package reference
  • Package/Repository
  • Channel
  • Channel template
  • Environment
  • Server
  • Zones
  • Global server (lowest level)

For example, suppose you define a value for a property named db_user on a channel. While deploying an instance of a particular package to this channel, you changed the value for the same property. This new value that you assigned at the time of deploying the package instance overrides the channel property.


You can set reference properties on the Properties tab, under References.

Related topics

Populating property values with dynamic variables

Creating and editing properties

Was this page helpful? Yes No Submitting... Thank you