In several deployment scenarios, a component needs the property value of another component to customize itself. In vRealize Automation, this process is called binding to other properties. You can design your components for property bindings, but you configure the binding when you assemble the blueprint.

In addition to setting a property to a hard-coded value, a software architect, IaaS architect, or application architect can bind Software component properties to other properties in the application blueprint, such as an IP address or an installation location. When you bind a Software property to another property, you can customize a script based on the value of another component property or virtual machine property. For example, a WAR component might need the installation location of the Apache Tomcat server. In your scripts, you can configure the WAR component to set the server_home property value to the Apache Tomcat server install_path property value in your script. As long as the architect who assembles the application blueprint binds the server_home property to the Apache Tomcat server install_path property, then the server_home property value is set correctly.

Your component scripts can only use properties that you have defined in those scripts.