vRealize Automation requires that you name the hosts in your installation according to certain requirements.
All vRealize Automation machines in your installation must be able to resolve each other by fully qualified domain name (FQDN).
While performing the installation, always enter the FQDN when identifying or selecting a machine. Do not enter IP addresses.
In addition to the FQDN requirement, Windows machines that host the Model Manager Web service, Manager Service, and Microsoft SQL Server database must be able to resolve each other by Windows Internet Name Service (WINS) name.
Configure your Domain Name System (DNS) to resolve these short WINS host names.
Preplan domain and machine naming so that vRealize Automation machines will begin and end with alphabet (a-z) or digit (0-9) characters, and will only contain alphabet, digit, or hyphen (-) characters. The underscore character (_) must not appear in the host name or anywhere in the FQDN.
For more information about allowable names, review the host name specifications from the Internet Engineering Task Force. See www.ietf.org.
In general, you should expect to keep the host names and FQDNs that you planned for vRealize Automation systems. You can change a vRealize Automation appliance host name after installation, but changing other vRealize Automation host names makes vRealize Automation unusable.
A best practice is to reserve and use static IP addresses for all vRealize Automation appliances and IaaS Windows servers. vRealize Automation supports DHCP, but static IP addresses are recommended for long-term deployments such as production environments.
You apply an IP address to the vRealize Automation appliance during OVF or OVA deployment.
For the IaaS Windows servers, you follow the usual operating system process. Set the IP address before installing vRealize Automation IaaS.