Property Priority Order of precedence

If a uDeploy property is defined in multiple places, its value is determined by the property priority or order of precedence. The following list defines the order of precedence from highest to lowest:

– Process
– Component version
– Resource
– Agent
– Environment
– Component
– Application
– System

If you have an environment property named ${p:environment/app.url} and a resource property with the same name, you can refer to the resource property by using ${p:app.url} or ${p:resource/app.url}.

Because the resource property is higher on the order of precedence than the environment property, in this case you must refer to the environment property by using the scoped format: ${p:environment/app.url}.

Anyway if you have a Replace Tokens Step, priority depends on the order of the Property List . Let’s suppose to have an environment property and an agent property with same name: hostname.fqdn

If Property List is like:

${p:environment/allProperties},${p:agent/allProperties}

agent property will win.

If Property List is like:

${p:agent/allProperties},${p:environment/allProperties}

environment property will win.

Middleware Analyst specialized on IBM UrbanCode Deploy (uDeploy), WebSphere Application Server (WAS), WebSphere MQ (WMQ), *NIX systems at CSE Consorzio Servizi Bancari - Bologna, Italy

Leave a Reply

Your email address will not be published. Required fields are marked *

seventeen − nine =