Red Hat SummitFuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.Este conteúdo não está disponível no idioma selecionado.
A.4. Variable Substitution
Overview
Copiar o linkLink copiado para a área de transferência!
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.
Simple variable substitution
Copiar o linkLink copiado para a área de transferência!
Simple variables can be substituted in a profile resource using the following syntax:
${PropName}
${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:
${karaf.home}- The directory where Red Hat JBoss Fuse is installed.
${karaf.data}- Location of the current container's data directory, which is usually
${karaf.home}/datafor a main container or${karaf.home}/instances/InstanceName/datafor a child container. ${karaf.name}- The name of the current container.
Substituting a profile URL
Copiar o linkLink copiado para a área de transferência!
The profile URL enables you to substitute properties from a specific PID. A variable substitution using a profile URL has the following format:
${profile:PID/Property}
${profile:PID/Property}
Where
PID is the OSGi Config Admin persistent ID (which corresponds to the profile resource PID.properties) and Property is the name of the property you want to substitute.
For example, the
fabric profile's org.fusesource.fabric.maven.properties resource includes the following property setting:
remoteRepositories=${profile:org.fusesource.fabric.agent/org.ops4j.pax.url.mvn.repositories}
remoteRepositories=${profile:org.fusesource.fabric.agent/org.ops4j.pax.url.mvn.repositories}
So that the
remoteRepositories property is set to the value of the org.ops4j.pax.url.mvn.repositories agent property (org.fusesource.fabric.agent is the PID for the agent properties).
Substituting a zk URL
Copiar o linkLink copiado para a área de transferência!
You can substitue the contents of a ZooKeeper node using the zk URL. The URL can be specified either as an absolute node:
${zk:/PathToNode}
${zk:/PathToNode}
Or you can reference configuration properties from a specific container using the following syntax:
${zk:ContainerName/Property}
${zk:ContainerName/Property}
The preceding syntax is effectively a short cut to the following URL reference:
${zk:/fabric/registry/containers/config/ContainerName/Property}
${zk:/fabric/registry/containers/config/ContainerName/Property}Recursive variable substitution
Copiar o linkLink copiado para a área de transferência!
It is also possible to use a variable within a variable (recursive substitution). For example, the
dosgi profile's org.fusesource.fabric.dosgi.properties resource defines the following property:
exportedAddress=${zk:${karaf.name}/ip}
exportedAddress=${zk:${karaf.name}/ip}How to reference the current version of a resource
Copiar o linkLink copiado para a área de transferência!
A potential problem arises with ZooKeeper URLs if you need to reference a ZooKeeper node that has a version number embedded in it. For example, suppose you want to reference the
my-profile profile's my-resource resource, which can be done using the following ZooKeeper URL:
${zk:/fabric/configs/versions/1.0/profiles/my-profile/my-resource}
${zk:/fabric/configs/versions/1.0/profiles/my-profile/my-resource}
Notice that the profile version number,
1.0, is embedded in this path. But if you decide to upgrade this profile to version 1.1, this means you must manually edit all occurrences of this ZooKeeper URL, changing the version number to 1.1 in order to reference the upgraded resource. To avoid this extra work, and to ensure that the URL always references the current version of the resource, you can use the following trick which exploits recursive variable substitution:
${zk:/fabric/configs/versions/${zk:/fabric/configs/containers/${karaf.name}}/profiles/my-profile/my-resource}
${zk:/fabric/configs/versions/${zk:/fabric/configs/containers/${karaf.name}}/profiles/my-profile/my-resource}
This works because the
/fabric/configs/containers/${karaf.name} ZooKeeper node contains the current profile version deployed in the container.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}