6.2

Figure 12‑1. Binding to Another Property in a Clustered Node
Auto-Binding to Other Properties
You can auto-bind to other properties by using the Auto-Bind meta data setup in a service and default
meta data in nodes, node arrays, services, and the WAR application component.
Based on the Auto-Bind meta data defined in a service by the application catalog administrator, the Auto-
Bind type appears as consume or expose to allow other properties to bind to it in the blueprint. In the
blueprint canvas, an Expose icon, , appears next to the Auto-Bind Expose properties and a Consume
icon, , appears next to the Auto-Bind Consume properties. The tooltips for the icons display the Auto-
Bind type and Auto-Bind tag information. For example, the Consume icon next to the webapps_dir
property shows the Auto-Bind Consume: Servlet Container, DIR information in the tooltip. The application
catalog administrator sets the service Auto-Bind type and tag parameters when creating a service or
editing an existing service. See Add a Service to the Library.
Preconfigured Components for Automatic Binding
WAR is the only application component that is preconfigured for auto-binding. You cannot edit the
predefined Auto-Bind type and tag parameters.
Adding an application component onto a service implies that properties can be set on either. In this case,
auto-binding happens twice. The source properties on the application component are set from target
properties on the service and the parent node or node array. Then, the source properties on the service
are set from target properties on the application component.
Table 12‑2. Preconfigured WAR Application Component
Application Component Property Auto-Bind Type Auto-Bind Tag
Linux WAR file Context Expose Context
Linux WAR file service_start Consume Servlet Container, Start
Using Application Services
VMware, Inc. 110