Show Table of Contents
Appendix C. Profile Property Resolvers
Abstract
When defining properties for a profile, you can use a variable substitution mechanism, which has the general syntax
${ResourceReference}. This variable substitution mechanism can be used in any profile resource, including the agent properties, PID properties, and other resources—for example, the mq-base profile's broker.xml resource references the ${broker.name} and ${data} variables.
C.1. Substituting system properties
Syntax
System properties can be substituted in a profile resource, using the following syntax:
${PropName}
Where
PropName can be the name of any Java system property. In particular, Java system properties can be defined in the following locations:
- The
etc/system.propertiesfile, relative to the container's home directory. - System property settings in the profile's agent properties.
Some of the more useful system properties defined in the
etc/system.properties file are, as follows:
Table C.1. System Properties
| System Property | Description |
|---|---|
${karaf.home} | The directory where Apache Karaf is installed. |
${karaf.data} | Location of the current container's data directory, which is usually ${karaf.home}/data for a main container or ${karaf.home}/instances/InstanceName/data for a child container. |
${karaf.name} | The name of the current container. |

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.