How Substitution Variables Are Resolved
Substitution variables are resolved during deployment time. Substitution variables bound to logging appender properties are resolved by logging configurations. Substitution variables bound to resource template properties are resolved by resource instances. Substitution variables bound to application, component, and binding properties are resolved based upon the node they are deployed to.
The resolution order goes from most specific to most general. For example, a substitution variable in a logging appender used for a node-level logging configuration will be resolved by searching for values at the levels node, host, environment, and enterprise. The process stops when a matching variable is found. If there is no value at any level, the value is undefined and will generate a warning when the node is provisioned.