7.2
Table Of Contents
- Custom Properties Reference
- Contents
- Custom Properties Reference
- Updated Information
- Using Custom Properties
- Custom Properties Grouped by Function
- Custom Properties for Blueprints and Deployments
- Custom Properties for Naming and Analyzing Deployments
- Custom Properties for Openstack Endpoints
- Custom Properties for Clone Blueprints
- Custom Properties for Linked Clone Blueprints
- Custom Properties for FlexClone Blueprints
- Custom Properties for Basic Workflow Blueprints
- Custom Properties for Linux Kickstart Blueprints
- Custom Properties for SCCM Blueprints
- Custom Properties for WIM Blueprints
- Custom Properties for vCloud Air and vCloud Director Blueprints
- Custom Properties for Networking
- Custom Properties for PXE Provisioning
- Custom Properties for vRealize Automation Guest Agent
- Custom Properties for BMC BladeLogic Configuration Manager Integration
- Custom Properties for HP Server Automation Integration
- Custom Properties Grouped by Name
- Custom Properties Underscore (_) Table
- Custom Properties A Table
- Custom Properties B Table
- Custom Properties C Table
- Custom Properties E Table
- Custom Properties H Table
- Custom Properties I Table
- Custom Properties L Table
- Custom Properties M Table
- Custom Properties O Table
- Custom Properties P Table
- Custom Properties R Table
- Custom Properties S Table
- Custom Properties V Table
- Custom Properties X Table
- Using the Property Dictionary
- Using Property Definitions
- Using Property Groups
- Index
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 design canvas. NSX
network, security, and load balancer properties are only applicable to vSphere machines.
N Network-specic custom properties that point to on-demand networks are not supported. For
example, you cannot use network custom properties, such as
VirtualMachine.Network0.NetworkProfileName, for on-demand NAT and on-demand routed network
components.
By default, a machine has one network device congured with the VirtualMachine.Network0.Name property.
You can congure additional network devices by using the VirtualMachine.NetworkN.Name custom property,
where N is the network number.
The numbering of network properties must be sequential, starting with 0. For example, if you specify
custom properties for only VirtualMachine.Network0 and VirtualMachine.Network2, the properties for
VirtualMachine.Network2 are ignored, because the preceding network, VirtualMachine.Network1, was not
specied.
Although general support for VMware vCloud
®
Networking and Security ™ 5.5.x (vCNS) ended in
September 2016, the VCNS custom properties continue to be valid for VMware NSX ™ purposes. See the
VMware Knowledge Base article End of Availability and End of General Support for VMware vCloud Networking
and Security 5.5.x (2144733) at hp://kb.vmware.com/kb/2144733 for more information.
Table 2‑18. Custom Properties for Networking Configuration
Custom Property Description
agent.download.url
When using port forwarding, species the private IP
address of your Amazon AWS tunnel machine and port for
your software agent le, for example
https://Private_IP:1443/software-
service/resources/nobel-agent.jar.
You can add this property, in combination with
software.agent.service.url and software.ebs.url,
to a reservation or the compute resource endpoint. You can
also use this property to specify a private address and port
when using PAT or NAT and port forwarding.
software.agent.service.url
When using port forwarding, species the private IP
address of your Amazon AWS tunnel machine and port for
the vRealize Automation software service API, for example
https://Private_IP:1443/software-service/api.
You can add this property, in combination with
software.ebs.url and agent.download.url, to a
reservation or the compute resource endpoint. You can also
use this property to specify a private address and port
when using PAT or NAT and port forwarding.
software.ebs.url
When using port forwarding, species the private IP
address of your Amazon AWS tunnel machine and port for
the vRealize Automation event broker service, for example
https://Private_IP:1443/event-broker-
service/api.
You can add this property, in combination with
software.agent.service.url and
agent.download.url, to a reservation or the compute
resource endpoint. You can also use this property to specify
a private address and port when using PAT or NAT and
port forwarding.
VirtualMachine.NetworkN.Address
Species the IP address of network device N in a machine
provisioned with a static IP address.
For Amazon, see Amazon.elasticIpAddress.ipAddress.
Custom Properties Reference
36 VMware, Inc.