Tenant administrators and business group managers can specify custom properties that apply to all component machines in a multi-machine service in the multi-machine blueprint. When the same property exists in more than one source, vRealize Automation follows a specific order of precedence when applying properties to the machine.

Custom properties in a multi-machine blueprint override properties specified in component blueprints. Runtime properties on the component machine, which are specified at request time or by editing the machine after it is provisioned, override runtime properties specified at the multi-machine service level. This allows the multi-machine blueprint to apply consistent behavior across all of its component machines, while allowing a user to override the multi-machine service properties for each component type.

Custom properties on multi-machine service and component machines are processed in the following order.

  1. Build profile specified on component blueprint

  2. Component blueprint

  3. Build profile specified on multi-machine blueprint

  4. Multi-machine blueprint

  5. Business group

  6. Compute resource

  7. Reservations

  8. Endpoint

  9. Request time specified on a multi-machine service

  10. Request time specified on a component machine

A property value specified in a source that appears later in the list overrides values for the same property specified in sources earlier in the list. Custom properties specified in the multi-machine service are applied to all component machines in the service. If a property is designated as Prompt User on a component blueprint, the value specified at request time is applied to all machines of the same component type that are provisioned as part of that request.

Some properties, such as Hostname, must be unique to each machine. Do not specify the property at the component level. If the Hostname property is specified at the component level, it is ignored.