7.3

Table 1‑44. Custom Properties V Table (Continued)
Property Description
Vrm.DataCenter.Location
Allows you to use a blueprint to provision machines on more than
one compute resource. You can add the
Vrm.DataCenter.Location property to a blueprint, or enable
the Display Location on Request option in the blueprint, to
require that the user supply a datacenter location when they
request machine provisioning.
Note If you enable the Display Location on Request option on
the blueprint, you do not need to also add the custom property.
Datacenter locations are configured in a
DataCenterLocations.xml file, which provides the location
values that are applied to compute resources.
For related information about adding datacenter locations, see
Configuring vRealize Automation.
Because the Vrm.DataCenter.Location property cannot
access the contents of the DatacenterLocations.xml file, you
must rely on users to provide property values that match the
locations provided in the DataCenterLocations.xml file.
Use this property if you want to use the datacenter location value
as input to an external action for another custom property.
Vrm.DataCenter.Policy
Specifies whether provisioning must use a compute resource
associated with a particular location, or if any location is suitable.
To enable this feature, you must add data center to a location file.
Associate each compute resource with a location.
Set to Exact (default) to provision a requested machine on a
compute resource associated with the location specified on the
blueprint. The request fails if no reservations match the
requested location. If the property is not present, the Exact
default is used.
Set to NonExact to provision a requested machine on a compute
resource with sufficient capacity and associated with the location
specified on the blueprint. If that compute resource is not
available, then use the next available compute resource with
sufficient capacity without regard to location.
Vrm.ProxyAgent.Uri
Allows you to override the default Vrm.ProxyAgent.Uri value
that is derived from the VMPS endpoint address in the
vRealize Automation Manager Service configuration file. The
configuration setting is often set to the local machine but you
might want to set it to the virtual IP (VIP) address.
You can specify the Vrm.ProxyAgent.Uri custom property on a
blueprint. Sample syntax is as follows:
Vrm.ProxyAgent.Uri=https://loadbalancer-vip/VMPS2Proxy
Custom Properties Reference
VMware, Inc. 98