7.0

Table 2‑16. Custom Properties for Analyzing Deployments
Custom Property Description
_debug_deployment
By default, all resources that are created by a provisioning
process are rolled back if provisioning fails. You can override the
default behavior by setting the _debug_deployment custom
property value to true. If provisioning fails, the debugging
custom property stops the resources from being rolled back so
you can identify which of the components failed to provision
successfully. None of the components in the failed catalog item
are accessible to the user, so this custom property is best used
during development and testing of new application blueprints.
To apply the custom property to an application blueprint, add
_debug_deployment to the Blueprint Properties page using
the Properties tab when you create or edit an application
blueprint.
This property is for blueprints that contain multiple components,
such as composite blueprints, and is ignored if applied to
standalone blueprints.
_deploymentName
Displays or hides the deployment name field from a published,
composite blueprint in the provisioning request details form. To
apply the custom property and display the name of the
deployment in the request details form, add
_deploymentName=true to the Blueprint Properties page
using the Properties tab when you create or edit a blueprint. By
default, the property is set to false, which suppresses the
deployment name.
Custom Properties for Networking
The vRealize Automation custom properties for networking specify configuration for a specific network
device on a machine.
Network assignments are performed during machine allocation. vRealize Automation retrieves network
information from the blueprint. If you want to assign more than one network, use the
VirtualMachine.NetworkN.Name custom property on your machine blueprint. If you do not provide
custom properties, allocation only assigns one network which is picked using a round robin method in
conjunction with the selected reservation.
For machine components that do not have a Network or Security tab, you can add network and security
custom properties, such as VirtualMachine.Network0.Name, to their Properties tab in the blueprint
canvas. However, NSX load balancer properties are only applicable to vSphere machines.
Note This information does not apply to Amazon Web Services.
By default, a machine has one network device configured with the VirtualMachine.Network0.Name
property. You can configure additional network devices by using the VirtualMachine.NetworkN.Name
custom property, where N is the network number.
Custom Properties Reference
VMware, Inc. 35