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, Auto-Bind Expose icon, appears next to the Auto-Bind Expose properties and a Consume icon, Auto-Bind 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 1. 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

Linux WAR file

service_stop

Consume

Servlet Container, Stop

Linux WAR file

webapps_dir

Consume

Servlet Container, DIR

Some nodes and node arrays have predefined Auto-Bind type and tag parameters for properties. You cannot edit these parameters. When a service or application component is added to a node or node Array, the source properties are taken from the service or application component and the target properties are taken from the node or node array.

Table 2. Predefined Node and Node Array Properties

Node Type

Property

Auto-Bind Type

Auto-Bind Tag

Node, Node Array

hostname

Expose

Hostname

Node, Node Array

ip

Expose

IP Address

Node Array

node-array-index

Expose

Node Array Index

When dependencies exist, the source properties are taken from the component that the link originates. Target properties are taken from the component from which the link is drawn, and from parent service or node components.

Property Compatibility

Auto-binding depends on the compatibility between Source and Target property types and Node type.

Table 3. Property Type and Node Type Compatibility

Source Property Type

Target Property Type

Node Type

Compatible

Array

String

Node

Yes

Array

Computed

Node

Yes

Array

String

Node Array

Yes

Array

Computed

Node Array

Yes

String

String

Node

Yes

String

Computed

Node

Yes

String

String

Node Array

No

String

Computed

Node Array

No