In several deployment scenarios, a component needs the property value of another component to customize itself. In Application Services, this process is called binding to other properties.

The application catalog administrator can modify property definitions in the script. For example, a WAR component might need the installation location of the Apache Tomcat server. The WAR component can set the server_home property value to the Apache Tomcat server install_path property value.

The Bash script for a component can use only its own properties. In addition to setting a property to a hard-coded value, Application Services allows a property to be bound to another property in the blueprint. When you bind to another property, you can customize a script based on the value of another component's properties and virtual machine properties such as IP addresses. To bind a property to another property, select the property value from the Blueprint Value drop-down menu in the Edit Property dialog box.

For a single virtual machine node, the referenced properties in the Blueprint Value drop-down menu are, NodeName:ComponentName:PropertyName.

For clustered virtual machines node, the referenced properties in the Blueprint Value drop-down menu are, all(NodeName:ComponentName:PropertyName). When another property refers to this cluster property, it gets the PropertyName property values from all of the virtual machines in the cluster. The predefined all(NodeName:node_array_index) property for clustered virtual machines gets the collection of node array indexes in the cluster. See Predefined Node Array Index Property.

For cluster and single nodes, the self:ComponentName:PropertyName value is used to indicate a component property from the virtual machine where the target component is running. For instance, if a WAR component is deployed in an Apache Tomcat server, the WAR server_home property can be set to self:tomcat:install_path to refer to the Apache Tomcat server running in the current virtual machine.

Node level properties such as IP address display as, NodeName:ip or self:ip. These properties belong exclusively to the virtual machine and not to any specific component in the virtual machine.

For IP addresses of virtual machines with multiple NICs, Application Services provides either a NodeName:NICx_ip or self:NICx_ip property. Where x reflects the NIC number. See Predefined IP Address Property.

Figure 1. Binding to Another Property in a Clustered Node


Bind a property to another property in a clustered node.